Suspension fault driving fast on twisty mountain road

[Ant_les]

Quick question. Does the computer store suspension faults or are they cleared when you restart? I drove a mountain road a couple days ago much faster than I should have. After a few minutes I got the amber suspension fault warning light. The next time I drove the warning was gone and the suspension can still raise and lower without issue. I'm curious what the fault was. I don't have an iidtool yet so I'm hoping the fault is still there. Also does anyone have a tool in the bay area California

 

[Greg9504]

Did you feel the traction control kick in? If so could be the bushings in one of the rear upper control arms. Although it will usually happen at lower speeds to. Unfortunately without the codes there are just too many things that could cause it. Even with the codes some problems are hard to track down.

Most but not all codes are stored with a mileage 'timestamp'.

If you plan to own the LR3 for any length of time get the IID tool.

 

[Houm_WA]

Hmmmm along those lines, what did this suspension fault look like? Which icons activated? Did the info screen say "Suspension Fault" and did the vehicle lower?

 

[Ant_les]

No traction light. Amber suspension light and a message on the info screen. The ride height did not change for the rest of the drive. I have a iidtool on the way. I was more curious if the code would stay in long enough to scan it. If it clears quickly I can take it to an indi Rover shop near me. I've owned it for about 4 weeks. Took it off roading a a few weeks ago. Everything worked as it should then. That extended mode is pretty helpful. These things are beasts. Definitely would give my old d2 a run for her money.

 

[Houm_WA]

Stock v stock an LR3 will crush a D2. My opinion but just looking at the measurables they don't compare. By the way, you can use the IIDTool to get to Extended Height on demand.

Your fault is probably something silly like a communication error.

 

[Greg9504]

I have a iidtool on the way. I was more curious if the code would stay in long enough to scan it. If it clears quickly I can take it to an indi Rover shop near me.

My experience has been that the codes will NOT clear unless you disconnect the battery or clear the code with a scan tool.
Here is a recent scan from my LR3 using the IID tool, vehicle was scanned with a little over 218758 km on it, it shows stored codes.

After you get the IID tool, read the codes (keep copy, app lets you email current stored codes to yourself), then clear and wait and see if the problem returns. The LR3 is constantly storing various codes. You have to **** out the 'common' ones. The one I was after P186D-00 (my rear diff locking motor is on the way out) . The brake light ones are causes by a brake light switch, it doesn't like it when it's cold out. I should replace the switch...

VIN: removed
L319 - LR3 2006
Vehicle scanned on 20-12-2019 15:51
Using IIDTool BT V3.0 B2134

Body Control

• B1B01-4A (6C) Key transponder - System internal failure - incorrect component installed
  ( at 216140 km )
• B1B01-87 (6C) Key transponder - Bus signal/message failure - missing a message
  ( at 214160 km )
• B1B02-28 (2F) Low frequency coil - General signal failure - signal bias level is out of range/zero adjustment failure
  ( at 214150 km )
• B1BA0-66 (6C) Excessive challenge requests or start attempt in storage mode - Algorithm based failure - signal has too many transitions/events
  ( at 214170 km )
• B1C44-67 (68) Rear wiper park position switch - Algorithm based failure - signal is incorrect after the event
  ( at 218030 km )
• B1C57-14 (6C) Passive start ignition relay coil circuit - General electrical failure - circuit short to ground or open
  ( at 214150 km )
• B1D00-15 (6C) Left low beam circuit - General electrical failure - circuit short to battery or open
  ( at 218640 km )
• B1D09-15 (28) Right trailer turn signal circuit - General electrical failure - circuit short to battery or open
  ( at 216810 km )
• B1D12-15 (2E) Volumetric alarm power circuit - General electrical failure - circuit short to battery or open
  ( at 214150 km )
• B1D14-15 (2F) Interior lamps 2 circuit - General electrical failure - circuit short to battery or open
  ( at 214150 km )
• U0155-87 (28) Lost communication with instrument cluster control module - Bus signal/message failure - missing a message
  ( at 214150 km )

Engine Petrol

• P0513-00 (68) Incorrect immobiliser key
• P0504-64 (68) Brake switch A/B correlation - Algorithm based failure - signal plausibility failure
• P0504-29 (68) Brake switch A/B correlation - General signal failure - signal is invalid

Instrument Pack

• U0102-87 (28) Lost communication with transfer case control module - Bus signal/message failure - missing a message
• U0132-87 (28) Lost communication with ride level control module - Bus signal/message failure - missing a message

Parking Brake

• U0101-87 (A8) Lost communication with transmission control module - Bus signal/message failure - missing a message
  ( at 217656 km )
• C1A55-64 (A8) Unknown
  ( at 217570 km )

Rear Diff

• P186D-00 (28) Clutch actuator stuck
  ( at 8803843 km )

Transfer Case

• P0562-00 (28) System voltage low
  ( at 0 km )

Vehicle Dynamic

• C1A96-62 (08) Brake lamp switch circuit - Algorithm based failure - signal compare failure
  ( at 218756 km )
• U1A4A-68 (08) Invalid data received from differential control module - rear - Algorithm based failure - event information
  ( at 218758 km )

Ventilation

• B1B74-00 (28) Front foot-defrost mode stepper actuator
  ( at 214982 km )
• B1B75-00 (68) Front foot-face mode stepper actuator
  ( at 214982 km )
• B1B76-00 (28) Front left air blend stepper actuator
  ( at 214982 km )
• B1B77-00 (28) Front right air blend stepper actuator
  ( at 214982 km )
• B1B78-84 (28) System pressure - Bus signal/message failure - signal is below allowable range
  ( at 214176 km )

 

[Ant_les]

that is pretty detailed

 

[El Solis]

Were you loaded up? Might have pushed a height sensor out of range on the twisty roads. I get that occasionally OffRoad, especially in off road height. GAP tool will tell you what tripped the fault, might not explain why it happened.

 

[Houm_WA]

I don't think a height sensor should go out of range unless the set height has been manipulated (like with an IIDTOOL or rods) and then Extended Height or Super Extended Height is invoked.

 

[El Solis]

I’ve had it happen in off road height without rods or height manipulation. Usually when you hit a dip or with a drop that causes a rapid drop of a wheel. Lights stay on for a few seconds then clear. Once I had to wait until I turned off the car to let it reset.