Some types of sensors have additional properties described below.

Battery capacity

This field is available for the battery level sensor. See the field description on the Additional Settings of Battery Level Sensors page.

Convert values to %

This option is available for the battery level sensor. See the option description on the Additional Settings of Battery Level Sensors page.

Filtering level

You can indicate the filtering level for the following sensor types: 

• voltage sensor;
• weight sensor;
• accelerometer;
• temperature sensor;
• engine revolution sensor;
• impulse fuel level sensor;
• custom sensor.

This option allows applying the smoothing algorithm to the sensor values. In the field,  indicate the level of such smoothing: from 0 to 255. The filtering level is indicated individually for each sensor.

You can find information about filtering the fuel level sensor values here.

Timeout

You can specify the timeout for the following sensor types:

• engine ignition sensor;
• engine efficiency sensor;
• real-time motion sensor;
  
• private mode;
• custom sensor;
• custom digital sensor.

The Timeout option is used to search for invalid intervals during the sensor operation. It is applied to historical data (reports) and data processed in real time. If an interval between two messages with sensor readings is longer than the value indicated for the Timeout option, the interval is considered invalid. In this case, the message before the invalid interval becomes the end of one interval and the message after the invalid interval becomes the beginning of the next one. The timeout is specified in seconds.

Example. Suppose that data messages from a custom digital sensor were received at 22:00,  22:30, 07:30 and 08:00. If the Timeout option is enabled, the report shows one continuous interval from 22:00 to 08:00. If you specify a timeout of 1 hour (3600 s), several intervals are formed. Since the difference between the first and second messages is less than an hour, they form the first interval (from 22:00 to 22:30). The difference between the second and third messages is more than an hour, therefore this interval (from 22:30 to 07:30) is considered invalid and is not taken into account. The difference between the third and fourth messages is less than an hour, therefore they form the second interval (from 07:30 to 08:00).

Consumption, l/h

This option is used to calculate fuel consumption mathematically for the sensors of the Engine ignition, Absolute engine hours and Relative engine hours types.

Binding engine efficiency sensors

The option is available for an ignition sensor, relative and absolute engine hours and allows binding the engine efficiency sensors of the unit to them. Once bound, the values of these sensors are taken into account when calculating fuel consumption. Select the sensor or sensors you want to bind. To select all the sensors at once, press Ctrl and click on any of them. If no sensor is selected, the calculation is carried out taking into account all the sensors of the appropriate type created for the unit.

Binding engine sensors

The option is available for a fuel level sensor and allows binding the engine sensors of the unit to it (ignition sensors, absolute engine hours, relative engine hours). Once bound, the values of these sensors are taken into account when calculating fuel consumption. Select the sensor or sensors you want to bind. To select all the sensors at once, press Ctrl and click on any of them. If no sensor is selected, the calculation is carried out taking into account all the sensors of the appropriate type created for the unit.

Calculate fuel consumption by sensor

This option is available for an impulse fuel consumption sensor, absolute fuel consumption sensor, and instant fuel consumption sensor. If the option is enabled, the data calculated by the sensor is taken into account in the Consumed row in statistics, as well as in reports in the Consumed by FLS, Consumed by AbsFCS, Consumed by InsFCS (depending on the sensor type), Consumed in motion, Consumed without motion, Avg consumption, etc. columns.

Below, you can learn how fuel consumption is calculated by each of these sensors.

Impulse fuel consumption sensor

When fuel consumption is calculated by this sensor, its values from the previous and current messages are taken into account. The previous value is subtracted from the current one and, if needed, the calculation table is applied to the resulting value. The sum of the values received on the interval corresponds to the amount of the fuel consumed.

For calculating fuel consumption, a sensor of this type should have a calculation table from impulses to liters (gallons).

Absolute fuel consumption sensor

This sensor shows the fuel consumption during all the period of vehicle operation. The absolute fuel consumption value increases continuously, but if the sensor memory overflows, the value is reset and the consumption is counted from zero. In order for the system to ignore this reset and continue to display the correct values (with the previous sensor readings in mind), use the With overflow option.

