User's Guide

Model: VSM3

Positioning Universal, Inc. - Confidential & Proprietary

7 Detailed Reset Logic

7.1 Device Reboot

Cold Boot

Any time there is a physical power up event the device checks the status of the Cold Boot

Settings parameter and sends a Cold Boot message, a GPS Acquired message, and a Stop

message at the appropriate time if they have been specified.

Warm Boot

Any time there is a warm boot event the device checks the status of the Warm Boot

Settings parameter and sends a Warm Boot message, a GPS Acquired message, and a

Stop message at the appropriate time if they have been specified.

Periodic Reboot

Based on a parameter, the device can be set to perform a reboot periodically to address

any unhandled issues that may arise in the device.

Watchdog Reboot

If the microprocessor hasn’t been able to reach processor idle loop for 20 seconds then

the unit is automatically rebooted. This is to stop any endlessly running loop from

hanging the unit. This reboot is reported as a Cold Boot and is treated as a Cold Boot

from the point of view of Boot Settings.

Update Reboot

Every time the device has its application or settings file updated, the device is rebooted.

Also if the device times out during update it will reboot. This reboot appears on server as

a Cold Boot and is treated as a Cold Boot from the point of view of Boot Settings.

7.2 Comm Module Reset

There are a number of conditions which trigger the comm module be reset.

No ACK Reset

If a message has been sent requiring an ack then a timer is set. If no ack is received

before the timer then the module will be reset. This logic is intended to cause the comm

module to be reset if it is locked up but still reporting some kind of comm update.

No Comm Available Reset

If the module has not reported that it is available for comm within the time specified then

the module will be reset.