Fuel thefts are displayed in reports when the data received from the tracker meets all the theft detecting criteria. However, in some cases, the Fuel Thefts table doesn’t show the results, although you know for sure that fuel was stolen and can see a sharp drop in the Fuel level chart in the report. By following simple recommendations from this article, you can fix the situation and understand the logic of some fuel settings.
Possible causes and their elimination
Sometimes it will be enough to follow only one tip from the list below. More often, you will have to follow several recommendations at once. But in some cases, you won’t be able to avoid detailed analysis of all fuel level sensor settings, as well as of the features of incoming messages and parameters.
At the same time, fixing the situation with the displaying of one theft often results in the emergence of other inconsistencies in fuel reports. Thus, there should be a comprehensive approach to the fuel data analysis, considering not one theft but several at a time.
1. Theft is ignored due to smoothing
Try to reduce the filtration level in the fuel level sensor settings.
You can also try enabling adaptive median filtration.
2. Theft is filtered by volume
Try to reduce the value of the Minimum fuel theft volume option in the fuel level sensor settings.
3. Theft takes place during short stops
Try to reduce the Minimum stay timeout option to detect fuel theft in the fuel level sensor settings.
4. Theft takes place in motion
Activate the Detect fuel theft in motion option in the fuel level sensor settings if the unit was actually moving at the moment of theft. Please note that in this case, in order to display the correct result, it’s recommended to enable the Time-based calculation of thefts.
Another method is to increase the minimum moving speed on the Trip Detector tab if the speed is not related to the actual trip of the unit but is related to the error in the initial data. However, if the speed in such messages is comparable to the speed of actual trips (for example, more than 10 km/h), you can probably delete such messages, and to avoid similar situations in the future, you can try to filter them out. Please keep in mind that you will not be able to recover messages deleted manually or as a result of message validity filtration, so pay special attention to these steps.