The fuel consumption is calculated by this sensor in the following way: the sensor value at the beginning of the interval is subtracted from the sensor value at the end of the interval and, if needed, the calculation table is applied.

Instant fuel consumption sensor

If this type of sensor is used, the hardware sends messages that contain the amount of the fuel consumed from the previous message till the current one. Accordingly, to determine the fuel consumption on an interval, the values of the InsFCS are summed.

For instance, the hardware has sent three messages with the following values: х1 = 0,01 l, х2 = 0,023 l, х3 = 0,048 l. The fuel consumption during this interval is: х1 + х2 + х3 = 0,01 + 0,023 + 0,048 = 0,081 (l).

Calculate data by the sensor

This option is available for fuel level sensors and for battery level sensors. See its description on the pages Additional settings of FLS and Additional settings of battery level sensors.

Maximum impulses

This option is displayed for impulse fuel consumption sensors and becomes available when the Calculate fuel consumption by sensor option is enabled. If there is a limit after which the impulse counter is zeroed (overflow), you can indicate it in this field. The value should be integer and greater than or equal to zero. However, with the limit indicated in case of an emergency reset, the calculations will be meaningless. In this case, the specified limit should be equal to zero.

Skip the first zero value

This option is displayed for impulse fuel consumption sensors and becomes available when the Calculate fuel consumption by sensor option is enabled. If the Skip the first zero value option is activated and the value of the Maximum impulses field is 0, the difference between the current and previous sensor values is taken into account when calculating the fuel consumption. If the value of the Maximum impulses field is nonzero, the Skip the first zero value option is not taken into account when calculating the fuel consumption.

With overflow

This option is available for the sensors that can be influenced by occasional resets (mileage sensor, absolute engine hours, absolute fuel consumption sensor). When this option is enabled, the system uses the following algorithm. The value from the latest message is compared to the previous one. If the value is greater than the previous one, their difference is added to the previous value. If it is less, the value from the latest message is added. This algorithm ensures that the resets are taken into account and correct data is obtained.

Overflow by raw data

This option is available only for the differential counter sensors with overflow. If it is activated, raw data is analyzed first, and then the calculation table is applied. It means that raw data (and not data processed with the calculation table, as it is in the case when the option is disabled) is taken to estimate overflow.

Validate separation

This property is available for the driver or ​trailer assignment sensors. If the option is activated, a driver assigned to the unit can be separated from it automatically only if an empty value or a separation code comes from the same parameter as the one used for assigning the driver. If the option is disabled, the empty value or the separation code received from any sensor leads to the separation of all the drivers assigned to the unit. The same applies to the trailers.

Separation code

This property is available for the driver or ​trailer assignment sensors. You can type a custom code in the Separation code field. If the code is specified, the driver/​trailer separation is carried out when an empty value or a separation code is received.

A number consisting of many characters can be indicated as a separation code if a long or text parameter which is not an expression is selected for the sensor without applying the calculation table. 

Do not show unit location

This option is available for the digital sensor of the Private mode type. Its activation allows hiding the information about the unit location in the monitoring panel, on the map, in reports, tracks, messages, etc. in case a private mode trip is detected. Next to the caption of such a unit, on the map and in the monitoring panel, the icon  is displayed and the last known location is shown instead of the current one. Mileage, engine hours and other unit data are not affected. See more details here.

This option is applied only to the messages which are received from the unit after you activate the option. Also, disabling the option doesn't return coordinates to the messages in which they were hidden while the option was enabled.

Text parameters

This option is available only for custom sensors. It should be activated if the sensor sends text parameters instead of numeric. In this case, in the table of intervals and colours, you can list these parameters and give them broader descriptions. For example, a device sends parameters error1, error2, error3, etc. In accordance with the documentation for the device, you can specify decryption for each parameter (i.e. Power supply disconnected, Invalid data, etc.). Besides, you can use the special character * (asterisk) which substitutes for any combination of characters. For example, you can indicate that the value error* should be always displayed as Error.