M&M FDT 1.2.1 Online Specification
 6.8 DCS Channel Assignment


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.8 DCS Channel Assignment

During the channel assignment the relationship between a channel provided by the DTM and a channel within the Frame Application (DCS channel) is established by the Frame Application. To do this, the Frame Application has to get the channel properties from the DTM. To get this information it asks the DTM for the channels of the current instance and iterates over the received channels.

For the assigned channels the Frame Application sets the read-only-flag within the channel parameters. This flag causes that the channel is not deleted until the channel assignment is released.

If a DTM instance represents a complete device, all information for channel assignment is available at this DTM.

In case of a modular device like remote I/Os which is represented by one DTM, the internal structure is also available via the parameter interface. From the channel assignment point of view this information allows the Frame Application to generate a structured presentation, so that there is no difference for a user whether he works with a single DTM or with several DTMs which represent the parts of the modular device.


Figure 4-6 - Single DTM

Used methods:
IFdtContainer::LockDataSet()
IFdtContainer::UnlockDataSet()
IDtmParameter::GetParameters()
IDtmChannel::GetChannels()
IFdtChannel::GetChannelParameters()
IFdtChannel::SetChannelParameters()

The following figure shows a sub structure with DTMs for modular devices especially for remote I/Os with modules of different vendor. The connection of the Device-DTM and its module DTMs is established via the standard topology methods. At this sub structure the Device-DTM is the gateway between the fieldbus and the proprietary backplane bus. So the communication can be realized by the mechanisms of nested communication.


Figure 4-7 - Modular DTM Structure

In this case ‘LinkedDevice’ specifies the connection between a communication channel of the bus coupler (DTM Device) and the modules (DTM Module) as well as the connection between a communication channel of a module and a connected device. Especially for a remote I/O the FdtChannels are similar to the slots at the backplane.

So if a DTM instance represents only a part of a device, the information for channel assignment has to be collected by the Frame Application In case of a modular device like remote I/Os, the gateway is signed as main DTM and is the start point to collect the information of the sub DTMs which at least belong to the same device. So the internal structure is represented by the topology. From the channel assignment point of view the channel information together with the topology allows the Frame Application to generate a structured presentation, so that there is no difference for a user whether he works with a single DTM or with several DTMs which represent the parts of the modular device.


Used methods:
IFdtContainer::LockDataSet()
IFdtContainer::UnlockDataSet()
IDtmParameter::GetParameters()
IDtmChannel::GetChannels()
IFdtChannel::GetChannelParameters()
IFdtChannel::SetChannelParameters()
IFdtTopology::GetChildNodes()



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