On-Device Odometer on the Remora3
Written by Matthew Clark-Massera
Updated at December 5th, 2023
Table of Contents
The Remora3 LTE-M/NB-IoT and Remora3 Global have the capability to accumulate run hours and odometer readings on board. The devices work out these values and send accumulated values to the server.
Many platforms calculate this server-side based on device data (including Telematics Guru), so it is not always necessary to configure this feature in order to track run hours or asset odometer readings.
Configuration
Turn-by-Turn Tracking
This functionality is made possible on the Remora3 due to its industry leading battery life, and Turn By Turn Tracking capability.
Digital Matter battery powered devices make use of accelerometers to detect they are on the move and increase the update rate accordingly. However for devices other than the Remora3, the device is still completely asleep most of the time - waking up on a timer (say every 3 min) to get a fix.
In contrast, if the Remora3 is set to Turn By Turn Tracking mode, while in trip it will turn on the GNSS module, leave it on, and acquire second by second fixes, incrementing the odometer as it goes.
While it's not a requirement to enable turn by turn tracking for the odometer readings, it makes sense to enable if you want a similar level of accuracy in the readings to a hard-wired device. 
Take note that the Remora3-Global does not have the ‘GPS Mode’ parameter above.
If Turn-by-Turn Trips are not configured, the odometer can still be calculated but it is calculated based upon the distance between the periodically logged points (which can still be very accurate if you log often enough!)
Enable Odometer
Ensure to update your firmware to the latest version! (1.6+ required for this feature on the Remora3 LTE-M/NB-IoT)
| Parameter | Function | Payload (for integrators) |
|---|---|---|
| Log Odometer and Run Hours | If enabled, the device will include the current odometer and run hour estimates in the end of trip device log. | Field 27 is sent with the 'End of Trip' log (Log Reason 2) Field 27 contains the asset's total Run Hour/Odo reading |
| Log Trip Distances and Lengths | If enabled, the device will include the distance travelled and time elapsed during the trip in the end of trip device log. | Field 26 is sent on the 'End of Trip' (Log Reason 2) This field gives the time and distance of the trip |
| Always Log Device Odometer and Run Hour Readings | If enabled the current odo and run hour estimates will be sent with every log. Some software platforms may require/expect the value in every log. | Field 27 is sent every log. |
| Always Log Trip Distances and Lengths | If enabled the trip distance and time elapsed estimates will be sent with every log during a trip. Some software platforms may require/expect the value in every log. | Field 26 is sent every log. |
Trip Tracking
Time and Distance readings are accumulated while the device is in trip.
The device can be set to record trips based on GPS Movement, or accelerometer activity as per Remora3 - Tracking Modes.
Setting Initial Values
Set Via SMS
| Device | Firmware Version |
|---|---|
| Remora3-Global | v1.4+ |
The following SMS Command can be used to set initial values. See this article for all SMS commands
The Digital Matter SMS App provides an alternative to using a mobile phone, and facilitates setting the ODO for many devices in bulk.
The commands are:
#*,ODO,<KMS>#*,RHOURS,<HOURS>E.g. #*,RHOURS,5200 To set 5200 hours of run-time
Set via ASYNC Message from Server
The device's odometer reading can be set via an asynchronous message sent from the server. Consult the DM WebAPI integration document for details.
What if my device resets?
The run hour and odometer values are stored in non-volatile memory. This means that if the device loses power, or otherwise resets, they are preserved - meaning the values won't become inaccurate if the device ever resets.