Upload
jett-carradine
View
213
Download
0
Tags:
Embed Size (px)
Citation preview
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
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
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
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
slide 5
The Function Block Concept
Algorithms
Type name
Internal data
Data outputsData inputs
Event outputsEvent inputs
Instance name
ControlExecution
Data flow
Event flow Event flow
Data flow
Introduced by IEC61131 Modified by IEC61499
Resource Block Transducer Block Function Block View Block Trend Block Alert Block
slide 6
FB-based IPMCS Application
Event flow
Data flow
Processinput
Processoutput
Composite FBElementary FB
slide 7
IPMCS Development ProcessWith Engineering Support System
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
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
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)
slide 11
The IEC61499 FB-based device model
Communication link(s)
Resource x
Controlled process
Resource zResource y
Application BApplication C
Application A
Device boundary
Communication interface(s)
Process interface(s)
= Data & event flow
IEC61804 for the development of the ESS
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
slide 13
IPMCS Development ProcessWith Engineering Support System
slide 14
4-layer architecture for IPMCS development
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
slide 16
IPMCS Development Process Using ESS
Add FB
ImportFB Type
FB Type
Repository
ESS
Device Type Repository
ImportDevice Type
XML file
IUIU
Application Layer
System Layer
FB1
FB2
FB3
FB4
nodeFieldbus B
Fieldbus A Backbone
IPT
Real world Layer
D1
D2
D3
slide 17
IPMCS Development Process Using ESS
Connect FB
ImportFB Type
FB Type
Repository
ESS
Device Type Repository
ImportDevice Type
XML file
IUIU
Application Layer
System Layer
FB1
FB2
FB3
FB4
nodeFieldbus B
Fieldbus A Backbone
IPT
Real world Layer
D1
D2
D3
slide 18
IPMCS Development Process Using ESS
Set time constraints
ImportFB Type
FB Type
Repository
ESS
Device Type Repository
ImportDevice Type
XML file
IUIU
Application Layer
System Layer
FB1
FB2
FB3
FB4
nodeFieldbus B
Fieldbus A Backbone
IPT {Time constraints}
Real world Layer
D1
D2
D3
slide 19
Add device
ImportFB Type
FB Type
Repository
ESS
Device Type Repository
ImportDevice Type
XML file
IUIU
Application Layer
System Layer
FB1
FB2
FB3
FB4
node
D1 D3 D2Fieldbus B
Fieldbus A Backbone
IPT {Time constraints}
Real world Layer
D1
D2
D3
IPMCS Development Process Using ESS
slide 20
Assign FB to device
ImportFB Type
FB Type
Repository
ESS
Device Type Repository
ImportDevice Type
XML file
IUIU
Application Layer
System Layer
FB1
FB2
FB3
FB4
node
D1 D3 D2Fieldbus B
Fieldbus A Backbone
IPT {Time constraints}
Real world Layer
D1
D2
D3
IPMCS Development Process Using ESS
slide 21
Set Configuration ParametersDownload FB to device
ImportFB Type
FB Type
Repository
ESS
Device Type Repository
ImportDevice Type
XML file
IUIU
Application Layer
System Layer
FB1
FB2
FB3
FB4
node
D1 D3 D2 Fieldbus B
Fieldbus A Backbone
IPT {Time constraints}
Real world Layer
D1
D2
D3
IPMCS Development Process Using ESS
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
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
slide 24
Field Device Model
Network Interface
Device
Application Management
EntityFB
Resource
Connections
Industrial Process Interface
Connection Points
FB
slide 25
Downloaded FB
Event Type
DataType
EventConnection
Predefined FB
User Defined Parameter
NameValueSlaveDomainSubnet
Device Type
1..*1..*
ConnectionPoint
Connection
sourceDestination
Industrial Process Interface
1..*1..*
Network Interface
NodeAddressProtocol
Resource
Item
FB Type
Application Management Entity
Device
SerialNoDeviceID
1..*1..*
1..*1..*
DataConnnection
Event Item
Function Block
Data Item
rangeunits
Field Device Model
slide 26
Add device Connect device/ set
configuration parameters Set device parameters
(parameter name, value)
Field Device API for ESS functionality
Application DevelopmentPhase
Engineering Tool
(Compiling)
Refined Device modelMachine-readablerepresentation
Machine Level
User Defined Parameters- Name : undefined- Value : undefined
Device Type- Name : undefined
1..*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..*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..*1..*1..*1..*
1..*1..*
<?xml version="1.0" encoding="UTF-8"?><!ELEMENT DataType(Identification?,VersionInfo+,CompilerInfo?,ASN1Tag?,(DirectlyDerivedType|EnumeratedType|SubrangeType|ArrayType|StructuredType))><!ATTLIST DataType Name CDATA #REQUIRED Comment CDATA #IMPLIED><!ELEMENT VersionInfo EMPTY><!ATTLIST VersionInfo Organization CDATA #REQUIRED Version CDATA #REQUIRED Author CDATA #REQUIRED Date CDATA #REQUIRED Remarks CDATA #IMPLIED><!ELEMENT ASN1Tag EMPTY><!ATTLIST ASN1Tag Class (UNIVERSAL | APPLICATION | CONTEXT | PRIVATE) #IMPLIED Number CDATA #REQUIRED><!ELEMENT CompilerInfo (Compiler*)*><!ATTLIST CompilerInfo header CDATA #IMPLIED classdef CDATA #IMPLIED>
User Level
Electronic DeviceDescription in XML
Device Proxy/wrapper
Engineering Tool
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}
IUIU
System Layer
node
D1 D3 D2Fieldbus B
Fieldbus A Backbone
Device Proxy or WrapperFB Table
FB4 Device Proxy or Wrapper
FB Table
FB2D1 D3 D2
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
slide 29
The Proposed Model Implemented on Profibus
IU
Profibus driver to DP deviceDRAM
VirtualField
Device
ProfibusDevice
VFD API
ProfibusAPI
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
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
DifferentManufacturer devices
Common device Description representation
HARTFFoundation
NOHAProfibus
LONWORKS
Device modelFieldbus specific
Different fieldbus devices
Common devicedescription
IEC61499(1990)
Device model requirements
General Device model based on FB used by ESS tool for automated application design
slide 32
IEC61804 Device Model
VirtualFieldbus
+ AddDevice()+ RemoveDevice()+ IdentifyDevice(PhysicalTag, NodeAd)+ FindTag()+ Configure()+ PublishTime(App, Link)+ GetDeviceStatus()+ ConnectFB()+ CreateDataType()+ DeleteDataType()+ CreateFB()+ DeleteFB()+ StartFB()+ StopFB()+ KillApp()
Item
- range : undefined- units : undefined- offsetOfVar : undefined- name- limitThreshold : float- ValidityIndex : boolean
+ read()+ write()
Revision
- DeviceProfile- accessPermission- StaticDataWriteLock
+ SetDeviceProfile()+ SetAccessPermission()+ SetDataWLock()
Identification
- CompPartNo : integer- Materials : string- SWVersion : string- HWVersion : string- WorkRange : undefined- RevisionNo : undefined- manufacturerNo : undefined- ModelNo : undefined- InstallationDate : undefined- PhysicalTag : undefined
+ NewTag()+ ChangeTag()+ UniqueTag()
Configuration
- range : undefined- offset/Eng. units : undefined- warningLevel : undefined- alarmLevel : undefined- samplingFreq : undefined- FilterTimeCt : undefined
+ RetrieveDefaultConfig()+ ReadAvailableFunctions()+ readActiveFunction()+ readConfigRevision()+ SetUserConfig()+ SetVendorConfig()
ItemType Device
- typeName : string- Name : string- Devstatus : (Available,Degrated,OutOfSrv)- NodeAddress : undefined
+ PowerOnTest(Devstatus)+ RunTimeTest(Devstatus)+ SetPhysicalTag()+ SetAddress()+ ClearAddress()+ FBStart(BlockTag)+ FBStop(BlockTag)+ Read()+ Write()+ NewDataType()+ GetDataType()+ GetFBType()+ GetConnection()+ GetVariable()
0..* 10..* 11..* 11..* 1
1..*
1
1..*
1
1
1
1
1
1..*
1
1..*
1
1
1..*
1
1..*
InitParameters
1
1..*
1
1..*
slide 33
IEC61499 Device Model
FBType
Device
- Name : undf ined
+ CreateRes()+ InitRes()+ StartRes()+ StopRes()+ DeleteRes()+ Query Res()
Application System 0..*1 0..*11..* 11..* 1
ResParameters
- Name : undef ined- Ty peName : undef ined- DataTy pe : undef ined- Init : undef ined
ResEventConnection
- Source : undef ined- Destination : undef ined- ResEv entTy pe : undef ined
ResDataConnection
- Source : undef ined- Destination : undef ined
ResFunctionBlock
- Name : undef ined- Ty pe : undef ined- Init : undef ined
FBTypeResourceType
- MaxDataCon : undef ined- MaxEv entCon : undef ined- PAccessPath : undef ined- RequiredExecTime : undef ined
1..*
1
1..*
1
1..*
1
1..*
1
1..*
1
1..*
11..*
11..*
1
1
1..*
1
1..*ItemTy pe
1 1..*1 1..*
FunctionBlock
- Name : undef ined- Ty peName : undef ined- Init : undef ined
Parameters
- Name : undef ined- DataTy pe : undef ined- Init : undef ined
EventConnection
- Source : undef ined- Destination : undef ined- Ev entTy pe : undef ined
DataConnection
- Source : undef ined- Destination : undef ined
FB
- Name : undef ined- Ty peName : undef ined- Init : undef ined
DeviceType
- Ty peName : undef ined11..* 11..*
1..*
1
1..*
1
1..*
1
1..*
1
1..*
1
1..*
1
ResInstDataCon
- Source : undef ined- Destination : undef ined
ResInstEventCon
- Source : undef ined- Destination : undef ined
Resource
- Name- Ty peName- PAccessPath : undef ined
+ CreateItem()+ CreateFB()+ CreateCon()+ InitItem()+ InitFB()+ InitCon()+ StartItem()+ StartFB()+ StartCon()+ StopItem()+ StopFB()+ StopCon()+ DeleteItem()+ DeleteFB()+ DeleteCon()+ Query Item()+ Query FB()+ Query Con()
1..*1 1..*1
1..*1 1..*1
1..*
1
1..*
11..*
1
1..*
1
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 typesFBType
Device Type
Real-world layerSystem layer
Application Layer
Extract Device Type
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
slide 36
Ev ent Ty pe
DataTy pe
Ev entConnection
User Def ined Parameter
BusParametersSlave/MasterDomain
SetParameterValue()
Dev ice Ty pe
Profibus
ConnectionPoint
DataTy peTy peOf Transportindex
Connection
sourceDestinationQuality
SetConnection()GetConnection()SetTimeBound()
Transducer Block
Network Interface
NodeAddress : undef inedProtocol : undef inedOperationMode : undef ined
GetAddress()SetAddress()ClearAddress()
Resource
ResourceID : undef ined
Conf igure()Init()SetResourceID()StartResource()StopResource()SetFBinRes()
Item
Av TrRate : undef inedMaxTrRate : undef inedPolling : booleanPacketLength : Integer
FB Type
Device
Prof ileNrDev iceID
SetDev iceTag()Retriev eDef aultConf ig()ReadAv ailableFB()SetConf ig()SetFBConnection()
DataConnnection
Event Item
Ty pe : undef ined
SetActiv eLev el()
Data Item
range : undef inedunits : undef inedindexinFB
InitData()SetRange()SetOf f set()SetAlarmLev el()SetWarningLev el()
Function Block
priority : undef inedSchedulingTurn : undef inedFBID : undef ined
SetScheduling()SetTimeBound(Ev entIn, Ev entOut)Start()Stop()GetFBTy pe()
Predef ined FB
1..*1..*
1..*1..*
1..*1..*
Profibus Device Model