4.10.1 Task Related FDT Interfaces

All FDT interfaces are task related. Each object must implement a mandatory set of interfaces expected by all other objects. By implementing optional FDT interfaces an object is able to support additional functionality, e.g., a DTM may provide documentation in XML format or special diagnostics, a frame-application may provide audit trail functionality.
Each object is able to determine the availability of such optional interfaces of other objects during runtime.
All defined FDT interfaces are fixed and will never be changed. Additional future extensions will be based on additional optional interfaces. A DTM or frame-application is then able to add a higher FDT version support by implementing or using such additional FDT interfaces.

Device Type Manager	Availability	User Interface	ActiveX Control User Interface	Device with Online Data	Gateway DTM	Communication-DTM for PC/Fieldus adapter
IPersistXXX	Mandatory
IDtm	Mandatory
IDtm2	Mandatory
IDtmActiveXInformation	Optional		Mandatory
IDtmApplication	Optional	Mandatory
IDtmChannel	Optional				Mandatory	Mandatory
IDtmDocumentation	Mandatory
IDtmDiagnosis	Mandatory
IDtmImportExport	Optional
IDtmInformation	Mandatory
IDtmInformation2	Mandatory
IDtmOnlineDiagnosis	Mandatory
IDtmOnlineParameter	Optional			Mandatory
IDtmParameter	Mandatory
IFdtCommunicationEvents	Optional			Mandatory	Mandatory
IFdtCommunicationEvents2	Optional			Mandatory	Mandatory
IDtmHardwareIdentification	Optional
IDtmSingleDeviceDataAccess	Optional			Mandatory
IDtmSingleInstanceDataAccess	Mandatory
IFdtEvents	Mandatory

DTM ActiveX Control	Availability
IDtmActiveXControl	Mandatory

FDT Channel	Availability	Channel with User Interface	Channel of Gateway DTM	Channel of Communication-DTM for PC/Fieldus adapter
IFdtChannel	Mandatory
IFdtChannelActiveXInformation	Optional	Mandatory
IFdtChannelSubTopology	Optional		Mandatory	Mandatory
IFdtChannelSubTopology2	Optional		Mandatory	Mandatory
IFdtCommunication	Optional		Mandatory	Mandatory
IFdtFunctionBlockData	Optional		Mandatory	Mandatory
IFdtChannelScan	Optional		Mandatory	Mandatory

FDT Channel ActiveXControl	Availability
IFdtChannelActiveXControl	Mandatory
IFdtChannelActiveXControl2	Mandatory

BTM	Availability
IBtm	Mandatory
IDtmActiveXInformation	Mandatory
IDtmChannel	Optional
IDtmDocumentation	Mandatory
IDtmDiagnosis	Mandatory
IDtmImportExport	Optional
IBtmInformation	Mandatory
IDtmInformation2	Mandatory
IDtmOnlineDiagnosis	Mandatory
IDtmOnlineParameter	Mandatory
IBtmParameter	Mandatory
IFdtCommunicationEvents	Mandatory
IFdtCommunicationEvents2	Mandatory
IDtmHardwareIdentification	Mandatory
IDtmSingleDeviceDataAccess	Mandatory
IDtmSingleInstanceDataAccess	Mandatory
IFdtEvents	Mandatory

BTM ActiveXControl	Availability
IBtmActiveXControl	Mandatory

Frame Application	Availability	With User Interface
IDtmEvents	Mandatory
IDtmEvents2	Mandatory
IDtmAuditTrailEvents	Mandatory
IFdtActiveX	Optional	Mandatory
IFdtActiveX2	Optional	Mandatory
IFdtBulkData	Optional
IFdtContainer	Mandatory
IFdtDialog	Mandatory
IFdtTopology	Mandatory
IFdtBtmTopology	Mandatory
IDtmScanEvents	Optional
IDtmRedundancyEvents	Optional
IDtmSingleDeviceDataAccessEvents	Mandatory
IDtmSingleInstanceDataAccessEvents	Mandatory

Furthermore, the prefixes FDT, DTM and BTM are reserved for identifiers and names defined in the FDT specification. This prevents conflicts of further releases with private extensions of interfaces or definitions.
In general, all FDT interfaces are designed with fieldbus- and manufacturer-neutral methods. Extensions for a new fieldbus are done via new XML schemas. Functional extensions for new tasks will be provided by new interfaces.

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