Сhangelog of tachograph functionality changes Supported protocol types: Teltonika Ruptela Queclink Xirgo ( Binary , MQTT ) BCE Squarell Useful articles: Using Tachograph functionality How to setup Tacho Bridge App Functionality ready to use.: Ability to upload files: drivers , memory . All types of tachographs: G1 , G2_1 , G2_2 . Automatic file upload. Ability to flexibly adjust the upload interval. Remote authentication of the tachograph is carried out through a cross-platform application developed specifically for flespi.

File name format change. Changed format of C1b, V1b file name for France. Added separator, '_' symbol of time format between date and time. Reason: bring the time format to a single form for all files: ddd, tgd, v1b/c1b. Before: VU file: FXX-NNN-ZZ2508011746.V1B Driver file: FXX-NNN-ZZ2508011746.C1B After: VU file: F_XX-NNN-ZZ_250801_1746.V1B Driver file: F_XX-NNN-ZZ_250801_1746.C1B

Fixed encoding parsing error for IS, FIN, EST, LT, LV countries. Previously caused a parsing error and interrupted the file saving process. The problem was in the encoding of fields for the driver file: name, surname, Issuing authority name.

Bug fix: fixed an issue where a file initiated manually, without an automatic download configuration, would not be correctly finalized.

Improved error handling for communicating with a company card via the TBA app. If a case is detected where the card is online and successfully receiving data, but for some reason the server does not receive a response from it, an event similar to the following will be logged: The company card '1110000000110000' is online and receiving data but not responding. Most likely, the problem is related to a data proxy issue or a poor internet connection. This issue is almost certainly caused by data proxy issues and, in rare cases, internet problems.

Internal update of parsing of tachograph memory files of generations: G2.1, G2.2.

Minor improvements to the functionality of the tachograph data download command.

Minor changes affect the tachograph memory data download command. Previously, when specifing data retrieval, the command could fail with an error stating that the parameter was not supported.

Fixing minor bugs. Improved uploading file stability. Improved file parsing.

Improved postprocessing of APDU commands from the tachograph for transmission to the company card. This change only applies to Stoneridge tachographs newer than v2424.

[Changelog] Tachograph functionality

EvgenyShatilo

Improved automatic download mechanism. Applies to the Ruptela and Squarell protocols:

Improved stability.
Each file type now has its own timestamp indicating the last download. This resolves the issue where one of the drivers was missing but the download cycle completed. Now, the missing file should be downloaded whenever the driver is found online.

Important: The update has reinitialized the automatic download configuration. The server will automatically update everything necessary as soon as the tracker connects. Rewriting the configuration affected the last successful tachograph data download, so the server will re-request data downloads for all file types specified in the configuration: driver1, driver2, and memory. After that, everything will function as usual.

EvgenyShatilo

Removed tacho file parsing, which was partially present in the content field as a result of command execution. This worked for Ruptela, Squarell, and Queclink devices.
Full file parsing will be available in Q1 2026 via a new plugin.

EvgenyShatilo

Improved tachograph file parsing for more stable file name determination.

EvgenyShatilo

Tachograph file parsing stability has been improved. This applies to the following protocols: Ruptela, queclink, Xirgo, Xirgo-mqtt, BCE, and Squarell.
This is due to an issue with file name identification (pre-parsing of the file). This update resolves the file name generation issue.

EvgenyShatilo

Updated timeouts after a failed file download or authorization attempt.
Fixed a bug where the scheduler interval might not reset and a file download attempt would fail.

EvgenyShatilo

Updated the download scheduler for all tacho protocols.
- Improved queue and timeout interval management.
- Multiple bug fixes.

EvgenyShatilo

Scheduler update.

Stability improvements.
Fixed a bug where an incorrectly set configuration could cause parsing to fail.

EvgenyShatilo

Fixed an issue with identifying the file names of first-generation tachograph memory files. The file name is now generated correctly.
Added a mechanism for detecting corrupted data within a tachograph file. Such files will be skipped.
Improved overall stability.
Bug fixes.

EvgenyShatilo

Improved file parsing:

String decoding update. In some cases, the tachograph may return some parameters, for example, vehicleRegistrationNumber mixed with 00 bytes and indents. Now this no longer causes an error.

EvgenyShatilo

Change in tachograph file validation behavior.
All files uploaded to the server are validated based on their data structure. If a tachograph file fails validation, it will be saved anyway but with the "corrupted: true" flag. If the file is completely valid, the corrupted parameter will be absent.
Example of the meta data:
meta:{ command_id : 177811111111111111 corrupted : true driver_first_name : "Name" driver_id : "000000000C1ABC00" driver_last_name : "LastName" plate_number : "AAA841OK" region : "BG" type : "tacho" }

EvgenyShatilo

Updated driver and memory file parsing.
Improved internal tacho functionality.