480 likes | 901 Views
Welcome at the PLCopen presentation. Check also the notes coupled to each slide. The big software problem. Managing Complexity. 100 – 10,000 – 1mio – 100mio Lines of Code. Exponentially increasing complexity. Why Structured Software Development ?.
E N D
Welcome at thePLCopen presentation Check also the notes coupled to each slide
Managing Complexity 100 – 10,000 – 1mio – 100mio Lines of Code Exponentially increasing complexity
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
… 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
“… the never ending story of software ” enhancements….. ….. new requirements ... …. new functionalities …. …. new wishes ...
Organization PLCopen for efficiency in automation TECHNICAL PROMOTIONAL COMMITTEES
TC1 Standards:the basis IEC 61131-3Harmonizing the way people look to controland now with the 3rd edition
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
An introduction in IEC 61131-3 is given in a separate presentation PLCopen on IEC 61131-3.pptx
The 3rd edition includes Object OrientationWhy? Main reason: To link better to the scared resources of engineers in the future The industry should better adopt to them then vice versa
Good news:3rd edition fully compatiblewith 2nd edition + extensions The OOP features are selectable and usable over time And many other enhancements and proposals to demote – like for IL
IEC 61131-3Harmonizing the way people look to controland PLCopen extends this basis
PLCopen Motion Control (TC2):The merge of Logic and Motion Logic Motion Control PLCopen IEC 61131-3
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)
An introduction in PLCopen Motion Control is given in a separate presentation PLCopen Motion Control.pptx
The next step: Adding Safety (TC5)(at machine level) Motion Control Safety Logic PLCopen IEC 61131-3
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 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
An introduction in PLCopen Safetyis given in a separate presentation PLCopen Safety.pptx
PLCopen Combining Logic, Motion and Safety Providing Structuring, Decomposition, Reuse and less training
TC4 Communication • OPC UA specifies HOW • PLCopen specifies WHAT
An introduction on OPC UA / PLCopen is given in a separate presentation PLCopen OPC UA.pptx
TC6 – XML Opening up the development environments by specifying XML formats for IEC 61131-3
XML (TC6) Producer of graphical and logical information XML Other Development tool Development tool Other Development tool XML XML XML Consumer of graphical and logical information
An introduction in PLCopen XML is given in a separate presentation PLCopen XML.pptx
TC3 - Benchmarking A benchmark is a reproducible, portable test to measure the performance of a given system in comparison to other systems
Benchmarking (TC3) Two different sets of benchmarks defined: • 5 different types of applications, which are typical for the usage of a PLC. • Measures each language feature of the IEC 61131-3 separately
PC2 - Training Important to create sufficient human resources capable to create and innovate
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 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
Some words to the Not-for-profit organization
PLCopen as a World-wide association Main Office in Europe Office in North America Office in China Office in Japan
One member – One vote small companies can have the same influence as large companies
More Information...and to download the specifications (f.o.c) www.PLCopen.org Free-of-Charge electronic Newsletter ‘PLCopening’ (in English) email: evdwal@PLCopen.org