1 / 17

Device Management Protocols Protocoles de gestion des appareils Gerätezugangsprotokolle

Industrial Automation Automation Industrielle Industrielle Automation. Device Management Protocols Protocoles de gestion des appareils Gerätezugangsprotokolle. FDT - DTM. 4. 4.2. unfinished. Prof. Dr. H. Kirrmann. ABB Research Center, Baden, Switzerland. FDT - DMT purpose.

sera
Download Presentation

Device Management Protocols Protocoles de gestion des appareils Gerätezugangsprotokolle

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Industrial Automation Automation IndustrielleIndustrielle Automation Device Management ProtocolsProtocoles de gestion des appareilsGerätezugangsprotokolle FDT - DTM 4. 4.2 unfinished Prof. Dr. H. Kirrmann ABB Research Center, Baden, Switzerland

  2. FDT - DMT purpose Integrate field devices (sensors and actors) of different manufacturers in any control or engineering system Device description file (HART, GSD) -> device type manager (DTM) DTM is a software module (~ driver) that comes with each device. DTM encapsulates the device's configuration, functions, parameters and describes the user interface Client Tags E&H devices BASF 900 600 Clariant 262 ? BEWAG 12’000 4000 GSK 250 Gargill (NL) 1500 600 Gargill (UK) 1300 600 EFG 250 170 BASF (DL) 500 DioSynth (NL) 700 Omya 130 over 1.5 Mio € installed base

  3. HART Field Device Configuration > 10 Device Suppliers > 100 Device Types > 10.000 I/Os

  4. Example: waste water treatment plant 500 magnetic flowmeters 400 thermal mass flowmeters 400 pressure/DP/submersile transmitters 140 radar and ultrasonic transmitters 50 optical TSS transmitters 40 dissolved oxygen analyzers 100 temperature transmitters 5000 electric actuators 400 pneumatic actuators 400 variable speed drives 100 motor control centers 600 switches, samplers, and approximately 100 PROFIBUS masters asset management: how can devices from many different manufacturers appear the same way to the control system and to the engineers ?

  5. HART The Situation of Today Function Charts Large DCS ? > 10 Device Suppliers > 100 Device Types > 10.000 I/Os Device Description Function Block Device Address Device I/Os Device Parameter Tool n Tool 1

  6. HSI Configuration P5001 0 ... 150 bar Shared Engineering Data: Tag I/O-Type Measuring Range Limit Value I/O Channel Assignment Device Parameters CEAG I/O HART The Goal Function Charts Master Configuration Slave Configuration Device Diagnosis > 10 Device Suppliers > 100 Device Types > 10.000 I/Os

  7. HART Overall Requirements • Consistent, plant-wide configuration of DCS, Fieldbus and devices • Integrated device configuration and documentation • Device integration with smallest effort DCS Devices • Integration of devices in all available tools • Tool support of individual device features

  8. The Still Open Question ... ... is , how to distribute the device type knowledge ? FF DDOS C ++ EDDL HART-DD GSD

  9. HART Device Components HART Component architecture Engineering Tool

  10. P5001 0 ... 150 bar CEAG I/O Device Component Device Configuration and Maintenance Device Component S900 I/O

  11. HART Engineering Environment for Components Device Component Engineering Tool handles device components as function blocks

  12. Engineering Environment for Components Device Component • 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

  13. DCS Manufacturer PNO Instrument Manufacturer Engineering Tool IFb UI DTM EngineeringApplication IFb Instance Data IFb LOG Human Interface+ Methods IFb Communication Data Base IFb Device Type Mgr IFb Type IFb Registry GSD IFb Reg Com Communication DLL Registry System Buse. g. Ethernet Controller PROFIBUS

  14. HART The Device Component ... ... belongs to a device ... is supplied with the device by the device manufacturer ... is no standalone tool ... is an ActiveX Component (COM/DCOM) ... has COM Interfaces as specified by PNO/ZVEI Working Group ... is called “ Device Type Manager “ (DTM)

  15. HART The Device Type Manager ... ... knows all business rules of the device ... contains all user dialogs ... does the device configuration and diagnosis ... generates the device specific documentation ... has no data storage capability ... has no direct device link to any device ... does not know anything about the engineering environment =

  16. Device Type Manager = HART The Device Type Manager ... ... supports one or several devices ... could be created from existing device tools ... could be automatically compiled from Device Descriptions ... could be developed from scratch ... should be an ActiveX Control for use in WebBrowser ... should be designed according to Microsoft Multi Layer Architecture

  17. How to make a DTM 1) universal DTM can be generated out of HART, but limited to HART universal commands and HART Common Practice Commands. see: CE, October 2002, Martin Zähringen, M&M Software

More Related