Introducing the tacho-file-parse plugin — a new plugin type for parsing raw tachograph files downloaded from driver cards and vehicle unit memory into structured JSON. What's included: Full parsing of driver card files (Gen1 and Gen2 v1/v2): activity records, work period locations, vehicles used, events & faults, border crossings, GNSS waypoints, cargo operations, and more Partial parsing of vehicle unit (VU) memory files (Gen1): VIN, odometer, activity changes, control records, company locks, download history, certificates — Gen2 VU support is in progress Automatic merging of split data chunks — tachograph files fragmented over low-bandwidth CAN bus are reassembled into a single coherent record Output is fully compliant with EU Regulation 2016/799 data structure Plugin output is accessible via REST API through the content field of the file entity

Improved parsing of the tachograph memory file: 2nd generation is updated. Added parsing of the first generation (currently only available within the overview)

Several fields that used to store the raw numeric country code now store the alphabetical code (e.g. 41 → "RO"). Changes by record: EF_Events_Data / eventVehicleRegistration — vehicleRegistrationNation: was raw %uint8 (e.g. 41), now alphabetical (e.g. "RO"). EF_Faults_Data / faultVehicleRegistration — vehicleRegistrationNation: was raw %uint8, now alphabetical. EF_Current_Usage / sessionOpenVehicle — vehicleRegistrationNation: previously written as raw numeric (with a separate temp var), now single alphabetical value. File types affected: Driver card files: events, faults, and current usage records. VU (Vehicle Unit) files: events and faults vehicle-registration records. Net effect: every vehicleRegistrationNation field is now consistently emitted as the alphabetical country code instead of the raw numeric value. Added guard for corrupted ActivityChangeInfo records . A corrupted structure has been detected in some G2 memory files. Whereas the tachograph is sending a record length of more than 2 KB instead of the specified 2 bytes. Log message: "The file is corrupted. ActivityChangeInfo should have a record size of 2 bytes, but has a %d".

cardIssuingMemberState is now reported as a country code (e.g. "D", "RO") instead of a numeric value. Authority and driving licence issuer names are returned with correct character encoding instead of escaped form.

Major update of tachograph file parsing This is a major update of the DDD file parser: it now reads everything the files contain. Two file types are fully supported - tachograph memory (VU) files and driver card files. All tachograph generations and versions: G1, G2.1, G2.2. Tachograph memory (VU files) VU files are now parsed completely for both generations: Gen1 and Gen2 (v1/v2). Previously even Gen2 files only had their overview and activities blocks decoded, and Gen1 was barely parsed at all. Although the two generations have different file structures, everything is adapted and the output is consistent: same blocks, same record shapes, with differences only where the regulation itself has them. The result nesting has changed: the output now explicitly shows the tachograph generation (VU_Tachograph / VU_Tachograph_G2) and the data section inside it - overview, activities, events and faults, speed, technical data (VuOverview, VuActivities[], VuEventsAndFaults, VuDetailedSpeed, VuTechnicalData). A useful addition to the output: the period for which the tachograph actually has data available for download. Empty card slots and unused seals are no longer emitted (previously they appeared as 0xFF filler objects). Driver cards More data is now extracted from the card's Gen2 section: for example, the last download date and the full set of certificates - for those who verify data signatures. The structure and field names are aligned with the VU file output - card data and tachograph data now read the same way. Only driver cards are fully parsed: workshop, control and company card files are rejected with an explicit error - previously they were silently parsed as driver cards, producing incorrect results. General All parameter, section and structure names were reviewed and brought in line with the regulation. A number of parsing inaccuracies were fixed: some data used to be decoded incorrectly or lost. Single-element arrays (CurrentDateTime, VIN, certificates, etc.) are now plain values. Corrupted or truncated files now produce an explicit error instead of partial or garbage JSON. ▎ Note: the new data will not appear in already uploaded files by itself - such files need to be run through the plugin again. You can do this via the API or with a message resend: it triggers the plugin, and the file is re-parsed with the full set of data.

[Changelog] tacho-file-parse plugin

EvgenyShatilo

Introducing the tacho-file-parse plugin — a new plugin type for parsing raw tachograph files downloaded from driver cards and vehicle unit memory into structured JSON.

What's included:

