Products / TPMS

TPMS Integration - What the Platform Receives, and What It Does Not Need

Most TPMS integrations fail on the same point: the platform team is asked to take a proprietary decoder as well as a data feed. This page is about the part we can settle without touching your backend - the packet, the format and what we forward.

Direct answers

  • Raw 8-byte sensor packets can be forwarded over CAN or RS232, so the platform does not need our decoder.
  • Data fields: sensor ID (4 bytes), pressure (0.1 bar), temperature (offset +40), sensor status and battery.
  • CRC is poly 0x07, init 0xFF, no reflection, MSB-first, covering bytes 0-6 - stated as parameters, not as a standard variant name.
  • Standard TPMS message sets can also be delivered as CAN frames, 500 ms period.
  • No NDA is required for the CAN or serial data format; the RF parameters are a separate matter.

1. Two integration modes: transparent vs decoded

Transparent mode forwards the sensor packet as it arrives. The platform receives the 8 bytes and applies its own decoder using the parameters above. Decoded mode sends structured CAN frames - pressure, temperature, status and wheel position already separated - at a 500 ms period. The first mode suits a platform that already has a TPMS decoder; the second suits one that wants values, not packets. Both are the same hardware; the difference is what the receiver forwards.

2-6. Platforms we are working through

1. Wialon

Wialon is on our integration list: we are in the process of integrating. What we can already do is the part that does not depend on their catalogue - forward raw sensor packets or structured frames over CAN or RS232, so your Wialon side does the decoding if you prefer to keep it. What we cannot do yet is point at a published device entry with our name on it, and we will not claim one before it exists.

2. Navixy

Navixy is on our integration list: we are in the process of integrating there as well. What we can already do is the part that does not depend on their catalogue - forward raw sensor packets or structured frames over CAN or RS232, so your Navixy side does the decoding if you prefer to keep it. What we cannot do yet is point at a published device entry with our name on it, and we will not claim one before it exists.

3. flespi

flespi is on our integration list: we are in the process of integrating there as well. What we can already do is the part that does not depend on their catalogue - forward raw sensor packets or structured frames over CAN or RS232, so your flespi side does the decoding if you prefer to keep it. What we cannot do yet is point at a published device entry with our name on it, and we will not claim one before it exists.

4. ThingsBoard

ThingsBoard is on our integration list: we are in the process of integrating there as well. What we can already do is the part that does not depend on their catalogue - forward raw sensor packets or structured frames over CAN or RS232, so your ThingsBoard side does the decoding if you prefer to keep it. What we cannot do yet is point at a published device entry with our name on it, and we will not claim one before it exists.

5. Traccar

Traccar is on our integration list: we are in the process of integrating there as well. What we can already do is the part that does not depend on their catalogue - forward raw sensor packets or structured frames over CAN or RS232, so your Traccar side does the decoding if you prefer to keep it. What we cannot do yet is point at a published device entry with our name on it, and we will not claim one before it exists.

7. What we do not do: we do not host your fleet logic

The platform is yours. We supply the sensors, the receiver and the data contract; we do not host your fleet rules, we do not become your system of record, and we do not need your customer data. If you want a platform instead of an API feed, we can provide one, but it is quoted as its own line and built from your requirement list rather than from a fixed feature sheet.

TPMS telematics: what the gateway actually sends

TPMS telematics: raw 8-byte sensor packets or structured CAN frames, 500 ms period, documented CRC.

On the telematics side the question is not what the sensor can measure but what leaves the machine. In transparent mode the 8-byte packet is forwarded and the platform applies the documented decoder (pressure in 0.1 bar, temperature offset +40, CRC poly 0x07, init 0xFF, no reflection, MSB-first, covering bytes 0-6). In decoded mode the receiver sends structured CAN frames at a 500 ms period. We do not require an NDA for the CAN or serial data format.

TPMS platform integration: packets or values

TPMS platform integration: choose packets (your decoder) or values (our frames), both over CAN or RS232.

There are two integration modes and the choice decides the work: transparent, where we forward the packet and the platform decodes it, or decoded, where we send pressure, temperature, status and wheel position as separate fields. The first suits a platform with an existing TPMS decoder; the second suits one that wants values. Both use the same receiver - only what it forwards changes.

What to send us

Tell us which platform you run, whether you want packets or decoded values, and how often you want them. With those three answers the data contract is usually settled in one exchange - and the format question stops being a blocker for the integration.

FAQ

Can we receive raw sensor packets instead of decoded values?
Yes. Transparent mode forwards the 8-byte packet over CAN or RS232, so your decoder applies the documented parameters (poly 0x07, init 0xFF, no reflection, MSB-first).
Do you require an NDA before sharing the data format?
No NDA is required for the CAN or serial data format; the RF parameters are a separate matter.
Is a device entry already published in these platforms?
Not yet. We are in the process of integrating with each platform listed on this page, and we will say so plainly until an entry exists.

Tell us the application

Send the vehicle, wheel count and where the data must end up. We answer in writing.