What it does
It reads the vehicle CAN bus and sends the data you choose over 4G (CAT.1). You decide which CAN frames matter and how often they leave the machine; we expose that data to you through an API.
Why our approach is different
We do not ask you for your CAN protocol. The protocol stays with you, defined and held on your side; we work from the data points you expose and hand them back over the API. That is the difference from units that require you to release your CAN definitions first.
What you get
- Change-triggered upload plus scheduled wake-up — the unit reports when something changes instead of streaming everything.
- Remote parameter tuning — CAN bitrate and sample points can be adjusted remotely, so one unit can serve different machine models.
- A/B dual-partition FOTA with resume and automatic rollback on failure.
- MQTT over TLS with mutual authentication and hardware-level encryption.
- GPS + BeiDou positioning, with geofence support.
- CAN pass-through firmware upgrade for an attached ECU / VCU (custom).
What we do NOT need
We do not need your CAN protocol document, your DBC file or your ECU source. You keep the definitions; we only need the list of data points you want reported and where they should go.
Tell us what data you need
Tell us what data you need — we reply within one business day.