On Board Run Hours for Digital Inputs - G70-4G
Table of Contents
Applies to:
Device | Firmware Version |
G70-4G | v1.17+ |
The G70-4G the capability to accumulate run hours and odometer readings on-board based on the Ignition input (see On Device Odometer and Run Hours).
Also, it can accumulate run hours onboard based on any Digital Input. This is useful to understand the usage of peripherals such as pumps.
Many platforms calculate this server-side based on device data (including Telematics Guru - Setting up Secondary Run Hours), so it is not always necessary to configure this feature in order to track run hours.
However, you can use this feature if your platform can not process the raw values server-side.
The On Device Run Hours feature is configured using the “Odometer" Advanced System Parameter tab and sends data in Field 27 of the integration payload.
This On-Board Run Hours for Digital inputs feature is configured using the “Run hour” Advanced System Parameter tab. The device sends data in the Analogue Data Fields (6 for INT16 and 7 for INT32) of the integration payload. This is great as most platforms can easily ingest data sent in Analogue Data Fields.
Configuration
Add the Run hour Tab and configure the desired behaviour.
Parameter | Function |
---|---|
Run Time X Digital Input | To select which Digital Input we want to monitor |
Run Time X Analogue Input | The accumulated Run hour data for the selected Digital Input will be sent in this Analogue Input field. |
Run Time X Active Level | To select which active level of the Digital Input we want to monitor |
Setting Initial Values using ASYNC Message
The device's run hour readings 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 values are stored in non-volatile memory. This means that even if the device loses power or otherwise resets, they are preserved. The values won't become inaccurate if the device ever resets.