A functioning TB20 configuration will always require a bus coupler and at least one peripheral module.
The DeviceNet Slave bus coupler connects the DeviceNet bus to peripheral modules. As a group 2 server, the coupler supports the “Predefined Master/Slave Connection Set” in accordance with sections 3-6 of the “CIP Networks Library Vol. 3.” In addition, the slave software, with the help of an “Unconnected Message Manager“ (UCMM), enables the dynamic setting up of multiple communications channels.
You can also choose from various combination possibilities for your I/O data and three kinds of DeviceNet connections: “Polled-I/O”, “Bit-Strobed-I/O,” and “COS/Cyclic-I/O.“ It is also equipped with a 2 kByte I/O data image table.
It recognizes all connected peripheral modules and assigns each module the inputs/outputs from the process image table.
Thanks to the TB20-ToolBox, it is easy to configure the system and the various module parameters and transfer them to the coupler.
A functioning TB20 configuration will always require a bus coupler and at least one peripheral module. The bus coupler supports hot-swapping for replacing modules during operation.