plcopen ® for efficiency in automation welcome at the plcopen presentation check also the notes...

PLCopen®

for efficiency in automation

Welcome

at the

PLCopen presentation

Check also the notes coupled to each slide

PLCopen®


PLCopen®


The big software problem

PLCopen®


Percentage of Software development costs in production systems (source: McKinsey)

0%

20%

40%

60%

80%

100%

1970 1980 1990 2000

Mechanic Electric Software

PLCopen®


Managing Complexity

100 – 10,000 – 1mio – 100mio Lines of Code

Exponentially increasing complexity

PLCopen®


Why Structured Software Development ?

Software = key to system quality: errors cost money

Increased requirements: 100 lines of codes now 10,000 lines

or even 100,000

Not a one-man job - but a team with different know how and

background

Commissioning, Installation, Maintenance, and

Improvements essential phases

PLCopen®


… software quality factors..

Failure Rates: difference between hardware and software

External Quality (‘Perceived value’) versus Internal Quality

Correctness, reliability, robustness, integrity, persistence,

safety

ease-of-use

PLCopen®


“… the never ending story of software ”

enhancements…..

….. new requirements ...

…. new functionalities ….

…. new wishes ...

PLCopen®


PLCopen®


Organization

TECHNICAL PROMOTIONALCOMMITTEES

T C1 T C2 T C3 T C4 T C5 T C6 P C 1 P C 2 P C 3 P C 4 P C 5

G en eral M ee tin g , BO M , M D

PLCopenfor efficiency in automation

PLCopen®


IEC 61131-3

Harmonizing the way people look to control

and now with the 3rd edition

TC1 Standards:the basis

PLCopen®


What is IEC 61131-3

Specifying an application program development environment

1 structuring tool - SFC

4 programming languages: 2 textual & 2 graphical

Program organization units for structuring and reuse

Strong data typing for error prevention

PLCopen®


IEC 61131 PartsProject Title Valid till

61131- 1, Ed 2.0 General information, 2003-05 2013

61131- 2, Ed 3.0 Equipment requirements and tests, 2007-07 2012

61131- 3, Ed 3.0 Programming languages (Currently CDV - Committee Draft for Voting) 2012+5

61131- 4, Ed 2.0 User guidelines (TR), 2004-07 2010

61131- 5, Ed 1.0 Communications, 2000-11 2013

61131- 6, Ed 1.0 Functional safety for PLC (Currently CDV - Committee Draft for Voting) 2012+5

61131- 7, Ed 1.0 Fuzzy control programming, 2000-08 2013

61131- 8, Ed 2.0 Guidelines applic. & implem. progr. languages (TR), 2003-09 2008

61131- 9, Ed 1.0Single-drop digital communication interface for small sensorsand actuators (SDCI) aka “IO-Link” (Currently CD - Committee Draft)

2012+5

PLCopen®


An introduction in IEC 61131-3 is given in a separate presentation

PLCopen on IEC 61131-3.pptx

PLCopen®


The 3rd edition includes Object Orientation

Why?

Main reason:To link better to the scared resources

of engineers in the future

The industry should better adopt to themthen vice versa

PLCopen®


Good news:

3rd edition fully compatible

with 2nd edition + extensions

The OOP features are selectableand usable over time

And many other enhancements

and proposals to demote – like for IL

PLCopen®


IEC 61131-3

Harmonizing the way people look to control

and PLCopen extends this basis

PLCopen®


PLCopen Motion Control (TC2):

The merge of Logic and Motion

IEC 61131-3

PLCopen

Logic Motion Control

PLCopen®


Status PLCopen Motion Control Part 1 – Function Blocks for Motion Control

Part 2 – Extensions

Part 3 – User Guidelines

Part 4 – Coordinated Motion

Part 5 – Homing procedures

Part 6 – Fluid Power (hydraulics)

Around 30 companies certified with over

40 products (check website for full list)

PLCopen®


An introduction in PLCopen Motion Control is given in a separate

presentation

PLCopen Motion Control.pptx

PLCopen®


The next step: Adding Safety (TC5)

(at machine level)

IEC 61131-3

