Wialon Platform User guide Tachograph control Generating tachograph reports Generating the "Vehicle unit events" report

Generating the “Vehicle unit events” report

Who can do it: Service provider, Customer
Where: Wialon Platform FleetSpace

Prerequisites
  • The Tachograph control module is enabled for the customer.
  • The user has the permission to request history on devices.
  • The vehicle unit files (device tachograph files) are requested and downloaded from the vehicles you want to include in the report. These files come from the Tachograph memory data slot type, not from the driver cards.

The Vehicle unit events report shows the events recorded by the tachographs of your vehicles. Unlike the driver reports, it’s built from the files downloaded from the vehicle units, not from the driver cards, so you can check what happened with the vehicle even when no driver card was inserted.

Use the report to detect vehicles driven without a card, to notice possible attempts to manipulate the tachograph, and to find the periods for which you have no vehicle data at all.

This report doesn’t require the Drivers module, unlike the Driver activity events and Tachograph infringements reports.

Generating the report

To generate the report, follow these steps:

  1. In Wialon Platform FleetSpace, go to the Reports page.
  2. In the report type list, select Vehicle unit events.
  3. Click the Period, UTC field, specify the report period, and click Apply. By default, the report covers the last 6 days.
  4. In the devices list, select one or more vehicles.
  5. In the event types list, select the types you want to include, or leave all of them selected.

The report is generated automatically after you select the vehicles and the event types. To reset a filter, click the icon grey cross icon next to it. If you clear the vehicles or the event types completely, the report isn’t generated.

The report period and all event times are shown in UTC, not in your account time zone. This matches the way tachographs record data, so the values can be compared with the original tachograph files.

Event types

You can include the following entries in the report:

Event type Description
Driving without card The vehicle was driven while no driver card was inserted into the tachograph. Such a record can point to misuse of the vehicle.
Power supply interruption The power supply of the tachograph was cut off. Such a record can point to an attempt to manipulate the tachograph.
Gaps in data A period for which the vehicle provides no records. Unlike the other items in this list, it isn’t an event recorded by the tachograph. See Gaps in data.

Gaps in data

A gap is a period between two downloads of the tachograph files of the same vehicle that isn’t covered by any of them. For example, if you download the files on August 19 and the next download covers the data only from August 25, the period between these dates stays uncovered, and the report shows a gap.

Gaps are calculated only for the vehicle files downloaded after the release of this feature. The files downloaded earlier aren’t analyzed, so no gaps are shown for them.

Companies must download the data of each vehicle unit at least every 90 days and keep it. Use this report together with the Due dates tab to check that you have no missing data.

Report results

The report is organized into two parts: a summary at the top and a detailed table below.

Summary

Card Description
Devices The number of devices that have at least one entry matching the selected filters.
Events The total number of entries found, including the gaps in data.

Report table

The results are grouped by device. The collapsed row shows the device name and the number of entries found for it. Click the icon to expand the row.

Column Description
Device The name of the device.
Event The type of the entry. In the collapsed row, it shows the number of events found for this device. See Event types.
Begin, UTC The date and time when the event or the gap started.
End, UTC The date and time when the event or the gap ended. The column is empty for the events that were still open at the moment of the download.

To sort the table, click a column header. Click the header again to switch between ascending and descending order. By default, the entries are sorted by the Begin, UTC column.

The Map button at the top of the page doesn’t apply to this report. Tachograph files of a vehicle unit contain no coordinates for these events, so the map stays empty.

Exporting the report

To download the report in CSV format, click CSV at the top of the page.

Questions and answers

Why is a vehicle missing from the report?

The report is built from the files downloaded from the memory of the tachograph, not from the driver cards. If no such files were downloaded for the vehicle, it has nothing to show. To get them, request the files manually and select the Tachograph memory data slot type in the request window.

If the files are requested automatically, check that the Tachograph memory data slot type is selected in the settings of the device. Otherwise, only the driver card files are requested.

The vehicles without entries matching the selected filters aren’t shown either.

How is this report different from the "Driver activity events" report?

The Driver activity events report is built from the driver card files and shows what the drivers did. The Vehicle unit events report is built from the vehicle files and shows what happened with the vehicle, even when no card was inserted. The Gaps in data entries also mean different things: in the driver report, a gap is a period not covered by the driver card files, and here it’s a period not covered by the vehicle files.

Why is the "Description" column empty?

The column is reserved for the additional details of an event, but the tachograph files currently provide none of them for the supported event types, so it stays empty for all entries.

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