Heavy equipment OEMs
Front-fit TPMS on new machines, with your protocol and your connector.
Every tire on every machine, one system
We are an industrial TPMS manufacturer: we design and build the entire chain in-house — sensors, receivers, repeaters, displays, CAN Bus DTUs and the 4G cloud platform. Connect your system to CAN, J1939, RS485, PROFINET, RS232 or Modbus, or use the DTU to put the whole fleet online with no custom wiring.
TPMS for the tyres. Telematics for the machine.
We supply either turnkey systems or the sensing hardware on its own. Most of our work is behind someone else's brand.
Front-fit TPMS on new machines, with your protocol and your connector.
Rigid and articulated haul trucks, wheel loaders, high-temperature duty.
RTG cranes, reach stackers, container handlers and stackers.
Depot-level monitoring across buses, trucks and trailers.
Commercial vehicle platforms that need tire data on the vehicle bus.
Documented protocol for your own controller, PLC or VCU.
Private-label kits and regional distribution programmes.
Battery-powered sensing nodes with 4G backhaul and an open API.
Most TPMS projects fail at the interface, not at the sensor. Tell us which controller has to receive the data and we build the chain around it.
An integrated receiver with CAN / J1939, RS485, Modbus RTU, Profinet or RS232 output. The controller reads tire data like any other node — no second display, no separate system.
The same receiver plus a 4G DTU becomes a connected unit reporting to a cloud dashboard: fleet overview, alarms, history per vehicle, and an open API into your own platform.
Up to 256 wheel positions on one vehicle with repeaters along the chassis. Delivered on a 160-wheel beam carrier; the largest machine we have instrumented carries 224 wheels.
One 433.92 MHz sensor platform, five ways to get the data where it is needed — from a standalone cab display to raw CAN-bus output for your own platform.
7" colour LCD, every tire at a glance, Bar/PSI and °C/°F switchable. Delivered on a 224-tire installation.
No display of its own — feeds tire data into your CAN bus, PLC, VCU or host display. Documented protocol for second development.
Live tire data in an App or PC platform, plus vehicle tracking, route history and anti-theft. Up to 42 tires per unit.
Beyond turnkey systems we supply sensing hardware on its own — for dashboard makers, integrators and IoT programmes that build their own product around it.
BLE 5.1 pressure and temperature sensor for motorcycle and light-vehicle dashboards. Pairs straight to CarPlay head units; CR1632 replaceable without re-pairing.
Component details →Battery-powered sensing nodes with 4G Cat.1 backhaul and an open API — door, temperature, humidity and vibration variants.
Platform details →Slow leaks, under-inflation and overheating cost more than tires — they cost uptime. Our systems watch every wheel and report where your operators already look.




Pick the duty that matches your machines, or go straight to the machines themselves.
Sensor, receiver, repeater, display and the cloud platform are all developed by our own hardware and embedded software team — so a change request never bounces between suppliers.
Protocol, enclosure, display UI, API and cloud dashboards can be adapted. Interfaces include CAN, RS485, Profinet, RS232, Modbus RTU and BLE.
In service with city bus fleets, port machinery and 160-wheel beam carriers. Industrial grade: IP68, −40 ~ +125 °C.
Sensor, receiver, repeater, display and cloud are all ours — a change request never bounces between suppliers.
Repeaters along the chassis extend coverage; delivered on a 160-wheel carrier, proven to 224 wheels.
CAN 2.0B, J1939, RS485, RS232, Modbus RTU, PROFINET and an open REST API.
Our own platform, running live fleets — not a third-party reseller arrangement.
28 axles × 8 wheels instrumented on a single machine.
Protocol, enclosure, display UI, API and packaging to your specification.
City bus fleets, port machinery, and 160-wheel beam carriers.
How tire data actually gets into a controller, and what we learn doing it.
A farm tyre runs on a hard road and in soft soil the same day, and the right pressure is not the same for both. Agricultural machinery is where that difference is largest - and where the site usually has no mobile network to fall back on.
"29-bit is not a marketing detail. It decides which filters your controller needs, whether your tool sees the frames, and where the mapping work lands."
The sentence that stops telematics projects is "we need your CAN protocol". Here is why we never ask, what we ask for instead, and four ways customers use it.
Send the wheel count, operating voltage and which controller should receive the data. We reply with a wiring plan, a sensor count and a quote.
Not just sensors. A working chain from the valve stem to the screen or the vehicle bus: sensors, receivers, repeaters, displays, gateways and the cloud platform — plus the protocol documentation your engineers need to integrate it.
Up to 256 wheel positions per receiver. Beyond that, or on very long chassis where the radio path is blocked, we add repeaters along the machine — a 160-wheel beam carrier uses 2 receivers and 12 repeaters.
Yes. The receiver publishes tire pressure, temperature and alarm data onto CAN 2.0B, and we supply the message map (DBC) so your controller, PLC or VCU can read it like any other node. J1939, RS485, RS232, Modbus RTU and PROFINET are also available.
That is our core market. We have instrumented rigid and articulated haul trucks, RTG cranes, reach stackers, container stackers and beam carriers, and we supply port machinery builders under their own brand.
The largest machine we have instrumented carries 224 wheels (28 axles × 8). The next size down in production is a 160-wheel bridge girder transporter.
Yes — that is most of what we do. Protocol, enclosure, display UI, cloud API, packaging and label language can all be adapted. Certification is scoped per target market as part of the programme.
Internal sensors −40 to +125 °C, external sensors −20 to +85 °C, IP68, 433.92 MHz licence-free radio, accuracy ±7 kPa (433.92 MHz) on pressure and ±3 °C on temperature.
Yes. We start with evaluation units and the pairing or protocol documentation so your technical contact can test against your own devices, then move to a pilot order.