Viper SC+™ IP Router for Licensed Spectrum PN 001-5008-000 Rev. C
| Page 126
4.9.2.
PACKAGE CONTROL
Package Control is the second (middle) tab of the Device Maintenance page. To navigate to this tab, select Device
Maintenance from the main navigation menu and click Package Control. From this tab you can view information about
installed firmware for the Modem and Radio and upgrade the Radio Firmware if necessary.
Package control is used for verifying a field upgrade of the Viper radio modem firmware. If the installation was
successful, the web page will display PASS. If the installation is incomplete or some files are corrupt, the web page will
display FAIL and will give an error message specifying which files are missing or corrupt.
If an upgrade problem arises and persists, click the Package Control once more and have the resulting messages
available when contacting CalAmp technical support.
Figure 74 – Device Management – Package Control
More information about using the Package Control tab for upgrading firmware is provided in Chapter 7. Upgrading
Firmware, which follows.
4.9.3.
WING COMMANDER
Wing Commander is the third (right-most) tab of the Device Maintenance page. To navigate to this tab, select Device
Maintenance from the main navigation menu and click Wing Commander. In this tab, you can configure Security and
other settings for the Wing Commander Protocol (WCP).
While the Viper can be upgraded locally or over-the-air in a one-to-one fashion using the standard FTP protocol, the
CalAmp Wing Commander Protocol (WCP) allows a DeviceOutlook™ server to efficiently and reliably upgrade a field of
Vipers OTA (over-the-air) in a one-to-many fashion using multicast UDP/IP.
Viper uses the Wing Commander protocol for communication with DeviceOutlook, which is CalAmp’s Device Manager.
DeviceOutlook allows for upgrading Viper firmware from a remote server. For a complete description of how to use
these settings, consult the WCP Client User Guide, the DeviceOutlook User Guide, and other related documents from
the CalAmp support website,
http://www.calamp.com/product-support
A typical upgrade scenario using DeviceOutlook is as follows. The DeviceOutlook server splits the firmware upgrade
archive into small numbered blocks, which it then multicasts to the Vipers. The DeviceOutlook server next polls the
Viper units to assess which blocks need to be re-sent. The Viper stores the received blocks in non-volatile memory as
they are received, maintaining the proper logical order even for blocks received out of order. When DeviceOutlook
establishes that the prescribed number of Vipers in the deployment have received all the blocks, it directs the Vipers to
install the image received and perform a station reset. As a last step, DeviceOutlook verifies that all Vipers have
successfully applied the firmware upgrade.