To work with the Advanced tab, the following access rights are required:
View detailed object properties. To see the parameters used in reports, message validity filtration and driver activity source.
Edit not mentioned properties. To edit the Unit caption colour, Track colours, Usage of sensor colours sections.
Edit trip detection. To edit the parameters used in reports and driver activity source.
Edit connectivity settings. To edit the parameters of message validity filtration.
The Advanced tab consists of several sections. In these sections, you can configure parameters for reports, track and sensor colours, filtration of unit messages, etc.
Parameters used in reports
The parameters available in this section influence the execution of reports.
|Consumption by rates|
Fuel consumption per 100 kilometres. Another unit of measurement can be used, depending on the selected measurement system. The default value is 0.
The option which allows you to specify a separate fuel consumption rate for a certain period. The default value is 0.
Urban speed limit
The maximum speed at which it is conventionally considered that the unit is moving within the city. Moving at a higher speed is considered as suburban mileage. You can use this setting in reports: in the Trips table, in statistics, in the advanced report on drivers.
Maximum interval between messages
The maximum interval between messages in seconds. If the specified value is exceeded, the system considers it as connection loss. It is shown in the Connection problems table, used when calculating intervals in the Engine hours table and when determining fuel consumption by math and by FLS.
Daily rate of engine hours
The daily rate of engine hours (in hours). This value can be used in the report on engine hours (when calculating utilization and useful utilization). The operation of engine hours is determined by the engine hours counter.
The coefficient used to correct the mileage calculated in Wialon in cases where it always differs from the actual mileage by a certain number of times.
Example. The mileage calculated in Wialon is 100 km, and the actual mileage (determined by the vehicle equipment) is 120 km. The mileage coefficient that should be specified in this field is 120/100 = 1.2.
In this section, you can select the method which should be used to determine speed limit violations on which you can later run a special report. Also, if you are running a report with a track, you can enable an option to add speeding markers to the map.
The following items are available for selection:
The system doesn't register speed limit violations. This item is selected by default.
Speed limit violations are registered in accordance with the specified conditions.
In the Fixed speed limit field, specify the maximum allowed speed for this unit. If the speed is higher than the specified value, the system registers a violation.
In the Min. speeding time field, specify how long the violation should last. If the violation lasts less than the specified time, the system doesn't register it.
Speed limit violations are registered in accordance with the restrictions indicated in Gurtam Maps (provided that the road limit is higher than 30 km/h).
In the Tolerance on speeding field, specify by what value the unit can exceed the speed limit so that the system doesn't register a violation. For example, the map shows a road limit of 60 km/h. The field value is 10 km/h. This means that if the unit is moving at a speed of up to 70 km/h, no violation is registered.
In the Min. speeding time field, specify how long the violation should last in order for the system to register it.
If you specify 0 in the Min. speeding time field, a speed limit violation is registered even if the unit sends one message with a speed value higher than the selected limit. The duration of this interval is indicated in reports as 00:00.
Driver activity by online data
In this section, you can select the source of information about the activity of the driver. This data helps to monitor in real time whether the driver sticks to the work and rest regime.
The information about the driver activity is shown in the tooltips of the unit and of the driver and in the extended information about the unit if the Driver activity by online data option is enabled in the user settings. Also, you can see this information in the Driver activity and Infringements tables in reports on drivers and in the Tacho View application.
The following data sources are available for selection:
New data on the driver activity is not calculated. But the tooltip of the unit or driver and the extended unit information display the data on driver activity calculated earlier, if any.
Parameters from tachograph
Online data on the driver activity is transmitted to the device from the tachograph installed on the vehicle, and then it is sent to the system. Not all of the device types support this feature.
Assignments and trips
The activity of the driver assigned to this unit is determined by online data as follows:
Wialon doesn't recalculate online data on the driver activity for the past period. Therefore, online data can only give you an approximate idea of whether the driver sticks to the work and rest regime. If you change the trip detector settings or data on the driver assignments, these changes are not applied to online data for the past period and are not reflected in reports.
You can get accurate data on the driver activity only in reports and in the Tacho View app using files from the driver card as a data source.
Unit caption colour
By default, the names of the units and the drivers assigned to them are shown on the map in red. However, you can select a different colour for each unit.
In this section, you can set the colour for tracks, that is, the lines of unit movement on the map. The tracks are mapped on the Tracks, Messages, Reports, and Monitoring tabs (the Quick track option).
Tracks can be single- or multi-coloured depending on the settings according to which the colour is determined. You can select one of the four options:
- by trips;
- by speed;
- by sensor.
The option selected in this section is also selected for the Tracks tab by default.
The track is divided into sections of different colours, each of which corresponds to one trip. Trips are detected by the trip detector.
The track is single-coloured. This option is useful when mapping tracks for unit groups because they don't merge with each other in this way. You can select a colour from the palette.
If you map several tracks in a row, the next colour from the palette is used for each track.
The track is multi-coloured depending on the unit speed. To add an interval, click on the icon , specify the speed values and the colour for the interval, and click OK. An empty value in the first field is considered as -∞, in the second as + ∞. You can select the colour from the palette or specify it in the HEX format in the field above.
The created intervals are shown on the line scale. To edit an interval, click on it, make changes, and click OK.
To reset the settings to the default ones, click on the icon to the right of the scale.
The track is multi-coloured depending on the values of the selected sensor. The list contains the sensors created for the unit. The value intervals and colours for tracks are specified in the sensor properties.
Usage of sensor colours
In this section, you can select the sensors the colours of which should be used for certain interface elements. The colours are configured in the sensor properties.
Below are the interface elements for which the colours of the selected sensors are used.
|Motion state signs|
The colours of the selected sensor are used for motion state signs on the map.
The colours of the selected sensor are used for the Battery level option in the work list on the Monitoring tab and in the menu of monitoring options on the map.
To configure a sensor which shows the battery level, you should create a custom sensor with the parameter in which data on the battery is received from the device. If the data is received in volts, and not in per cent, then you should also fill in the calculation table in the sensor properties so that the data is displayed correctly.
Message validity filtration
All messages from units are registered in the database. However, some messages can be invalid, for example, due to data fluctuations or lack of coordinates. Such messages distort the values of mileage, tracks, indicators in reports, etc.
In order for the system not to take invalid messages into account, enable the Message validity filtration option and configure the required criteria: the number of satellites, unit speed, or the accuracy of coordinates. Here you can also enable the options for determining the location by LBS and filtering the messages identified as invalid by the device itself.
Regardless of the settings in this section, any messages with zero or no coordinates are filtered automatically. A message is considered invalid if at least one coordinate (longitude or latitude) is equal to zero.
Filtration is applied only to GPS data, so if an invalid message contains other parameters, for example, sensor values, they can still be used in the system.
The settings in the section apply only to the messages received after the settings have been adjusted.
Allow positioning by cellular base stations
This option allows using cellular base stations (LBS) to determine the unit location, for example, when GPS data is not valid. The data obtained this way is not as accurate as GPS data and shows only an approximate location.
LBS data is used only if the Allow positioning by cellular base stations option is enabled and there is GPS data that doesn't meet the specified filtration criteria. If there is no GPS data, LBS data is not used. In addition, messages with LBS data are not taken into account in the trip detector and eco driving.
|Skip invalid messages|
The option allows ignoring the GPS data identified by the device as invalid. Some devices (controllers) send special parameters which identify invalid coordinates. Also, the current time and the last valid coordinates are specified in the message. The system considers such a message to be without positional data and doesn't use it for mapping tracks, determining the location, and so on.
In this field, you can specify the minimum number of satellites that should be used to determine the coordinates in order for the message to be considered valid. The recommended number is at least four.
|Maximum HDOP value|
In this field, you can specify the maximum HDOP value with which messages are considered valid. HDOP stands for horizontal dilution of precision. The smaller this value is, the more accurate the coordinates are.
|Maximum speed value|
In this field, you can specify the limit for speed values. If it is exceeded, the message is considered invalid. If 0 is specified, this filtration criterion is not taken into account.
Determine the location by Wi-Fi points
This option is displayed for devices that can determine the location by Wi-Fi points. When it is activated, the options described below become available.
|Minimum number of Wi-Fi points||Here you should specify the minimum number of Wi-Fi points with which the messages should be considered valid. You can indicate only an integer value. The minimum allowed value is 2.|
|Maximum number of Wi-Fi points|
In this field, you should specify the maximum number of Wi-Fi points which should be taken into account when determining the unit location. If the number of available points is greater than the number indicated here, the points with a stronger signal are used. You can indicate only an integer value. The minimum allowed value is 2.
|Location accuracy, m||In this field, you should specify the location accuracy in meters. The smaller the value, the more accurate the received coordinates. A message is considered invalid if its accuracy value is greater than the specified one. You can enter an integer or fractional number more than or equal to zero.|
Messages with Wi-Fi data are not taken into account in the trip detector and eco driving.
If the Allow positioning by cellular base stations option (see the section above) is also enabled for the unit and there is valid GPS, LBS and Wi-Fi data, the system determines the unit location using Wi-Fi data in the first place. If Wi-Fi data is invalid (that is, doesn't match the specified settings or the point address hasn't been found), the system uses GPS data. LBS data is the last to be used.
You can see that the unit location has been determined by Wi-Fi points in the following places of the system:
- in the Motion state section of the Dashboard tab;
- in the work list of the Monitoring tab (the Motion state option);
- in the table of data messages from the unit (the messages with the unit location determined by Wi-Fi are highlighted in purple).