Long term tracking across large areas requires monitoring as to how the devices are functioning especially battery powered assets.
For example; knowing that your device will experience low coverage situations and planning for these in advance could save you months of battery life.
With powered devices, being able to monitor the data coming out of the unit could alert you to wiring issues, extreme temperatures, and faults with the device.
|OEM System Parameters||Telematics Guru monitoring|
OEM Server Device Counters
You can access the device counters in OEM for an individual device by entering the device number in oemserver.com/Device and selecting 'Details'
In this menu, you can see details for the individual device statistics such as battery life, and total times spent doing different processes.
If you find you have high ratio of failed GPS fixes to successful, or failed uploads to successful, you may have to look at widening your parameters to enable the device to gain a fix or complete an upload.
Oyster 2 - Device Counters
1. Current Battery Percentage
2. Failed Action Times
-Failed GPS fix Time
-Failed Upload Time
3. Maximum Temperature measured
4. Currently Uptime of unit
If you're using Telematics Guru, this data is also projected into the Battery Management Page under Assets > Battery Management
More information on battery management page here
OEM Server parameters
For a more indepth discussion on GPS debugging, see our knowledge base article - 'GPS Troubleshooting'
For more information on Upload timeout debugging, see our knowledge base article - 'Cellular battery powered Timeouts'
Telematics Guru Device Monitoring
- If straight after the ignition goes off, external power goes. Means the power is not a constant source and is only on when the engine is on.
- If the device is permanently in trip with the ignition on, IGN has been wired to constant power.
Manage Asset > Telemetry IO
1) The external power wired to a non-permanent source. This is shown below and is consistent with the external voltage(V) reporting zero when the trip ends. This can be due to a wiring issue, or an isolation switch is in relay
2) Battery flat & External power not wired to constant source. This is shown by having only trip logs in the telemetry, and no heartbeat logs. Telemetry usually ends with 'Digital input changed' or 'End of Trip' log reasons, commonly during the middle of the day or end of work time periods.
Manage Asset > Telemetry
3) Loss of Cellular reception. Aside from Analogue 4's values which can sometimes be confusing, you can tell a device has lost reception at a point, then back-filled the records when the unit has reconnected by seeing a 'Transmission delay' record.
For more information on cellular reception troubleshooting, click here for our main knowledge base article
Reports > Analogue Mapping Report
4) Another way to see external voltage issues is to run an Analogue Mapping Report. By selecting one or multiple analogues out of Battery Voltage, External voltage, Temperature or GSM reception, you can determine if the issue is a systemic one, or a situational one.
Reports > Devices not Connecting Report
Under Support Reports in Telematics Guru is a helpful report that you can schedule to run every 24 hours to notify you of any devices that have no connected and committed data in the last X hours.