PLCopen

Logic Motion ControlSafety

PLCopen®


Reasons to merge – a changing environment

The tendency to move from one motor (master axis) to

multiple axes, driven by mechatronic solutions;

The availability and acceptance of digital networks with

safety functionality built-in;

The inherent move from hardwired safety functionalities to

software solutions;

The increasing importance of safety related issues

regarding personnel and machines (Governmental

requirements )

PLCopen®


PLCopen Safety Specifications

Part 1 - Concepts and Function Blocks

Part 2 - User Examples

Part 3 – Extensions

Part 4 – Extensions for Presses

Separate user document: Logic, Motion, Safety

PLCopen®


An introduction in PLCopen Safetyis given in a separate presentation

PLCopen Safety.pptx

PLCopen®


PLCopen

Combining Logic, Motion and Safety

Providing Structuring, Decomposition, Reuse and less training

PLCopen®


Communication (TC4)

PLCopen®


TC4 Communication OPC UA specifies HOW

PLCopen specifies WHAT

PLCopen®


OPC-UABaseVariableType

OPC UA Part 5

OPC-UA DI

Examples

IEC 61131-3 OPC-UA

CtrlProgramType

BaseObject TypeOPC UA Part 5

CPU_A100

CtrlTaskType

Main

nInput

CtrlResourceType

CtrlFunctionBlockType

CtrlConfigurationType

PLC_Z345 FB_MotorControler

FB_MotorControler:MotorControler1

fOutput

bLocal

bLocalMain

CPU_A100:CPU1

CtrlProgramOrganizationUnitType

DeviceType

TopologyElementType

ConfigurableObjectType

ConfigurableComponentsType:Resources

ConfigurableComponentsType:Resources

FB_MotorControler:MotorControler2

CPU_A100:CPU2

Priority

BlockType

PLCopen®


An introduction on OPC UA / PLCopen is given in a separate presentation

PLCopen OPC UA.pptx

PLCopen®


TC6 – XML

Opening up the development environments

by specifying XML formats for IEC 61131-3

PLCopen®


XML (TC6)

Developmenttool

OtherDevelopmenttool

OtherDevelopmenttool

Producer ofgraphical and logicalinformation

Consumer ofgraphical and logicalinformation

XML

XML

XML

XML

PLCopen®


PLCopen®


An introduction in PLCopen XML is given in a separate presentation

PLCopen XML.pptx

PLCopen®


TC3 - Benchmarking

A benchmark is a reproducible, portable test to

measure the performance of a given system in

comparison to other systems

PLCopen®


Benchmarking (TC3)

Two different sets of benchmarks defined:

1. 5 different types of applications, which

are typical for the usage of a PLC.

2. Measures each language feature of the

IEC 61131-3 separately

PLCopen®


PC2 - Training

Important to create sufficient humanresources capable to create and innovate

PLCopen®


PLCopen Coding Guidelines: Goals

Overall: Increase the quality of the software for industrial

applications

How?: By defining a set of Rules, Coding Patterns and

Guidance on how to use them in Industrial Automation

PLCopen®


PLCopen Coding Guidelines - subgroups

Coding Conventions (incl. Naming conventions and Rules)

Software quality issues and software consistency

Creating PLCopen compliant FBs (Design Pattern)

Structuring and decomposition via SFC: do’s & don’t s

Guidance for documentation in software programs

Library usage

Software Development Process

PLCopen®


Some words to the

Not-for-profit organization

PLCopen®


PLCopen as a World-wide association

Office in Japan

Main Office in Europe

Office in North America Office in China

PLCopen®


One member – One vote

small companies can have the

same influence as large companies

PLCopen®


PLCopen®


PLCopen – providing a suite of specifications

PLCopen®


More Information...and to download the specifications (f.o.c)

www.PLCopen.org

Free-of-Charge electronic Newsletter ‘PLCopening’ (in English)

email: [email protected]

plcopen ® for efficiency in automation welcome at the plcopen presentation check also the notes...

Documents

software bringspage

costs of software

car software

software quality factors

good software quality

big software problemplcopen

plcopen presentationcheck

story of software enhancements