Land Rover Diagnostic Aid Bulletin

Technical Service Bulletin Стр.
1 из 9
No.LA418-
Technical Service 004
14
Bulletin
.ru
July 2006
Subject/Concern: Discovery 3/LR3 - Diagnostic Aid for Multiple Diagnostic Trouble Codes
Models:
Discovery 3 / LR3 VIN- range: 5A300394 Onwards
Markets: All
Section: 418-00
ce
Summary:
A customer may report a concern that mutliple warning lamps and messages are being
cascaded on the message center i.e. ABS, followed by DSC, then air suspension,
transmission etc. Investigation using diagnostic equipment reveals many diagnostic
trouble codes (DTCs) stored in different control modules, including codes with 'P', 'C' and
'U' prefixes. In some cases in excess of fifty DTCs have been recorded, making the start
point for diagnosis difficult to establish and the first DTC logged not neccesarily correcting
the issue.
rvi
Cause: The complex nature of the vehicle can cause a cascade effect with a fault code
logging in more than one control module. DTCs with the 'U' prefix can cascade
around the vehicle control modules as invalid data, lost communication or
control area network (CAN) bus faults as can be logged by each module. A fault
which is local to a system and only applicable to that system is classed as a
'hard fault' (e.g. engine sensor 'P' prefix codes and suspension sensor 'C' prefix
codes). A hard fault which will result in data for engine torque, engine speed,
road speed etc. being invalid will then cascade around the vehicle systems as 'U'
codes. The other systems then switch to default mode as designed. For
example, the Dynamic Stability Control system (DSC) requires an engine torque
signal to control engine power during DSC activity and so will log a fault withing
se
the DSC control module when the cascaded 'U' code is seen. The root cause for
illumination of, for instance, an ABS/DSC warning lamp can lead the technician
to investigate the ABS control module first. It may not be obvious that the root
cause is within the engine control module . For example, a diesel exhaust gas
recirculation (EGR) fault (a hard fault local to the engine), results in the engine
control module being unable to calculate 'engine torque'. This torque will be
transmitted on the CAN as invalid data and will cause the ABS, DSC and air
suspension to enter default mode and illuminate amber warnings because they
all need engine torque data to function fully.
Action: Should a customer express concern regarding the above, refer to the Diagnostic
LR
Procedure detailed in this bulletin to help establish the root cause of the logged
DTCs.
Diagnostic Procedure
Procedure to follow if many 'P' and 'C' codes are
present also with 'U' network codes.
NOTE: Most 'P', 'C' and 'B' prefixed DTCs are 'hard faults' which can be rectified, but a small number are
http://gtr.franchise.landrover.com/extdealerlrprod/xml/parsexml.jsp?XMLFile=G9133... 22.01.2007
Technical Service Bulletin Стр. 2 из 9
due to errors in other systems. Most 'U' codes are due to errors originating from other systems, but a
small number are hard faults which can be rectified.
NOTE: In instances where only 'P' or 'C' codes are stored (no 'U' codes), check for other TSB information
.ru
issued for the particular DTC or symptom.
NOTE: Do not begin working on the rectification of any DTCs, especially 'U' prefixed codes, without
following this procedure.
1. Read the DTCs from ALL control modules and list in groups of 'P', 'C', 'B' and 'U'
prefixes.
2. Review the 'P' and/or 'C' DTCs against the list on Table 1.
1 . If a 'P' or 'C' DTC is not listed in Table 1 this is a 'hard fault' with the relative
system and needs to be rectified first. In most cases, this will usually be the root
cause of the DTC logging cascade. Diagnose the problem as directed by the
ce
diagnostic equipment or using TSB information relevant to code present, clear all
other logged codes, and test the vehicle to confirm the repair. If this action
rectifies the complaint, no further action is required.
2 . If the 'P' or 'C' DTC is listed in Table 1, it is unlikely to be a 'hard fault' with the
related system. Ignore these codes for the time being.
3. Review the 'B' DTCs for instrument pack (IPK), supplementary restraint system (SRS)
and the headlamps against the list in Table 1.
1 . If a 'B' DTC is not listed in Table 1 this is a 'hard fault' with the relative system
and needs to be rectified first. In most cases, this will usually be the root cause of
the DTC logging cascade. Diagnose the problem as directed by the diagnostic
rvi
equipment or using TSB information relevant to code present, clear all other
logged codes, and test the vehicle to confirm the repair. If this action rectifies the
complaint, no further action is required.
2 . If the 'B' DTC is listed in Table 1, it is unlikely to be a 'hard fault' with the related
system. Ignore these codes for the time being.
4. Review the 'U' codes against the list in Table 1.
1 . If a 'U' DTC is listed in Table 1 this is a 'hard fault' with the relative system and
needs to be rectified first. In most cases, this will usually be the root cause of the
DTC logging cascade. Diagnose the problem as directed by the diagnostic
se
equipment or using TSB information relevant to code present, clear all other
logged codes, and test the vehicle to confirm the repair. If this action rectifies the
complaint, no further action is required.
If a problem remains.
5. NOTE: Ensure a full DTC listing is available.
If a problem remains with the vehicle or the DTC cannot be analysed by this TSB,
contact the Land Rover dealer technical assiatance helpline for further help.
LR
Table 1
NOTE: This table indicates the following DTC data, applicable to Land Rover Discovery 3/LR3 and
Range Rover Sport: P, C and B codes which are NOT necessarily hard faults, and U codes which ARE
hard faults
Problem
Cascaded Cascaded Fault is
is Local
Control DTC Log DTC Log Local
to this Helptext
Module DTC -Invalid - Lost to this
DTC System Category
Containing Description data comms System
OR (below)
DTC (Yes or (Yes or (Yes or
Cascaded
No) No) No)
(Yes or
No)
Gasoline Engine Wheel speed
C003100 Y Y C
Control Module signal
.ru
Wheel speed
(ECM) C003400 Y Y C
signal
Wheel speed
C003700 Y Y C
signal
Wheel speed
C003A00 Y Y C
signal
Wheel speed
C129600 Y Y C
signal
Wheel speed
C129700 Y Y C
signal
ce
Wheel speed
C129800 Y Y C
signal
Wheel speed
C129900 Y Y C
signal
Invalid ABS
P050000 Y Y A
data
P050162 Vehicle speed Y A
P050164 Vehicle speed Y A
Brake switch
P050429 Y
plausibility
rvi
Brake switch
P050464 Y
plausibility
Incorrect
P051300 Y A
security key
CCF data
P061000 Y
mismatch
VIN data
P063000 Y
mismatch
Security Target
se
P063305 ID Transfer Y Y C
Process Failed
TCM MIL
P070000 Y A
request
4WD switch low
P277200 Y D
cct
immobilizer
Diesel Engine signal error -
P1259 Y A
LR
Control Module ECM ID transfer

