Page 1 printed at 8/3/2017 PLCopen ® for efficiency in automation Introduction in IEC Check also the notes coupled to each slide.

Presentación del tema: "Page 1 printed at 8/3/2017 PLCopen ® for efficiency in automation Introduction in IEC Check also the notes coupled to each slide."— Transcripción de la presentación:

1 Page 1 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Introduction in IEC 61131-3 Check also the notes coupled to each slide for further explanation

2 Page 2 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation the future is here PLCopen TC1 : Standards links to IEC 61131-3 Harmonizing the way people look to control

3 Page 3 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Fiction? Imagine *you are in industrial control *working with 4 different brands of controls *using different dialects in their programming languages * struggling to match the level of your software engineers with the operators and maintenance people on the factory floor *& seeing that your competitor does better Why? What’s wrong ?

4 Page 4 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Out of the jungle The current variety of problems can be vastly reduced via standardization... and such a standard is available

5 Page 5 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 “The best thing that happened to industrial control” Sugar Lantic on Automation Maillist

6 Page 6 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The 9 parts of the IEC 61131 Standard ProjectTitleValid till 61131- 1, Ed 2.0General information, 2003-052013 61131- 2, Ed 3.0Equipment requirements and tests, 2007-072012 61131- 3, Ed 3.0 Programming languages (Currently CDV - Committee Draft for Voting) 2012+5 61131- 4, Ed 2.0User guidelines (TR), 2004-072010 61131- 5, Ed 1.0Communications, 2000-112013 61131- 6, Ed 1.0Functional safety for PLC (Currently CDV - Committee Draft for Voting) 2012+5 61131- 7, Ed 1.0Fuzzy control programming, 2000-082013 61131- 8, Ed 2.0Guidelines applic. & implem. progr. languages (TR), 2003-092008 61131- 9, Ed 1.0 Single-drop digital communication interface for small sensors and actuators (SDCI) aka “IO-Link” (Currently CD - Committee Draft) 2012+5

7 Page 7 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 1131 versus IEC 61131  The good news is – there is no difference  It is an international harmonization of all the IEC standards and the localized versions

8 Page 8 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Programming languages / Industrial Control Programming Standardizing the way people work with controls

9 Page 9 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Programming languages / Industrial Control Programming...with support for people with different backgrounds

10 Page 10 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The IEC 61131-3 Standard Common Elements Programming Languages

11 Page 11 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 : Common Elements Variables & Data Types What is this? 01010101 10101010 Historically Reference to a physical memory location Reference to a physical Input

12 Page 12 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 : Common Elements Variables & Data types Temperature_Sensor_1 : Integer Symbolic representation via labels Restricted area for I/O mapping Hardware independent software code Result: higher transparency & readability And less errors

13 Page 13 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 : Common Elements Software Model Configuration Resources Tasks

14 Page 14 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Software Model Configuration Communication Function

15 Page 15 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Software Model Configuration Communication Function Resource

16 Page 16 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Software Model Task Resource Configuration Communication Function

17 Page 17 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Software Model Execution control path Task Program Task Program Task Program Task Resource Configuration Communication Function

18 Page 18 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 Software Model Global and direct variables Access path Execution control path Variable access path FB Task Program FB Task Program Task Program FB Task Resource Configuration Communication Function Function Block Variable

19 Page 19 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 vs conventional PLC Global and direct variables Access path Execution control path Variable access path FB Task Program FB Task Program Task Program FB Task Resource Configuration Communication Function Function Block Variable

20 Page 20 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Conventional PLC vs IEC 61131-3 Task 1 Program Task Resource Read inputs Do Calculations Set Outputs Endless Loop: Task 2 Task 3 Task 4 Time based Events based Time based

21 Page 21 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Common Elements: Tasks IEC 61131-3 EmbeddedPLCs PC based Control SoftLogicDrivesLON nodesDCS

22 Page 22 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Common Elements : Tasks & Datatypes RPM =2000 Windows CE or any other IEC 61131-3 tasks SCADA & HMI tasks I/O Communication tasks OPC UA Multi –functional Operator Panel I/O Communication bus

23 Page 23 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC 61131-3 : Common Elements COMMON ELEMENTS a.o. Data Types&Variables Configuration, Resources, Tasks Programming Organization Units, POUs * Functions * Function Blocks * Programs

