Run the RDM-7 on Any CAN Bus With a DBC File

Running something nobody has heard of? A one-off controller, a bespoke loom, a race car with a bus somebody else designed? If it speaks CAN, the RDM-7 can display it. You bring the map.

Two ways in, both already in the firmware

• Import a DBC file. If you have the bus definition, load it in RDM Studio and the channels come across.
• Define channels by hand. If you do not have a DBC, you can build channels yourself from the message IDs.

There is also a CAN analyser in Studio that shows you the raw frames on the bus, so you can blip the throttle, watch which ID changes, and bind it to a widget. That is often faster than finding documentation for an obscure device.

What this costs you

Your time, and only your time. There is no extra licence, no unlock, and no charge for the capability. What you give up is that you are the one who knows the message IDs, and we cannot check them for you. Get a scaling wrong and the dash will faithfully show you the wrong number.

It is the last resort that means nobody is turned away, not the path we would send you down if a preset exists for your ECU.

Before you go this way

Check the supported list first — there may already be a preset, which reads more and reads it faster for none of the effort. And if your ECU is common but missing, tell us. Requests decide which presets get built next, and once one exists it reaches every owner over Wi-Fi at no cost.

What you get

800x480 IPS touchscreen, around 50 fps, under 20 ms from bus to screen. Up to 128 CAN channels. Logging to microSD at 1 to 200 Hz in plain CSV, so it opens in Excel or Python. The dash also transmits on CAN, so any on-screen button can send a message to your ECU, a body controller or a relay.

Display, logging and CAN transmit only. The RDM-7 does not tune your ECU.