NIgor

Member
So i bought 2004 discovery 2.
It has three amigos and fault codes are:
-rear left abs sensor signal too low
-rear right abs sensor signal too low

Earlier it also had
-rear left abs sensor signal erratic

Seller said that fault came when rear diff was repaired. I checked rear left sensor, cable looked okay and i removed o-ring. but still same problem.

I can remove fault codes and dash lights turn off but after 20 meters lights come back. Also right after i remove codes it does something really weird. it might be that it brakes by itself or it puts tracs on. When i checked real time data left rear sensor won't give speed information when i start moving but others do. Rear left sensor starts to give data in some point.
I hope its just faulty sensor or bearing. Any ideas? Abs ring also looked fine.
 
You could spend hours playing around cleaning and putting a new sensor on. Just stick a new bearing on it and hope it cures it.
It did on mine.
 
Had same issue with same hubs. I changed rear hub and sensor and changed front hub and sensor and problem kept coming back changed rod from drop arm on steering box as ball joint on drop arm end knackered had to do reset about 6 times. I find when doing work on abs I need to reset a few times before it settles down it now been off for awhile and no sign of faults at moment. Almost fogot after changing hub I had hub seal that didn't work so fluid leaked inside of hub past abs o'ring I cleaned that up and replaced hub seal used sillicone sealant instead of the sensor o'ring from advice from landyzone user seams to work.
 
Last edited:
Don't wanna hijack this thread, but I don't wanna keep posting about these bloody lights!!

I had an extremely bad wheel bearing that i've now replaced, and plugged in the abs sensor, and it came up with " 4064 - Sensor right hand front (sensor DC failure, broken wire, sensor impedance too high/low) - CURRENT"

I think it was at first the crown connection was too tight which i opened up, maybe a little too much. but i've closed them back up... the question is, is there a way to reset the three amigos without the code reader (the guy who has one is on his honeymoon! and I have an MOT this week), some nifty little tricks or something like pushing the accelerator 6 times to bring on the engine light or something??
 
Don't wanna hijack this thread, but I don't wanna keep posting about these bloody lights!!

I had an extremely bad wheel bearing that i've now replaced, and plugged in the abs sensor, and it came up with " 4064 - Sensor right hand front (sensor DC failure, broken wire, sensor impedance too high/low) - CURRENT"

I think it was at first the crown connection was too tight which i opened up, maybe a little too much. but i've closed them back up... the question is, is there a way to reset the three amigos without the code reader (the guy who has one is on his honeymoon! and I have an MOT this week), some nifty little tricks or something like pushing the accelerator 6 times to bring on the engine light or something??

Is this a problem on a Discovery 2, or on your Defender?
If it's a Defender then I would suggest that you ask in that section, however as far as I know the only and proper way to clear historic faults is using a code reader. Some, but not all codes will reset themselves as you drive. But either way, they aren't just a PITA, they're indicating that there might be something wrong which needs addressing.
You say you "don't want to keep posting about these bloody lights", I presume you are referring to the ABS, TC and HDC, which are coloquially know as the "3 Amigos".
The only way to definitively track down a problem on a Disco 2 which can give rise to those lights is a compatible code reader: Nanocom, Hawkeye, Lynx or Testbook. Everthing else might give non-sensible results. Then, once you have a definitive result, believe it.
In your case, if the proper code reader says "4064 - Sensor right hand front (sensor DC failure, broken wire, sensor impedance too high/low) - CURRENT" Then check and examine the wiring to that sensor, don't go whinging that you've already changed the rear nearside hub and that didn't do anything. Remember also that more than one fault can exist on a system which once you clear the first fault the next one can pop up.
Your local indie garage might be able to read and reset the codes for you, failing that the nearest LR stealer can do it.
 
Is this a problem on a Discovery 2, or on your Defender?
If it's a Defender then I would suggest that you ask in that section, however as far as I know the only and proper way to clear historic faults is using a code reader. Some, but not all codes will reset themselves as you drive. But either way, they aren't just a PITA, they're indicating that there might be something wrong which needs addressing.
You say you "don't want to keep posting about these bloody lights", I presume you are referring to the ABS, TC and HDC, which are coloquially know as the "3 Amigos".
The only way to definitively track down a problem on a Disco 2 which can give rise to those lights is a compatible code reader: Nanocom, Hawkeye, Lynx or Testbook. Everthing else might give non-sensible results. Then, once you have a definitive result, believe it.
In your case, if the proper code reader says "4064 - Sensor right hand front (sensor DC failure, broken wire, sensor impedance too high/low) - CURRENT" Then check and examine the wiring to that sensor, don't go whinging that you've already changed the rear nearside hub and that didn't do anything. Remember also that more than one fault can exist on a system which once you clear the first fault the next one can pop up.
Your local indie garage might be able to read and reset the codes for you, failing that the nearest LR stealer can do it.

