ComAp Inteli Mains NT BaseBox, Communications Manual

Page: 70 / 152

IGS-NT Communication Guide
70
Connection of I-LB+ or other bridging modules
Note: If I-LB+ (or other bridging module) is to monitor all the site, it is recommended to place it at the position 1.
If there is preferably monitored one group (within one switchboard) and the other controllers not at all or only
seldom, option 2 is more suitable. Remote connection to let’s say controller 7 is possible in this case but data
transfer will be quite slow.
5.5 I-CR-R module properties
5.5.1 I-CR-R module functions
Intercontroller CAN bus redundancy – basic description of terminology used:
Local CAN bus – a bus going from the module to the local controller(s) = within one switchboard; name
on the sticker CAN1 CONTROLLER; in standard installation (with no redundancy) this would be the
intercontroller bus (CAN2)
Primary intercontroller CAN bus – a bus interconnecting all I-CR-R modules and providing 1 to 1
replacement of standard intercontroller CAN bus (CAN2); name on the sticker CAN EMS
Backup intercontroller RS485 bus – secondary bus interconnecting all I-CR-R modules; transmits only
intercontroller communication (Load Sharing, VAr Sharing, Power Management), not the remote
communication (I-LB, IG-IB connection to a PC monitoring tool); controller with address 1 must be
presented in the system to make backup bus working
The module preferably uses the Primary CAN bus line for data transfer. However, if the connection from any
of the controllers connected to other I-CR-R modules is broken the module automatically re-routes it to the
Backup RS485 line and continues in operation. From controllers’ point of view, no data transfer interruption
is observed.
It is possible to indicate the problem with Primary or Backup buses using “fake” SHBOUT6 message which
is normally used for signal sharing among the controllers. See jumper description further in the text.