Skip to main content
All CollectionsKnowledge Articles (External support work base)Software solutions
How to fix problem with jumps in values for mileage, fuel consumption (from on-Board computer)
How to fix problem with jumps in values for mileage, fuel consumption (from on-Board computer)
Albert Basiul avatar
Written by Albert Basiul
Updated over 7 months ago

Description

There may be cases where TrustTrack shows very high fuel consumption or mileage values (which actually weren't there) in a short period of time. This may be due to erroneous mileage or fuel consumption values received from the on-board computer.

Below are the most effective ways to check and fix the problem:

Steps:

1 - Check in the history menu the consumption in liters and mileage in kilometers to see if the displayed value could be correct.

In our case, the photo shows an example with the correct mileage, but with a significantly overestimated fuel consumption.

Pic1.png




2 - To check the possible reasons and to choose a solution to the problem, you need to open the object settings in the LCM (admin panel), click objects --> view / edit --> activate the display of the checked parameters and click on the "save" button as in the attached photos.

Pic2.png
mceclip6.png
mceclip8.png




3 - Log in to the account of the web user being checked and select the desired object by opening its history --> analysis by coordinates --> click on the button indicated in the photo to activate the display of the required parameters in the table and on the graph.

Pic3.png
Pic4.png




4 - Find the moment where, in the absence of movement according to GPS coordinates and speed, the "fuel used" fuel consumption values ​​change significantly (similarly, in some situations, the "mileage" value may change, which will look similar to the same "jump on the graph").

Pic5.png




5 - If the value of fuel consumption (or mileage in similar situations) returned to the previous values ​​after some time, then you can apply a filter in the object settings (!) by setting the Min - Max values ​​in such a way that it filters out an erroneous value. So it's better to set the limit similar to the value in the photo

Value should be more wrong value:
197042*0.5 = ~100,000

But less correct value:
266819*0.5 = 133409

In our case:
-125000

Pic6.png
Pic7.png
Pic8.png



A similar way of solving the problem with "jumping" values ​​works for "mileage" as well.


6 - Also, one of the solutions to the problem with jumps in fuel consumption would be to use the Canbus HRFC ("CAN high resolution engine total fuel used") parameter. At the same time, a prerequisite for applying this method will be reading and changing this parameter and the absence of "jumps" as you can see on the graph.

mceclip3.png
mceclip4.png


To apply this method, you can select for fuel consumption in "Custom input 13 / Fuel Consumption " --> "CAN high resolution engine total fuel used" --- while setting the necessary constants as shown in the photo below (after setting, saving all changes by clicking the "save" button.

mceclip12.png




7 - After that, you can recalculate the accumulated history for a period not exceeding 3 months* (*currently this is the limit for recalculation).

Pic9.png



After such actions the problem should be resolved and you can double-check it .
You can see the correct values:

Pic10.png
Did this answer your question?