IEC 62453-1 pdf download – Field device tool (FDT) interface specification – Part 1: Overview and guidance

IEC 62453-1 pdf download – Field device tool (FDT) interface specification – Part 1: Overview and guidance

IEC 62453-1 pdf download – Field device tool (FDT) interface specification – Part 1: Overview and guidance
Device and module-specific software components are of several types to cover integration ofproducts commonly used in automation systems. DTM objects can, for example,representnormal measurement and control devices.There are specializations of DTMs which represent:
.software entities or function blocks that are movable and may be hosted by different
modules in a network, also known as Block DTM(BTM) objects;
modular equipment combinations,such as lO stations with plug in boards to providecombinations of l/O and control functions also known as Module DTM objects.
A Communication Channel represents the entry point to a fieldbus or point-to-pointcommunication. lt provides fieldbus interface independent services. In general,the protocolspecific services are mapped to the services provided by the channel.The services may beused by the Frame Application or a DTM to exchange data with a connected device or toinitiate a function (e.g. identification request,device reset, broad-cast, etc.).
FDT defines the services each of the components has to provide and the data which isexchanged by those. The services are defined in a fieldbus independent way, but someexchange fieldbus specific data.The content and data format for manufacturer independentfieldbuses is defined in the IEC 62453-3xy specifications defining the protocol profileintegration in FDT.FDT also enables manufacturers to define their own content and dataformats, for example for a manufacturer specific fieldbus or point-to-point communication.
The main features of the FDT concept are:
. Frame Application is the representation of the host tool where the DTMs are interacting
with the control system, maintenance or engineering application;
DTM is the main concept and can be applied for simple devices but also for modulardevices, software components (function block);
nested communication is provided to meet the requirement of heterogeneous andhierarchical networks where the intelligent field devices are connected. This is thebackground for various communication parts in the standard;
graphical interfaces are provided to provide interactive access to the functionality of theintelligent field devices and its DTM to the human beings.These aspects are representedby so called presentation objects.
4.3.2Frame Applications
Frame Applications provide the runtime environment for the FDT system. Depending on theintended use Frame Applications may have different appearances (e.g. standaloneconfiguration and engineering system).The following general requirements apply to all FrameApplications:
device and module-specific knowledge is not necessary;
. ability to manage all DTM instances and store instance data;
ability to manage and create DTM communications and connections (including anynecessary message routing);
guarantee of system-wide consistent configuration;
enables multi-user and serverlclient operation (optional);takes care of data versions and consistency.
FDT is a specification to facilitate the interaction between device-specific objects (i.e.presentation and DTM) and the Frame Application.This is shown in Figure 4.
A Frame Application provides the runtime environment for device specific objects. Typically, the Frame Application comprises client applications that use DTMs, a database for persistent
storage of device data, and a communication link to the field devices.
Client applications are single applications focusing on specific aspects such as configuration,observation, channel assignment, and using the functionality provided by the DTM as a
NOTE The IEC 62453 series distinguishes between the specification of the interactions between objects (e.g.Frame Applications and DTMs) and the implementation technology for the implementation of those objects. It specifies only the behavior that the objects are expected to provide to client applications that use them.
4.3.3 Device Type Manager
DTM objects are supplied by the device manufacturer together with the device. The following
properties are characteristic for the DTM:
• generally not a standalone tool;
• graphical user interfaces as defined by this specification;
• all rules of the device are known;
• all user dialogs are contained;
• user interface (multilingual including help system);
• parameter validity check (also depending on other device-specific parameters);
• automatic generation of dependent parameters;
• processing sequences are defined for complex calibration, and setup procedures where needed;
• reading and writing of parameters from/to the field device;