Tacho Bridge Card

This type of device is designed to connect to the company card from flespi during tachograph authentication. In other words it serves as a bridge between the company card and the tachograph to exchange data.

The device ident must match the real company card number shown on the smart card to avoid confusion when there are two or more cards.

Tacho Bridge Application which is installed on user's computer or server is itself represented as Tacho Bridge App device in flespi while each card connected to it should be registered as Tacho Bridge Card device.

For more information and for setup instructions follow this guide.

Protocol: tacho-bridge Manufacturer: N/A Change log: tacho-bridge

Usage specifics

Parameters (9)

Commands (1)

AI Assistant

Here’s the like of JSON you get

{
    "ident": "352625333222111",
    "position.altitude": 273.61,
    "position.hdop": 0.7,
    "position.latitude": 49.069782,
    "position.longitude": 28.632826,
    "position.satellites": 18,
    "server.timestamp": 1650636570.426424,
    "timestamp": 1650636570.426424,
    "device.type.id": "Tacho Bridge Card",
    "channel.id": 1111,
    "protocol.id": "tacho-bridge"
    "engine.ignition.status": true
    ...
}

How to consume this nice JSON

The easiest way is to make a REST API request like this

curl -X GET  --header 'Authorization: FlespiToken XXX' 'https://flespi.io/gw/devices/<device id>/messages'

Explore REST API Show more ways to consume data How to connect my Tacho Bridge Card to flespi

How to send commands to Tacho Bridge Card?

You can send a specific command. Show all commands

You can also

Modify messages

Add or remove parameters, inject data from LBS and reverse-geocoding services, etc.

Learn what plugins can do

Aggregate data

Determine trips and stops, catch events, detect geofence ins/outs, and more.

Learn about flespi analytics capabilities

Name

Type

Unit

Description

Sources

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

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

Title

Name

Description

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

Tacho Bridge Card

Here’s the like of JSON you get

How to consume this nice JSON

How to send commands to Tacho Bridge Card?

You can also

Modify messages

Aggregate data

More devices from N/A (3)