Resources / Application

224 Wheels on One Screen: What a TPMS Has to Do

· 6 min read

The screen is the easy part

Putting 224 wheel positions on one display is ordinary interface work: lay out the tiles, group them by axle, decide what colour a 20 kPa drop should be. No front-end developer calls that the hard half.

The hard half is not on the screen. It is 224 radio links that have to close through a steel chassis, 224 identities that have to stay correct after every tyre change, and a repeater layout decided from a drawing before anyone climbs under the machine. At 224 positions those three decide whether the project works.

What the industry ships, and what 180 actually counts

Most off-the-road tyre pressure systems are specified around 24 to 36 wheel positions per vehicle. That is not an accident: it matches the way a truck, a wheel loader or a reach stacker is built.

The larger published figures come from multi-trailer combinations: a transceiver on each trailer, daisy-chained back to a common network, with the totals adding up along the train to 180. But the number describes the network, not the radio link. Every hop is still short and every trailer still has its own box, so the radio problem per link stays small while the integration problem grows with the trailer count.

We go the other way: one machine, 224 wheel positions on one screen, with 256 wheel positions per receiver as the addressing ceiling. Capacity is not what limits the design, and even so the number is earned in the field, not printed on a page.

224 is 28 axles of eight

224 is not a round number chosen for a brochure. It is 28 axles at eight wheels each — the shape of a beam carrier or a large modular trailer on a heavy haul route.

The 160-wheel, 20-axle beam carrier in our reference installation is the smaller sibling: twelve repeaters along the frame, with the wheel positions split across two receivers, each reporting its own group. The cab screen presents the machine as one list, because that is the granularity an operator can act on; underneath, the radio and addressing work is segmented.

Problem one: identity has to survive the machine, not the install

On a six-wheel machine a sensor is a sensor. On a 224-wheel machine the sensor is a data record.

Every position needs a number fixed before the first sensor goes on and unchanged for the life of the vehicle: which end counts as axle one, side defined by the direction of travel rather than a fitter's left hand, inner and outer on a dual or eight-wheel axle. Then a written replacement procedure, because a tyre fitter will swap a sensor and the map has to survive it.

The failure is quiet and expensive. Two positions swapped in the record, and the display reports a hot tyre on the axle that is fine while the axle that is not fine shows nothing. Nobody finds that by reading the screen; they find it in the file. Addressing is an address space of 256 positions; a wheel map is a document agreed, written down and handed over with the machine.

Problem two: repeater placement comes from the axle drawing

"How many repeaters for 224 wheels" has no answer, and a supplier who quotes a ratio is guessing.

At 433.92 MHz the signal behaves much like light: it travels well in air and poorly through steel plate, axle housings, hydraulic runs and cargo. Twenty-eight axles occupy a length a rigid truck would use for four, so positions sit in each other's radio shadow, and the shadow moves when the load changes. Repeaters go where one zone's data can reach the next, and the zones are cut by structure rather than by the wheel count.

That is why "one repeater every four axles" is wrong in both directions: it over-specifies a compact trailer and under-specifies a long carrier. The plan starts from the axle drawing — spacing, electrical cabinet, tank, and the mounting points the vehicle design permits — and is verified position by position before the machine leaves. It is the method behind the twelve repeaters on that 160-wheel carrier, and the same logic on XCMG, ZOOMLION and SANY port and construction machines.

Problem three: refresh period against the bus ceiling

A position reporting every 500 ms is a frame every 500 ms. At 224 positions that is 448 frames a second before anything else shares the bus. On a 250 kbps CAN network with 29-bit identifiers that is roughly a quarter to a third of the bus — fine until the machine controller wants to send its own messages.

The trade-off is not "buy more bandwidth". It is deciding which positions need the short period. Load-bearing axles on a loaded move deserve the fast cycle; a spare group on a parked machine needs a trend, not a 500 ms sample. The default period is 500 ms and it is configurable per group; that setting belongs to the layout, not to the final checkbox. Getting it wrong looks like a sensor fault and is a bus-planning fault.

The numbers the system has to hold

ItemValue
Pressure0–1400 kPa gauge (100–1500 kPa absolute), ±7 kPa
Temperatureinternal sensor −40 to +125 °C; external sensor −20 to +85 °C
Wheel positionsup to 256 per receiver
Radio433.92 MHz, licence-free
SealingIP68
InterfacesCAN 2.0B (11-bit or 29-bit extended frame, the 29-bit form carrying J1939-format messages), RS485 with Modbus RTU, RS232, PROFINET through a gateway
Internal sensor bandsteel band cut to the rim circumference: 1650 mm is the most common truck and bus length, 2500 mm has been supplied where the rim was larger, and any length is a cutting step rather than a development
Certification statusCE in progress

Three questions before a repeater count is real

1. The axle and wheel-position drawing. Not the total — the layout, with axle groups and the tyre type on each. A total gives the scale; the drawing gives the radio zones.

2. Where a receiver and a repeater are permitted to sit, and who signs that off. The usual places are the gooseneck, the first axle group or a deck edge. A radio-perfect mount the design authority will not allow is not a mount.

3. Which controller the data goes into. CAN into the machine controller, RS485 to a PLC, RS232 to a gateway, or a cab display — the outlet is a specification decision, and it changes the harness and the alarm semantics, not the sensor.

Worth adding the environment: a mining truck and a port machine are hostile in different ways, and IP68 buys protection from water, not from impact.

What to send

The useful conversation is not about sensors. Send the axle layout, the wheel count, where your controller sits and the environment, and the answer comes back as a repeater plan, a wheel-map structure and a commissioning procedure, with the hard radio sections called out honestly.

The figures above come from machines we have built. How we handle multi-axle TPMS explains the range, the beam carrier installation documents a delivered 160-wheel machine, and the repeater planning note covers the geometry. The same radio argument applies to larger tyres on mining trucks, and the interface range is on the products page. Send us the axle layout and we will tell you the repeater count for that machine.

← All articles