All changes to Tacho Bridge App will be published here

Instructions for setting up and using Tacho Bridge Application. This is an open-source application for remote authentication of a tracker and tachograph. Repository link: Tacho Bridge Application Setting up the application Download and install the application on your device. Currently, versions are available for Windows and MacOS . Linux is in the active testing stage. After launching the application, you need to configure the company cards for further work. The application supports simultaneous work with several cards. There is no software limitation on the number of cards, but testing was carried out simultaneously with only two connected cards. In order to configure the card, you must first connect it to the computer and the application screen will display information about the connected card: reader name + ATR . ATR is a unique card key that is used to exchange data with the tachograph. This means that everything is identified correctly. To configure the card, you need to click on the + button and enter the company card number written on the card in the window that opens and save. After this, the ATR will disappear and only the company card number will remain visible. Next, you need to enter the server settings so that the application can connect to the server. The channel must be created with the **tacho-bridge** type. Next, you need to create devices with the Tacho Bridge Card type for each company card. The company card number used when configuring the card in the application must be used as the device identifier. The final stage of configuration. In order for the tracker to know which company card to contact, the company card number must be entered into the device. For example, as it is done in Ruptela. Next, you need to send a command from the desired device request_tachograph_file. Select the desired file type to download (Driver slot 1, Driver slot 2, Tachogrpah memory data) and add the command to the sending queue. If the tracker and tachograph are configured correctly, then the company card will be authenticated first, then there will be instructions for downloading the file and, if successful, the file will be uploaded to the server. configuration file and logs The application stores data in the user directory Documents/tba. This folder contains the configuration file config.yaml and application logs. The configuration file stores all application settings, including added cards. The application writes a detailed log of its work to the log.txt file. If errors occur in the application, the logs will help to understand the cause of the error. Application states When a new company card is added, only ATR will be displayed in the interface and the card icon will be gray. This means that the card is working properly, is correctly identified, but is not fully configured. In order to fully configure it, you need to add the company card number as indicated above. After configuration, the card icon will be green, this means that the card is configured, connected to the server and ready to work. If the card is removed from the reader, the card icon will be crossed out and will be gray, this means that the card is not connected to the reader and cannot be used.

Update to version v0.5.5. Fixed: Fixed README. Improved debugging. The MQTT keep-alive package interval has been increased from 300 to 550 seconds. Modification of linter and tsconfig configuration. Added ignoring of bundle build files. Correction of color scheme. .gitignore update. Feature: Added CHANGELOG. Added mechanism for validating card numbers according to Annex 1C regulation, (EU) 2016/799. added mechanism for deleting duplicate cards from config The user notification mechanism has been improved. Upgrade Tauri from version 1x to 2x. Updating all related dependencies, as well as cargo libraries. Version 2х of Tauri has many significant changes, including the structure and configuration of the project. More details here .

Update to version v0.5.6 . Fixed: Fixed potential issue with saving/updating configuration. Added extended debug log when saving configuration. Fixed a potential issue with updating the visual state of the connected card. Changing the frequency of ping packets for MQTT sessions from 550 to 120 seconds. Added handling of behavior when the OS does not grant permission to write the configuration and log. Added user notification. Feature: Added logging of information about the operating system on which the application is running. Added a mechanism for getting the latest version of the application from the repository. Notification to the user in the form of a notification in the UI.

Update to version v0.5.7 . Fixed: Improved authorization control. Added handling of unfinished authorization process due to the fault of the tracker. Tacho Bridge App device connection issue is fixed. Corrections have been made to saving the configuration. Configuration caching has been improved. Fixed issue with displaying current card number in edit dialog. Resize the application UI to a smaller size. Made a few corrections README.md Feature: The 'App ident' field now has a strict format. Constant prefix TBA + a 13-digit number. The number is formed from the current timestamp in microseconds format and the first 13 digits are taken. This is necessary so that a unique identifier is generated by default within the flespi account. The prefix is added to separate the card and app devices identifiers.

