Code
P1905
LAND ROVER
P — Powertrain
Control module configured for end-of-line test mode
Views:
UK: 10
EN: 110
RU: 19
AI status
Completed
Completed
100%
Causes
- Module left in factory/end‑of‑line test mode after assembly or service
- Incomplete or interrupted module programming or calibration
- Corrupt or incorrect module coding (wrong part number or VIN mismatch)
- Software defect or failed update that sets test flag
- Lost or incorrect non‑volatile memory data (NVM) in module
- Battery disconnection or voltage event during programming
Symptoms
- MIL / warning indicator illuminated (may be manufacturer‑specific message)
- Limited or disabled functions controlled by the affected module
- Related systems (CAN devices) showing communication or missing module errors
- Vehicle may enter limp mode or show degraded performance (depending on module)
- Service message at start-up indicating module configuration required
What to check
- Retrieve and record all current and historic DTCs and freeze frame data from the affected module
- Check module identity: part number, software/calibration level, VIN stored in module
- Inspect recent service history for programming or module replacement
- Confirm battery voltage is stable (use known good battery or charger during diagnostics)
- Check CAN and power/ground circuits for the module for proper connectivity
- Attempt to clear code and re‑scan to see if code returns immediately
Signal parameters
- Module test_mode_flag (EOL/test mode status)
- VIN programmed in module
- Module software/calibration part number and version
- Power supply voltage (VBatt) at module
- CAN bus communication status and message counts
- Ignition cycle counter and module uptime
Diagnostic algorithm
- Read and save all DTCs and freeze frame data from the affected control module and related modules.
- Verify vehicle battery voltage is within specification and stable; connect battery charger if necessary.
- Check module part numbers, software level and VIN stored in module for mismatches or obvious errors.
- Attempt to clear the DTC. If it does not return, perform functional tests to confirm normal operation.
- Use the appropriate manufacturer diagnostic tool to read the module configuration mode or EOL/test flag.
- If module is in EOL/test mode, follow manufacturer procedure to exit test mode: perform module coding/parametrization or run the EOL exit routine.
- If programming previously failed or was interrupted, reflash or recode the module with the correct software and VIN using the dealer-level tool.
- Recheck for related communication codes (U‑codes) and repair any CAN/power/ground issues before reprogramming.
- After successful configuration/reflash, clear DTCs, cycle ignition per procedure and verify code does not return during road test.
- If the module still reports test mode after correct programming and wiring checks, consider replacing the control module following OEM replacement and coding procedures.
Likely causes
- Module never configured from EOL/test state to production state
- Interrupted reflash or module programming session
- Wrong calibration or parameter set loaded into module
- CAN communication errors prevented successful module configuration
- Replacement module installed but not coded to vehicle
Fault status
Status
Control module configured in end‑of‑line (EOL) / test mode. Module must be configured/coded to production state or reprogrammed to restore normal operation.
Repair difficulty: Medium
Diagnostic time: 0.5-3.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
1
Send to email