Fleetrun
Hecterra
NimBus
Other apps
Wialon for Android/iOS
Logistics
Wialon Local
Wialon Hosting
Distance Tag
WiaTag
Configurator
LeaseControl
en
en ru es
Contents
Counters
  • counters
  • unit_properties

To work with counters, the Edit counters access right is required. 

On the General tab, apart from other properties, you can configure the mileage, engine hours and GPRS traffic counters.


In order for the engine hours and mileage by sensors to be calculated correctly, the device should send data with the required sensor parameters at least once every 100 messages.


Mileage counter

You can select one of the following mileage calculation methods:

MethodDescription
GPS

Calculation based on GPS coordinates (possible for any unit).

When calculating the mileage, an altitude value is not taken into account if the difference between this value and the one from the following message exceeds 500 meters.

Mileage sensor

Calculation based on the mileage sensor.
Relative odometerCalculation based on the Relative odometer sensor which counts the distance travelled since the last message.
GPS + engine ignition sensorCalculation based on GPS coordinates and the readings of the ignition sensor.

If a sensor (including a validation sensor) needs a parameter from the previous message, such a sensor cannot be used as a method of mileage calculation. The exception is the relative odometer.

The selected calculation method influences the data in reports (mileage, duration), tracks (mileage), and messages (distance). If the selected method is based on a sensor which is not configured for the unit, the mileage values are equal to zero.

Engine hours counter

The counter of engine hours calculates the working time based on the following sensors:

  • engine ignition sensor;

  • sensor of absolute engine hours;

  • sensor of relative engine hours.

The counter values are indicated in hours, therefore, you can use fractional values rounded to the nearest hundredths. Use a point as a separator.

If a sensor (including a validation sensor) needs a parameter from the previous message, such a sensor cannot be used as the method of calculating engine hours. The exception is the sensor of relative engine hours.

The counter of engine hours is used in many report tables.

If the unit has a sensor of absolute engine hours, but the counter uses the ignition or relative engine hours sensor, then the initial and final values of engine hours in reports may differ from the data in messages.

GPRS traffic counter

The GPRS traffic counter is designed to calculate the volume of the received and transmitted traffic. 

To reset the counter, click Reset counter. Immediately after that, the system will suggest saving the sensor value in the unit history. 

You can run the GPRS traffic report for this counter.

Counter values

In the Current value field opposite each counter, you can specify the value from which mileage, engine hours or traffic should be calculated. Enable the Auto option to the right of the field in order for new data to be added to this value automatically.

The values of the counters are updated every 10 minutes.

To reset counter values manually, type 0 in the Current value field. 

In addition to the method mentioned above, you can set and reset counter values using jobs or notifications.

The values of engine hours and mileage counters can be shown in the unit tooltip and in the extended unit information.

The Timeout option from the sensor properties and the Maximum interval between messages option from the Advanced tab are taken into account only in reports and don't work for counters online.

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