Tacho Bridge App

Tacho Bridge App is an open-source application for Windows, Mac OS or Linux designed to provide remote authentication of a tracker and tachograph via the company card.

Application is installed on the computer (tacho card hotels supported) and provides an interface between cards inserted into smart card reader and flespi. Whenever the tracker needs to authenticate the tachograph using company card the application will provide such functionality.

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.

Check setup guide for more information.

Protocol: tacho-bridge Manufacturer: Gurtam Change log: tacho-bridge

Usage specifics

Parameters (9)

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 App",
    "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 App to flespi

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

Tacho Bridge App

Here’s the like of JSON you get

How to consume this nice JSON

You can also

Modify messages

Aggregate data

More devices from Gurtam (3)