CAN network planning & termination

01 / GUIDE

Will two devices communicate just because both have CAN?

No. Match the supported bus type, bitrate, message protocol, identifiers and data interpretation. ISO 11898-2 covers the high-speed CAN physical interface, not a universal application message format. A dashboard, ECU or lambda module still needs compatible protocol support or an explicitly supported configuration.

02 / GUIDE

Should every CAN bus measure 60 ohms?

On a conventional high-speed CAN bus with two 120-ohm end terminators present, a suitable unpowered resistance check is typically about 60 ohms. Check topology and built-in termination first. Some MaxxECU GEN2 revisions disconnect their software-controlled resistor when unpowered, so one reading alone is not a universal pass or fail test. Never measure resistance on a live circuit.

03 / GUIDE

CAN Lambda installation checks

Use the exact ECU wiring diagram; verify every circuit for continuity and shorts before connecting power.

Match the CAN speed and sensor address, provide protected heater power, and follow the ECU's CAN termination requirements. Plug-in ECUs may need additional CAN-access cables.

04 / GUIDE

Record the network configuration

Keep a node list with each device model, bitrate, protocol profile, message identifiers and termination location. Record the hardware and firmware revisions alongside the wiring drawing.

Power up a known configuration first. Confirm that the ECU receives plausible data and reports stale or missing messages before enabling control functions that depend on that data.