The RM-Primis ECU broadcasts its engine and vehicle data on the CAN bus, so dashboards, data loggers, power distribution modules (PDMs), telemetry and any other CAN device can read it. The protocol is open: download the DBC file or the Excel protocol sheet below and load it into your device.
It works with AiM dashboards, ECUMaster ADU, Haltech IC7, Racepak, CANchecked, RealDash, motorsport data loggers, custom Arduino or STM32 projects and CAN gateways: any device that can decode standard CAN frames.
How CAN works, in short. CAN is a two-wire network (CAN-H and CAN-L, a twisted pair) that every device on it shares. Each device sends short messages of up to 8 bytes, each with an ID that says what it is, and every other device hears every message and keeps the ones it is interested in. The ECU sends its data as a set of messages with known IDs; a dashboard that knows the protocol picks out rpm from one message, coolant temperature from another, and so on. The DBC file is that knowledge in a standard form: which ID holds which value, in which bytes, with which scaling.
| File | Use it for |
|---|---|
| DBC file | Dashboards, loggers and CAN analysis software that read DBC files |
| Excel protocol sheet | A readable reference: CAN IDs, byte layout, scaling, units and signal descriptions |
Open Setup → CAN bus → Broadcast. The bus speed and termination are on Setup → CAN bus → Settings.
The ECU sends two groups of messages:
| Group | Rate | What they carry |
|---|---|---|
| 50Hz messages (Base + 0x00 to 0x0F) | Every 20 ms | Fast engine data: rpm, MAP, throttle, lambda, ignition, injection, boost, speed and more |
| 10Hz messages (Base + 0x10 to 0x1F) | Every 100 ms | Slower data: temperatures, pressures, fuel used, status and more |
Base CAN ID is the identifier of the first message; each following message takes the next ID:
| Base CAN ID | Base + 0x00 | Base + 0x01 | Base + 0x02 |
|---|---|---|---|
0x600 |
0x600 |
0x601 |
0x602 |
Choose a base ID that does not clash with other devices on your bus. Switch on only the messages your devices use, to keep the bus traffic low. The ? beside each message in RM-Tuner shows what it carries, byte by byte.
Some messages are reserved for future firmware features and may not carry data yet.
RM-Tuner's CAN bus → Analyser shows the frames on the bus, to check what the ECU and the other devices are sending.
A worked example. A dash shows the engine speed, the coolant temperature, the lambda and the oil pressure. Engine speed and lambda are in the first 50 Hz message, coolant temperature in a 10 Hz message, and the oil pressure from an analog input in the analog inputs message: switch on those three messages, import the DBC, and map the four values to the dash's gauges.
From this page: primis_can_protocol.dbc. The Excel sheet has the same protocol in a readable form.
Check the bus speed matches, the bus is terminated at both ends, the messages are switched on in Broadcast, and the dashboard uses the same base ID.
Contact customer support at [email protected].
Related pages: CAN bus gear gauge · 8HP CAN bus and transmission · Wiring diagram