Siemens SINUMERIK 840D sl Operating Manual page 515

If such a component was assigned a DO variable manually or via the Topo XML file, this DO
variable can also be used to specify the user-specific DO name and DO number. For each
component that is assigned a DO variable, an appropriate type must also be specified via the
"dotype" attribute.
The possible DO types are:
● SINAMICS S
● Integrated (NCU)
● Extended (NX)
● ACTIVE INFEED CONTROL
● SERVO
● SMART INFEED CONTROL
● BASIC INFEED CONTROL
● TB30
● DMC20 / DME20
● TM31
● TM41
● TM15
● TM120
● CULINK
● Determine INFEED from hardware
● Determine TM from hardware
DO - referencing components
DRIVE-CLiQ components that do not generate their own DO, but are assigned to a DO, can
be assigned to any existing drive objects.
DO - referencing components:
sensor_module,
damping_module voltage_sensing_module
The specification of "doref" references a DO and thus specifies the association of the
component to the DO. To do this, the same DO variable is used as that specified for the required
DO via the "dovar" attribute. This allows, for example, Sensor Modules on a hub to be assigned
to a SERVO-DO.
The "sm" attribute of the "sensor_module" element designates the encoder as 1st or 2nd
encoder of the DO. It must then be used if the encoder cannot be assigned uniquely.
For modeling DQI/SMI motors, a motor must be specified on the sensor_module along with
the encoder. The motor must also be removed from the associated motor_module.
The associated components must be identified with the attribute group="<name of the
composite component>".
SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo
Operating Manual, 12/2017, A5E36537479B-AE
Create MyConfig - Topo
6.9 Interface Topo XML
515