2007 Range Rover Sport workshop fun

[Guineafowl]

Messages:
Special programs not available
Parking brake fault

Lights:
Parking brake
Suspension
ABS
Traction control (I think: triangle with exclamation inside, arrow going around)

Codes: P0500:00 Vehicle speed sensor A seems to be the one recorded at the mileage the lights came on.

Does it mean one of the speed sensors is faulty, but it won’t tell me which one? I can’t get live data. Topdon Artidiag 800, which is proving to be quite crap, unless it just needs getting used to. My mate turned up with the car and a left rear speed sensor to fit, so we did, but no change.

 

[Guineafowl]

To add, I did try to bench-test the old sensor. Its a two-wire, but appears to be an active type, not the simple variable reluctance I was expecting.

Apparently it needs a 12V supply, one side via a 100ohm resistor current shunt, then you put the scope either side of that. I did get blips as a piece of metal passed the sensor, but not the nice train of square pulses I was hoping for. This was on an old CRO, however.

 

[Ubique]

Firstly, you're looking in the wrong place!
P = Powertrain
C = Chassis
B = Body
U = Communications
P0500-00 is indeed 'Vehicle speed sensor A' but is a code from the transmission, not ABS (which would be a C code)
Essentially it means that a composite speed signal is not being broadcast on HS-CAN from the ABS module - or not being received by the TCM...
At the moment, you're at the top of the funnel with lots of possibilities, you should be able to read live data by going into the module (ABS initially and selecting the live data button) to check wheels speeds for plausibility. A quick check is to see if the navigation is tracking your position & speed correctly using it's diagnostic screen (PIN is 753) then check vehicle signals, if OK, then all wheel speeds are plausible and the composite speed is being broadcast.

 

[Ubique]

Wiring diags...

Done a bit more digging - 'Vehicle speed invalid signal received over CAN' is confirmed as the cause, one quick check is the steering angle sensor - that can cause all the warnings & issues you describe. If you put the 4x4i display on the infotainment screen, you should see the wheel angle - check this with the actual position, I have known the sensor to become loose on the steering column... it won't always set a DTC but the ABS will detect implausible inputs and disable the composite speed signal output as it can't be relied upon.

 

[Guineafowl]

Thanks, as ever. When I had the GAPIID, I could watch all the wheel signals as I went along, but I sold that on here a while back, thinking I’ll never see a Disco/RRS again…

Will do the suggested checks when he turns up again, and cheers for the wiring diagrams.

I did once see a defective SAS - another mate’s Disco 3 would brake hard if you steered hard left or right. It turned out that the vehicle, not knowing where the steering wheel was, was sensing the differing wheel speeds when turning and ascribe this to wheel slip. He just needed it to work long enough to make the journey to Glasgow to trade it in, so I told him to turn off the TC. It also had a defective MAF sapping the power, so I disconnected that.

 

[Ubique]

This could be so far out the ABS has given up!

I've just checked, the Artidiag 800BT has the ability to read live data (and reset the SAS!) so you should be good to go

 

[reb78]

Do they have the same issues with yhe brake light switch as the d3? The symptoms sound right.

 

[Ubique]

Brake light switch would set a plausibility DTC - and hang on to gears in an auto. I don't remember that particular issue causing the suspension to error though.

 

[hotponyshoes]

I'd check battery condition and state of charge as well.
That getting tired causes all sorts of random issues.

 

[qwakers]

yup the topdon absolutely can view live data. it in fact is the most important feature of any scantool.

 

[reb78]

Brake light switch would set a plausibility DTC - and hang on to gears in an auto. I don't remember that particular issue causing the suspension to error though.

Ah. Sorry. I looked back and the symptoms are not the same. On the d3 the brake switch typically causes an abs error, suspension sinks to bump stops and 50mph max warning on dash.

I'll butt out!

 

[Ubique]

I'd check battery condition and state of charge as well.
That getting tired causes all sorts of random issues.

That's true, although a speed signal error would clear on a restart if there was a 'brownout' during initial cranking as it's not a latching DTC - a battery disconnect/reconnect after ~10 mins of letting it 'sleep' won't hurt though.

 

[Kram]

Thanks, as ever. When I had the GAPIID, I could watch all the wheel signals as I went along, but I sold that on here a while back, thinking I’ll never see a Disco/RRS again…

Will do the suggested checks when he turns up again, and cheers for the wiring diagrams.

I did once see a defective SAS - another mate’s Disco 3 would brake hard if you steered hard left or right. It turned out that the vehicle, not knowing where the steering wheel was, was sensing the differing wheel speeds when turning and ascribe this to wheel slip. He just needed it to work long enough to make the journey to Glasgow to trade it in, so I told him to turn off the TC. It also had a defective MAF sapping the power, so I disconnected that.

I find that somewhat dishonest.

 

[dobbslc]

yup the topdon absolutely can view live data. it in fact is the most important feature of any scantool.

It's worth checking the Topdon has the latest update for this manufacturer. My 600 will give me live data on everything I've tried it on.