BS EN 62453-2:2017 pdf download.Field Device Tool (FDT) Interface Specification Part 2: Concepts and detailed Description (IEC 62453-2:2016).
This part of IEC 62453 explains the common principles of the field device tool concept. These principles can be used in various industrial applications such as engineering systems, configuration programs and monitoring and diagnostic applications.
This standard specifies the general objects, general object behavior and general object interactions that provide the base of FOT.
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.
IEC 61131 (all parts), Programmable controllers
IEC!TR 62390:2005, Common automation device — Profile guideline
IEC 62453-1:2016, Field Device Tool (FDT) interface specification — Part 1: Overview and guidance
IEC 62453-3xy (all parts), Field Device Tool (FDT) interface specification — Part 3xy:
Communication profile integration
3 Terms, definitions, symbols, abbreviated terms and conventions
3.1 Terms and definitions
For the purposes of this document, the terms and definitions given in IEC 62453-1 as well as the following apply.
3.1.1 Child DTM
DTM instance in an FDT Project, which is classified by its relation to a Parent DTM
Note I to entry; Any DTM which uses FDT communication may be classified as Child DTM (i.e. Device DTM, Gateway DTM. Module DTM and BTM)
3.1.2 FDT version
implementation version defined by the related technology specific organization
4 Fundamentals
4.1 General
Clause 4 introduces the FDT model and covers topics which are specific to the requirements
of field device integration.
4.2 Abstract FDT model
4.2.1 FDT model overview
The UML class diagram in Figure 2 provides an overview of the objects defined in FDT and their relationships to each other.
4.2.2 Frame Application (FA)
4.2.2.1 General
Frame Applications are able to handle any type of device by integrating corresponding DTMs without the need for device-specific or fieldbus-specific knowledge. Depending on the intended use Frame Applications may provide different appearance and features (e.g. standalone configuration or engineering system of a DCS). Typically, the Frame Application comprises client applications focusing on specific aspects such as configuration, observation, I/O planning, and using the service provided by the DTMs.
The Frame Application is the runtime environment for the DTMs. It provides the services described in 7.7 which may be used by the hosted DTMs.
4.2.2.2 System communication
If the Frame Application has built-in communication capabilities, then it is able to provide Communication Channels (see 4.2.4.3) which provide the services to access the fieldbus. In this case it has full control over communication and is able perform low-level actions such as monitoring or filtering. Frame Applications without build-in communication capabilities are using Communication DTMs (see 4.2.3.2.2). Figure 3 shows the relation between the Frame Application and the Communication Channel object.
The Frame Application’s channel objects represent the gateway from the FOT-specific to the
Frame Application-specific communication. On the Frame Application’s side the
Communication Channel may be a PC I/O board or an engineering topology with processing
units and proprietary bus systems.
4.2.3 Device Type Manager (DTM)
4.2.3.1 DTM Business Logic overview
The DTM Business Logic (DTM BL) encapsulates device-specific functions and protocolspecific definitions. Thus a Frame Application is able to handle any type of device by integrating corresponding DTM Business Logic without the need for device or fieldbus-specific knowledge.
The DTM BL provides the services described in 7.2 (see Figure 4). From a Frame Application’s point of view, all management and task-related interactions with the device functionality are available via these services.
The Frame Application’s channel objects represent the gateway from the FOT-specific to the
Frame Application-specific communication. On the Frame Application’s side the
Communication Channel may be a PC I/O board or an engineering topology with processing
units and proprietary bus systems.
4.2.3 Device Type Manager (DTM)
4.2.3.1 DTM Business Logic overview
The DTM Business Logic (DTM BL) encapsulates device-specific functions and protocolspecific definitions. Thus a Frame Application is able to handle any type of device by integrating corresponding DTM Business Logic without the need for device or fieldbus-specific knowledge.
The DTM BL provides the services described in 7.2 (see Figure 4). From a Frame Application’s point of view, all management and task-related interactions with the device functionality are available via these services.BS EN 62453-2 pdf download.