failed
immobilizer
comms error -
(ECM) P1602 Y B
timeout
occurred
immobilizer -
P1621 challenge does Y
not match
immobilizer -
P1622 key status Y
unknown
Vehicle speed
P1934 Y A
signal
Brake switch /
P1935 Y Y C
.ru
sensor signal
Clutch switch /
P1936 Y A
sensor signal
Diagnostic tool
P193A Y A
problem
Slip Control
C1A0088 CAN Bus off Y
System
SAS fault -
(SCS/ABS/DSC) C1B0027 Y A
check SAS
ce
SAS fault -
C1B0029 Y A
check SAS
SAS fault -
C1B0061 Y A
check SAS
SAS fault -
C1B0064 Y A
check SAS
SAS fault -
C1B0092 Y A
check SAS
SAS fault -
C1B0092 Y A
check SAS
rvi
Throttle pedal
Transmission
P012100 pos sensor A cct Y
Control Module
- Plausibility
wheel speed
(TCM) P050000 Y Y C
from CAN
Plausibility with
P050100 wheel speed Y A
from CAN
se
Output shaft
P072164 speed sensor - Y D
Plausibility
Lost comms
U010387 Y
with gear shifter
Invalid data
U040462 from gear Y
shifter
Invalid data
U040464 from gear Y
LR
shifter
Invalid data
U040486 from gear Y
shifter
Rear
CAN initiation
Differential U1A1449 Y
failure
Control Module
(RDCM)
Air Suspension U1A1449 CAN initiation Y
failure
Compressor
U200067 Y
temp sensor
.ru
Valve cct short
U200701 Y
to ground
Valve cct short
U200711 to ground when Y
inactive
Valve cct
U200719 Y
current too high
Valve signal
U200767 incorrect after Y
event
ce
Terrain CAN initiation
U1A1449 Y
Optimisation failure
Ignition switch
Electronic Park input circuit
C1A5564 Y D
Brake failure
(plausibility)
CAN initiation
(EPB) U1A1449 Y
failure
rvi
Switch general
U200201 Y
electrical failure
Dynamic Roll CAN initiation

