Future Design MCT-CM, User Manual

Page: 33 / 247

MCT-CM
33
3.4.1.2 US2000B Communication Module to Loop Controls
Communications Wiring Example (FDC-9300 controller shown)
3.4.2 Assigning the Proper Communications Settings
The MCT-CM can support up to ten C-Series R22 controls or up to ten FDC 300 Series controls depending
upon the firmware version installed in the CM. Each loop control must have its own communication address.
The allowable address range is 1
– 10 corresponding to Loop Input #1 – 10 in the MCT Configurator.
Communication addresses must be assigned to all controls on the communications link beginning with 1, up to
the total number of controls.
As control loops are enabled in the MCT Configurator, the MCT will automatically use the Loop Input # as the
corresponding controller address. If more than one loop control has the same address, or a loop input is
enabled but a control is not assigned to that address, the MCT will report a communications alarm for that loop
input when the runtime application is started.
NOTE: The order of the loop controls on the communication link is not important. The communications
address for a control can be assigned regardless of its position on the link.
In addition to the communications address, the baud rate, data bits, stop bits and parity settings must also be
set to match the control module of the MCT. The MCT control module uses the factory default communication
rate of 9600 baud, 8 data bits and 1 stop bit; however, the parity of the C-Series R22 or FDC 300 Series control
must be changed from the factory default of “even” to “none”.