Vehicle Moving but Distance Not Recorded

In some cases, a vehicle may be moving but the distance covered is not recorded in the platform. This can occur when the device is not providing the required ignition or movement data, when the ignition port configuration is incorrect, or when no device data is being received.

Example Questions

• • Why is distance not recorded even though the vehicle is moving?
  • Why is the distance showing as zero in the report?
  • Why is distance data missing for a vehicle?
  • Can an ignition port issue affect distance calculation?
  • What should I check when no distance is recorded?

Symptoms / How to Identify

• Vehicle is physically moving, but distance is not recorded.
• Distance may show as zero or remain unchanged.
• Ignition data may be incorrect or unavailable.
• Device may have stopped sending data.
• Distance may work correctly after removing or correcting an incorrect ignition port configuration.

Information Required Before Troubleshooting

• Vehicle/Object name.
• Device/IMEI details.
• Date and time of the issue.
• Distance report or relevant report screenshot.
• Device raw data/logs.
• Ignition port configuration.
• Ignition wire connection, if applicable.

Troubleshooting Steps

1. Check whether the device is sending data to the platform for the affected period.
2. Verify whether distance data is being received/calculated correctly.
3. Check the device's ignition data and confirm that it is stable.
4. Verify the configured Ignition Port for the device.
5. If an incorrect or problematic ignition port is configured, remove or correct the ignition port configuration and verify the distance again.
6. Check the physical ignition wire connection at the device/hardware level.
7. If no device data is being received, investigate the device's communication, SIM, and network connectivity.
8. Once the device is sending the required data correctly, verify the distance in the relevant report.

Possible Cause

• Incorrect ignition port configuration.
• Ignition wire or connection issue.
• Unstable or incorrect ignition data.
• Device not transmitting data to the platform.
• Required movement/vehicle data is not being received for distance calculation.

Resolution / Action

First verify device communication and ignition data. If the issue is caused by an incorrect ignition port configuration, correct or remove the configuration and verify the distance calculation again.

If an ignition wire is connected, verify its physical connection at the device end.

If no data is being received from the device, resolve the device communication/network issue first. After the device starts transmitting valid data, recheck the distance report.