Mounting the Board

To mount the SNIB2 expansion board:

1. Turn all system power off: remove the connector for the standby battery, disconnect the AC power connector or the power supply fuse.

2. Install the new SNIB2 board into the upper left corner of the enclosure using the supplied screws. If there are additional expansion boards to install, install them first using the supplied standoffs. Install the SNIB2 board last so that it is at the top of the stack.

3. Connect the EBIC5 connector. Reconnect the AC power connector (or power supply fuse), then reconnect the standby battery connector. The controller board's yellow test LED should light; the other lights go through a start up sequence. When the sequence is complete, the yellow test LED goes out and the other lights stabilize.

4. If required, connect an RJ-45 network cable to the SNIB2 Ethernet connector.
   

   

5. If you stack boards, make sure the SNIB2 is on top of the stack

Wiring the Board

To connect RS-485 serial cables between SNIB2s:

1. Turn all system power off by first removing the connector for the standby battery, then disconnect the AC power connector or the power supply fuse.

2. Punch out the knockout in the controller enclosure where you plan to route the RS-485 cable. You can either route this wire through the same opening you’re using for controller board connections, or knock out a new opening.

3. Route the wires through the opening. If it makes serial wiring easier, detach each green connector from the board as needed.

4. Loosen the screws on each RS-485 connector plug you will be using.

5. Remove insulation from the wire and insert the specified wires into the green connectors at the required slots as shown to the right.
   

   

6. Tighten the screws until the wire is securely fastened in the slot.

7. If you removed the green connector in step 3, push the green connector into the appropriate socket until it locks into place. The connector and socket are keyed, so there is only one way to plug it in.

8. Reconnect the system power by first connecting the AC power connector, then connecting the standby battery connector.
   

   

Standard Cable: SNIB2 RS-485 installations with standard 18-, 20-, and 22-gauge shielded twisted-pair cable should use 9600 or 38400 bps. Do not use higher speeds. If you have communication problems at 38400 bps, reduce it to 9600 bps. Installations with NET*MUX4s are limited to 9600 bps.

Cat5 Cable: For new SNIB2-to-SNIB2 RS-485 installations, we recommend making your cables with Cat5 or equivalent grade cable to the appropriate 5-pin green connectors. Pick one color wire, such as brown, to use for Ground. Distances up to 4000 feet can be achieved with this RS-485 cabling type. If there is no NET*MUX4 involved, you can use 57600 or 115200 bps.

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:

This controls the baud rate for the RS-485 multi-drop line and the RS-232 connection. 57600 and 115200 bps are only available if your RS-485 cables are made from Cat5/Cat6 data grade wire. These speeds are not recommended for installations using:

• RS-232 connections to host

• 18- to 22-gauge shielded twisted-pair cable

• NET*MUX4s

• Mixed SNIBs/SNIB2s

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

• When upgrading a group of controllers which all utilize the SNIB2, the primary SNIB2 should always be upgraded first, then proceeding to the downstream controllers in order (i.e. primary controller, 1st downstream controller, 2nd downstream controller, etc.) until the entire group has been upgraded

• 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.