Jobs on Counters

Actions with Counter Values

Actions with Counter Values

To create jobs for counters, you should have:
  • the Create, edit, delete jobs access right to the resource;
  • the Use unit in jobs, notifications, routes, retranslators access right to units;
  • the Edit counters right to units.

There are three types of counters in the system: a mileage counter, a counter of engine hours, and a GPRS traffic counter. You can configure them on the General tab of the unit properties.

The following types of jobs are used for working with counters:

  • save and/or change the value of the mileage counter;
  • save and/or change the value of the engine hours counter;
  • save and/or reset the value of the GPRS traffic counter.

These jobs allow changing counter values and saving them in the unit history or messages as a parameter value. Saving the values may be necessary if data on mileage or engine hours is not sent by the device, but is calculated in the system using GPS or an ignition sensor.

Automatic actions with counter values are also performed by means of notifications (Set counter valueStore counter value as a parameter). In the case of notifications, this occurs when the specified conditions are met, and in the case of jobs, this occurs according to the specified schedule, regardless of the conditions.

Save and/or Change the Value of the Mileage Counter

In the settings of this job, you can select one or more actions related to changing and saving the mileage counter values.


The following options are available:

OptionDescription
Specify a new value of mileage counterAllows resetting the mileage counter to zero or specifying any value for it. For this purpose, enable the option and enter the value (in km) which should be applied after the job is carried out.
Save the counter value as a parameter in a unit message

Allows saving the mileage counter value as a parameter in a message. Further on, you can create a mileage sensor based on this parameter and use this sensor to get the counter values in reports (the Initial mileage and Final mileage columns). You can also see the saved values by requesting data messages from the unit. The mileage value is shown in metres or feet, depending on the measurement systems of the unit.

To use the option, enable it and enter the parameter name in the field. You can use only latin letters, special characters are not allowed. If the parameter name consists of several words, use an underscore instead of a space (for example, can_distance).


Save the counter value in the unit historyIf the option is enabled, the mileage counter value is saved in the unit history. As a result, an event is registered in the system and you can see it in the Events or Chronology tables in reports.

Save and/or Change the Value of the Engine Hours Counter

The same actions are available in this job as in the previous one, but apply to the counter of engine hours.

You can select the following options:

OptionDescription
Specify a new value of engine hours counter

Allows resetting the engine hours counter to zero or specifying any value for it. For this purpose, enable the option and enter the value (in hours) which should be applied after the job is carried out. 

Save the counter value as a parameter in a unit message

Allows saving the counter value as a parameter in a message. You can create a sensor of engine hours based on this parameter.

The parameters saved this way are available in data messages. Their value is shown in seconds.

To use the option, enable it and enter the parameter name in the field. You can use only latin letters, special characters are not allowed. If the parameter name consists of several words, use an underscore instead of a space (for example, eng_hours).

It is advisable to save the counter values while the vehicle is parked, for example, once a day at night.
Save the counter value in the unit historyIf the option is enabled, the counter value is saved in the unit history. As a result, an event is registered in the system and you can see it in the Events or Chronology tables in reports.

Save and/or Reset the Value of the GPRS Traffic Counter

The jobs of this type are usually used to:
  • automatically reset the counter of consumed traffic on a regular basis (for example, once a month);
  • save the values of consumed traffic in the unit history and run reports on it.

You can select the following options in the job settings:

OptionDescription
Save the counter value in the unit history

Allows saving the counter value in the unit history. As a result, an event is registered in the system and you can see it in the Events or Chronology tables in reports.

If the Reset the GPRS traffic counter option is also enabled, the counter reset is saved as an event and is shown in the GPRS traffic table in reports.

Reset the GPRS traffic counter

Allows resetting the counter value to zero. 



    • Related Articles

    • Creating Jobs

      Creating Jobs To create jobs, you should have: the Jobs service enabled in the account or billing plan properties; the Create, edit, delete jobs access right to the resource; the Use unit in jobs, notifications, routes, retranslators access right to ...
    • Jobs Overview

      Jobs To use jobs, the Jobs service should be enabled in the properties of the user’s account or billing plan. A job is a set of actions which are performed automatically according to the specified schedule. These actions include sending a command, ...
    • Data in Reports

      Data in Reports Time The time of completion/start/end of any state is displayed in the reports in the format specified in the General section of a report template. In the tables that include the duration of a state, the hours may not be combined into ...
    • Odometer/Run Hour Readings

      Pulse GPS has the ability to keep track of run hours (engine hours) and odometer readings.  The video below shows how to manually set up odometer readings for your asset.  1. Click on the Odo/Run Hour Readings icon on the dashboard or Odo/Hours from ...
    • Data Messages

      Data Messages Data messages are messages sent to the server from the unit device. As a rule, they contain information about the unit speed and location at the time of sending, the message generation time, and other parameters depending on the device ...