Fleetrun
Hecterra
NimBus
Other apps
Wialon for Android/iOS
Logistics
Wialon Local
Wialon Hosting
WiaTag
Configurator
LeaseControl
en
Contents
Fuel Fillings
  • tables
  • fuel_fillings

This report table allows you to find out where and when the vehicle was refilled. The table is generated taking into account the fillings registered manually and those detected by fuel level sensors. The parameters for the report are set in the properties of fuel level sensors. If no fuel fillings are found for the indicated report interval, the table is not generated.

If you believe a fuel filling was detected by mistake, you can mark it as false and exclude it from the report.


The table can contain the columns described below.

ColumnDescription
TimeThe moment of the most significant change in the fuel level.
LocationThe location of the unit at the time of filling (if a filling is registered manually, the location of the unit is detected on the basis of the messages received at the time of filling registration).
Initial fuel levelThe fuel level before the filling.
Final fuel levelThe fuel level after the filling.
FilledThe volume of filled fuel (the name of the sensor can be indicated in parenthesis).
Registered

The volume of registered fuel.

In order for the volume of a fuel filling registered manually and the same fuel filling detected automatically to be shown in one row and compared, their time must match. For more information, see Event registration.

DifferenceThe difference between the detected and registered filling volume.
DescriptionA brief description indicated during the manual registration of fuel filling.
Sensor nameThe sensor which detected the filling.
DriverThe name of the driver (if identified).
TrailerThe name of the trailer (if it was assigned).
CountThe number of fillings.
CounterThe indications of the counter sensor.
MileageThe mileage sensor value at the moment of filling. If the mileage parameter was not saved throughout the reported period, the mileage is counted from 0.
Avg value of custom sensor

The average value of the custom sensor registered during the filling.

This and the following columns of custom sensor values show 0 if the value is invalid. For example, if the value is not within the bounds set in the calculation table.
Min value of custom sensorThe minimum value of the custom sensor registered during the filling.
Max value of custom sensorThe maximum value of the custom sensor registered during the filling.
Initial value of custom sensorThe value of the custom sensor registered before the filling.
Final value of custom sensorThe value of the custom sensor registered after the filling.
NotesAn empty column for your custom comments.
Video

Files saved during the filling using the Video module. To watch them, click on the icon (the number of grouped files is indicated to the right of it, if several). If several grouped files are available, you can select the required one in the drop-down list in the upper-left corner.

The column is available if the Video monitoring service is activated in the account properties.

ImageThe images received from the unit. Viewing images in reports and the functions available while doing this are described here.

The table may show rows with fillings and drains marked as false. To do this, the Show false events option must be enabled in the report settings.

The interval filtration by geofences/units, drivers, trailers, filling volume, and sensor masks can be additionally applied to this table. Note that in the case of sensor masks, interval filtration is only applied to the fuel filling detected by sensors.

You can use special markers for this report to mark places of fillings on the map.

Information on fuel drains can be found here.

Questions and answers

  A vehicle has been refuelled, but I cannot find this filling in the report. Why?

Possible explanations and actions:

1. Incorrect settings for trip detector.

The option to analyze fuel filling only at stops is set in the properties of the fuel level sensor, however, the trip detection is not adjusted correctly. Either disable filling detection at stops or change trip detector settings (in particular, increase minimum moving speed or maximum distance between messages).

2. High filtration level of FLS.

Decrease the filtration level of FLS in its properties (recommended are values up to 15) or set the Calculate filling volume by raw data option.

3. High value of minimum filling.

Decrease the value of the minimum filling volume in the properties of the fuel level sensor.

  Reports show incorrect mileage. What should I do?

Possible explanations and actions:

1. Outliers of data.

To detect such outliers, build a track of unit movement for the appropriate period. Outliers of data will be seen on the track as dashed lines.

Ways to overcome outliers:

  • Enable filtration of unit positional information in messages (on the Advanced tab of unit properties). This will not affect old messages but applied to new ones.
  • To correct data in reports, change settings of trip detection, in particular, reduce Maximum interval between messages and increase Minimum satellites.

2. Incorrect settings or operation of the mileage counter.

  • Check the mileage counter settings on the General tab of unit properties.

  Do reports display the data on the manual assignment of the driver after the data storage period expires?

Yes, but only if the driver has not had other assignments since they were last assigned to the unit.


If you find a mistake in the text, please select it and press Ctrl+Enter.
Thank you for your feedback!
Report a mistake
Text with the mistake Comment
Maximum 500 characters