24 Page 24 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Functions ….. * Standard functions ADD, SQRT, SIN, COS, GT, MIN, MAX, AND, OR, etc. * Your own defined functions: FUNCTION SIMPLE_FUN : REAL VAR_INPUT A, B : REAL; C : REAL := 1.0; END_VAR SIMPLE_FUN := A*B/C; END FUNCTION

25 Page 25 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation …. & Function Blocks  Standard Function Blocks Hysterisis Q XIN1 XIN2 EPS BOOL REAL

26 Page 26 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation …. & Function Blocks  Standard Function Blocks  Additional supplied Function Blocks Hysterisis Q XIN1 XIN2 EPS BOOL REAL

27 Page 27 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation …. & Function Blocks  Standard Function Blocks  Additional supplied Function Blocks  Your own defined Function Blocks Hysterisis Q XIN1 XIN2 EPS BOOL REAL

28 Page 28 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation …. & Function Blocks  Standard Function Blocks  Additional supplied Function Blocks  Your own defined Function Blocks  All FBs are highly re-usable in same program, different programs or project Hysterisis Q XIN1 XIN2 EPS BOOL REAL

29 Page 29 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Function Block example Hysterisis Q XIN1 XIN2 EPS BOOL REAL 1 EPS 0 XIN2 Q

30 Page 30 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Function Block example FUNCTION_BLOCK HYSTERISIS VAR_INPUT XIN1, XIN2 : REAL; EPS : REAL; (* Hysterisis band *) END_VAR VAR_OUTPUT Q : BOOL := 0 END_VAR IF Q THEN IF XIN1 < (XIN2-EPS) THEN Q := 0 (* XIN1 decreasing *) END_IF; ELSIF XIN1 > (XIN2 + EPS ) THEN Q := 1; (* XIN1 increasing *) END_IF; END_FUNCTION_BLOCK Hysterisis Q XIN1 XIN2 EPS BOOL REAL 1 EPS 0 XIN2 Q

31 Page 31 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Programs : design via building bricks Automation application Start : BOOL; Emergency : BOOL; Limit : INT; PROGRAM GLOBAL LocalType FUNCTION INPUT Local Type FUNCTION_BLOCK INPUT OUTPUTIN_OUT EXTERNAL Local Type

32 Page 32 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Structure & Advantages of POUs  Create own Function Block Libraries (per application area)  FBs are tested and documented  Make libraries (world wide) accessible  Re-use as much as possible  Change programming to creating networks of FBs  Save 40% on next project

33 Page 33 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Sequential Function Chart, SFC  Powerful graphical technique for describing the sequential behavior of a control program  Used to partition a control problem  Shows overview, also suitable for rapid diagnostics Step 1 N FILL Step 3 Step 2 S Empty Transition 1 Transition 2

34 Page 34 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Sequential Function Chart, SFC  Powerful graphical technique for describing the sequential behaviour of a control program  Used to partition a control problem  Shows overview, also suitable for rapid diagnostics  The basic elements are STEPS with ACTION BLOCKS and TRANSITIONS  Support for alternative and parallel sequences Step 1 N FILL Step 3 Step 2 S Empty Transition 1 Transition 2

35 Page 35 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation SFC : alternative sequences Step 1 N FILL Step 3 Step 2 b S Empty Transition 1b Transition 2b Step 2 a S Empty Transition 1a Transition 2a

36 Page 36 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The IEC 61131-3 Standard Common Elements Programming Languages

37 Page 37 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The IEC 61131-3 Programming Languages Instruction List Structured Text Function Block Diagram Ladder Diagram C:= A AND NOT B A B C -| |--|/|----------------( ) LDA ANDNB STC AND A C B

38 Page 38 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The IEC 61131-3 Standard Common Elements Programming Languages Top Down Bottom Up

39 Page 39 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation IEC Programming Environments Many of them offer:  graphical programming screens  support for multiple windows  mouse operation  pull-down menus  built-in hypertext help function  software verification during design

40 Page 40 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation What are the benefits ?

41 Page 41 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Users? Which Users? Education InstallationMaintenanceProgrammingProcess cntrlDiscrete MnfSystem Integrator YOU ??

42 Page 42 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Users? Which Users? Automobile production lines Water treatment plant Food processing and packaging machinery Cable manufacturing Semi-conductor clean room automation Theme-park roller coasters Nuclear waste treatment plant This wide range encompass different skills

