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

1. Download and install the application on your device. Currently, versions are available for Windows and MacOS. Linux is in the active testing stage.
2. 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.
   
3. 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.
   
4. 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.
   
5. 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.
   
6. 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.
   
7. 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.