Mounting the Board
...
To mount the SNIB2 expansion board:
...
| Note |
|---|
If a MEB/BE, MEB/CE, or MEB/CB board is installed, do not remove it. Removing any of these boards will cause the controller to malfunction and requires a system cold start. This will erase all additional information in their memory and requires complete system download. |
Wiring the Board
To connect RS-485 serial cables between SNIB2s:
...
In order to use the SNIB2, your controller must include CCM Vn. 7.3.08 or higher. Use Vn. 7.4.02 or higher if your computer has Velocity 3.0.
Setting up the Board
Before you can install the SNIB2, you must first set the required DIP switches on the three switch banks as shown below:
...
Baud rates only apply to the SNIB2's RS-485 and RS-232 ports. The SNIB2's Ethernet port is used for host-to-controller connections and runs at 10/100 BaseT speeds. All SNIBs/SNIB2s in an RS-485 multi-drop sequence must be set to the same speed, and if connected to a host PC using RS-232 direct connection, the same speed must also be used. For example, if one SNIB2 in the sequence is set to 9600, all other SNIBs and SNIB2s (and the RS-232 host connection, if used) must be set to the same baud rate.
CCM and SNIB2 Firmware Upgrade Path
Identiv recommends that a single CCM be upgraded at a time. Though, Velocity software supports the firmware upgrade of multiple CCM boards, but this should never exceed 5 controllers at a time, possibly less depending on the system topology
Never upgrade the master controller at the same time as any downstream controllers
Additional considerations should be made for upgrades to downstream controllers, as these are communicating via RS-485 which is a slower communication protocol than TCP/IP. The default baud rate for downstream communication is 9600 baud, though this can be increased but should only be done when using data grade wiring between controllers
...
While it is acceptable to upgrade multiple downstream devices simultaneously, never attempt to upgrade the master and downstream SNIB2 devices at same time. Keep in mind that updating multiple downstream devices should consider the communication constraints mentioned above.
Firmware Downloads
When CCM Firmware starts to download, Velocity splits the firmware file into multiple smaller segments and send it to SNIB2, this phase will take about 5 to 6 minutes. During this phase, the controller will remain fully functional.
After the file transfer is completed, the SNIB2 starts sending the updated packets to the CCM, at this point the controller logs off and becomes inoperative. The complete flashing and reboot process take about 8 minutes to 10 minutes and the controller is back on-line.
...