The concept
Provide a standard for organising the interfaces (read/write - start/stop) between the engineering tool of your choice and software components which support the field device.
The standardized interface is provided by the Field Device Tool (FDT) and decouples the enineering tool and software component which provides the engineer input.
The Engineer uses the software component, Device Type Manager (DTM) to fully configure the intelligent field device.
DTM -> Solving the problem of intellegent field device engineering
The core of the FDT concept is the Device Type Manager (DTM), a component that is delivered by the device manufacturer. This can be used in all systems that support the FDT interface. The DTM is the configuration and management component for a field device. It is familiar with all of the device’s rules (plausibility checks) and contains all graphical user dialogs, device configuration, diagnosis, and maintenance. DTMs are loaded into the automation system libraries in a similar way to a printer driver in the Office environment.
FDT -> Solving the problem of engineering tool choice
FDT specifies an interface for data exchange between the field devices software components and the engineering tool. The FDT concept, using the DTM, offers integration capabilities precisely where they are most needed in the areas of engineering, diagnosis, service, and asset management. The FDT specification can be implemented in either system integrated tools or stand alone tools, the choice is yours.
The Result
- If the engineering tool of your choice has adopted the open FDT standard then you can choose to use DTM's to configure intellegent field devices.
- The engineering tool is responsible for:
-> Communications to field devices
-> The engineering database
-> The Engineering Application
- The DTM is responsible for
-> Providing the engineer interface (Graphic User Interface)
-> Providing access to the full device features
-> Managing information transfer to the field device (simplifies many engineering activities)
- Cost savings for all aspects of engineering and device support
Benefits of the FDT/DTM methodology
- Efficient intelligent device management
-Similar device types (e.g. Pressure) are presented within the engineering tool with the same style, reducing engineering effort
-Automatic management of all device rules (presentation of related data) simplifying device support
- Open, standardized interface
-If your engineering tool of choice supports FDT then you can use the DTM methodology
-This is a standard supported by the major intelligent device vendors
- Freedom to select your choice of engineering tool
-The engineering tool looks after all communications protocols, local storage database files.
-The DTM looks after all device specific configuration and engineer displays
- Support full device functionality
-As the DTM is provided by the device vendor then it will fully support all device functions
-The device vendor uses a style guide such that device types such as Pressure, Temperature are displayed to the engineer in a uniform format.
ABB EngineerIT tools using FDT
Within ABB, the FDT/DTM methodology is supported by both our stand alone tool DSV401(SMART VISION) and system integrated tools, too.
ABB DTM's
ABB fully support the FDT/DTM methodology with DTM's available for PROFIBUS and HART product including complex devices such as multivariable transmitters and Remote I/O. ABB has also developed universal DTM's to extend this new technology to field devices yet to benefit from this technology.
Read more ....
FDT is an open standard
The FDT specification provides the interfaces between the device-specific DTM and the system-specific engineering tools. Since the end of 2000, it has been released in Version 1 of PROFIBUS International and can be downloaded from the Internet (www.profibus.com). Today, FDT is already used by a number of manufacturers not only for PROFIBUS but also for HART devices. Work is currently in progress on modifying it to accommodate further communications protocols such as FOUNDATION fieldbus.