Fuel Consumption and Distance Data Issues

Fuel consumption and distance values may be missing or incorrect when the required data has not been received from the device, an expected event has not been captured, or the ignition port is not functioning correctly.

Before reporting these discrepancies as platform issues, users should complete the initial verification of device data, event records, ignition status, and fuel sensor readings. These checks help identify whether the issue originates from missing input data, device configuration, or platform processing.

Example Questions

• • Why is fuel consumption not showing for a vehicle?
  • Why is distance missing even though the vehicle has travelled?
  • Why has a fuel-related event not been captured?
  • Why is the expected event not triggering?
  • Why is no fuel data being received from the device?
  • Can a faulty ignition port affect distance calculation?
  • What should be checked before escalating a fuel consumption issue?
  • Why does the platform show no consumption when the vehicle has completed trips?
  • How can I determine whether a discrepancy is caused by missing device data or a platform issue?
  • What initial verification steps should be completed before raising a support ticket?

Symptoms / How to Identify

• Fuel consumption is missing because the expected event was not captured.
• Distance is not displayed because the ignition port is not functioning correctly.
• An expected fuel-related event has not been triggered.
• No fuel sensor data has been received from the device.
• Fuel consumption or distance values are reported as incorrect without verification of the underlying device data.

Information Required Before Troubleshooting

Collect the following information before escalating the issue:

• Vehicle number or object details.
• Device model and configuration, where available.
• Affected date and time range.
• Fuel consumption and distance values displayed in the platform.
• Relevant System Log or raw device data.
• Confirmation of whether fuel data is being received.
• Confirmation of whether the expected event has been captured.
• Ignition port status and relevant device configuration.
• Screenshots or report extracts showing the discrepancy.

Troubleshooting Steps

Step 1: Verify whether device data is being received

Check the available logs or raw data for the affected vehicle and period.

• If no fuel data is received, investigate the device's fuel data input and configuration.
• If data is being received, proceed to verify the expected events and calculations.

Step 2: Check whether the expected event was captured

Review the event records to confirm whether the event required for the relevant fuel calculation was received or recorded.

If the event was not captured, investigate the event data and device-side configuration before concluding that the platform calculation is incorrect.

Step 3: Verify the ignition port

If distance is missing, check whether the ignition port is functioning and whether the relevant ignition data is being received correctly.

A malfunctioning ignition port may affect distance-related data, depending on the configured calculation logic.

Step 4: Verify fuel sensor data

Confirm that fuel readings are being received from the device. If no fuel data is available, investigate the sensor, wiring, device configuration, and incoming data as applicable.

Step 5: Review the calculation inputs

Once the required data and events are confirmed, review the relevant fuel consumption and distance calculations. Ensure that the report selected matches the vehicle's fuel monitoring configuration.

Step 6: Escalate with verified evidence

If all initial checks are complete and the discrepancy persists, share the affected vehicle details, logs, event records, and screenshots with the technical team for further investigation.

Possible Cause

Fuel consumption or distance discrepancies may occur due to one or more of the following:

• The required event was not captured.
• The ignition port is not functioning correctly.
• The expected event was not triggered.
• Fuel data was not received from the device.
• The initial verification of device data and event records was not completed before escalation.

Resolution / Action

Complete the initial verification steps before raising a platform-related issue.

1. Confirm that the device is transmitting the required data.
2. Verify that the expected events are captured.
3. Check the ignition port if distance data is missing.
4. Confirm that fuel sensor readings are being received.
5. Review the relevant calculation inputs and report configuration.
6. Escalate unresolved discrepancies with supporting logs and screenshots.

If further clarification is required, arrange a training session to explain the platform's fuel consumption and distance calculation logic.