Tacho-bridge protocol

Tacho-bridge connects company cards to flespi so that trackers can authenticate with the tachograph remotely and download tachograph files.
flespi parses the Tacho-bridge protocol messages into a JSON object with the fields listed below in the Parameters tab.

The tacho-bridge protocol connects company cards to flespi, so that trackers can authenticate with the tachograph remotely and download driver card and tachograph memory files. Downloaded files are stored in the device media.

The company cards stay in smart card readers or card racks on your computer, where the Tacho Bridge Application connects them to this channel.

How to set it up:

1. Create a channel with the tacho-bridge protocol.

2. Install the Tacho Bridge Application and enter the channel address in its Server address field.

3. Create a device with the Tacho Bridge App type, using the App ident from the application as its ident.

4. Link each company card in the application to its number, written on the card.

5. Create a device with the Tacho Bridge Card type for each card, using the card number as its ident.

6. Enter the company card number in the configuration of the tracker's device.

7. Download files with the Request tachograph file command or the Automatic file request option. Some trackers start the upload by themselves.

To restrict who can connect, fill in the Application authentication section of the channel configuration and enter the same username and password in the application settings.

See the Tacho integration guide for the details and the Tacho Bridge App guide for the application and card racks.

channel.id
number
ID of channel that received a message
device.id
number
ID of device that received a message
device.name
string
Name of device that received a message
device.type.id
number
ID of device type of device that received a message
ident
string
Device unique identifier like serial number, IMEI, etc
media
boolean
Message contain media file
media.video
object
Video file in media storage
peer
string
IP:port from which device connecting to the channel
protocol.id
number
ID of protocol
server.timestamp
number
seconds
Timestamp when server received a message
timestamp
number
seconds
Message timestamp
Properties
Communicate with card
communicate
Send data to tacho card and return card response
finish: Finish communication session
sender: Sender device id
payload: Binary payload in HEX form
protocol: Card T protocol
Fetch application logs
fetch_logs
Fetch the application log file for the given period; the zipped log is attached to the command result
period: Log period