C0068

Code

Generic C — Chassis

Chassis Control Module Communication Fault

Brand: Generic

Type: C — Chassis

Views: UK: 6 EN: 11 RU: 9

AI status

Completed

ready

Completed 100%

Page language: EN

Causes

Open, short or intermittent wiring on the communication bus (CAN/LIN) to the chassis control module
Poor or missing power/ground to the chassis control module
Corroded or loose connector pins at the module or gateway
Failed chassis control module
Related module(s) not responding or pulling the bus down
Blown fuse or failed power distribution to the module

Symptoms

ABS/traction/stability warning lamp(s) illuminated
Loss of features controlled by chassis module (stability control, traction control, hill assist)
Intermittent or constant communication-related fault codes visible with a scan tool
Reduced drivability or safety system disablement
Multiple communication-related DTCs present (U-codes or other C-codes)

What to check

Read all stored and pending DTCs and freeze frame data with a capable scan tool
Check for related U-codes indicating network-wide problems
Inspect fuses and power distribution related to chassis control module
Perform a visual inspection of module connectors and wiring for corrosion, damage, or loose pins
Verify battery voltage is within specification during key on/engine running
Use a scan tool to check if the chassis module is present and responding on the network

Signal parameters

CAN recessive voltage: ~2.5 V on both CAN High and CAN Low with key ON (no dominant bits)
CAN dominant state: CAN High ~3.5 V, CAN Low ~1.5 V during communication bursts
Bus idle: low error frame count, stable voltages near 2.5 V
Message frequency: module transmitters typically 1–50 Hz depending on message (verify expected IDs and cycle times from manufacturer data)
Termination resistance: approximately 60 ohms across CANH and CANL with system powered off
Observed symptoms: high error counts, frequent error frames, missing message IDs, or long message intervals indicate bus issues

Diagnostic algorithm

Record current DTCs, freeze frame, and perform a full network scan to identify additional codes (U-codes, other C-codes).
Check battery voltage and charging system; ensure stable supply during diagnostics (>12 V).
Inspect fuses, power and ground circuits for the chassis control module; repair any faults and verify voltages at the module connector.
Perform visual inspection of module connectors and harness for corrosion, water ingress, damaged wires, or loose pins; repair as required.
Using a scan tool, verify whether the chassis control module is present on the network and whether expected messages/IDs are active. Note message rates.
If module is absent or messages missing, check CANH/CANL voltages at the module with key ON using a multimeter; then use an oscilloscope to verify waveform integrity and dominant/recessive transitions.
Measure termination resistance across CANH/CANL with the system powered off; confirm ~60 ohms. If incorrect, trace to find missing/shorted terminator.
Perform a wiggle/pressure test on wiring and connectors while monitoring for code changes to find intermittent faults.
Isolate segments: disconnect downstream modules or branches to locate faulted section. If a single module causes the bus to fail, disconnect it to confirm.
If wiring and power/ground are good but communication still fails, update or reflash module software if available and verify configuration. Consider swapping with a known-good module only after confirming wiring/power are correct.
After repairs, clear codes and road-test while monitoring the network to confirm the fault does not return.

Likely causes

Damaged CAN high/low pair near module or junction connector
Bad chassis module ground or battery supply (low voltage events)
Faulty gateway or another module causing bus error frames
Connector corrosion at module or harness splice
Aftermarket device tied into bus causing faults
Intermittent wiring fault that appears under vibration

Fault status

⚠️ Status

Chassis control module communication fault detected — module messages missing or bus errors present.

🟡 Repair difficulty: Medium

⏱️ Diagnostic time: 0.5-2.0 hours

Similar codes

Your experience will help others

+100 karma for a short comment :)

Was this AI description helpful?

Your feedback helps improve AI descriptions.

👍 Like 0 👎 Dislike 0

Send to email