1. Field Device Specification for the Development of Function Block Oriented Engineering Support Systems Authors: Prayati, A., Thramboulidis, K. Electrical & Computer Engineering University of Patras GREECE

2. slide 2 IPMCS application development process Field device specification – current status Engineering support system - field device model requirements Field device model Case study: wrapping a Profibus device Conclusions Overview

3. slide 3 Overview IPMCS application development process Field device specification – current status Engineering support system - field device model requirements Field device model Case study: wrapping a Profibus device Conclusions

4. slide 4 Traditional IPMCS Development Industrial process measurement and control systems. Industrial control based on traditional monolithic applications impossible to integrate and to expand. Proprietary solutions: Siemens, echelon etc. Need Modularity Flexibility Extensibility Reusability Interoperability

5. slide 5 The Function Block Concept Algorithms Type name Internal data Data outputsData inputs Event outputsEvent inputs Instance name Control Execution Data flow Event flow Data flow Introduced by IEC61131 Modified by IEC61499 Resource Block Transducer Block Function Block View Block Trend Block Alert Block

6. slide 6 FB-based IPMCS Application Event flow Data flow Process input Process output Composite FB Elementary FB

7. slide 7 IPMCS Development Process With Engineering Support System

8. slide 8 Overview IPMCS application development process Field device specification – current status Engineering support system - field device model requirements Field device model Case study: wrapping a Profibus device Conclusions

9. slide 9 Current Status (1) HART DDL 4-20ma point-to-point communication. Concepts: methods, variables, variable commands, parameter (dependencies). (+) Interpretable (human-readable format). (+) Parameter dependencies provide robustness. (-) Limited application area. NOHA Textual device description. Concepts: functional unit with data flow. (+)Flexibility, cost, maintenance, connectivity, safety, reliability. (-) No events

10. slide 10 Fieldbus foundation (+) FB-based application description (-) No details regarding the mapping to the real device Profibus (+) FB-based device profiles (-) Profibus specific format-GSD file with detailed device description Lonworks (-) Lonworks specific format-XIF file with detailed device description Current Status (2)

11. slide 11 The IEC61499 FB-based device model IEC61804 for the development of the ESS

12. slide 12 Overview IPMCS application development process Field device specification – current status Engineering support system - field device model requirements Field device model Case study: wrapping a Profibus device Conclusions

13. slide 13 IPMCS Development Process With Engineering Support System

14. slide 14 4-layer architecture for IPMCS development

15. slide 15 ESS functionality Insert industrial process parameters in the application layer Design the application (FB diagram) Insert field devices in the system layer Design the system (device diagram) Verify the application Download the application

16. slide 16 IPMCS Development Process Using ESS Add FB Import FB Type Reposit ory ESS Device Type Repository Import Device Type XML file IU Application Layer System Layer FB1 FB2 FB3 FB4 node Fieldbus B Fieldbus A Backbone IPT Real world Layer D1D2D3

17. slide 17 IPMCS Development Process Using ESS Connect FB Import FB Type Reposit ory ESS Device Type Repository Import Device Type XML file IU Application Layer System Layer FB1 FB2 FB3 FB4 node Fieldbus B Fieldbus A Backbone IPT Real world Layer D1D2D3

18. slide 18 IPMCS Development Process Using ESS Set time constraints Import FB Type Reposit ory ESS Device Type Repository Import Device Type XML file IU Application Layer System Layer FB1 FB2 FB3 FB4 node Fieldbus B Fieldbus A Backbone IPT { Time constraints } Real world Layer D1D2D3

19. slide 19 Add device Import FB Type Reposit ory ESS Device Type Repository Import Device Type XML file IU Application Layer System Layer FB1 FB2 FB3 FB4 node D1D3D2 Fieldbus B Fieldbus A Backbone IPT {Time constraints} Real world Layer D1D2D3 IPMCS Development Process Using ESS

20. slide 20 Assign FB to device Import FB Type Reposit ory ESS Device Type Repository Import Device Type XML file IU Application Layer System Layer FB1 FB2 FB3 FB4 node D1D3D2 Fieldbus B Fieldbus A Backbone IPT {Time constraints} Real world Layer D1D2D3 IPMCS Development Process Using ESS

21. slide 21 Set Configuration Parameters Download FB to device Import FB Type Reposit ory ESS Device Type Repository Import Device Type XML file IU Application Layer System Layer FB1 FB2 FB3 FB4 node D1D3D2 Fieldbus B Fieldbus A Backbone IPT {Time constraints} Real world Layer D1D2D3 IPMCS Development Process Using ESS

22. slide 22 Field Device Requirements IEC61804 Connections implemented by the appropriate experts group IEC61499 Communicated signals: data/event in the Resource boundary. Time-criticality is not considered. Option for defining and downloading new FB Option for defining fieldbus specific parameters

23. slide 23 Overview IPMCS application development process Field device specification – current status Engineering support system - field device model requirements Field device model Case study: wrapping a Profibus device Conclusions

