Protocols

CAN Bus

Vehicle communication protocol for reading data from the vehicle ECU.

CAN Bus (Controller Area Network) is a serial communication protocol developed by Bosch in 1986 that allows electronic components in a vehicle to communicate with each other without a central controller.

How does it work?

In a modern vehicle, dozens of electronic modules (ECU, ABS, transmission, instruments) need to share information. CAN Bus acts as a "data highway" connecting all these modules in a shared network.

Protocols supported by Rinho

Spider IoT and Smart IoT devices support native CAN Bus reading with the following protocols:

  • OBDII: Standard for cars and pickup trucks. Reads RPM, speed, fuel, temperature and error codes.
  • J1939: Standard for heavy trucks (Volvo, Scania, Mercedes-Benz, MAN, DAF). Accesses advanced engine and transmission data.
  • EBS: Electronic braking systems. Monitors air pressure, pad wear and brake status.
  • IESCAN: Protocol for agricultural and industrial machinery.

Data available via CAN Bus

DataAvailability
Engine RPMOBDII, J1939
Real speedOBDII, J1939
Fuel levelOBDII, J1939
Instant consumptionJ1939
Engine temperatureOBDII, J1939
OdometerOBDII, J1939
Engine hoursJ1939
Error codes (DTC)OBDII, J1939

Advantages of native CAN Bus

Unlike external adapters, Rinho's native CAN Bus reading requires no additional accessories. The device connects directly to the vehicle's OBD2 port or diagnostic connector without cutting cables.

Frequently asked questions

Answers to the most common questions about this topic.

It is an internal communication network connecting all electronic modules in the vehicle (engine, brakes, transmission, instruments) allowing them to share data with each other.
No, Spider IoT and Smart IoT devices have built-in native CAN Bus reading. They connect directly to the OBD2 port without external accessories.
CAN Bus is present in most vehicles manufactured after 2008. Heavy trucks use J1939 and cars/pickups use OBDII. Older vehicles may not have an OBD2 port.