Create Account
for Discounts / VAT
for Discounts & Correct VAT
Land Rover Fault Codes Explained: How to Diagnose at Home
Land Rover fault codes are the starting point for diagnosing almost any warning light or drivability problem on a modern Land Rover or Range Rover. When the engine management light, transmission warning or suspension fault indicator appears, the ECU has logged a diagnostic trouble code that describes which circuit or system triggered it. Reading that code takes less than five minutes with the right cable or tool, and it tells you where to look before spending money on parts. This guide explains how fault codes work, which diagnostic cable or tool you need for your model, how EOBD applies to Land Rover and Range Rover, and how to interpret what you find.
Key points
- EOBD applies to Land Rover petrol engines from 2001 and diesel engines from 2004 onwards
- Td5 Defenders are not EOBD compliant and require a dedicated platform such as the Nanocom Evolution or Hawkeye. The GAP IIDTool does not support the Td5
- A generic OBD2 reader reads basic powertrain codes; the GAP IIDTool reads Land Rover proprietary modules including ABS, airbag and suspension systems
- Circuit range and rationality codes often point to a wiring or connector fault, not a failed component
- Always read and confirm the fault before ordering parts
This guide covers reading fault codes on Land Rover and Range Rover using EOBD-compatible tools and Land Rover-specific diagnostic interfaces. It covers which tool to use, how EOBD compliance works by model year, and how to interpret circuit-type codes that point to wiring faults. For a full indexed list of codes and their meanings, see the Land Rover fault code index. ECU reprogramming and module coding are not covered here.
Contents
What are Land Rover fault codes?
When a sensor, actuator or control module on a Land Rover detects a reading outside its expected range, the ECU logs a Diagnostic Trouble Code (DTC) and typically illuminates a warning light on the instrument cluster. The code identifies the system, circuit or component involved, and in some cases the nature of the fault itself.
Fault codes follow a five-character format. The first character is a letter that identifies the system: P for powertrain (engine and gearbox), B for body (airbags, SRS, climate, instrumentation and comfort systems), C for chassis (ABS, braking, suspension and steering), or U for network and communication faults. The second character indicates the code's origin: 0 means a standardised code defined by the SAE and shared across all EOBD-compliant vehicles; 1 means a manufacturer-specific code that applies only to Land Rover systems; 2 indicates a second SAE-standardised range used for additional powertrain codes. The remaining three characters identify the specific circuit or fault and can include letters as well as digits, as in P24A4.
A code such as P0299 means: powertrain system, standardised code, turbocharger or supercharger underboost condition. A manufacturer-specific P1xxx code means: powertrain system, Land Rover proprietary code, and the remaining digits describe a system or circuit specific to Land Rover. Manufacturer-specific codes require a Land Rover-aware diagnostic tool to read meaningfully, because a generic scanner may display the code number without any description.
Is my Land Rover EOBD compliant?
EOBD (European On-Board Diagnostics) is the EU implementation of the OBD2 standard. EU regulations required EOBD compliance from January 2001 for new petrol-engine vehicles and from January 2004 for new diesel-engine vehicles. Any Land Rover or Range Rover sold new in the EU after those dates must have an EOBD-compliant diagnostic port and must support the standardised diagnostic protocol through it.
In practice for Land Rover owners:
Discovery 3 (2004 to 2009). TDV6 diesel, EOBD compliant from launch. A generic EOBD reader will access powertrain codes. Land Rover-specific modules (suspension, terrain response, transfer box) require an IIDTool or equivalent.
Discovery 4 (2009 to 2016). TDV6 and 3.0 SDV6 diesel, fully EOBD compliant. A generic reader covers engine and transmission codes. IIDTool or Hawkeye for full system access.
Defender 2.4 TDCi (2007 to 2011) and 2.2 TDCi (2011 to 2016). EOBD compliant. Generic readers work for engine management codes. The 2.4 TDCi is a Ford-sourced Puma engine and responds well to generic EOBD tools.
Defender Td5 (1998 to 2006): not EOBD compliant. The Td5 uses a proprietary Lucas engine management system. A generic OBD2 scanner will find the diagnostic port and may connect, but it cannot read Td5 engine data through the standard protocol. You need a dedicated Td5-capable platform. The Nanocom Evolution and Hawkeye both support Td5 diagnostics. The GAP IIDTool does not cover the Td5. It supports Defender models from the 2007 TDCi onwards.
Range Rover L322 (2002 to 2012). Diesel variants compliant from 2004 model year onwards. V8 petrol from 2002. Full system access requires IIDTool or equivalent.
Range Rover Sport L320 (2005 to 2013). As L322. EOBD compliant for engine codes; proprietary tool needed for suspension and terrain system codes.
Freelander 2 (2006 to 2014). Fully EOBD compliant. Generic readers work well for engine management.
The critical rule: if your Land Rover has a Td5 engine, do not use a generic OBD2 reader and assume a blank result means no faults. The Td5 system will not communicate through the standard EOBD protocol.
Which diagnostic cable or tool do you need?
The diagnostic cable connects your tool or laptop to the vehicle's EOBD port. The tool itself determines what you can read. There are three practical tiers for Land Rover owners.
Tier 1: Generic EOBD reader
A generic EOBD scanner or Bluetooth reader connects to the 16-pin EOBD port and reliably reads standardised powertrain (P0xxx) codes on any compliant vehicle. Depending on the scanner and how the vehicle implements the EOBD gateway, it may also access some body, chassis and network codes. For a Discovery 3, Discovery 4 or Defender TDCi, this gives you engine management fault codes and live sensor data for the powertrain. It will not access Land Rover-specific modules such as the Hill Descent Control unit, active suspension ECU or Terrain Response system. A generic reader is adequate for straightforward engine management diagnosis on compliant models. It is not adequate for a Td5 Defender.
Tier 2: GAP IIDTool (Land Rover specific)
The GAP IIDTool (available in Bluetooth and professional G3/G4 variants) is a Land Rover and Range Rover-specific diagnostic interface. It reads both the standardised EOBD codes and the full range of Land Rover proprietary module codes across all systems, including ABS, airbag, suspension, transfer box, terrain response, HEVAC and body systems. It covers Defender models from the 2007 TDCi (Puma) onwards and does not support the Td5. For a home user working on TDCi Defenders, Discovery 3 and 4, Freelander 2, Range Rover Sport L320, or L322 models from approximately 2005 onwards, the IIDTool is the most capable home-user option. The diagnostic interface cables that connect the IIDTool to the vehicle EOBD port are listed in our cables collection. The IIDTool itself is in the workshop tools and diagnostic equipment collection.
Tier 3: Hawkeye
Hawkeye is a Land Rover-specific professional diagnostic platform that pre-dates the IIDTool and remains in use in many independent workshops. It requires a dedicated update cable to keep the software current. Hawkeye covers a broad range of Land Rover and Range Rover models including pre-EOBD vehicles such as the Td5 and reads the full proprietary module set. It is better suited to a workshop environment than home use.
Professional systems (T4, TestBook, SDD, IDS) are Land Rover's official workshop platforms. SDD and IDS require specialist hardware, software and JLR licensing and are generally impractical for home use. They are the systems used for ECU programming and module calibration, not for reading and clearing fault codes at home.
How to connect and read fault codes
Step 1: Locate the EOBD port. On most Land Rover and Range Rover models, the EOBD port is in the driver's footwell, below and to the right of the steering column, within reach from the driver's seat. On older Defender models the port location varies and may be near the fusebox area under the dashboard. The Land Rover parts catalogues include wiring diagrams that show port location and pin assignments for individual models.
Step 2: Connect the cable or interface. With the ignition off, plug the diagnostic cable or Bluetooth interface into the EOBD port. If using a wired reader, connect it to your laptop or handheld unit.
Step 3: Turn the ignition on. Turn the key to position II (ignition on, engine not started). The diagnostic tool powers up through the EOBD port and begins communication with the vehicle.
Step 4: Read fault codes. Select "read fault codes" or "read DTCs" in your diagnostic software. The tool will query each module in sequence and return any stored codes. Note each code and its description.
Step 5: Record and research. Before clearing anything, write down every code and its description. Cross-reference against the full list of Land Rover fault codes to understand what each circuit or system is flagging. A single warning light can be triggered by multiple stored codes, and some codes are secondary effects of a primary fault.
Step 6: Clear and retest. Once you have identified the likely cause, clear the codes, drive under the conditions that originally triggered the light, and recheck. If the same code returns, the fault is active. If it does not return, the fault may be intermittent or was caused by a condition that has resolved. Low battery voltage is a common cause of multiple transient codes on Land Rover models.
Common Discovery 3 and Discovery 4 fault codes
The TDV6 and 3.0 SDV6 diesel engines used in the Discovery 3 and Discovery 4 produce a recognisable set of recurring fault codes.
P0299: Turbocharger underboost. The ECU is not seeing the expected boost pressure from the turbocharger. Common causes on TDV6 engines include a failed or sticking variable vane actuator, boost pressure sensor failure, or a split intercooler hose. Check the boost circuit before replacing the turbocharger unit.
P0340 / P0345: Camshaft position sensor circuit. The TDV6 has two camshaft position sensors, one per cylinder bank, each mounted in the cylinder head. Both are vulnerable to oil contamination and connector degradation. These codes often accompany difficult cold starting. Confirm by testing sensor resistance before replacing.
P2453: DPF differential pressure sensor range or performance. The DPF system compares exhaust pressure before and after the filter. A failed pressure sensor or blocked sensor pipe will produce this code before the filter itself is the problem. Check the sensor and its connecting hoses before condemning the DPF.
P24A4: Particulate filter bank 1 restriction too high. This code typically indicates excessive restriction within the DPF and is best confirmed with live differential pressure data. It often follows P2453 and multiple regeneration failure codes.
For Discovery 4 electrical system fault codes and the specific codes associated with limp mode events, the Discovery 4 Limp Mode guide covers the common patterns in depth.
Common Defender fault codes
Defender Td5 (1998 to 2006): not EOBD compliant
The Td5 engine management system uses a Lucas Td5 ECU with a proprietary diagnostic protocol and does not communicate through the standard EOBD gateway. With a Nanocom Evolution or Hawkeye, common Td5 codes include injector coding faults (the Td5 has five individually coded injectors, and code mismatches produce rough running and smoke), crank position sensor circuit faults (a known failure on high-mileage Td5 engines), and fuel pressure regulator faults. Without a Td5-capable tool, a Td5 Defender will show no communicable fault codes even when major faults are present. This is the most common reason Td5 owners report that a scanner "shows nothing wrong."
Defender 2.4 TDCi and 2.2 TDCi: EOBD compliant
The Ford-sourced Puma TDCi engines are fully EOBD compliant and respond to generic readers.
P0380: Glow plug circuit fault. The TDCi glow plug relay and individual plug circuits are commonly flagged in cold weather after high mileage. Test each plug individually with a current clamp before replacing all four.
P0191: Fuel rail pressure sensor range or performance. A fuel pressure sensor circuit fault on the TDCi often accompanies hard starting and loss of power. Check the sensor wiring and connector before replacing the sensor or the high-pressure fuel pump.
P0401: EGR flow insufficient. The TDCi EGR system is prone to carbon build-up, restricting flow and triggering this code. Clean or replace the EGR valve and inspect the EGR cooler before clearing.
When a fault code points to a wiring fault
Not every fault code means a component has failed. A significant proportion of diagnostic codes on Land Rover and Range Rover indicate a circuit problem: degraded wiring, a corroded connector, or a failing cable rather than the sensor or module at the end of the circuit.
The fault code structure provides a clue. Codes described as "sensor circuit range or performance" or "sensor circuit no signal" can mean a failed sensor or can mean the wiring between the sensor and the ECU is open, shorted, or introducing resistance. Codes with descriptions such as "range or performance," "low input," "high input," or "intermittent" in the code name are describing a signal or circuit behaviour, and can point to wiring just as readily as a failed component.
When a code describes a circuit rather than a component failure, check the wiring before replacing the part. Inspect the connector for corrosion or pushed-back pins, check the cable routing for chafing against metal or heat sources, and test continuity and resistance in the circuit with a multimeter. A corroded battery earth lug or a degraded transducer cable can generate multiple unrelated-looking codes across different systems simultaneously on older Defenders and Discovery models.
The electrical and diagnostic cables collection covers battery cables, transducer cables and diagnostic interface leads. For wiring loom and sensor components, the Land Rover Electrical Parts category covers the broader electrical system.
The Freelander 2 common faults guide also covers how circuit-type codes led to wiring diagnosis on that platform.
Fault code resources and next steps
Once you have read your codes, cross-reference each one against the fault code index before deciding on a repair. A single warning light can mask several stored codes, and identifying the primary fault saves time and parts cost.
For wiring diagrams that show circuit routing and connector locations, the Land Rover parts catalogues link to model-specific documentation that makes circuit tracing faster. Workshop tools and diagnostic equipment including the GAP IIDTool BT and IIDTool Pro are in the workshop tools and diagnostic equipment collection.
Related guides
Discovery 4 Limp Mode: Electrical Causes
Battery, alternator and electrical fault codes that trigger multi-system warnings
Freelander 2 Common Faults and Fixes
Fault diagnosis patterns and circuit code interpretation on the Freelander 2
Parts and tools
Electrical & Diagnostic Cables
Diagnostic interface cables, battery cables and connectors
Workshop Tools
GAP IIDTool, Hawkeye update cable and diagnostic equipment
Land Rover Electrical Parts
Wiring looms, sensors, relays and electrical components
Frequently asked questions
Can I use a generic OBD2 scanner on a Land Rover?
A generic OBD2 or EOBD scanner will work on Land Rover and Range Rover models that are EOBD compliant: petrol engines from 2001 and diesel engines from 2004 onwards. It will reliably read standardised powertrain (P0xxx) codes and, depending on the scanner and vehicle, may also access some body, chassis and network codes. It will not access Land Rover proprietary module codes covering systems such as active suspension, Terrain Response, Hill Descent Control or transfer box ECUs. For those systems, you need a Land Rover-specific tool such as the GAP IIDTool. A generic scanner will not communicate at all with a Td5 Defender engine management system, because the Td5 does not support the EOBD protocol.
What is the difference between EOBD and OBD2?
EOBD (European On-Board Diagnostics) and OBD2 (the US standard) are parallel implementations of the same underlying diagnostic standard. Both use the same 16-pin connector, the same five-character DTC format, and share the same standardised code definitions for the P0, B0, C0 and U0 ranges. The difference is in the legislation that mandated them: OBD2 was required on US market vehicles from 1996, and EOBD was required on EU market vehicles from 2001 for petrol and 2004 for diesel. In practice, a vehicle sold as EOBD compliant in the EU will also communicate with a device labelled as OBD2 compatible. EOBD is the technically correct term for EU-market Land Rover and Range Rover models.
Is a Td5 Defender EOBD compliant, and what tool does it need?
No. The Defender Td5 (1998 to 2006) uses a Lucas engine management system with a proprietary diagnostic protocol that pre-dates EOBD. The vehicle has a 16-pin diagnostic port, and a generic OBD2 reader will connect to it but will not be able to read Td5 engine management data through the standard EOBD protocol. The GAP IIDTool does not support the Td5. Its Defender coverage starts with the 2007 TDCi. To diagnose a Td5 you need a dedicated platform: the Nanocom Evolution and the Hawkeye system both support full Td5 diagnostics. Without one of these tools, the Td5 system will return no fault codes to a standard scanner even when active faults are present.
What diagnostic tool is best for home use on a Discovery 3 or Discovery 4?
The GAP IIDTool Bluetooth is the most practical choice for a home user working on a Discovery 3 or Discovery 4. It reads both the standardised EOBD codes and the full range of Land Rover proprietary module codes, including the air suspension ECU, transfer box, terrain response system and HEVAC, which a generic reader cannot access. It connects via Bluetooth to a phone or tablet running the IID Tool app. For reading and clearing engine management codes only, a generic EOBD reader is sufficient and considerably cheaper, but it will not access the body and chassis systems where many Discovery 3 and Discovery 4 problems originate.
What does a circuit range or rationality fault code mean on a Land Rover?
A circuit range or rationality code (labelled as "sensor circuit range or performance" or "signal outside expected range") means the ECU is receiving a signal that is outside the values it expects under those operating conditions. This does not necessarily mean the sensor has failed. It can also mean the wiring between the sensor and the ECU has increased resistance due to corrosion, that a connector has a corroded or pushed-back pin, or that the reference voltage or earth return circuit for that sensor is compromised. Before replacing the sensor, test wiring continuity and resistance, inspect the connector, and check the earth path. On older Defenders and Discovery models, a corroded battery earth lug or a degraded cable in the sensor circuit is a frequent cause of rationality codes across multiple unrelated systems simultaneously.
Where is the EOBD diagnostic port on a Land Rover Defender and Discovery?
On the Discovery 3 and Discovery 4, the EOBD port is in the driver's footwell, below and to the right of the steering column, typically accessible without removing any trim. On the Defender TDCi, the port is usually under the dashboard on the driver's side, near the fusebox area. The exact location varies between model years and body variants. On pre-EOBD vehicles including the Td5 Defender, the diagnostic port is in a similar location but the connector does not carry the standard EOBD protocol through all pins. The Land Rover parts catalogues include wiring diagrams that show diagnostic port location and pin assignments for each model.
Budget Parts. Land Rover fault code guide and diagnostic cables, stocked in the Netherlands for EU dispatch. Updated June 2026.
Leave a comment