24. slide 24 Field Device Model Network Interface Device Application Management Entity FB Resource Connections Industrial Process Interface Connection Points FB

25. slide 25 Field Device Model

26. slide 26 Add device Connect device/ set configuration parameters Set device parameters (parameter name, value) Field Device API for ESS functionality Application Development Phase Engineering Tool (Compiling) Refined Device model Machine-readable representation Machine Level User Defined Parameters - Name : undefined - Value : undefined Device Type - Name : undefined 1..* ConnectionPoint - Type : Input,Output - Analog : boolean - RangeSamplFreq : undefined - TimeForBroadcast : undefined Resources - ResourceID : undefined + SetID() + ConnectFB() + CreateFB() + DeleteFB() + StartFB() + StopFB() + CreateResource() + DeleteResource() + StartResource() + StopResource() Network Interface - Devstatus : undefined - NodeAddress : undefined - Protocol : undefined - OperationMode : undefined Industrial Process Interface 1..* Process Unit + Configure() + Init() + DNLFB() Device - SerialNo : integer + SelfTest(Devstatus) + CheckDeviceID() + UniqueTag() + SetDeviceTag() + GetDeviceTag() + SetAddress() + GetAddress() + GetStatus() + ClearAddress() + ReadData() + WriteData() + GetFBType() + SetConnection() + GetConnection() + SetFbinTask() + NewDataType() + NewTask() + RetrieveDefaultConfig() + ReadAvailableFB() + readActiveFB() + SetUserConfig() + SetVendorConfig() + InitParam() 1..* <!ELEMENT DataType (Identification?,VersionInfo+,CompilerInfo?,ASN1Tag?,(DirectlyDerivedType |EnumeratedType|SubrangeType|ArrayType|StructuredType))> <!ATTLIST DataType Name CDATA #REQUIRED Comment CDATA #IMPLIED > <!ATTLIST VersionInfo Organization CDATA #REQUIRED Version CDATA #REQUIRED Author CDATA #REQUIRED Date CDATA #REQUIRED Remarks CDATA #IMPLIED > <!ATTLIST ASN1Tag Class (UNIVERSAL | APPLICATION | CONTEXT | PRIVATE) #IMPLIED Number CDATA #REQUIRED > <!ATTLIST CompilerInfo header CDATA #IMPLIED classdef CDATA #IMPLIED > User Level Electronic Device Description in XML Device Proxy/wrapper Engineering Tool

27. slide 27 Assign FB to device downloadFB (FB type) establishEventConnection (FBout, FBin, output event, input event) establishDataConnection (FBout, FBin, output data, input data) setIPTConnection (FB handle, input data/event, IPT entry) IU : update table (data, event) Set time constraints setTimeBound FD API for ESS functionality (2) Application Layer FB1 FB2 FB3 FB4 IPT {Time constraints} IU System Layer node D1D3D2 Fieldbus B Fieldbus A Backbone Device Proxy or Wrapper FB Table FB4 Device Proxy or Wrapper FB Table FB2 D1 D3 D2

28. slide 28 Overview IPMCS application development process Field device specification – current status Engineering support system - field device model requirements Field device model Case study: wrapping a Profibus device Conclusions

29. slide 29 The Proposed Model Implemented on Profibus IU Profibus driver to DP device DRAM Virtual Field Device Profibus Device VFD API Profibus API

30. slide 30 Conclusions 4-layer architecture and FB construct very helpful for: Capturing the key abstractions for ESS analysis Addressing complexity of distributed IPMCS Our model enables the engineer to: Exploit FBs provided by smart devices Assign functionality to legacy Field Devices Common field device model provides modularity, flexibility, extensibility, interoperability, reusability this work will help to the direction of developing interoperable IEC 61499-compliant ESSs

31. slide 31 Device Model for the Development of IPMCS with ESS Heterogeneous Systems User Layer (2000) Function Block Interoperability Standards Fact Need Concept Distributed Application design Automation IEC61804 (1992) ESS tool requirements Industrial Networks Real-timeliness Real-time constraints Different Manufacturer devices Common device Description representation HART FFoundation NOHA Profibus LONWORKS Device model Fieldbus specific Different fieldbus devices Common device description IEC61499 (1990) Device model requirements General Device model based on FB used by ESS tool for automated application design

32. slide 32 IEC61804 Device Model

33. slide 33 IEC61499 Device Model

34. slide 34 ESS functionality (1) System Requirements Extract functionality Extract Data/Control signals Select FB from library Connect Data/Event of FBs Set Time Constraints Assign FB to Resource Select Device from Library Implement Connections Download FBSet Configuration Prms Get Device Description Extract FB typesFB Type Device Type Real-world layer System layer Application Layer Extract Device Type

35. slide 35 Identify device Self test (test parameters) Get configuration (parameter) Write data(FB handle, input event, data index) VFD API for Run-time operation

36. slide 36 Profibus Device Model