Mounting the Board
...
To mount the SNIB3 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. |
Setting the Board’s DIP Switches
Before installing the SNIB3, you must first set the required DIP switches on the three switch banks:
...
Baud rates only apply to the SNIB3’s RS-485 port. The SNIB3’s Ethernet port is used for host-to controller connections and runs at 10/100/1000 BaseT speeds. All SNIB2s and SNIB3s in a mixed RS-485 multi-drop sequence must be set to the same speed. For example, if one SNIB2 in a mixed sequence is set to 9600, all other SNIB2s and SNIB3s must be set to the same baud rate.
CCM and SNIB3 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.
...
If you have a combination of SNIB2 and SNIB3 you must make sure all SNIB3 controllers are connected first on the RS-485 drop. You cannot go from a SNIB3 to a SNIB2 and then to another SNIB3. Furthermore, your Port Settings within Velocity must be set to XNET2 when a SNIB2 is in the downstream line.
Firmware Download Rules
When CCM Firmware starts to download, Velocity splits the firmware file into multiple smaller segments and send it to SNIB3, 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 SNIB3 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 to 10 minutes and the controller is back on-line.
Wiring the Board
To connect RS-485 serial cables between SNIB3s:
...