ai_413_fdt_dtm
TRANSCRIPT
-
7/31/2019 AI_413_FDT_DTM
1/15
12004 March, HKEPFL - Industrial Automation 4.1 Device Access Protocols
Device Management ProtocolsProtocoles de gestion des appareils
Gertezugangsprotokolle
FDT - DTM
Prof. Dr. H. Kirrmann ABB Research Center, Baden, Switzerland
Industrial AutomationAutomation IndustrielleIndustrielle Automation
4.2
4.
-
7/31/2019 AI_413_FDT_DTM
2/15
2 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
FDT - DMT purpose
integrate field devices (sensors and actors) of different manufacturers in any control orengineering system
device description file (HART, GSD) -> device type manager (DTM)
DTM is a software module (a kind of driver) that comes with each device.DTM encapsulates the device's configuration, functions, parameters and describes theuser interface
-
7/31/2019 AI_413_FDT_DTM
3/15
3 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
Field Device Configuration
> 10 Device Suppliers> 100 Device Types
> 10.000 I/Os
HART
-
7/31/2019 AI_413_FDT_DTM
4/15
4 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
The Situation of Today
Device DescriptionFunction BlockDevice AddressDevice I/OsDevice Parameter
HART
> 10 Device Suppliers
> 100 Device Types> 10.000 I/Os
Function Charts
? Large DCS
Tool 1
Tool n
-
7/31/2019 AI_413_FDT_DTM
5/155 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
The Goal
HART
Device Diagnosis
Slave ConfigurationMaster Configuration
Function Charts
> 10 Device Suppliers
> 100 Device Types> 10.000 I/Os
CEAG I/O
P5001 0 ... 150 bar
Shared Engineering Data:
Tag
I/O-TypeMeasuring RangeLimit ValueI/O Channel AssignmentDevice Parameters
HSI Configuration
-
7/31/2019 AI_413_FDT_DTM
6/156 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
Overall Requirements
HART
Consistent, plant-wide configuration of DCS, Fieldbus and devices Integrated device configuration and documentation
Device integration with smallest effort
Integration of devices in all available tools
Tool support of individual device features
Devices
DCS
-
7/31/2019 AI_413_FDT_DTM
7/157 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
HART-DDGSD
FF
DDOSC ++
The Still Open Question ...
... is , how to distribute the device type knowledge ?
EDDL
-
7/31/2019 AI_413_FDT_DTM
8/158 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
Component architecture
HART
Engineering Tool
Device Components
HART
-
7/31/2019 AI_413_FDT_DTM
9/15
9 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
Device Component
CEAG I/O
P5001 0 ... 150 bar
Device Configuration and Maintenance
DeviceComponent
S900 I/O
-
7/31/2019 AI_413_FDT_DTM
10/15
10 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
Engineering Environment for Components
Engineering Tool handles
device components asfunction blocksHART
Device Component
-
7/31/2019 AI_413_FDT_DTM
11/15
11 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
Engineering Environment for Components
no device specific knowledge required
manages all device instances and stores all instance data
offers individual communication and routing services via DCS-system.
controls plant-wide consistent configuration
offers data life cycle control for device parameters
has multi user and server/client architecture
Device Component
-
7/31/2019 AI_413_FDT_DTM
12/15
12 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
InstrumentManufacturer
DCSManufacturer
Engineering Tool
EngineeringApplication
Communication
IFb UIIFb Instance Data
IFb Device Type Mgr
IFb Type IFb Registry
Registry
IFb Reg Com
DTM
IFb LOGIFb Communication
PNO
GSD
DLL
HumanInterface+Methods Data
Base
PROFIBUS
System Buse. g. Ethernet Controller
-
7/31/2019 AI_413_FDT_DTM
13/15
13 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
The Device Component ...
... belongs to a device
... is supplied with the device by the devicemanufacturer
... is no standalone tool
... is an Active X Component (COM/DCOM)
... has COM Interfaces as specified by PNO/ZVEIWorking Group
... is called Device Type Manager (DTM)
HART
-
7/31/2019 AI_413_FDT_DTM
14/15
14 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
The Device Type Manager ...
... knows all business rules of the device
... contains all user dialogs
... does the device configuration anddiagnosis
... generates the device specificdocumentation
... has no data storage capability
... has no direct device link to any device
... does not know anything about the engineering environment
=
HART
-
7/31/2019 AI_413_FDT_DTM
15/15
15 4.2 FDT-DTM2004 March, HKEPFL - Industrial Automation
The Device Type Manager ...
... supports one or several devices
... could be created from existingdevice tools
... could be automatically compiledfrom Device Descriptions
... could be developed from scratch
... should be an Active X Control for use inWebBrowser
... should be designed according to Microsoft MultiLayer Architecture
Device TypeManager
=
HART