Need help deciphering Fault codes

[duderduderini]

Hi Everybody
Just activated my IID Bt tool
The faults list is long and distinguished
I was hoping for some help into figuring out what needs to happen from here
Many thanks
Nick

Model L320 - Range Rover Sport 2006
Vehicle scanned on 15 Apr 2017 7:25:33 PM
IIDControl 2.9.4.5 Android - IIDTool BT V3.0 B2444

Body Control

• B1B01-87 (6C) Key transponder - Bus signal/message failure - missing a message
( on 20-07-2013 08:07:59 at 130520 km )

• U0155-87 (28) Lost communication with instrument cluster control module - Bus signal/message failure - missing a message
( on 01-09-2013 18:42:58 at 131990 km )

Engine TDV6

• P140A-00 (2D) Exhaust gas recirculation sensor C - circuit low

• P0196-00 (68) Engine oil temperature sensor circuit range/performance

• P140E-00 (2C) Exhaust gas recirculation position sensor C minimum/maximum stop performance

Instrument Pack

• U0102-87 (2E) Lost communication with transfer case control module - Bus signal/message failure - missing a message

• U0132-87 (2E) Lost communication with ride level control module - Bus signal/message failure - missing a message

Suspension

• C1A74-1C (28) Rear left height sensor mechanism - General electrical failure - circuit voltage out of range
( on 20-07-2013 21:01:24 at 130522 km )

• C1A05-1C (28) Rear left height sensor - General electrical failure - circuit voltage out of range
( on 03-01-2014 10:56:14 at 135836 km )

• C1A07-62 (68) Cross articulation - Algorithm based failure - signal compare failure
( on 30-01-2014 14:37:12 at 137264 km )

Terrain Response

• U0132-87 (28) Lost communication with ride level control module - Bus signal/message failure - missing a message
( on 31-01-2014 14:10:50 at 137436 km )

Transfer Case

• P0562-00 (28) System voltage low
( on 15-04-2017 19:20:49 at 0 km )

• U0132-86 (28) Lost communication with ride level control module - Bus signal/message failure - signal is invalid
( on 20-07-2013 21:01:24 at 130522 km )

Vehicle Dynamic

• U0421-68 (08) Invalid data received from ride level control module - Algorithm based failure - event information
( on 20-07-2013 21:01:24 at 130522 km )

• U0132-87 (08) Lost communication with ride level control module - Bus signal/message failure - missing a message
( on 30-01-2014 14:37:12 at 137264 km )

[DiscoJeffster]

First thing I'd say is clear them all and see what reappears. Second thing. Go into advanced within the Faults section and select 'Pending' fault types as well, as some faults will stay pending that you'll still want to know about.
I have a permanent fault between the audio system and parking sensors for example, but it does t seem to affect anything that I can detect.

[Graeme]

I would clear all faults as most are old then check again in a few days.

[duderduderini]

Hi again
Thanks for the advice.
here is the new list
Vehicle scanned on 16 Apr 2017 11:54:00 AM
IIDControl 2.9.4.5 Android - IIDTool BT V3.0 B2444 Engine TDV6
• P140A-00 (2D) Exhaust gas recirculation sensor C - circuit low

Instrument Pack
• U0132-87 (26) Lost communication with ride level control module - Bus signal/message failure - missing a message

Suspension
• C1A74-1C (2C) Rear left height sensor mechanism - General electrical failure - circuit voltage out of range
( on 04-03-2014 01:15:30 at 142080 km )

Transfer Case
• U0132-86 (28) Lost communication with ride level control module - Bus signal/message failure - signal is invalid
( on 04-03-2014 01:15:30 at 142080 km )

Vehicle Dynamic
• U0421-68 (08) Invalid data received from ride level control module - Algorithm based failure - event information
( on 04-03-2014 01:15:30 at 142080 km )

I have the egr block kit from x8r and being a 2006 model I don't anticipate any software issues
the ride level control module.. the rear left ride height sensor may be the key to the rest. I have read enough posts to think that it may be a broken wire Ill check continuity first if possible.
Does anybody know where the wire goes once it plugs into the loom?
The dates are wrong on the fault codes. The kilometer reading is today's reading.. i don't get what it infers re the date
I think Graeme might be able to advise me on this as to where to start
Thanks again
Nick

[Graeme]

As the HS can-bus wires are in the same connector at the suspension ecu as the rear height sensors, I would ensure that the front-most suspension ecu connector is properly seated. You might want to unplug it and check that all its contacts are properly in the connector.

The suspension ecu is located high up the driver's side A pillar, accessed by removing door seal next to the the foot-well side kick panel, lifting the front of the tread plate enough to slide the side panel rearwards, then remove the panel above the pedals.

You might consider monitoring the height sensor signals with your IIDTool to see what the LR is doing.

[duderduderini]

Thanks graeme

[Graeme]

It is possible that there is a short circuit in the 5V supply to the LR sensor and that the short circuit is interrupting the suspension module's can-bus operation. Monitoring the height sensors with the tool might be a better starting point as it's easy to do and will show whether it's always zero voltage or intermittent.

[duderduderini]

On the way to Narrandera.. on the bump stops. Luckily i had mu iid tool and cleared the fault by the side of the road and once it leveled and compressor turned off i pulled the fuse.
It was a cross articulation error.. i didnt have time to email the log but later that day i put the fuse back in (ie in the afternnon some 5 hours after this started) and no problems.
I have noticed the problem is related to initial start up on a coldish morning.
I shall run live data on the way to work this week to see if the values stray from 0 volts
Thanks
Nick

[duderduderini]

I logged 3 trips today with some values but i can only access one in graph form. Whilst the iid tool is handy for this, when i view the log file and then try to export it as a pdf viam email.. it says cant send empty file. I can view the log file but when i look for the file in the iid folder on my phone it isnt there which is real handy.
Anyway im posting 2 files if anyone could be bothered helping.
The voltages to the sensor and from the sensor (rear left) where ok in the morning run But have a look at the height data. I noticed that the rear left would go from say .012 as an example to .00012 as in the actual figure would change by an order or several orders of magitude whilst the right one wouldnt until about the 20 minute mark.
I have tried several times to access the other logs but am being thwarted
Thanks