M&M FDT 1.2.1 Online Specification
 6.4 Registration of Protocol Specific FDT Schemas


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

Up to FDT Specification

6.1 DTM Peer To Peer Communication
6.1.1 Establish a Connection between DTM and Device
6.1.2 Asynchronous Connect
6.1.3 Asynchronous Disconnect
6.1.4 Asynchronous Transaction
6.2 Nested Communication
6.2.1 Generate Systemtopology
6.2.2 Establish a Connection between DTM and Device
6.2.3 Asynchronous Transaction
6.3 Topology Scan
6.3.1 Scan Network
6.3.2 Cancel Topology Scan
6.3.3 Provisional Scan Result Notifications
6.3.4 Scan for Communication Hardware
6.3.5 Manufacturer specific Device Identification
6.4 Registration of Protocol Specific FDT Schemas
6.5 Configuration of a Fieldbus Master
6.6 Starting and Releasing Applications
6.7 Channel Access
6.8 DCS Channel Assignment
6.9 Printing of DTM Specific Documents
6.10 Printing of Frame Application Specific Documents
6.11 Propagation of Changes
6.12 Locking
6.12.1 Locking for Non Synchronized DTMs
6.12.2 Locking for Synchronized DTMs
6.13 Instantiation and Release
6.13.1 Instantiation of a New DTM
6.13.2 Instantiation of an Existing DTM
6.13.3 Instantiation of a DTM User Interface
6.13.4 Release of a DTM User Interface
6.14 Persistent Storage of a DTM
6.14.1 State machine of instance data
6.14.1.1 Modifications
6.14.1.2 Persistence
6.14.2 Saving Instance Data of a DTM
6.14.3 Reload of a DTM Object for Another Instance
6.14.4 Copy and Versioning of a DTM Instance
6.15 Audit Trail
6.16 Comparison of Two Instance Data Sets
6.16.1 Comparison Without User Interface
6.16.2 Comparison With User Interface
6.17 Failsafe Data Access
6.18 Set or Modify Device Address With User Interface
6.19 Sets or Modifies Known Device Addresses Without User Interface
6.20 Display or Modify All Child Device Addresses With User Interface
6.21 Device Initiated Data Transfer
6.22 Starting and Releasing DTM User Interface in Modal Dialog
6.23 Parent Component Handling Redundant Slave
6.24 Initialization of a Channel ActiveX Control
6.24.1 Supports IFdtChannelActiveXControl2
6.24.2 Does Not Support IFdtChannelActiveXControl2
6.25 DTM Upgrade
6.25.1 Saving Data from a DTM to be Upgraded
6.25.2 Loading Data in the Replacement DTM
6.26 Usage of IDtmSingleDeviceDataAccess::ReadRequest / Write Request
6.27 Instantiation of DTM and BTM

6.4 Registration of Protocol Specific FDT Schemas

In order to add new protocol support to the FDT specification and to existing Frame Application installations, a CommDTM installation must provide protocol specific schemas. There are two cases:

  1. Protocol specific schemas accepted and published by FDT-JIG. These schemas may be released independent on a FDT specification release.
  2. Schemas of a proprietary protocol. In this case all CommDTMs and Device-DTMs are provided in one consistent package. Consistency of all related data must be ensured internally by DTM.

The following structure explains an overall workflow:

  • Installation of DTMs with a channel implementing IFdtCommunication.
    • CommDTM is installed and contains in its setup the merge module of the protocol specific schemas.
    • CommDTM copies the schemas to a CommDTM specific certain path.
  • DTM library update DTMDeviceType information is used for DTMCatalog information.
    • IDtmInformation::GetInformation(), returns an XML document containing schema version and path of protocol specific schemas.
    • Frame Application compares this information with the already known schemas.
    • Frame Application checks, if schemas are already available in Frame Applications sub schema path and copies the schemas if not, or if higher version is offered.
    • Frame Application is responsible to synchronize the schema files over all subdirectories.
    • Frame Application gets additional protocol specific device identification information from a DTM by calling IDtmInformation2::GetDeviceIdentificationInformation().


Sequence diagram: Add new protocol specific schemas to Frame Applications schema sub path

Used methods:
IDtmInformation::GetInformation()


Sequence diagram: Frame Application reads protocol specific device identification information of DTMDeviceTypes
© 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.