SPN 5606 FMI 20: Meaning and Fix
SPN 5606 FMI 20 indicates the Adaptive Cruise Control Readiness Status parameter has drifted abnormally high, transitioning into an error condition (10b) that prevents the cruise control system from accepting ACC controller commands despite being otherwise configured. This fault commonly appears after replacing or reprogramming a vehicle’s ECM without properly recalibrating ACC network parameters, or following a CAN bus wiring fault that corrupts readiness status signals transmitted over the PGN Cruise Control/Vehicle Speed 3 frame.
Common Symptoms
- ACC System Disabled: Adaptive cruise control becomes completely inoperative; driver notices inability to engage following-distance or speed-holding functions.
- Cruise Control Lockout: Standard cruise control may remain functional but ACC-specific commands from the radar controller are entirely rejected by the ECM.
- Dashboard Warning Illumination: ACC or cruise control warning indicators activate on the instrument cluster, accompanied by a driver information system alert message.
- CAN Bus Fault Logging: Telematics and fleet management systems log repeated J1939 PGN readiness status anomalies, indicating persistent signal integrity degradation.
Probable Causes
- ECM Software Misconfiguration: Incorrect ACC parameter encoding after ECM reflashing causes the readiness status bit to report erroneous high-state condition persistently.
- CAN Bus Signal Corruption: Damaged or improperly terminated CAN-H/CAN-L wiring induces bit-level errors that shift the readiness status byte above valid thresholds.
- ACC Radar Controller Fault: Failing adaptive cruise radar module transmits malformed readiness request frames, causing the ECM to detect a data-drifted-high error condition.
- Defective Vehicle Speed Sensor: Erratic vehicle speed signal feeding Cruise Control/Vehicle Speed 3 PGN corrupts readiness parameter calculations inside the ECM logic module.
Advanced Technical Analysis
The ECM continuously monitors the two-bit readiness status field within SPN 5606 against valid states: 00b (Off), 01b (On), and 10b (Error). FMI 20 triggers when the decoded parameter value drifts and stabilizes above the expected operational range without returning to a valid state within a manufacturer-defined debounce window, typically 500 milliseconds per Bosch EDC17 calibration tables. This microcontroller-level comparison runs each CAN receive interrupt cycle, flagging persistent high-state drift as a confirmed diagnostic fault.
Electrically, FMI 20 data-drifted-high faults in J1939 networks are often linked to CAN bus termination resistor failures or shield grounding discontinuities. A missing 120-ohm termination resistor causes signal reflections that distort binary-encoded status bits, pushing decoded values artificially high. Technicians should measure CAN bus differential voltage under load, expecting 1.5V to 2.5V differential; values consistently above 3.0V indicate line integrity issues. Debouncing timers inside the ECM prevent transient reflections from triggering false faults, so a confirmed FMI 20 implies sustained electrical anomaly.
Upon confirming SPN 5606 FMI 20, modern ECMs implementing SAE J1939-based safety architectures immediately assert an ACC inhibit flag, preventing any torque or braking modification commands from the adaptive cruise controller. Mercedes-Benz Actros and MAN TGX platforms additionally engage a limp-home cruise strategy, maintaining basic fixed-speed cruise availability while disabling radar-linked following-distance control. This fallback protects drivetrain components from conflicting torque demands that could arise if a corrupted readiness signal allowed simultaneous competing control inputs from both standard and adaptive cruise modules.
Long-term diagnostic strategy requires logging SPN 5606 readiness parameter values using an SAE J1939-compliant diagnostic tool across multiple ignition cycles. Technicians frequently encounter this fault on vehicles returning from independent workshops where ECM reprogramming was performed without updating ACC variant coding. Verified repair procedures include recalibrating ACC system parameters using manufacturer-specific tools such as MAN-cats or Mercedes-Benz Xentry, followed by a complete CAN network topology inspection. Preventive maintenance should include annual CAN bus resistance checks and ACC radar sensor mounting torque verification per OEM service intervals.
Step-by-Step Troubleshooting Guide
- Read Live J1939 Data: Connect a J1939-compliant diagnostic scanner and monitor SPN 5606 readiness status bits live across multiple ignition cycles to confirm drift.
- Inspect CAN Bus Wiring: Measure CAN-H and CAN-L differential voltage and resistance; verify 120-ohm termination at both network endpoints per SAE J1939-11 specification.
- Verify ECM Variant Coding: Use OEM diagnostic software to confirm ACC system variant coding matches vehicle specification; recode if post-ECM replacement parameters were not transferred.
- Test ACC Radar Module: Substitute a known-good ACC radar controller and verify SPN 5606 returns to valid 01b state, confirming or eliminating the radar module as fault origin.