It's a Discovery 2 td5 yes, and yes I mean the three amigos as that is the thread I've posted in.

I'm not whinging about it, I'm just merely stating what I've done (so people didn't fire the usual questions for me to check against) since that 4064 error code, I believe I've fixed it, just curious if there was a nifty trick to reset them, it's brand new wiring, that came with the hub.

tbh, I'm tempted at the local LR indy, just I know where I get my MOT his Snap on code reader does sweet fook all :p:p
 
It's a Discovery 2 td5 yes, and yes I mean the three amigos as that is the thread I've posted in. I'm tempted at the local LR indy, just I know where I get my MOT his Snap on code reader does sweet fook all :p:p
That's the reason why you'll find so many members going on about using a Nanocom Evo, Hawkeye, Lynx or Testbook for reading and correcting the codes on the Disco 2. The diesel Disco didn't become fully OBDII compliant until the Disco 3 in mid-2004. The petrol Disco was compliant at an earlier date.
The reason why I asked about the vehicle, etc. is when I see a message in a thread, I do try to provide some information which might be helpful but with no vehicle mentioned, I looked at your profile which shows a 'fender.
I would be interested in what code reader was used to give you that diagnosis, but you ought to check the wiring, especially the plug and socket around that sensor since it does mention the resistance being out of spec.
As I've already said, AFAIK the only way to clear and/or reset the detected trouble codes (DTCs), including any stored historic codes is using one of the above code readers, and that's also the only way to get sensible code results too.
 
That's the reason why you'll find so many members going on about using a Nanocom Evo, Hawkeye, Lynx or Testbook for reading and correcting the codes on the Disco 2. The diesel Disco didn't become fully OBDII compliant until the Disco 3 in mid-2004. The petrol Disco was compliant at an earlier date.
The reason why I asked about the vehicle, etc. is when I see a message in a thread, I do try to provide some information which might be helpful but with no vehicle mentioned, I looked at your profile which shows a 'fender.
I would be interested in what code reader was used to give you that diagnosis, but you ought to check the wiring, especially the plug and socket around that sensor since it does mention the resistance being out of spec.
As I've already said, AFAIK the only way to clear and/or reset the detected trouble codes (DTCs), including any stored historic codes is using one of the above code readers, and that's also the only way to get sensible code results too.

Yeah, I should probably update my picture cause I use my disco more often as it's heavenly on the motorway in comparison, I have technically 'gifted' the 90 to my dad but still use it time to time.

It was the all mighty Lynx unit that provided that bit of info, there was a number of 'historical' codes it had kept hold of, but when I wiped it, the only one that came back was that 4064 code.

looks like I may be without a car for a few days till he is back off the honeymoon :p
 
The code is saying something about the impedance of the sensor being out of spec. If you have a Digital Multi Meter then the resistance measured across the sensor should be in the range of 950-1100 Ohms.
I would definitely advise you to carefully check the wiring, especially the plug and socket and between the bodywork and the wheel; that could be where the movement might cause a wire to break.
There was another member who told of a problem showing on his code reader which turned out to be a problem on the opposite front wheel sensor. So, check both.
 
Update to the current situation Bri-

Checked the wiring and it all seems good, all the bungs and cable holders are clipped and they don't seem to be moving anytime soon, couldn't spot any signs of the wire being damaged or crushed etc.

Only code that comes up now is " 4084 - Sensor Right Hand Front (Intermittent Sensor Output During Driving, Broken Wire) - Historical "

I am not sure why it's coming up as historical because the lights were out, when they come on and I pull over to read it, it's already historical in the matter of 2 minutes.

Just wondering on the new hub that I bought (BritPart) do I need to set the Air gap? I know it's saying the Obvious Broken Wire, but the wiring on it is brand new, surely it can't be a broken wire on the ABS sensor?
 
Errors can be caused by

Bearing wear.
Sensor disturbed.
Sensor removed and refitted incorrectly.
Sensor wiring rubbed through.

Usually fixed with new hubs
 

Similar threads