Fuel Fill or Drain Event Not Recorded in the Fuel Fill/Drain Report

Fuel Fill or Drain events may not appear in the Fuel Fill/Drain Report even when the fuel level changes on the graph. This can happen when the fuel calibration parameters do not match the vehicle's actual fuel behavior or when sensor fluctuations are incorrectly identified as fuel events.

Common configuration factors include Fill Difference, Drain Difference, Fill/Drain Speed Threshold, Consecutive Fill/Drain Duration, Data Filtration Level, Detect Drain in Motion, Consider Stop Data, and Consider Power Port.

The calibration should be configured to detect genuine fuel events while avoiding false events caused by normal sensor fluctuations.

Example Questions

• • Why is a fuel refill not showing in the report?
  • Why is a fuel drain not being detected?
  • Why is the fuel level changing on the graph but no Fill/Drain event is generated?
  • Why are some refill events being ignored?
  • Why are false refill events being generated?
  • Why does reducing the Fill Difference generate too many false events?
  • What is the purpose of Fill Difference?
  • What is the purpose of Drain Difference?
  • Why is Fill Speed Threshold preventing refills from being detected?
  • How can I detect small refills while avoiding false events?
  • Why is fuel drain while the vehicle is moving not being detected?
  • How should the fuel filtration level be configured?

Symptoms / How to Identify

• Fuel level changes are visible on the fuel graph, but no corresponding Fill/Drain event appears in the report.
• Genuine refill events are being ignored.
• False refill or drain events are being generated due to fuel-level oscillations.
• Small refills are not being detected.
• Drain events occurring while the vehicle is moving are not detected.
• Fuel events are affected by vehicle stop/power conditions.
• Changing the Fill Difference alone does not resolve the issue.

Information Required Before Troubleshooting

Collect the following information:

• Vehicle/Object name.
• Device/IMEI details.
• Date and approximate time of the expected Fill/Drain event.
• Fuel graph for the affected period.
• Fuel Fill/Drain Report.
• Fuel calibration settings.
• Fill Difference
• Drain Difference
• Fill Speed Threshold
• Drain Speed Threshold, if applicable
• Consecutive Fill Duration
• Consecutive Drain Duration
• Data Filtration Level
• Detect Drain in Motion
• Consider Stop Data
• Consider Power Port
• Distance-based and Duration-based Fuel Consumption settings, where applicable.
• Raw fuel data from the device, if required.

Troubleshooting Steps

1. Verify the Fuel Graph

Check the fuel graph for the period when the Fill/Drain event was expected.

• Confirm whether the fuel level actually increased or decreased.
• Check whether the change is a genuine fuel event or normal sensor fluctuation.
• Note the approximate amount and duration of the fuel-level change.

Important: A fuel-level change on the graph does not automatically mean that the platform will generate a Fill/Drain event. The change must satisfy the configured detection conditions.

2. Check Fill Difference

Fill Difference defines the fuel-level increase required for the system to recognize a refill.

• If the value is too high, smaller genuine refills may be ignored.
• If the value is too low, normal sensor fluctuations may be detected as refills.
• Configure the value according to the minimum genuine refill quantity that needs to be detected.

For example, if the client needs the system to detect refills of 10 litres, the calibration should be tested against an actual 10-litre refill rather than simply increasing the threshold to eliminate false events.

3. Check Drain Difference

Drain Difference defines the fuel-level decrease required for the system to recognize a drain event.

• If the value is too high, genuine smaller drains may be ignored.
• If it is too low, normal fuel fluctuations may be detected as drains.
• Configure it according to the actual fuel sensor behavior and required detection level.

4. Check Fill/Drain Speed Threshold

Verify whether a Fill Speed Threshold or applicable drain speed threshold is configured.

A restrictive speed threshold can cause legitimate fuel events to be ignored.

Check whether:

• The actual refueling speed falls within the configured range.
• The threshold is suitable for the vehicle and fuel sensor.
• Genuine refill events are being filtered out because of the configured threshold.

If the threshold is found to be preventing valid events, adjust or disable it based on the required fuel monitoring behavior and test with new data.

5. Check Consecutive Fill/Drain Duration

Verify the Consecutive Fill Duration and Consecutive Drain Duration.

These settings help identify continuous fuel increases or decreases as genuine Fill/Drain events.

If the duration requirement is not satisfied, the fuel change may not be recognized as an event.

6. Check Data Filtration Level

Fuel sensors can generate small fluctuations or oscillations even when no actual refueling is taking place.

The Data Filtration Level is used to process fuel data and reduce the impact of such fluctuations.

• Increase filtration when significant fluctuations are generating false events.
• Lower filtration when the fuel data is already stable and smaller genuine events need to be detected.
• After changing the filtration level, review the graph and report again.

The calibration should balance:

Detecting genuine refills/drains + eliminating false events caused by sensor fluctuations.

7. Check Detect Drain in Motion

If the fuel drain occurred while the vehicle was moving:

1. Check whether Detect Drain in Motion is enabled.
2. If it is disabled, the moving drain may be ignored.
3. Enable the option where required.
4. Verify that the required Distance-based Fuel Consumption and Duration-based Fuel Consumption settings are configured under the Profile tab.
5. Save the configuration and verify new drain events.

8. Check Consider Stop Data

Verify whether Consider Stop Data is enabled according to the required fuel calculation behavior.

This setting determines whether stopped-vehicle data is considered in fuel calculations and event detection.

9. Check Consider Power Port

Verify Consider Power Port when fuel events appear to be affected by power fluctuations or power port connection/disconnection.

Power-related changes can create fuel-level variations that may result in false Fill/Drain events.

10. Compare the Report With Raw Data

If the configuration appears correct:

• Compare the fuel graph with the Fill/Drain Report.
• Compare the event quantity with the raw fuel data received from the device.
• Verify whether the device itself is sending the expected fuel-level changes.
• If the raw data does not contain the expected change, investigate the sensor/device rather than the report.

Possible Cause

• Fill Difference is configured too high or too low.
• Drain Difference is configured incorrectly.
• Fill/Drain Speed Threshold is preventing genuine events from being detected.
• Consecutive Fill/Drain Duration requirements are not being met.
• Data Filtration Level is not suitable for the sensor behavior.
• Fuel sensor is generating normal oscillations or fluctuations.
• Detect Drain in Motion is disabled.
• Required fuel consumption configuration for Detect Drain in Motion is incomplete.
• Consider Stop Data or Consider Power Port settings are affecting event detection.
• Fuel calibration does not match the actual fuel sensor behavior.
• Device is not sending the expected fuel-level data.

Resolution / Action

Review and adjust the fuel calibration based on the actual behavior of the vehicle and fuel sensor.

The following parameters should be evaluated together:

• Fill Difference – to determine the minimum fuel increase recognized as a refill.
• Drain Difference – to determine the minimum fuel decrease recognized as a drain.
• Fill/Drain Speed Threshold – to ensure genuine events are not filtered out.
• Consecutive Fill/Drain Duration – to confirm continuous fuel changes.
• Data Filtration Level – to reduce false events caused by sensor fluctuations.
• Detect Drain in Motion – to detect drain events while the vehicle is moving.
• Consider Stop Data – according to the required calculation behavior.
• Consider Power Port – to avoid false events caused by power-related fluctuations.

After making the required changes:

1. Save the fuel calibration.
2. Allow new fuel data to be received.
3. Check the fuel graph.
4. Verify the Fill/Drain Report.
5. Compare the event with the raw device data.
6. Confirm that genuine events are detected and false events are minimized.