43 Page 43 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy)

44 Page 44 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy) Creating a focus to problem solving via software re-usability (reduced application investment and supplier dependency)

45 Page 45 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy)  Creating a focus to problem solving via software re-usability (reduced application investment and supplier dependency) Reduced misunderstandings and errors

46 Page 46 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy)  Creating a focus to problem solving via software re-usability (reduced application investment and supplier dependency)  Reduced misunderstandings and errors Programming techniques usable in more environments (general industrial control)

47 Page 47 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy)  Creating a focus to problem solving via software re-usability (reduced application investment and supplier dependency)  Reduced misunderstandings and errors  Programming techniques usable in more environments (general industrial control) Combining harmoniously different components from different locations, companies or countries, or projects

48 Page 48 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy)  Creating a focus to problem solving via software re-usability (reduced application investment and supplier dependency)  Reduced misunderstandings and errors  Programming techniques usable in more environments (general industrial control)  Combining harmoniously different components from different locations, companies or countries, or projects Increased connectivity (investment protection)

49 Page 49 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Benefits  Reduced waste of human resources (in training, debugging, maintenance and consultancy)  Creating a focus to problem solving via software re-usability (reduced application investment and supplier dependency)  Reduced misunderstandings and errors  Programming techniques usable in more environments (general industrial control)  Combining harmoniously different components from different locations, companies or countries, or projects  Increased connectivity (investment protection)

50 Page 50 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation How to use IEC 61131-3 an example: Structuring Software Development with IEC 61131-3 7 steps to success

51 Page 51 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Software Development Cycle Design / Development / Installation / Maintenance.. phases

52 Page 52 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation … software development cycle... enhancements….. ….. new requirements... …. new functionality …. …. new wishes... “… the never ending story of software ”

53 Page 53 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation What’s the topic here? Structuring Software Development with IEC 61131-3 meaning: internal Software Quality In the sense of: Understandable, Reusable, Verifiable, Maintainable, Isolation

54 Page 54 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Managing Complexity 100 – 10,000 – 1mio – 100mio Lines of Code Exponentially increasing complexity

55 Page 55 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Why Structuring ?  The ever increasing role of Software on system quality: errors cost money  Requirements increased dramatically: 100 lines of codes now 10,000 lines  SW development: not a one-man job anymore, but a team with different know how and background  Commissioning, Installation, Maintenance, and Improvements are essential parts of the development process

56 Page 56 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Advantages of Structuring Better Overview Better Basis for (internal) Communication Better Focus to problem solving Basis for reusable software “Self-documenting”

57 Page 57 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Software Program vs. Software Product  Made by an individual for own use  Limited functionality  User interface less important  Little documentation  Individual development style  Made by a group for usage by others  Larger functionality  User interface very important  Well documented  Accepted SW engineering methods

58 Page 58 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Exploratory Style vs. Software Engineering Method  Based on error correction  Finding errors during final product testing  Coding is the goal, creating quickly a working system, and modifying till satisfactory  Focused to error prevention  Find errors as early as possible  A structured approach, clear specifications, clear phases  Periodic reviews during all stages of the project

59 Page 59 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation (Costly) Engineering Habits  Reuse work from similar former projects  Include them into the new project  And start adapting them to the new project requirements Copy - Paste & Modify

60 Page 60 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Dangers of copy paste & modify The “not-invented-here syndrome” – only own artifacts (developed in the past) Non-predictable quality Prone to errors and reuse potential is wasted Unsystematically Difficult to maintain and manage Very costly over the life cycle

61 Page 61 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Modern Software Development Process A small overview

62 Page 62 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Modern Software Development Process  Defined in several clearly separated phases - project definition  Top-down approach  Multiple disciplines involved  Multiple people involved  Different backgrounds  Based on Functional Requirements

63 Page 63 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Example of Software Development Process Different Phases “Waterfall – model” Analysis Design Development Installation Maintenance..

64 Page 64 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Example of Software Development Process V-model Link between Specification and testing

65 Page 65 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The X-Model for SW Development Sub-system Integration and Testing System Installation and Testing Component Identification Sub-system Design Module Development Library Construction Catalogue Management System Design Component Design Component Development

66 Page 66 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The X-Model for SW Development Sub-system Integration and Testing System Installation and Testing Component Identification Sub-system Design Module Development Library Construction Catalogue Management System Design Component Design Component Development Application Software

