Use Control Expert to create a collection of and variables that support communications and the transfer of data between the and the various local slaves, distributed devices, and corresponding I/O modules.
You can create DDDTs and corresponding variables in the Control Expert . 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:
-
Unity Pro 8.1: T_BMENOC0301, T_BMENOC0311
-
Unity Pro 10.0 or later: T_BMENOC0301_2, T_BMENOC0311_2
NOTE:
You cannot interchange these DDDT types in your applications:
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 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.).
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:
-
Read the status of connections and communications between the Ethernet communication module and distributed EtherNet/IP and Modbus TCP devices:
-
The status is displayed in the form of a HEALTH_BITS array consisting of 32 bytes.
-
A bit value of 0 indicates the connection is lost or the communication module can no longer communicate with the distributed device.
-
Toggle a connection ON (1) or OFF (0) by writing to a selected bit in a 16-word DIO_CONTROL array
-
Monitor the value of local slave and distributed device input and output items that you created in Control Expert.
Displaying the Order of Input and Output Items
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:
NOTE 2: Device variables are in this format:
NOTE 3: Local slave variables are in this format:
|