M&M FDT 1.2.1 Online Specification
 2.4.1 The Device Type Manager (DTM)


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.4.1 The Device Type Manager (DTM)

There are different types of fieldbus devices installed on a plant. Therefore, you need one or several DeviceTypeManagers (DTMs) to handle these different devices. Fieldbus device manufacturers deliver the DeviceTypeManagers. They are installed in the system, so that the system can be dynamically extended by installing new DTMs for new fieldbus devices.

It depends on the software design of the DTMs, whether they are responsible for one device type or a group of device types. It is possible to implement even one very powerful DTM for a group of targeted device types.

Usually, one DTM handles one device type and knows everything about its specific parameters, behavior, and limitations.


Figure 2-4 - The DTM Interfaces

The interfaces IDtm and IDtmInformation have to be implemented by each DTM. These interfaces provide the base functions and information for controlling a DTM. From a Frame Application’s point of view, all task-related interfaces for the interaction with the device functionality are available via these interfaces. Which task related interfaces are provided depends on the capability of the DTM and the according device. Each interface will be described in detail at its own chapter.

In order to represent the device’s I/O connections or process values accessible for data exchange with the Frame Application, the DTM can implement an FDT-Channel object (Process Channel). This object implements at least the IFdtChannel interface that gives access to all parameters of the channel which describes the channel itself.

If the device provides communication functionality, like a fieldbus adapter or a gateway, the FDT-Channel object must implement further interfaces for the communication via this channel (Communication Channel). Each interface of the FDT-Channel object will be described in detail at its own chapter.



© 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.