Productos / TPMS
PROFINET TPMS — through a gateway, stated plainly
Our receiver does not have a PROFINET port. PROFINET is reached through an RS232-to-PROFINET gateway, which is a separate item quoted on its own line. Writing it this way now saves a commissioning argument later.
The honest architecture
sensors --433.92 MHz--> receiver --RS232--> gateway --PROFINET--> your PLC
The receiver is unchanged: it does what it does on any other machine. The gateway is the part that speaks PROFINET, and because it is a separate part it can be swapped, upgraded or replaced without touching the tyre system.
Why we say it this way
It is easy to write "we support PROFINET" and let a buyer assume a native port. That assumption survives the quotation, the purchase order and the shipping, and then meets reality on the first commissioning day — usually with the integrator standing in a plant that is already behind schedule. A gateway in the bill of materials is cheaper than that conversation.
What a project needs
- One receiver with the RS232 interface fitted at the factory.
- One RS232-to-PROFINET gateway, quoted separately, one per machine in the usual case.
- Your PROFINET side: the gateway appears as a PROFINET device that your PLC configures like any other. Network planning, addresses and segment layout stay with you.
- The register/IO mapping: supplied with the gateway and the receiver's integration note, so the two halves are documented against each other rather than assumed.
When a gateway is the wrong answer
If the machine has a free CAN port, CAN is simpler — no extra part, no extra failure point. If the PLC has an RS485 port, Modbus RTU is simpler for the same reason. The gateway exists for networks that are PROFINET-first and will stay that way. We will say which case yours looks like rather than sell the extra part by default.
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) |
Questions we are asked
Is PROFINET built into the receiver?
No. It is reached through the RS232-to-PROFINET gateway. The receiver offers one interface of CAN, RS232, RS485 or Modbus RTU, chosen at the factory — for this architecture it is RS232.
How many gateways does a fleet need?
That is a project decision, and it is usually one per machine rather than one per site, because each receiver has its own serial link. Tell us the machine count and we will lay out the options rather than quote a number blind.
What does the gateway cost?
It is quoted separately per project as its own line item. We do not fold it into the sensor price because it is a different part with a different lifetime.
Send the PLC model and the existing network
Tell us the controller (Siemens or otherwise), whether the segment is PROFINET already, and the machine count. We will reply with the architecture, the parts list and what documentation you would receive. Receiver and sensor range · All configurations · PLC integration · Modbus RTU
Tell us the application
Send the vehicle, wheel count and where the data must end up. We answer in writing.