Advanced Properties

Advanced Properties

Required access: View detailed properties — to view parameters for reports, driver's activity source, and messages filtration settings (the first, the second, the third, and the last sections); Edit not mentioned properties — to edit color schemes of the track/sensor (middle sections); Edit trip detector and fuel consumption — to edit report parameters, and driver's activity source; Edit connectivity settings — to edit parameters of messages filtration (last section).

On the Advanced tab of the Unit Properties dialog, various parameters are set for generating reports, colors for tracks are adjusted, and speed limitations are set.

Parameters Used in Reports

Consumption by rates, l/100 km
In this field the fuel consumption per 100 km is indicated. To modify it, you need the Edit trip detector and fuel consumption access right towards the unit. Positive digital values can be introduced here. The default value is 0.

Urban speed limit
This setting is used in the report on trips. If the unit goes with the speed under indicated here, it is considered as urban mileage. If the speed is higher, this mileage is regarded as suburban. This property can be used in the trips reports, statistics, and in the advanced drivers reports.

Maximum interval between messages
Indicate the maximum interval between messages (in seconds). The excess of the specified value is interpreted by the system as a connection loss. This is reflected in the connection problems report, while calculating intervals in the engine hours report and during the mathematical calculation of fuel consumption.

Daily engine hours rate
Indicate the daily rate of engine hours to use this value in the engine hours report (when calculating the utilization and useful utilization). The engine hours operation is defined by the corresponding counter.

Mileage Coefficient

The mileage coefficient is useful to compare the detected mileage with the mileage by odometer. The corresponding column can be included in any tabular report containing information about mileage, and in the statistics.

Speeding

In this section, a method for speeding detection can be selected. The selected option defines the order of further actions.

None

The default setting for this method is set to None. It means that speedings are not registered by the system (this option is relevant, for example, for stationary units where such data is not necessary).

Use fixed limit

Fixed limit as a method of speeding detection means that the speed limit for a unit is chosen individually. In other words, the maximum speed limit for a unit is specified in the corresponding field. Upon receiving messages with the speed higher than the indicated one, the speeding is registered by the system. Moreover, here you can enter the minimum speeding duration (1 second by default). Any speeding with duration less than the indicated one is not registered by the system as speeding.

Use limits from roads

Using this method you do not indicate any particular speed limit, but the registration of speeding depends on the current speed limitation road signs used on various road sections. In other words, the system contains the data on speed limits for the particular road section, and if a unit exceeds this speed limit, the speeding is registered. If this method has been chosen, you can indicate the tolerance on speeding value. It means that speeding consists of a total of speed limit and tolerance values. For example, in some countries exceeding speed limit by 10 km/h is not a violation, that is why you can indicate 10 km/h tolerance on speeding. Therefore, on an area with a speed limit of 60 km/h, the unit can move with a speed of 70, and this speed is be considered a speeding. Moreover, here (the same as for the previous method) the minimum speeding duration can be indicated.

  In order to register the speeding, it is necessary to receive at least two speeding messages in a row.

Speedings are registered in the system, and subsequently you can generate a speedings report. Moreover, during building a track you can enable speeding markers which highlight the corresponding events on the track.

Driver Activity

Information on driver activity helps to track whether the driver follows the AETR standards or not. Such information is displayed in the unit or driver tooltips as well as in the extended unit information if the corresponding checkbox is indicated in the User Settings dialog.

This section allows to choose the source for determining driver activity. The dropdown list contains 3 items: None, Tachograph, and Bindings. If the None item is chosen, the unit or driver tooltips, or the extended unit information do not show the current data on the driver activity. If the Tachograph item is chosen, the information on the activity of a driver bound to this unit is received from the tachograph installed in the vehicle. If the Binding item is chosen (for example, if a vehicle is not equipped with a tachograph), the activity of a driver bound to this unit is determined in the following way:

  • Driving status is registered as the driver activity when either trip or stop have been detected for a unit.
  • Work status is registered when parking has been detected.
  • Rest status is registered upon unbinding a driver from such a unit.

Unit label color

By default, the names of the units and drivers assigned to the units are red on the map. However, you can change this color here and even set various colors for different units.


Track Colors

Different colors can be used to show on the map not only the unit itself, but also its movements (tracks). Tracks can be built in the Tracks panel, Messages panel, Reports panel, or in the Monitoring panel (quick tracks).

Track segments can be colored differently depending on speed, sensor values, and so on. These properties are set individually for each unit. Note that such settings of colors as By speed, By sensor, and Single are mutually exclusive (only one can be chosen).


