Issue
When using the Modbus RTU and Modbus IP X Drivers it is important to determine which controller and port can support the electrical standards used by the 3rd party device.
Product Line
Andover Continuum
Environment
Continuum Netcontroller II and bCX1 controllers that have been X Driver enabled.
XDriver, Modbus RTU, IP, Infilink, Infilink200, B-Link. RS-232, RS-485
JBUS
Cause
Controller ports and 3rd party devices come in various electrical standards (RS-232, RS-485, RS-422), which ports support the various standards?
Resolution
There are two Continuum Modbus X Drivers:
Modbus RTU: This allows the connection of 3rd party Modbus RTU slaves via the serial data RS-232, RS-485 or RS-422 electrical standards. RS-232 is a point to point connection to 1 device, RS-485 & RS-422 support a bus topology for connection of multiple 3rd party devices.
The Continuum controller will be the Modbus RTU Master and will poll the 3rd party device that must be a slave.
The bCX1-CR controllers have 2 ports that can be configured for Modbus:
Comm1 RS-232
Comm2 RS-232 or RS-485 port
The Netcontroller II controllers support:
Comm1 - RS-232 or RS-485
Comm2 - RS-485
Comm3 - RS-232
Comm4 - RS-422
The ACX57xx controllers support:
Comm1 - RS-485
Notes
An Infilink200 or B-Link may be used to convert RS-232 to RS-485 if required.
The J Bus protocol is a subset of the Modbus protocol and so the Modbus XDriver is used for J Bus Systems.
Modbus IP: The bCX1, ACX57xx and the Netcontroller II all support the Modbus IP protocol that connect via the Ethernet IP connection. This XDriver can be configured to support either Client or Server modes. Although the communication is physically via the Ethernet port, one of the Serial ports is required to be X Driver enabled to load the software, this serial port is then no longer available for other purposes.
This XDriver requires Ethernet X Driver support to be enabled on the port.