U1A1449 Y
Control Module failure
Valve over
(DRCS) U200798 Y
temperature
Adaptive CAN initiation

se
U1A1449 Y
Headlamps failure
Lost comms LH
(AFS) U1A3887 Y
lamp
Lost comms RH
U1A3987 Y
lamp
ECU
U300000 Y
malfunction
U300016 Voltage too low Y
U300017 Voltage too high Y
LR
U300042 Memory failure Y
Adaptive CAN initiation

U1A1449 Y
Headlights failure
Lost comms LH
(AFS/LCM) U1A3887 Y
lamp
Lost comms RH
U1A3987 Y
lamp
Indicator faulty
Restraints
B00D268 (Invalid data Y
Control module
IPK)
Indicator
(RCM) B00D287 timeout (Lost Y
comms IPK)
.ru
Crash output SC
B1A5514 to ground or Y
open
Private CAN
U1A0064 config Y
error/plausibility
Private CAN bus
U1A0088 Y
fault
CAN initiation
U1A1455 Y
failure
Data not
ce
U201A51 programmed Y
(F124)
Incorrect
U201B4A component Y
(F125)
Data not
U201B51 programmed Y
(F125)
Incorrect
U201C4A component
rvi
Y
(F126)
Data not
U201C51 programmed Y
(F126)
Adaptive Cruise Private CAN bus

U1A0088 Y
Control off
CAN initiation
U1A1449 Y
failure
se
Battery/ECU
Y
reset
Help Text Category A - Invalid Data

LR
This type of diagnostic trouble code is caused when one or more control modules installed to
the vehicle receives invalid data from another control module. Multiple electrical systems
can be affected when a failure of this type occurs. For example; The electronic park brake,
automatic transmission, engine management and center differential all rely on wheel speed
information being correctly broadcast by the vehicle dynamics control module in order to
function correctly. If invalid information is broadcast by the vehicle dynamics control module
to the recipient modules listed above, an invalid data diagnostic trouble code will be stored
in each given control module or modules. When this fault occurs it can in turn cause any of
the recipient control modules to change behaviour and/or alter information being broadcast
to other systems on the vehicle, i.e. cascading DTC logging.
As a result of this type of failure the customer will often report unexpected vehicle operation
with regard to warning lamp, warning message or audible warning activity.
Invalid data transmitted by a control module is generally caused by an electrical/mechanical

problem in that control system, e.g. a faulty wheel speed sensing circuit. In this example
above; the following actions must be taken in order to fully investigate this failure:
.ru
Perform a 'complete vehicle' diagnostic trouble code read (from ALL control modules)
Review all stored diagnostic trouble codes in each control module attempting to
establish a trend between failures, e.g. several control modules report invalid data
received from one common control module as described above.
Investigate and repair all permanent or intermittent diagnostic trouble codes in the
order 'P', 'C', 'B' and 'U' unless the diagnostic equipment help text provided for any
given fault instructs you to ignore the failure, or the help text refers to Invalid data
and/or lost communications.
If 'P', 'C', 'B' or 'U' diagnostic trouble code(s) have been investigated and repaired,
perform a complete vehicle diagnostic trouble code clear. If any 'P', 'C', 'B' or 'U'
diagnostic trouble code either logs or re-logs during the repair confirmation test
ce
repeat the steps above as necessary.
If no 'P', 'C', 'B' or 'U' diagnostic trouble codes are stored other than those previously
instructed to ignore; the following action should be taken:
If the customer has reported any problem with vehicle operation with regard to
warning lamp, warning message or audible warning activity, please contact the Dealer
technical support line for further advice.
If there have been no customer complaints relating to the above conditions, perform a
complete vehicle fault code clear.
rvi
Help Text Category B - Lost Communications
This type of diagnostic trouble code is caused when one or more control modules installed to
the vehicle does not receive data from another control module when expected. Multiple
electrical systems can be affected when a failure of this type occurs for example;
Electronic park brake, automatic transmission, engine management and the center
differential, all rely on wheel speed information being correctly broadcast by the vehicle
dynamics control module in order to function correctly. If information broadcast by the
se
vehicle dynamics control module does not reach any of the recipient modules listed above, a
lost communications diagnostic trouble code will be stored in the given control module or
modules. When this fault occurs it can in turn cause any of the recipient control modules to
change behaviour and/or alter information being broadcast to other systems on the vehicle,
e.g. cascading failure.
As a result of this type of failure the customer will often report unexpected vehicle operation
with regard to warning lamp, warning message or audible warning activity.
The following actions must be taken in order to fully investigate this failure:
LR
Perform a 'complete vehicle' diagnostic trouble code read (from ALL control modules).
establish a trend between failures, e.g. several control modules report lost
communications with one common control module as described above.
instructed to ignore, the following action should be taken:
.ru
If the customer has reported any problem with vehicle operation with regard to warning
lamp, warning message or audible warning activity, an intermittent fault may be present on
the vehicle. Based upon the review of stored diagnostic trouble codes, please check the
integrity of the following areas for each of the control modules identified by a lost
communications diagnostic trouble code:
Communications network harness and connector.

