Toggle Side Panel

Shopping Cart

No products in the basket.

Shopping Cart

No products in the basket.

Close search
Home / DTC / C1A35 — Chassis Control Module — Internal Configuration Fault

C1A35 — Chassis Control Module — Internal Configuration Fault

Detailed page for trouble code C1A35.

34,571codes
59brands
11,925generic
22,646specific
All codes P-codes (Powertrain) B-codes (Body) C-codes (Chassis) U-codes (Network/User) Tesla Alerts
Reset
Code

C1A35

LAND ROVER C — Chassis

Chassis Control Module — Internal Configuration Fault

Brand: LAND ROVER
Type: C — Chassis
AI status
Completed
ready
Completed 100%
Page language: EN

Causes

  • Corrupted or invalid module configuration data (EEPROM/flash).
  • Failed internal memory, processor or software fault inside the CCM.
  • Interrupted or failed software/update (incomplete reflash).
  • Power supply event (low battery, surge) that corrupted module data.
  • Poor ground or intermittent supply causing configuration validation failures.
  • Water ingress or physical damage to the module housing or connector.

Symptoms

  • ABS, ESC or traction/stability warning lights illuminated.
  • Loss or restriction of chassis-related features (e.g., ABS, DSC, adaptive suspension).
  • Instrument cluster message indicating module fault or service required.
  • Possible fault memory with multiple related CAN communication codes.
  • Symptoms may be intermittent depending on power/communication conditions.

What to check

  • Read all stored DTCs and freeze frame data using a JLR-approved diagnostic tool (Pathfinder/SDD or equivalent).
  • Verify vehicle battery voltage and condition; ensure >12.4 V during diagnosis and programming.
  • Inspect CCM connector and wiring for corrosion, bent pins, damage or water ingress.
  • Check fuses and power/ground circuits to the CCM for proper voltage and resistance.
  • Confirm other modules on CAN bus show normal communication (no gateway errors).
  • Check module part number, hardware and software/calibration IDs against vehicle build data.

Signal parameters

  • CCM supply voltage (VBatt) and ground integrity
  • CCM internal temperature (if available)
  • Software calibration ID / part number reported by CCM
  • Configuration checksum or CRC status (if reported)
  • CAN bus alive messages from CCM and gateway
  • Diagnostic session status (programming active/inactive)

Diagnostic algorithm

  1. Connect a recommended manufacturer diagnostic tool and record all DTCs, freeze frame and module information (hardware/software IDs).
  2. Verify battery state of charge and charging system; if low, charge or connect a stable power supply before further testing.
  3. Inspect CCM connector and harness for damage, corrosion or water entry; repair any issues and retest.
  4. Confirm proper power and ground at the CCM with a multimeter; check for intermittent voltage drops with key cycles.
  5. Check CAN bus integrity: verify termination, continuity and observe traffic with a diagnostic tool or oscilloscope; rectify any bus/connector faults.
  6. Compare CCM software/calibration ID to vehicle build and other module data. If software mismatch or missing configuration is identified, perform reflash/reload of correct calibration using manufacturer tooling.
  7. If a software reflash fails or reports memory errors, attempt a reprogram/reinitialize per manufacturer procedure. Follow required steps exactly (battery support, tool versions, sequence).
  8. After reprogramming, clear DTCs and perform full road test and function checks for chassis systems. Re-scan for return of code.
  9. If code persists after correct software update and verified power/CAN, consider module replacement. When replacing, ensure correct part number and perform required module coding/configuration to match vehicle.
  10. If replacement is performed, follow manufacturer pairing/coding and confirm all linked modules/gateway accept the new CCM; re-check for related codes.

Likely causes

  • Corrupted calibration or configuration after a failed software update.
  • Battery went flat or was disconnected during module programming.
  • Module part number/software level does not match vehicle gateway data.
  • Damaged internal memory (EEPROM/flash) or processor fault.
  • Poor battery voltage or bad ground at module connector.
  • Water or corrosion on module connector pins causing intermittent faults.

Fault status

⚠️ Status
Chassis Control Module — Internal Configuration Fault (module detected invalid/corrupted configuration or failed internal validation).
🟡 Repair difficulty: Medium
⏱️ Diagnostic time: 1.5-3.0 hours

Similar codes

C1A36 C1A30 U0100 U0415 P0606 U0422
413

Browse 413 LAND ROVER manuals: repair procedures, diagnostics, wiring diagrams, component locations, service data and Labor Times by year, model and trim.

LAND ROVER

Your experience will help others
+100 karma for a short comment :)
Keep it short and practical. Up to 500 characters.
Send to email

Report

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts
  • Invite this member to groups
  • Message this member
  • Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Report

You have already reported this .