Update to version Pre-release v0.5.8 . Feature: Add configuration to sign and notarize Apple bundle! The build has been verified and signed by Apple, so the application no longer generates warning messages or suspicious actions. For more details, see README.md in the section "MacOS code signing and notarization". Now the application binary file is universal for launching on any architecture (x86, ARM). The required part of the binary file will be launched itself depending on the architecture.

Update to version RELEASE v0.5.8 . (full list of changes) Feature: Add configuration to sign and notarize Apple bundle! The build has been verified and signed by Apple, so the application no longer generates warning messages or suspicious actions. For more details, see README.md in the section "MacOS code signing and notarization". Now the application binary file is universal for launching on any architecture (x86, ARM). The required part of the binary file will be launched itself depending on the architecture. Fixes: Fixed bugs when processing data from the server. Improved stability of the application during long-term use of cards. Some components a little bit redesigned.

Update to version RELEASE v0.5.9 . Fixes: Fixed the problem of connecting Tacho Bridge App connection without connected cards to the computer. Fixed the problem of incorrect card initialization in the application configuration. Cards that are mistakenly defined with an empty ATR will not be saved. Fixed an issue where Windows Virtual Reader was incorrectly identified as the primary reader to use.

Update to version RELEASE v0.6.0 . Features: Added functionality for automatic protocol detection for communication with a smart card, which allows working with any version of the tachograph. In simpler terms, authentication now works with stoneridge hardware and other.

Update to version RELEASE v0.6.1 . Features: Protocol detection mechanism is improved. Now the protocol is selected based on the card's preferences, which improves the stability of authentication with old-generation tachographs and Stoneridge .

Major update to version RELEASE v0.7.0 . ⚠️ Attention! The new version of the application will reset the assigned cards. You will need to re-bind them only on the application side! This is done intentionally to avoid uncontrolled behavior due to the use of the old identifier. 🆕 Features Redesigned UI: Fully reworked interface — now cleaner, more modern, and user-friendly. Allows pre-configuring cards even without physical connection. Multiple cards can be created at once and later linked to a connected card. Cards can now be named to simplify searching in the list. New Card Management Architecture: Major overhaul of how cards are handled inside the app. Improved card processing flow and more robust logic for sending APDU commands. Unique card identifiers are now based on ICCID instead of ATR, resolving issues with collisions where different cards were mistakenly treated as the same. 🛠️ As part of this change, the local configuration format has been updated: Old format: ATR = card_number New format: card_number is now a structured object containing metadata (ICCID, expiry date, etc). ⚠️ Important: Automatic migration from the old format is not possible. Previously linked cards will need to be re-linked manually. This is intentional, as ATR-based mapping could not guarantee uniqueness. Linux bandle for amd64 architecture. Assembled as an AppImage file that includes everything you need, but depending on the distribution, it may sometimes require additional libraries to work with smart cards. For more information, see README. 🛠 Fixes Crash Prevention on Faulty Readers Fixed a critical issue where a physically damaged reader or broken driver caused the app to hang in an infinite loop. Fixed Card State Handling on Linux when adding or removing a card manually. Resolved a problem where triggering card state changes programmatically didn’t work correctly on Linux. Miscellaneous Bugfixes and Refactoring Minor code improvements, better error handling, cleaner logs. UI changes and guide : Current connected readers with cards and their status are displayed in the upper block. New cards that are connected but not created have a link icon. When clicking on a new card, it is possible to link with previously created ones or immediately create a new one and link. All created cards in the configuration are displayed in the lower block. They can also be deleted there using the trash can icon.

[Changelog] Tacho Bridge App

EvgenyShatilo

Update to version v0.5.7.

Fixed:

