M&M FDT 1.2.1 Online Specification
 2.11 Fieldbus independent Integration


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.11 Fieldbus independent Integration

The fieldbus independent integration of DTMs into a Frame Application is realized by bus category ids defined within the protocol specific annex. These bus category ids are defined as UUIDs.

For validation of topology during system planning runtime information of a DTM must be used. The same category ids are used as parameters of interface methods and within the XML documents used for the interaction between DTMs and Frame Application. The bus information is specified within the XML schemas like DTMParameterSchema or FDTHARTChannelParameterSchema and is available via the according bus independent interfaces. The information about the supported fieldbusses can be used to validate the bus topology or a connection during communication.

For further fieldbusses the definition of category ids can be extended complement on another fieldbus specific XML schema. The fieldbus independent FDT schemas handle the category ids just as an identifier within an attribute and each FDT component can use this information and the parameter of interface methods for validation.

Due to this mechanism the Frame Application must only know the category ids of its direct connected busses. For lower sub-topologies it just needs the contents of the category attribute within the XML documents for validation. Should the occasion arise, it is up to the DTM developer to define new category ids for proprietary bus systems and to install his DTM with this category id according to the FDT installation requirements.



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