Single (constant track color)
Activate this option so that the color of the route always remains permanent. This is convenient when building tracks for groups of units, so that the tracks of different units do not merge with each other. Select color from the palette.




By Speed (speed based track colors)
Activate this option to change the color of the track depending on the speed. To set the values for the speed intervals and indicate their colors, click the add interval button (). The track color is set for each interval individually. In other words, it is necessary to set an interval, pick its color, and click OK. Afterwards, the same procedure should be done for the rest of intervals. Pay attention to some peculiarities of setting intervals and choosing their color that can be useful:


  • No value in the first field corresponds to -∞, in the second — to +∞;
  • Adding an interval which intersects with an existing one and reaches beyond it, the added interval is set instead of the existing one;
  • Adding an interval which intersects with an existing one without reaching beyond it, the added interval is inserted inside the existing one. Moreover, both the intervals to which the existing one was divided, receive its text and color.
  • You can either choose a necessary color from the color picker or indicate its text value (in HEX) in the corresponding field.

Upon completion, the intervals of the selected color are displayed on the scale. Each interval of the scale and the color assigned to it can be edited. To do so, click the corresponding interval on the scale and set the required parameters. To reset the intervals you entered and display the default intervals on the scale, click the corresponding button to the right of it ().



By Sensor (sensor based track colors)
Activate this option to change the color of the track depending on the indication of a particular sensor. Choose a necessary sensor from the dropdown list (the list is formed on the basis of all the sensors created for a unit). For each sensor created, you can set interval values and pick their colors on the corresponding tab. Therefore, when this option is activated, the colors indicated on the interval scale in the properties of the selected sensor are used to draw the track.



Usage of Sensor Colors

From the dropdown list, select the sensor, the colors of which you would like to use for visualization of the sensor state in the monitoring panel or to indicate the units on the map by the color according to the latest sensor value.


Messages Validity Filtration

All the messages are stored in the system without any exception. However, in the case of data spikes, lack of coordinates, etc. such messages may distort the mileage count and various indications in the reports. That is why, it is recommended to enable the filtration of data, in which invalid messages are not taken into account. To adjust the filtration settings, fill in the fields described below. Please note, that the filtration applies only to new messages.


Allow positioning by cellular base stations
Positioning by cellular base stations (LBS detection) is an alternative method of defining unit location. This method involves the use of cellular base stations as reference points for the location detection. Note that the method is not as accurate as the use of GPS, and just allows to receive the approximate location. When enabling this checkbox, the LBS detection is used only if it is newer than the GPS data.



Skip invalid messages
Some controllers may send a flag about coordinates validity/invalidity in messages. A message with invalid coordinates is marked by the flag of invalidity, and when sending such a message to the server, the current time and the last valid coordinates are given. gTrack will consider this message as a message without position data, and it will be not used when constructing movement tracks, detecting location in reports, etc. However, if this message contains other parameters (such as sensors), they will be used.



Minimum satellites
If the number of satellites locked is lower, the message is considered to be invalid. Some types of equipment can give out the correct coordinates with only two satellites. The recommended value is at least three.



Maximum HDOP value
HDOP stands for the Horizontal Dilution of Precision. HDOP is an error in the horizontal plane, at which the messages are considered valid. The smaller this parameter, the more accurately the coordinates are determined. If the HDOP value in the message is greater than the specified value, this message is marked as non-valid. Any messages with missing or zero coordinates, also undergo filtering, even if the device did not mark such a message as invalid. A message is recognized as invalid if at least one coordinate (longitude or latitude) is zero.



Maximum speed value
The messages containing speed higher than or equal to one set here are marked as invalid.



    • Related Articles

    • Unit Properties Transfer

      Almost any unit properties can be imported and exported: General properties Unit name, device type, phone number(s), unique ID(s), device access password (from the General tab). Icon Icon of the unit and the state of the Rotate icon checkbox. Note ...

    • User Properties

      User  properties are configured when creating, editing or copying a user in a special dialog on several tabs. The availability of different tabs and parameters depends on the access you have towards the user. Two tabs are available in any case ...

    • Sensor Properties

      ...

    • Account Properties

      Account Properties dialog can contain up to 6 tabs. Their availability depends on the access rights. General The General tab has 3 sections. However, only the first one is available to the users with the minimum access. This section holds the name of ...

    • Advanced Reports

      Advanced reports are reports on unit groups and users (except the 'Log' table), all tables for drivers, trailers, and their groups, as well as report on logins for resource. These report types are defined when creating a template. Reports on Unit ...