Control module power supply harness and connector.
Control module ground supply harness and connector.
If no faults are found during these checks please contact the Dealer technical support line
ce
for further advice.
If there have been no customers complaints relating to the above conditions, perform a
complete vehicle fault code clear
Help Text Category C - Lost Communications or Invalid Data
This type of diagnostic trouble code is caused when one or more control modules fitted to
the vehicle does not receive data from another control module when expected, or the data
rvi
received is invalid. Multiple electrical systems can be affected when a failure of this type
occurs, for example:
Electronic park brake, automatic transmission, engine management and the center
differential all rely on wheel speed information being correctly broadcast by the vehicle
dynamics control module in order to function correctly. If invalid information is broadcast by
the vehicle dynamics control module or the data broadcast is not received by the recipient
modules listed above, an invalid data or lost communications diagnostic trouble code will be
stored in the given control module or modules. When this fault occurs it can in turn cause
any of the recipient control modules to change behaviour and/or alter information being
broadcast to other systems on the vehicle, i.e. cascading failure.
se
As a result of this type of failure, the customer will often report unexpected vehicle
operation with regard to warning lamp, warning message or audible warning activity.
Invalid data transmitted by a control module is generally caused by an electrical error in

that control system, e.g. a faulty wheel speed sensing circuit in the example above.
The following actions must be taken in order to fully investigate this failure:
LR
Perform a 'complete vehicle' diagnostic trouble code read (from ALL control modules).
establish a trend between failures, e.g. several control modules report lost
communications with one common control module as described above.
instructed to ignore, the following action should be taken:
If the customer has reported any problem with vehicle operation with regard to warning
lamp, warning message or audible warning activity an intermittent fault may be present on
.ru
the vehicle. Based upon the review of stored diagnostic trouble codes, please check the
integrity of the following areas for each of the control modules identified by a lost
communications diagnostic trouble code:
Communications network harness and connector.

Control module power supply harness and connector.
Control module ground supply harness and connector.
If no faults are found during these checks please contact the Dealer technical support line
for further advice.
ce
If there have been no customers complaints relating to the above conditions perform a
complete vehicle fault code clear
©2006 LandRover
rvi
se
LR

Land Rover Diagnostic Aid Bulletin

Uploaded by

Copyright:

Available Formats

Land Rover Diagnostic Aid Bulletin

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Land Rover Diagnostic Aid Bulletin

Uploaded by

Copyright:

Available Formats

Technical Service Bulletin Стр.

5. NOTE: Ensure a full DTC listing is available.

Control Module ECM ID transfer

Air Suspension U1A1449 CAN initiation Y

Dynamic Roll CAN initiation

Adaptive CAN initiation

U300042 Memory failure Y

Adaptive CAN initiation

Adaptive Cruise Private CAN bus

Help Text Category A - Invalid Data

Invalid data transmitted by a control module is generally caused by an electrical/mechanical

Communications network harness and connector.

Help Text Category C - Lost Communications or Invalid Data

Invalid data transmitted by a control module is generally caused by an electrical error in

instructed to ignore, the following action should be taken:

Communications network harness and connector.

You might also like