Page Comparison

How does the CCM behave when performing a firmware upgrade through SNIBs?

SNIB - this was the initial version of the communication board.  The SNIB board does not have any firmware of its own.  When performing a CCM firmware upgrade through a SNIB, the controller will immediately go into an offline state and all doors become inoperable until the firmware upgrade completes.  This means that the controller was in an offline mode for access decisions and events during this upgrade.  In addition, the CCM flash process clears the CCM BIOS initially and then performs the upgrade.  As a result, should any issues occur during the upgrade process, the CCM could be made inoperable and require a return to the factory to be reprogrammed.

SNIB2/3 - these are the newer, upgraded versions of the communication board, with SNIB3 being the latest.   These versions introduced a different way of upgrading the CCM Firmware. When you start the CCM firmware download, Velocity will split the firmware file into multiple smaller segments and send it to SNIB2/3, this phase will take about 5 to 6 minutes. During this phase, the controller will remain fully functional. Once the file transfer is completed, the SNIB2/3 starts sending the update packets to the CCM, at this point the controller logs off and it is no longer operational. The complete flashing and reboot process will take about 8 to 10 mins and the controller will come back online.

Identiv recommends that a single CCM be upgraded at a time.  The Velocity software will support 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.  As related to the baud rate, an understanding of the wiring distance and performance limitations should be considered before making this setting change. Please contact Identiv support should you have further questions on this.