A possible explanation is that the unit is included in a group to which the user has some access.

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 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.

1. You need a tachograph and a tracker which supports unloading DDD files.

2. Create a driver in the monitoring interface. The value of the Code field must correspond to their personal card's number.

3. Create a sensor of the Driver assignment type and add the unit to the driver's automatic assignment list.

4. Create a command for unloading a DDD file on the Commands tab of the unit properties. The command syntax may vary depending on the device type.

5. For sending a command of querying a DDD file, the unit must have an open TCP connection (the timeout depends on the type and the configuration of the tracker).

6. After unloading a DDD file the following line appears in the messages: 

• driver_card1_file=C_хх_1256.ddd, register_ddd=0 — the unloading has been successful, but the file hasn't been attached to the driver (not enough access rights to the resource or there is no driver with such a code);
• driver_card1_file=C_хх_1256.ddd, register_ddd=1 — the unloading has been successful, the file has been attached to a definite driver.

The syntax of the response depends on the type of device used. Some devices send an additional response by means of the Chat with drivers window.

The time needed for unloading a file depends on the tracker (it may take from 5 to 30 minutes approximately).

7. You can view the downloaded file and check the driver's work for a previous interval in the application Tacho View.

8. The DDD files from a driver's card are stored in a resource. The storage period of such files is not limited; they are deleted together with the resource they belong to.

Different algorithms are used when processing messages for the mobile application and the Wialon reports. In some cases, the results of processing may differ. See more about the reasons for such discrepancies.