Products / TPMS

TPMS on an AGV: nobody walks around this machine

An AGV has no cab and no driver, so the two ways a tyre problem is normally found - a walk-around and a driver's feel - do not exist. The pressure reading has to go somewhere the terminal can watch, and it has to be attached to a machine that nobody stops for a tyre check.

What happens after a power cycle

On an AGV the receiver loses power every time the machine is switched off. Sooner or later every customer asks the same question: after a power cycle, does the tyre data come back on its own, or does somebody have to go and re-pair the sensors?

We tested it on a working machine. All eight wheel readings dropped to zero, then came back without any manual step - the right side first, then the left. The last wheel position returned at about four minutes. No reset, no re-pairing, no operator action.

That is the behaviour you want on equipment that is powered down between shifts: nobody has to remember to check the tyre screen in the morning.

Power cycle on a working AGV: the readings drop to zero, then come back without any manual step. About four minutes to the last wheel position.

Five power-cycle tests, five recovery times

We ran the cycle five times on the same machine, logging at the CAN output (29-bit extended frames, protocol 0x18FDB1D8):

TestTPMS framesLast wheel position has data
11,7045 min 17 s
21,3464 min 18 s
31,5684 min 42 s
41,6854 min 59 s
51,6074 min 26 s

The average is about 4 min 44 s. The spread is not a fault: each sensor keeps its own clock and every transmission carries a random delay, which is what stops the packets from colliding on the air. So "about five minutes" is the honest figure, and a minute either way is normal.

The slowest position was not the same wheel each time - position 31 in runs 1 and 4, position 11 in runs 2 and 3, position 21 in run 5. That is the clearest evidence that this is a scheduling behaviour, not a weak spot on one wheel.

One honest detail about the machine: it has 16 wheel-position slots and 8 sensors fitted (outer position on each axle, inner slots empty). The recovery figure above is for those eight sensors.

FAQ

After a power cycle, does the tyre data come back by itself?
Yes. We tested it on a working AGV: all eight wheel readings dropped to zero and returned without any manual step, the last position at about four minutes. No re-pairing, no operator action.

How long does the recovery take?
On the machine we tested, about four minutes from power-on to the last wheel position reporting. The right side came back first, then the left.

What is different on an AGV

The machine runs fixed routes at low speed, which sounds easier than a road vehicle - and it is easier for everything except the tyre. An AGV carries a fixed load on the same wheels, on the same floor, all shift, so a tyre that is slowly going down changes the handling without changing anything an operator would notice. There is no driver to feel it and no walk-around that would catch it.

The second difference is where the data goes. An AGV is already connected: it has a fleet controller, a route planner and a terminal system. A tyre pressure that lands in its own little app is a reading nobody uses; a tyre pressure that lands in the fleet controller is a maintenance ticket.

What we fit

  • Internal sensors at the hub: on the 120-tonne UHV frame carrier we instrumented, the sensors sit inside the wheel, 12 wheel positions on that machine.
  • Up to 256 wheel positions per receiver - a fleet of AGVs shares one address plan with the terminal's other machines.
  • 0-1400 kPa gauge (100-1500 kPa absolute), accuracy ±7 kPa; internal sensors rated -40 to +125 °C, IP68.
  • Into the fleet controller: CAN 2.0B (11-bit or 29-bit extended frames), RS485 with Modbus RTU, RS232, or PROFINET through a gateway.

Commissioning on an automated machine

The layout question is the same as on any multi-wheel machine - axle drawing, receiver position, repeater positions - but the commissioning step is different: an AGV is usually part of a production line that cannot be stopped for a full day, so the sensor IDs and the wheel-position table are agreed before the vehicle is taken out of service, and the retrofit happens in the terminal's maintenance window.

See the AGV installation page for the machine we instrumented, and port machinery for the wider terminal picture.

FAQ

How many wheel positions does an AGV need?
It depends on the frame: the 120-tonne UHV carrier we instrumented has 12. The receiver handles up to 256, so a fleet shares one plan.
Can the data go into the terminal system instead of a separate app?
Yes. The receiver outputs CAN 2.0B, RS485 with Modbus RTU, RS232, or PROFINET through a gateway, and the message layout is documented.
Do you need to stop the AGV for installation?
It is a retrofit in the maintenance window: sensor IDs and the wheel-position table are agreed first, so the vehicle is out of service only for the fitting.

Tell us the application

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