Technical FAQs

Ask a Question

How we can differentiate between different types of PlantStruxure DTM's

The PlantStruxure architecture complies with the FDT standard and provides some adaptations to facilitate the system configuration, including the fieldbus configuration. The PlantStruxure architecture is mainly based on five DTM categories combining DTM types and their functions:

•Comm DTMs are either pure communication DTMs when connected to Ethernet devices, or support a gateway function to allow a remote connection to another fieldbus (e.g. Modbus Serial Line, CANopen, Profibus, and so on). In the PlantStruxure context, a comm DTM can combine the communication and gateway functions of standard DTMs

•FieldBus (FB) master DTMs include a fieldbus configuration and management function using the FDT technology and an optional remote master device configuration and management function. A fieldbus master DTM (e.g. Eth Master DTM or Profibus PRM V1 Master DTM) combines the communication, gateway and fieldbus configuration functions. It must be the first DTM activated from a FDT frame when used. The fieldbus master DTMs use PlantStruxure specific interfaces to be integrated in Unity Pro – they cannot be used in other environments

•Gateway DTMs are used to transition between different communication paths responsible for the inter-protocol mapping (for instance, between Ethernet Modbus TCP and Modbus Serial Line) 

•Device DTMs are specific DTM software programs that provide device level services (e.g. ATV or TeSys) or can be the DTM interface associated to a non-DTM device tool such as Advantys Configuration Software

•Generic DTMs are generated from a device description file (e.g. DDXML files or EDS files for CANopen) and provide generic services.
Was this helpful?
What can we do to improve the information ?