Trip Detector | Wialon Hosting

User Guide Monitoring System Units Unit Properties Trip Detector

Trip Detector

trip_detector
unit_properties

Prerequisites

To access the Trip detector tab, the Reports service must be enabled in the properties of your account or billing plan. Also, you must have the following access rights to the unit:

View detailed object properties. To view the tab.
Edit trip, driving and health check settings. To edit the tab.

The parameters of the trip detector are used to determine movement, trip, stop and parking intervals.

To work with the tab, familiarize yourself with the following concepts:

Concept	Definition
Movement	The intervals in which the speed was higher or equal to the value from the Minimum moving speed field are regarded as movement. Each unit message is considered separately. However, if the GPS coordinates movement detection method is selected, then movement is understood as the mismatch of coordinates between two messages in a row.
Trip	A trip is an interval during which the conditions of all the trip detector parameters are met. These conditions depend on the selected movement detection method and are described in the table below. When detecting trips, the system considers each separate message as well as their sequence. Trips can include stops.
Stop	A stop is an interval during which the speed was lower than the value from the Min. moving speed field, but the duration of which was less than the value from the Min. parking time field. When a stop is detected, a trip is not interrupted. If an interval has only one message with a speed value lower than the minimum speed, the time of this message is considered to be both the beginning and the end of a stop. Instead of the duration value, the tooltip of the stop marker shows N/A, and the reports show 0:00:00. Example. The value 1 km/h is specified in the Min. moving speed field. At 09:00:00, the unit sent a message with a speed value of 2 km/h, then at 09:01:00 it sent a message with a speed of 0 km/h, and after that, at 09:02:00, a message with a speed of 1 km/h was received. In this case, 09:01:00 is considered to be the time of the stop beginning and end, and the stop duration is unknown.
Parking	A parking is an interval during which the speed was lower than the value from the Min. moving speed field, but the duration of which was greater than or equal to the value from the Min. parking time field. When a parking interval is detected, a trip ends.

Unit messages with the data determined by LBS and Wi-Fi points are not taken into account in the trip detector.

Movement detection methods

The selected movement detection method determines the way the trips are detected. The following methods are available:

Method	Description
Speed	This method can be used for all types of devices which send speed values determined by GPS or another source. If you select this method, a trip is detected when both of these conditions are met: the unit speed is higher or equal to the minimum moving speed; the parameters of the Allow GPS correction option are met unless speed is determined by another source.
GPS coordinates	This method can be used for devices which don't send speed values, but transmit location data determined by GPS. If you select this method, a trip is detected when both of these conditions are met: the coordinates in the received message are different from the ones in the previous message; the parameters of the Allow GPS correction option are met (the option is enabled by default).
Engine ignition sensor	This method is available only if the unit has a sensor of the same-name type. A trip is detected when these three conditions are met: the engine ignition sensor is on; the unit speed is higher or equal to the value from the Min. moving speed field; the parameters of the Allow GPS correction option are met (if this option is enabled). A trip is terminated if the engine ignition sensor is off or the speed value is less than the minimum one. The trip also ends if the timeout specified for the sensor is exceeded. If the speed value is invalid or unavailable, the unit movement is detected according to the ignition state.
Mileage sensor	This method is available only if the unit has a sensor of the same-name type which sends absolute mileage values. A trip is detected when these three conditions are met: the mileage sensor value has increased; the unit speed is higher or equal to the value from the Min. moving speed field; the parameters of the Allow GPS correction option are met (if this option is enabled). If the speed value is invalid or unavailable, the unit movement is detected according to the increase in the mileage sensor values.
Relative odometer	This method is available only if the unit has a sensor of the same-name type which determines the distance travelled by the unit since the last message. A trip is detected when these three conditions are met: the relative odometer value is greater than zero; the unit speed is higher or equal to the value from the Min. moving speed field; the parameters of the Allow GPS correction option are met (if this option is enabled). If the speed value is invalid or unavailable, the unit movement is detected according to the non-zero values of the relative odometer.

If the Engine ignition sensor, Mileage sensor or Relative odometer method is selected, and the unit has multiple sensors of a suitable type, the system uses the sensor with the smallest ID to determine trips.

Movement parameters

After you select the movement detection method, specify values of parameters which should be taken into account in trip, stop and parking intervals.