Full parsing of driver card files (Gen1 and Gen2 v1/v2): activity records, work period locations, vehicles used, events & faults, border crossings, GNSS waypoints, cargo operations, and more
Partial parsing of vehicle unit (VU) memory files (Gen1): VIN, odometer, activity changes, control records, company locks, download history, certificates — Gen2 VU support is in progress
Automatic merging of split data chunks — tachograph files fragmented over low-bandwidth CAN bus are reassembled into a single coherent record
Output is fully compliant with EU Regulation 2016/799 data structure
Plugin output is accessible via REST API through the content field of the file entity

EvgenyShatilo

Improved parsing of the tachograph memory file:

2nd generation is updated.
Added parsing of the first generation (currently only available within the overview)

EvgenyShatilo

Several fields that used to store the raw numeric country code now store the alphabetical code (e.g. 41 → "RO"). Changes by record:
- EF_Events_Data / eventVehicleRegistration — vehicleRegistrationNation: was raw %uint8 (e.g. 41), now alphabetical (e.g. "RO").
- EF_Faults_Data / faultVehicleRegistration — vehicleRegistrationNation: was raw %uint8, now alphabetical.
- EF_Current_Usage / sessionOpenVehicle — vehicleRegistrationNation: previously written as raw numeric (with a separate temp var), now single alphabetical value.
  
  File types affected:
  Driver card files: events, faults, and current usage records.
  VU (Vehicle Unit) files: events and faults vehicle-registration records.
  Net effect: every vehicleRegistrationNation field is now consistently emitted as the alphabetical country code instead of the raw numeric value.
Added guard for corrupted ActivityChangeInfo records. A corrupted structure has been detected in some G2 memory files. Whereas the tachograph is sending a record length of more than 2 KB instead of the specified 2 bytes. Log message: "The file is corrupted. ActivityChangeInfo should have a record size of 2 bytes, but has a %d".

EvgenyShatilo

Improved tacho file processing and checking for corrupted data.

EvgenyShatilo

cardIssuingMemberState is now reported as a country code (e.g. "D", "RO") instead of a numeric value.
Authority and driving licence issuer names are returned with correct character encoding instead of escaped form.

EvgenyShatilo

Tachograph file parsing improved: fixed parsing of activity data from vehicle unit memory files (DDD).
All daily activity records loaded in the file are now parsed, including detailed substructures: card insertion/withdrawal cycles, work period places, GNSS positions, specific conditions, border crossings, and load/unload operations.

EvgenyShatilo

Major update of tachograph file parsing

This is a major update of the DDD file parser: it now reads everything the files contain. Two file types are fully supported - tachograph memory (VU) files and driver card files. All tachograph generations and versions: G1, G2.1, G2.2.

Tachograph memory (VU files)

VU files are now parsed completely for both generations: Gen1 and Gen2 (v1/v2). Previously even Gen2 files only had their overview and activities blocks decoded, and Gen1 was barely parsed at all. Although the two generations have different file structures, everything is adapted and the output is consistent: same blocks, same record shapes, with differences only where the regulation itself has them.
The result nesting has changed: the output now explicitly shows the tachograph generation (VU_Tachograph / VU_Tachograph_G2) and the data section inside it - overview, activities, events and faults, speed, technical data (VuOverview, VuActivities[], VuEventsAndFaults, VuDetailedSpeed, VuTechnicalData).
A useful addition to the output: the period for which the tachograph actually has data available for download.
Empty card slots and unused seals are no longer emitted (previously they appeared as 0xFF filler objects).

Driver cards

More data is now extracted from the card's Gen2 section: for example, the last download date and the full set of certificates - for those who verify data signatures.
The structure and field names are aligned with the VU file output - card data and tachograph data now read the same way.
Only driver cards are fully parsed: workshop, control and company card files are rejected with an explicit error - previously they were silently parsed as driver cards, producing incorrect results.

General

All parameter, section and structure names were reviewed and brought in line with the regulation.
A number of parsing inaccuracies were fixed: some data used to be decoded incorrectly or lost.
Single-element arrays (CurrentDateTime, VIN, certificates, etc.) are now plain values.
Corrupted or truncated files now produce an explicit error instead of partial or garbage JSON.

▎ Note: the new data will not appear in already uploaded files by itself - such files need to be run through the plugin again. You can do this via the API or with a message resend: it triggers the plugin, and the file is re-parsed with the full set of data.