For integrators and developers

Build your solution on Rinho hardware

Telematics hardware with an open protocol: read CAN, report to your own server, and integrate it into your platform. No mandatory platform.

View the protocolTalk to our technical team

+200,000

devices across Latin America

2007

designing hardware and firmware in Argentina

16

integrated platforms

TAIP + IPS

open protocol, no mandatory platform

You bring the software. We bring the hardware that integrates.

Rinho manufactures the telematics hardware. The platform, the rules and the alerts are yours: the device measures and transmits, your system decides.

Your platform

Open protocol, no mandatory platform

Devices report to your own server over TAIP or Wialon IPS (TCP/UDP), with redundant destinations. Public documentation and an example UDP server to get the integration running in hours.

See compatible platforms
  • TAIP / Wialon IPS output (TCP/UDP)
  • Reports to your server (AWS IoT Core, on-premise, etc.) with no Rinho-hosted platform
  • Compatible with Wialon, Traccar, Flespi, Cybermapa and 10+ platforms
  • Protocol integration guide and example server included
Vehicle data

CAN profiler: read any signal

Capture up to 29 CAN/J1939 signals with standard DBC formula, including fault codes (DM1, SPN+FMI). Configurable from the browser. And if a proprietary signal resists, we adjust the firmware: we're the manufacturer.

  • Up to 29 configurable CAN signals (DBC format)
  • Standard J1939 PGNs: engine hours, fuel, RPM, temperature, odometer
  • DM1 fault codes (SPN+FMI)
  • Adjustable firmware for proprietary CAN
Tough areas

Connectivity where there's no signal

WiFi and Starlink with no SIM, dual-SIM for redundancy, and store & forward: the device buffers on board and back-fills when the link recovers. Up to ~49,000 records, with a non-volatile buffer that survives power cycles.

  • WiFi client / Starlink (2.4 GHz), no SIM
  • Dual-SIM for redundancy
  • Store & forward: ~49,000 records on board
  • Non-volatile event buffer
In-house design

Buy direct from the manufacturer

Our own hardware and firmware. If a proprietary CAN signal resists, we adjust the firmware for your case. We define volumes, pricing tiers, training and support together.

  • In-house hardware design and firmware
  • Firmware adjustable to your use case
  • Volume and tier pricing
  • Training, warranty and support

Everything you need to integrate

Public technical resources to get started today.

Protocol integration guide

Technical document with everything needed to build the receiver.

Download PDF

Example UDP server

Code on GitHub to get the parser running fast.

View on GitHub

Web configurator

Configure CAN and parameters from the browser over USB.

Open configurator

Datasheets

Technical specs for Spider and Smart IoT.

View products

Technical guides

What you need to evaluate the integration before writing a single line of code.

Firmware 1.09.24 for integrators

Remote DFOTA, LIFO/FIFO engine, Wialon IPS and binary reports.

Read the guide

Send GPS data to your own server

TAIP vs Wialon IPS, a sample UDP receiver and real frame parsing.

Read the guide

J1939: which engine data you can read

RPM, fuel, hours and odometer on heavy trucks, plus custom signals with CXECU.

Read the guide

Wialon IPS protocol on every device

Compatibility with any platform that already speaks Wialon IPS v1.1.

Read the guide

Building on Rinho?

Tell us your use case and we'll help you integrate — or set up a distribution arrangement.

Let's talk