Page
22
of
32
Updating Firmware
1. If not already connected, repeat steps 1 to 5 in section
2;
2. Click on the Manage Device tab;
3. Select the device from the drop down menu;
4. Click on the Update Firmware group below;
5. Follow the instructions displayed on the Syrinix Device Manager; NOTE: The RED heartbeat light must
come on. When asked, select the
xxxxxx_PMS.bin
which was downloaded in step 8 of section 2.
Updating configuration
The updated firmware requires the new configuration file which you should have downloaded from
RADAR.
1. If not already connected, repeat steps 1 to 5 in section 2;
2. Click on the Manage Device tab;
3. Select the device from the drop down menu;
4. Click on the Update Configuration group;
5. Click Update Configuration;
6. Select the updated mission file and click open;
7. A box confirming the application of the mission file should appear
Re-deploy
1. Follow the instruction in the manual for deployment up to the point where the GPS lock is achieved.
2. If updating from software versions prior to 100648 the device will re-initialise the file system on start-
up. This process takes around 20 minutes and the device will display progress. This only happens on the
first start-up following a software update.
3. Complete the deployment process
6.13
Battery Life
Battery life is designed to meet 12
–
18 months based on an ambient temperature of 20°C, a combined signal
quality score (CSQ) of 8 and standard operating use transmitting summary data and 3 transients per day (3
minute events).
The device can be configured to set the
number of “event” and “daily log” retries should communication fail
on the first attempt. This will shorten the life of the battery and is therefore the utilities decision of data
availability versus battery performance. Please note that, setting a high level of resends, or requesting a very
sensitive level of transient alert communications will negatively impact battery life. The S3 sensitivity score
should be configured by the utility once the unit has been installed for a few days and the background S3 score
has been evaluated. Setting the S3 score too low may result in transients being continuously detected and
transmitted resulting in a significant reduction in battery life.
