Why are the running hours shown in the report incorrect?

Issue Title

Incorrect running hours

Issue Summary

Running hours may be incorrect when the device sends an incorrect ignition or engine-status value, the required data is missing or delayed, or the system calculates running hours using incorrect configuration or parameters. This can cause the reported running time to be higher or lower than the actual engine operating time.

Symptoms / How to Identify

Reported running hours do not match the actual engine operating time.
Running hours are higher or lower than expected.
Running hours are shown even when the vehicle engine was OFF.
Running hours are missing when the engine was running.
Running hours differ between reports or system modules.
Running hours increase unexpectedly while the vehicle is stationary.
The report shows unusually long or short running periods.

Information Required Before Troubleshooting

Vehicle/Object name or ID
Device IMEI/Serial Number
Device model and protocol
Report name
Date and time range
Running hours shown in the report
Expected/actual running hours
Ignition/engine status
Relevant Status/Raw Data
Device configuration
Report filters and calculation settings
Screenshot or exported report
Whether the issue affects one vehicle or multiple vehicles

Troubleshooting Steps

Check on Device

Verify the actual engine ON/OFF status during the affected period.
Check the ignition/engine status generated by the device.
Verify whether the ignition status changes correctly when the engine is turned ON and OFF.
Check the relevant ignition or engine-hours parameter in the device data.
Verify the device's ignition wiring or engine-status input, if applicable.
Check for missing, delayed, or duplicate ignition data.
Verify device configuration and transmission settings related to ignition or engine status.

Check in System

Verify the report's date, time range, vehicle, and filters.
Open Status/Raw Data and review ignition/engine-status data for the affected period.
Compare the device's ignition data with the running hours shown in the report.
Check the vehicle's history or trip data for the same period.
Verify the system's running-hours calculation method.
Check the configured ignition/engine parameter mapping.
Verify timezone and date-boundary settings.
Compare running hours across other relevant reports or system modules.

Compare and Identify

Incorrect ignition/engine status from the device: Investigate device wiring, sensor, configuration, or hardware.
Correct device data but incorrect running-hour calculation: Investigate system calculation or parameter mapping.
Missing ignition data: Investigate device transmission or network connectivity.
Different values across reports: Verify report calculation methods, filters, and time ranges.

Possible Causes

Incorrect ignition status.
Incorrect ignition wiring.
Faulty ignition input or sensor.
Incorrect device configuration.
Missing or delayed ignition data.
Incorrect engine-hours parameter.
Incorrect parameter mapping.
Incorrect report calculation method.
Timezone or date/time configuration issue.
Device firmware or protocol issue.
System-side calculation issue.

Resolution / Action

Compare the actual engine status, device ignition data, system raw data, and report running hours for the same time period.

If the device is generating incorrect ignition/engine data, investigate the device, wiring, sensor, or configuration. If the device data is correct but the report calculates incorrect running hours, verify the system calculation and parameter mapping and escalate to the technical/system team if required.

For escalation, provide the vehicle ID, IMEI, report name, date/time range, actual running hours, reported running hours, ignition data, configuration, and relevant raw data.