e. If a voice update only (audio) is being performed:
The cloud sends the new voice file to GO, the voice file is applied, then the connection is
ended by GO. If GO is used during this process it can corrupt the voice file, this could
cause audio to behave in unexpected ways, but will not affect other operations of the
device. To remedy this issue, perform the update again. Please note: the size of the
voice file is large and uses a significant amount of data when updated.
If more than one task or file update is required, then the update order is:
• Log read
• Configuration
• Cellular firmware
• Voice
• Firmware – this is always last because the reflash process requires a system reset
• 3G test signal is sent to monitoring following the reflash.
NOTE: If the firmware files are updated together, the cellular firmware update does not disconnect
GO from the cloud. This will only be done when the firmware update has been completed.
Additional Reports to Monitoring
12.1 3G Test Signals
• GO will send a 3G test signal over the cellular network at a predefined period of hours set in
the configuration file. This is typically set to 48 hours.
• When the 3G test signal is sent, GO will also perform a NITZ (Network Identity and Time Zone)
update. NITZ is the process of getting the current local time from the cellular tower.
• This time will be used to reset the system clock which is accurate within 10 minutes when
performing test signals every 48 hours. The system clock is used to determine night time hours
and the system log.
Important Note:
The user can pick up GO at any point during a cloud update and use it to send an alert. (The
cloud connection process will end automatically if either button is pressed).
WARNING - There is one exception; GO will not function for approximately 10 seconds during
the firmware reflash process. The user will need to press both buttons together after the
reflash process to send the alert.
To Next Page
Loading...
