Products / TPMS
TPMS for PLC integration
Your PLC is the master; our receiver is a node it polls. That is the whole design idea, and it decides every question that follows: which interface is fitted, who starts the conversation, and what the integrator has to write.
Where this fits
Heavy plant, production lines and retrofit projects often already have a control system: a PLC scanning a machine, or a SCADA layer above it. Tyre pressure is one more signal in that system, and the practical question is not the sensor — it is how the receiver presents itself on the bus your controller already uses.
The three ways in
- Serial. RS232 or RS485 on the receiver, polled by the PLC as a Modbus RTU slave. This is the shortest path on machines with an existing serial port.
- CAN. The receiver puts frames on the machine CAN bus and the controller reads them. The frame map is documented, not guessed.
- PROFINET. The receiver stays on RS232 and an RS232-to-PROFINET gateway presents it to a Siemens-style network as a PROFINET device. The gateway is a separate item, quoted separately per project.
Two things to decide before you order
One interface per unit. The receiver is built with one interface — CAN, RS232, RS485 or Modbus RTU — chosen at the factory. If a project needs two paths, that is two units or a gateway, not a setting.
Who is master. In Modbus RTU our receiver is a slave only. Your PLC is the master and starts every read; the receiver does not initiate traffic and cannot act as a master on your network. In CAN and in PROFINET-through-gateway the same logic holds — the node with the control logic owns the conversation.
Register map and scaling
The register map and the scaling for pressure and temperature are documented in the integration note supplied with the unit, and a DBC is available for the CAN variant. We do not publish the register table as a web page because it differs by interface and by project configuration — the document you receive is the one that matches the unit you receive.
What the receiver offers
| Parameter | Value |
|---|---|
| Wheel positions | up to 256 per receiver |
| Interface | one of: CAN · RS232 · RS485 · Modbus RTU — chosen at the factory, one per unit |
| Data period | 10 ms (receiver-to-bus refresh) |
| CAN bitrate | 250 kbps, software configurable |
| Supply | 10–30 V DC |
| Receiver protection | IP68 |
| Pressure accuracy | ±7 kPa |
| Temperature accuracy | 1 °C (error ≤ ±3 °C) |
Gateway as a separate line item
Where PROFINET is required, the gateway is quoted on its own line, not folded into the sensor price. It is an independent part that can be replaced without touching the receiver, and a project with several machines needs its own decision on how many gateways it wants — usually one per machine rather than one per site.
Questions we are asked
Can the receiver act as a Modbus master?
No. Slave only. If your architecture needs a master on that segment, that role belongs to your controller or to a gateway.
Does the receiver have a PROFINET port?
No. PROFINET is reached through an RS232-to-PROFINET gateway. We would rather say that clearly than let a purchase order assume a native port.
How many wheel positions can one receiver handle?
Up to 256. On a typical heavy-plant machine the limiting factor is the radio path and the repeaters, not the count.
Tell us what your controller already speaks
Send the PLC model and the bus you already use on that machine — Modbus RTU, CAN, PROFINET through a gateway, or a serial port that is free. With that we can say which interface to fit and what you would receive. Receiver and sensor range · All configurations · Modbus RTU detail · PROFINET detail
Tell us the application
Send the vehicle, wheel count and where the data must end up. We answer in writing.