67 Page 67 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The X-Model for SW Development Sub-system Integration and Testing System Installation and Testing Component Identification Sub-system Design Module Development Library Construction Catalogue Management System Design Component Design Component Development Reusable Components (FBs)

68 Page 68 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Requirements on Engineering Tools 1.Support creation and reuse of technical, non-technical and combined entities 2.Support creation of a structured domain repository (like a library) 3.Enable multi-user access on the components 4.Provide configuration management 5.Cover more than one engineering phase and discipline 6.Encourage a reuse on different levels of granularity

69 Page 69 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Decomposition and Reuse PROGRAM GLOBAL LocalType Automation application FUNCTION INPUT Local Type FUNCTION_BLOCK INPUT OUTPUTIN_OUT EXTERNAL Local Type

70 Page 70 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Decomposition

71 Page 71 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Reuse via Standardized Function Blocks

72 Page 72 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation A hierarchy of abstraction Top- down

73 Page 73 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Bottom-up after top-down Top- down Bottom up First decompose – then fill it in

74 Page 74 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation How does that look in IEC 61131-3 ? 7 Steps to Success with a Fermentation Control System

75 Page 75 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Fermentation Process Heater band Acidic reagent Alkali reagent Harvest valve pH sensor Temperature sensor Feed valve Agitator

76 Page 76 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation How to create a control program for this in a structured way?

77 Page 77 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Step 1 : Identification of external Interfaces to the System  Feedback from the temperature sensor  Feedback from the pH sensor  Feedback from the valve positions  Feedback from the motor (speed)  Output to the valves  Output to the motor  Output to the heater band

78 Page 78 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Step 2: Definition of the main signals between System and Plant In this example there is no coupling to the plant, but it could have been, like:  … coupling to main vessels with liquids  … coupling to transportation system / filling station after harvesting

79 Page 79 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Step 3: Definition of all Operator interactions, overrides and supervisory data For the operator we define:  …a ‘Start’ button  …a ‘Stop’ button  …a ‘Duration’ input Now we have defined all the interfaces

80 Page 80 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Step 4: Brake down from top in logical partitions  MainSequence - filling, heating, agitating, fermenting, harvesting, cleaning.  ValveControl - operating valves used to fill and empty the vessel's  TemperatureControl - for controlling the temperature  AgitatorControl - agitator motor control  pHControl - PH-control

81 Page 81 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Step 5: Definition of the required POUs (Programs and Function Blocks)  Using the definitions above and  representing it in the graphical way …

82 Page 82 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Fermentation Control Program

83 Page 83 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation MainSequence in Sequential Function Chart, SFC Presenting the main process states

84 Page 84 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The Actions Blocks and Transitions can be programmed in any of the four IEC Programming Languages

85 Page 85 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The IEC 61131-3 Programming Languages Instruction List (IL) Structured Text (ST) Funktion Block Diagram (FBD)Ladder Diagram (LD) LDA ANDNB STC C:= A AND NOT B A B C -| |--|/|----------------( ) AND A C B

86 Page 86 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Step 6: Definition of scan cycle time requirements for the different parts of the application  In this example we have only one cycle in continuous mode  The remaining time can be used for other cycles like:  …. the filling / transportation system  … checking boundaries and error conditions (in a parallel sequence)

87 Page 87 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation And last but not least: Step 7: Configuration of the System: Definition of Resources, Tasks and linking of programs with physical I/O  Depending on the system involved  Includes physical mapping of symbols to I/O  Mapping of the resource (read: CPU’s in the system)  Definition of the scan cycles and events (as defined in Step 6)

88 Page 88 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation Conclusion  The Software development process has changed: more requirements.. more functionalities.. more code.. more people involved.. … more requirements / wishes  Structuring and Decomposition are essential parts of modern software development  IEC 61131-3 has the right basis to fulfill your requirements

89 Page 89 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation The association PLCopen Together we can make it happen: Standardization in Industrial Control Programming WE NEED YOUR SUPPORT FOR THIS ! Join the organization PLCopen

90 Page 90 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation

91 Page 91 printed at 8/3/2017 www.PLCopen.org PLCopen ® for efficiency in automation More Information... www.PLCopen.org  Free-of-Charge electronic Newsletter ‘PLCopening’ (in english) email: evdwal@PLCopen.org