Improved authorization control. Added handling of unfinished authorization process due to the fault of the tracker.
Tacho Bridge App device connection issue is fixed.
Corrections have been made to saving the configuration. Configuration caching has been improved.
Fixed issue with displaying current card number in edit dialog.
Resize the application UI to a smaller size.
Made a few corrections README.md

Feature:

The 'App ident' field now has a strict format. Constant prefix TBA + a 13-digit number. The number is formed from the current timestamp in microseconds format and the first 13 digits are taken. This is necessary so that a unique identifier is generated by default within the flespi account. The prefix is added to separate the card and app devices identifiers.

EvgenyShatilo

Update to version Pre-release v0.5.8.

Feature:

Add configuration to sign and notarize Apple bundle! The build has been verified and signed by Apple, so the application no longer generates warning messages or suspicious actions. For more details, see README.md in the section "MacOS code signing and notarization".
Now the application binary file is universal for launching on any architecture (x86, ARM). The required part of the binary file will be launched itself depending on the architecture.

EvgenyShatilo

Update to version RELEASE v0.5.8. (full list of changes)

Feature:

Add configuration to sign and notarize Apple bundle! The build has been verified and signed by Apple, so the application no longer generates warning messages or suspicious actions. For more details, see README.md in the section "MacOS code signing and notarization".
Now the application binary file is universal for launching on any architecture (x86, ARM). The required part of the binary file will be launched itself depending on the architecture.

Fixes:

Fixed bugs when processing data from the server.
Improved stability of the application during long-term use of cards. Some components a little bit redesigned.

EvgenyShatilo

Update to version RELEASE v0.5.9.

Fixes:

Fixed the problem of connecting Tacho Bridge App connection without connected cards to the computer.
Fixed the problem of incorrect card initialization in the application configuration. Cards that are mistakenly defined with an empty ATR will not be saved.
Fixed an issue where Windows Virtual Reader was incorrectly identified as the primary reader to use.

EvgenyShatilo

Update to version RELEASE v0.6.0.

Features:

Added functionality for automatic protocol detection for communication with a smart card, which allows working with any version of the tachograph. In simpler terms, authentication now works with stoneridge hardware and other.

EvgenyShatilo

Update to version RELEASE v0.6.1.

Features:

Protocol detection mechanism is improved. Now the protocol is selected based on the card's preferences, which improves the stability of authentication with old-generation tachographs and Stoneridge.

EvgenyShatilo

Major update to version RELEASE v0.7.0.

⚠️ Attention! The new version of the application will reset the assigned cards. You will need to re-bind them only on the application side! This is done intentionally to avoid uncontrolled behavior due to the use of the old identifier.

🆕 Features

Redesigned UI:
- Fully reworked interface — now cleaner, more modern, and user-friendly.
- Allows pre-configuring cards even without physical connection.
- Multiple cards can be created at once and later linked to a connected card.
- Cards can now be named to simplify searching in the list.
New Card Management Architecture:
- Major overhaul of how cards are handled inside the app.
- Improved card processing flow and more robust logic for sending APDU commands.
- Unique card identifiers are now based on ICCID instead of ATR, resolving issues with collisions where different cards were mistakenly treated as the same.
  🛠️ As part of this change, the local configuration format has been updated:
  Old format: ATR = card_number
- New format: card_number is now a structured object containing metadata (ICCID, expiry date, etc).
  ⚠️ Important: Automatic migration from the old format is not possible. Previously linked cards will need to be re-linked manually. This is intentional, as ATR-based mapping could not guarantee uniqueness.
Linux bandle for amd64 architecture. Assembled as an AppImage file that includes everything you need, but depending on the distribution, it may sometimes require additional libraries to work with smart cards. For more information, see README.

🛠 Fixes

Crash Prevention on Faulty Readers
Fixed a critical issue where a physically damaged reader or broken driver caused the app to hang in an infinite loop.
Fixed Card State Handling on Linux when adding or removing a card manually.
Resolved a problem where triggering card state changes programmatically didn’t work correctly on Linux.
Miscellaneous Bugfixes and Refactoring
Minor code improvements, better error handling, cleaner logs.

