Working with Device DDTs
Original instructions
Introduction
Use Control Expert to create a collection of device derived data types (DDDTs) and variables that support communications and the transfer of data between the PAC and the various local slaves, distributed devices, and corresponding I/O modules.
You can create DDDTs and corresponding variables in the Control Expert DTM. Those program objects support your network design.
There are different default device names, depending on the version of Unity Pro or Control Expert in which you built your application:
NOTE:
You cannot interchange these DDDT types in your applications:
  • The T_BMENOC0301 and T_BMENOC0311 DDDTs is only supported in Unity Pro 8.1.
  • The T_BMENOC0301_2 and T_BMENOC0311_2 DDDTs are only supported in Unity Pro 10.0 or later.
Use the DDDTs for these tasks:
You can double-click the name of the DDDT in the Project Browser at any time to view its properties and open the corresponding EDS file.
NOTE: For applications that require multiple DDDTs, create an Alias name that logically identifies the DDDT with the configuration (module, slot, local slave number, etc.).
DDDT Variables
You can access the DDDTs and the corresponding variables in Control Expert and add them to a user-defined Animation Table. Use that table to monitor read-only variables and edit read-write variables.
Use these data types and variables to perform these tasks:
Displaying the Order of Input and Output Items
In the Project Browser, view the DDDTs.
The Data Editor displays each input and output variable. When you open the first input and output variables, you can see both the connection health bits (DEVICE_OBJ_HEALTH) and the connection control (DEVICE_OBJ_CTRL) bits.
This table shows the rule assignment for connection numbers:
Inputs
Order
Outputs
health bits (note 1)
1
control bits (note 1)
Modbus TCP input variables (note 2)
2
Modbus TCP output variables (note 2)
local slave input variables (note 3)
3
local slave output variables (note 3)
EtherNet/IP input variables (note 2)
4
EtherNet/IP output variables (note 2)
NOTE 1: Health and control bits are in this format:
  •     i. By device type:
    • a. Modbus TCP
    • b. local slave
    • c. EtherNet/IP
  •     ii. Within each device type:
    • a. by device or local slave number
    • b. within a device (by connection number)
NOTE 2: Device variables are in this format:
  •     i. by device number
  •     ii. within a device (by connection number)
  •     iii. within a connection (by item offset)
NOTE 3: Local slave variables are in this format:
  •     i. by local slave number
  •     ii. within each local slave (by item offset)