Integration of the Future FDI Device Packages into FDT Based Systems

Related Vendors

DÜPERTHAL Sicherheitstechnik GmbH & Co. KG

TURCK GmbH

Italvacuum, Srl

FDT defines a software interface between device drivers, the DTMs (Device Type Managers) and FDT Frame Applications [4]. In this context, a DTM can represent both a field device and a communication device (e.g. Gateway, Remote I/O). The technology is thus open to all manufacturers and all communication protocols. Currently, over 12 protocols are supported — both from the area of process automation (e.g. Hart, Profibus, and Foundation fieldbus) and from factory automation (e.g. Interbus S, IO-Link, DeviceNet, CANopen). In order to meet additional customer requirements from the industry, the FDT Group has been working on Version 2.0 of the FDT specification since the beginning of 2009. This should be completed in 2010.

Both technologies have proven their worth and justified their existence in various applications and industries [5]. However, the variety of EDDL profiles, system-specific special considerations and the co-existence of two independent standards result in high costs for device manufacturers and cause many problems for users.

Device integration tomorrow — FDI Device Packages

The FDI project (Field Device Integration), which was initiated at the request of many users, is therefore pursuing the aim of a standardized device integration solution for process automation. The aim is to integrate the two technologies of FDT and EDDL into a joint solution. [6]

With FDI, a field device is represented by an FDI Device Package. This package is provided for every device and, depending on the requirements of the device, contains up to four different elements (Figure 1):

• The Device Definition describes the data of the device and their structure. This element forms the information model of the device and must therefore always be present.

• The Business Logic describes the rules for accessing the device data and their dependencies. Based on the current status of the data, this is used to define which respective data are visible and can be read and/or written.

• The User Interface Description (UID) describes the operating structure of the device. The device data are arranged in a menu structure accordingly.

• User Interface Plug-ins (UIPs) are special device functions and user interfaces (e.g. diagnostic functions for valves) in the form of software components.

(ID:21618550)