Parameter	Description
Min. moving speed	The minimum speed value which should be considered as the beginning of movement. It is specified so that the outliers of GPS coordinates and device errors are not considered as movement when the unit is parked. If you specify 0 for this parameter, the unit stops are not detected. In this case, the system detects only trips and parking intervals.
Min. parking time	To detect parking intervals, specify the minimum number of seconds during which the unit should be motionless in order for the system to consider it as parked. If the unit has been parked for less than the specified time, it is considered as a stop within the trip. If during a trip the time between two successive messages is greater than or equal to the specified value, the trip ends. If the Allow GPS correction option is enabled, the minimum value of this parameter should be 10 seconds.

Parameter

Description

Min. moving speed

The minimum speed value which should be considered as the beginning of movement. It is specified so that the outliers of GPS coordinates and device errors are not considered as movement when the unit is parked.

If you specify 0 for this parameter, the unit stops are not detected. In this case, the system detects only trips and parking intervals.

Min. parking time

To detect parking intervals, specify the minimum number of seconds during which the unit should be motionless in order for the system to consider it as parked. If the unit has been parked for less than the specified time, it is considered as a stop within the trip.

If during a trip the time between two successive messages is greater than or equal to the specified value, the trip ends.

If the Allow GPS correction option is enabled, the minimum value of this parameter should be 10 seconds.

Allow GPS correction

The Allow GPS correction option is always enabled for the Speed and GPS coordinates movement detection methods. If you use another method, you can disable this option. If the option is enabled, you should specify the values of the following parameters:

Parameter	Description
Min. number of satellites	Specify the minimum number of available satellites to detect a trip. The recommended number is at least four.
Max. distance between messages	Specify the maximum distance between two messages after which the current movement interval should be stopped and a new one started. This value should be indicated in metres.
Min. trip time	Specify the minimum movement time in seconds which should be considered as a trip. This is required to exclude false detections of trips, for example, during short movements in a car park or a traffic jam. This parameter is applied to a sequence of messages.
Min. trip distance	Specify the minimum distance in metres which the unit should travel so that its movement is considered as a trip. This is required to exclude possible equipment errors when determining the unit location. This parameter is applied to a sequence of messages.

Questions and answers

Reports show incorrect mileage. What should I do?

Possible explanations and actions:

1. Outliers of data.

To detect such outliers, build a track of unit movement for the appropriate period. Outliers of data will be seen on the track as dashed lines.

Ways to overcome outliers:

Enable filtering of unit positional information in messages (on the Advanced tab of unit properties). This will not affect old messages but applied to new ones.
To correct data in reports, change settings of trip detection, in particular, reduce Maximum interval between messages and increase Minimum satellites.

2. Incorrect settings or operation of the mileage counter.

Check the mileage counter settings on the General tab of unit properties.

A vehicle has completed a trip. There are messages with 70 kph speed, but the trip is not shown in the report. What is the reason and what should I do?

Possible explanations and actions:

Movement detection is set incorrectly in the trip detector, e. g., the ignition sensor is out of operation or configured improperly.
If some filtering of intervals is selected in the reports template (by minimum mileage, by stops, etc.), those filters can weed out this trip. Clear the filters or correct them.
The interval for data transmission which is set in the device is bigger than Minimum parking time option set in the trip detector. Either configure the tracker to send data more often or increase minimum parking time value.
Check other parameters of the trip detector.

Why are 'stars' displayed in the parking points on the track?

The reason is a slight inaccuracy in coordinates sent by the tracker. It is absolutely normal for any type of equipment. This inaccuracy is appreciable, particularly at parkings. A unit stays still, however, the coordinates sent by the tracker slightly differ from each other. That is why 'stars' appear at the places of parkings.

You may want to get rid of those 'stars' to make the track look more intelligible. To weed off the stars at parkings, apply the trip detector to that track:

When building a track on the Tracks tab or by quick track method, activate the checkbox Apply trip detector on the Tracks tab.
When getting a track through reports, in the report template settings choose Trip tracks (and not All messages on map) to apply the trip detector. If you build a track on the Messages tab, the trip detector cannot be applied because that track shows all the messages registered in the unit database.

Make sure that the trip detector is adjusted correctly. Additionally, you can activate the message validity filter on the Advanced tab of unit properties.

If you find a mistake in the text, please select it and press Ctrl+Enter.

Was this helpful?

Download

All pages

Only this page

Download PDF file

Download Word document

Maximum 1000 characters