Need help? Request a callback Working hours: 9:00 AM – 5:30 PM

Automotive & fleet

Telematics: vehicle data you can rely on.

Our telematics platform reads data from the vehicle’s own bus, keeps it safe when coverage drops, and delivers it to a cloud platform, fleet portal and mobile apps. Designed and built by LIDAVI since 2019.

Talk to usRead the white paper
OBD-II & CANReads standard and heavy-vehicle data
Wi-Fi + cellular + BLEAutomatic failover between links
Never loses dataSD-card buffering and replay
Live fleet viewMap, trails, stats and apps

Capabilities

From the vehicle bus to the fleet portal

Vehicle bus access

OBD-II PID polling, CAN 2.0A/B up to 1 Mbit/s, UDS diagnostics and J1939 for heavy vehicles.

Configurable acquisition

Signals, polling intervals and deadbands set in a JSON file on the device — no firmware rebuild needed.

Trips & fault codes

Automatic trip detection from engine and motion state, and periodic diagnostic-trouble-code scans.

GPS & motion

Location with every record, plus inertial data for driving behaviour.

Resilient connectivity

Wi-Fi preferred, automatic cellular fallback, and Bluetooth LE for onboarding and phone-local data.

Offline buffering

Data is spooled to the SD card during coverage loss and replayed to the cloud on reconnect.

Safe field updates

Bootloader and update path for both controllers, with firmware images served from the cloud.

Fleet portal & apps

Live map with vehicle list and route trail, admin portal, and Android and iOS apps.

Architecture

Two controllers, one job each

The vehicle unit splits responsibilities: one microcontroller owns the vehicle bus, the other owns connectivity and storage. A simple framed serial link joins them. If the network fails, the vehicle side keeps working and nothing is lost.

  • Domain controllerCAN, OBD-II, UDS and J1939; aggregates each signal over a time window.
  • Cloud controllerWi-Fi, cellular and BLE; writes records to SD and publishes over MQTT.
  • Cloud platformMQTT broker, ingest service, time-series database, API, identity and firmware store.
  • Portals & appsFleet portal, admin portal, Android and iOS apps.
Telematics architecture The vehicle's OBD-II and CAN bus connects to the domain controller, which links over UART to the cloud controller. The cloud controller stores data on an SD card and sends it over Wi-Fi or cellular via MQTT to the cloud platform, which serves the fleet portal and mobile apps. Bluetooth connects the device to phones for onboarding. Vehicle ECUsOBD-II · CAN · J1939 Domain controllervehicle bus & diagnostics Cloud controllerWi-Fi · LTE · BLE SD cardoffline buffer & replay Cloud platformMQTT · ingest · time-series DBAPI · identity · firmware store Fleet portal & appslive map · admin · iOS · Android UART link MQTT
Vehicle unit, cloud and apps.

Engineering

Built and documented to last

Systems model

The platform is described in a SysML v2 model, from context and use cases to requirements and verification, maintained in our Blueprint tool.

Decision records

Architecture decisions such as the link protocol, toolchain and offline sessions are recorded as ADRs.

Local test stack

The whole cloud runs locally in containers, with a simulator that publishes vehicle telemetry for testing.

History

Five-plus years of telematics

  1. 2019
    • R&D begins · OBD-II device prototypes.
  2. 2020
    • First generation · two-controller device, MQTT cloud, portals and apps.
  3. 2025
    • Second generation · self-hostable cloud, live fleet map, configurable acquisition.

Use cases

What fleets use it for

Fleet tracking

Live location, trips and route history.

Vehicle health

Fault codes and diagnostic data for maintenance.

Driving behaviour

Speed, acceleration and engine data per trip.

OEM & integrators

Firmware and cloud adapted to your own device or vehicle.

Telematics

Put telematics in your vehicles

Tell us about your fleet or device. We will show the platform and propose a pilot.

Contact usRead the white paper