UI changes and guide:
Current connected readers with cards and their status are displayed in the upper block.

New cards that are connected but not created have a link icon. When clicking on a new card, it is possible to link with previously created ones or immediately create a new one and link.

All created cards in the configuration are displayed in the lower block. They can also be deleted there using the trash can icon.

EvgenyShatilo

Pre-release of version 0.7.1-alpha is open.

EvgenyShatilo

release v0.7.2

🛠 Fixes

The T protocol detection mechanism for connecting to the card has been reworked. The PC/SC library now handles this completely automatically.
Fixed bug with ICCID detection when connecting a card.
README.md updated. Added usage information.
The code for migrating the old configuration version to the current one has been removed.

🆕 Features

Updated Rust toolchain and dependencies: rumqttc 0.24→0.25.1, reqwest 0.12→0.13.2, tauri 2.5→2.10.3, pcsc 2.8→2.9.0
Passive APDU sniffer parses plaintext EF data from VU↔card SM traffic (tachograph SM uses DO'81 plain value, no encryption). Recognises EF_Identification (0520) and EF_Application_Identification (0501).
CardConfig extended with sniffer-populated fields — card_type, structure_version, company_name, company_address, expire — persisted in config.yaml and synced to the frontend.
Card info display — extended view (card type, generation, expire, company name/address) in the smart cards list; condensed view in the reader block.
Added display of the last successful authentication status + timestamp. The config stores UTC; displayed in the local time zone.

EvgenyShatilo

release v0.7.3

🛠 Fixes

Card removal now asks for confirmation — a misclick no longer silently deletes a saved card.
Config is saved atomically (temp file + rename), so a crash mid-write can't corrupt config.yaml.
Logger no longer panics if $HOME/$USERPROFILE is missing (falls back to a local log dir), and opens the log file once to avoid a startup race.
Reader rows are keyed by reader name, fixing stale/duplicated entries in the UI.
Auth result is now saved off the MQTT event loop, so writes don't block it.
Card-number duplicate check fixed for reserved names like constructor/proto.

🆕 Features / Improvements

MQTT and PCSC reconnects now use exponential backoff (10s → 300s cap) instead of a fixed 10s, avoiding tight reconnect loops.
Reworked frontend events: listeners attach on mount / detach on unmount, are wired before frontend-loaded to fix a startup race, and ignore malformed payloads.
APDU sniffer no longer leaks memory — per-client state is cleared on disconnect.
App survives a poisoned mutex instead of panicking; event logging moved to the structured logger.
request/… → response/… topic rewrite now swaps only the prefix, avoiding mangled topics.
Added unit tests for config, APDU sniffer, MQTT, reconnect, and logger.

EvgenyShatilo

Lisle Design Smart Card Rack support (alpha)

This release introduces support for the Lisle Hyper Card smart card rack. The integration is fully server-driven: the application acts as a transparent bridge, with all rack protocol logic living on the server side. The application automatically detects every card inserted into the rack and brings each configured card online as a regular card session, with tachograph remote authentication fully working through the rack. This is an alpha version: the functionality is complete and operational, but occasional issues are possible and will be promptly fixed in upcoming releases. The version also includes a significant number of fixes and improvements, which will be described in the stable release notes.

Note: If you have installed the Lisle Design driver for using the Tacho Hotel as a regular reader via the standard PC/SC interface, we strongly recommend uninstalling it, as it may cause malfunctions. The application communicates with the hardware directly via the serial port.

EvgenyShatilo

v0.8.0-alpha.6

Fixed an issue with Windows devices. Lisle Rack might not be detected correctly.
Improved stability when transferring data to the server.
Added a notification if the COM port is busy with another application (this may happen if you are using native applications from Teltonika, Xirgo, and others).
See the full changelog here.