A receiver when you want the data somewhere other than a phone The sensor does not need one. But if your product needs the reading in its own controller or on its own screen, we build that too.
Discuss a receiverThree ways to get the data out
Which one is right depends entirely on where the reading has to end up. If it is going to a rider's phone, you need none of these.
Phone app only
The sensor pairs directly with the app. Lowest cost, nothing to install, nothing to wire. The right answer for most two-wheel and retrofit applications.
Into your own controller
A receiver with a serial (UART) or CAN output that your own ECU, display or telematics unit reads. We will scope the protocol with you.
Standalone display
A display we build to your specification, for vehicles where the driver should not be looking at a phone.
Interface options
| TR-100R-UART | Serial output receiver, for controllers and displays that expect a UART stream. |
|---|---|
| TR-100R-CAN | CAN output receiver, for integration into a vehicle network. |
| Display | A standalone display, scoped per programme. |
Availability, stated plainly. The receiver is an optional item we build to order, not an off-the-shelf part with a stock number. Timelines depend on the interface and enclosure you need, and we will give you a written estimate rather than a guess.
If your project needs long-range reception and bus integration, our industrial 433.92 MHz range on gzvia.com is the better starting point.
Want samples or a specification for your programme?
Tell us the vehicle, wheel count, where the data should go, and the label language for your market. We answer in writing.