Fleetrun
Hecterra
NimBus
Other apps
Wialon for Android/iOS
Logistics
Wialon Local
Wialon Hosting
Distance Tag
WiaTag
Configurator
Wialon Hosting
Contents
Jobs on Counters
  • jobs
  • counters

Three types of counters are used in Wialon: counters of mileage, engine hours, and GPRS traffic. They are configured on the General tab of the unit properties.

Jobs on counters allow you to automate the saving of the counter values and also adjust the accounting of mileage, engine hours, and GPRS traffic.

Mileage counters

With the help of this job, you can save the current value of the mileage counter, reset it to zero or any other value, and save it as a parameter in the message.

To set a new value or reset the counter, enable the New value for mileage counter option and enter the required value in the field. The counter will obtain this value each time the job is executed. Depending on the resource settings, different measurement systems can be used.

Enable the Store counter value as parameter of unit data message option to save the counter value as a parameter in the data message (you should create a sensor with this parameter for the unit). It allows displaying the initial and final mileage in the report on trips. The parameter name should be indicated in Latin letters, special characters are not allowed. If the parameter name consists of several words, use an underscore instead of space (for example, can_distance).

It is advisable to store the counter values while the unit is parked, for example, once a day at night.

The Store counter value in unit history option can be used to store the current mileage counter value. It is advisable to enable it if the counter is subject to reset to zero according to the job.

Engine hours counters

This type of job is similar to the previous one, but it is applied to the engine hours sensors.

Enable the Store counter value as parameter of unit data message option to save the current value of the engine hours counter as a parameter in the message, which allows you to subsequently create an engine hours sensor on its basis. When entering the parameter name, it is advisable to use underscores instead of spaces. For more accurate calculations it is advisable to store the counter values during the parking of the vehicle, for example, once a day at night.

The Store counter value in unit history option is responsible for storing the value. In the New value for engine hours field, you can enter a new value (in hours) which will be applied to the counter after the job is completed.

For the job to be performed successfully, the creator of the resource to which the job belongs should have the Edit counters access right to the unit.

If you save the values of traffic, mileage, engine hours or counters in the unit history, they are recorded in the system as registered events, which allows you to display them in the reports on events or chronology later. Saving the value of the counter as a parameter in the message occurs in the unit database in such messages as data messageThe engine hours value is displayed in seconds, and the mileage value, depending on the unit settings, is in meters or feet.

GPRS traffic counters

This job is used to:

  • regularly reset the traffic counter automatically;
  • store the GPRS traffic counter value in the unit history, which allows you to receive reports on consumed traffic.

If the Store counter value in unit history option is enabled, each traffic reset is registered in the system, and then you can generate a report on events or a report on traffic to see the traffic consumption.

The Reset GPRS traffic counter option is used to reset the counter to zero when the job is performed.

If both options are enabled, the counter value is reset and saved in the history according to the specified schedule when the job is performed.

Thank you for your feedback!