M&M FDT 1.2.1 Online Specification
 2.2 Where FDT Fits


Interfaces and Methods   -   Schemas   -   FDT Specification   -   Quicklinks   -   Abbreviations

Up to FDT Specification

2.1 FDT Overview
2.2 Where FDT Fits
2.3 General FDT Architecture and Components
2.4 Overview of Objects and Interfaces
2.4.1 The Device Type Manager (DTM)
2.4.2 The Block Type Manager (BTM)
2.4.3 The FDT Frame Application
2.5 Synchronization and Serialization Issues
2.6 Parameter interchange via XML
2.6.1 Examples of usage
2.7 Persistent Storage Story
2.7.1 Persistence Overview
2.7.2 Persistence Interfaces
2.8 Basic features of a session model
2.9 Basic Operation phases
2.9.1 Roles and Access Rights
2.9.2 Operation Phases
2.10 Abstract FDT Object Model
2.11 Fieldbus independent Integration
2.12 Scanning and DTM Assignment

2.2 Where FDT Fits

Although FDT is primarily designed to control the functionality of a device and for accessing data to configure parts of the control system, FDT interfaces can be used in many places within an application. At the lowest level they can get raw data from the devices into a SCADA or DCS to configure the bus master. At a higher level the Frame Application can start a device specific diagnosis application via the DTM. The architecture and design makes it possible to build and to integrate scalable DTMs, where the functionality depends on the capabilities of the device.

The scalability of DTMs will be explained later on.



© by M&M Software GmbH, parts of this website taken from FDT Interface Specification Version 1.2.1, © by FDT Group, AISBL.
This website is published for support of M&M products as granted in license conditions, chapter 2.1.
Last updated 2015-02-05 15:17
Email: FDT Technical Support Line.