Ok I’m back took everyone’s advice and got the scan tool Foxwell NT520. Then I performed the plan b bypass. I’m happy to say all lights are gone except for the most important one for inspection. The brake indicator light is still on. I cannot get it to flash using the lamp test with the scanner. I have rechecked the hand brake switch and brake fluid float switch and both are working correctly. What am I missing? Any one have a similar issue. Thanks for all the previous responses. I feel the finish line is close just need a little more help
2003 discovery scammed
- Thread starter Blar
- Start date
Have you checked your parking brake switch? If you don't have any codes then it is more than likely a switch problem. I believe if you go under the brake module in the Foxwell, you can see what switches are on.
Beyond the parking brake (as Canus said), if the BRAKE light is on, that means your brake fluid is low. If it's full, see if you can move the screen in the reservior around and "unstick" the sensor. I've had that happen on a few vehicles.
I think for me the money would be better spent to buy other packages and not the Disco2 shittery. The Disco 2 only has a couple modules on a CAN network. Before all the manufacturers went to can networks for all modules interfacing with every system was hard. The T4 uses cable ends and sometimes short little adaptors between cable ends to get into restraints and whatever.
Instrument cluster on 05 to 09 LR3 and Range Rover Sports from 06 to 09. They do some crazy shit. I could post endlessly on how hard it is to pull the trigger on a $1000 cluster when its so damn hard to rule it out. So for me the answer would be to have a known good cluster and a way to program it to any vehicle. When I first started seeing the clusters fail it was probably late 2008. The cluster is the gateway in these vehicles, the gatways job is to get info from high speed CAN to med speed CAN. It's that general function that the cluster will fail to perform. The dash lights up like a Christmas tree, the suspension dropps to the bump stops. The door locks cycle if the failure is on the med speeed. Thing wont start if somebody shuts them off thinking a key cycle will fix it.
They usually store different faults for coms to multiple modules. I will usually print out the codes after I duplicate the problem and if I do that three times you would think it's 3 different cars with 3 totally different problems. A guy I work with has no problem throwing that cluster dart and hes always right. I'm the one who showed him the shit, but he has a feel for it early on when stuff starts to not make sense.
Thats why I would pay 500 for a scanner that would program around VINs. Everything else it could do would just be a bonus.
With this post, I welcome you. (sarcasm) You're finally a Disco connoisseur.
Also, I'm terribly sorry
But, for advice and help, you're
in the right place
Also, I'm terribly sorry
But, for advice and help, you're
in the right place
From RAVE:
A red brake graphic (all except NAS vehicles) or red BRAKE legend (NAS vehicles), to warn of low brake fluid
level, handbrake on and brake control system failure affecting EBD.
EBD is described as:
l Electronic Brake Distribution (EBD), to control distribution of hydraulic pressure between front and rear axles.
Replaces mechanical pressure limiting valve of previous systems.
Also, going by RAVE, there are no SLABS faults that will only illuminate the brake warning light. That leaves us with 2 things, low fluid switch or e-brake switch.
A red brake graphic (all except NAS vehicles) or red BRAKE legend (NAS vehicles), to warn of low brake fluid
level, handbrake on and brake control system failure affecting EBD.
EBD is described as:
l Electronic Brake Distribution (EBD), to control distribution of hydraulic pressure between front and rear axles.
Replaces mechanical pressure limiting valve of previous systems.
Also, going by RAVE, there are no SLABS faults that will only illuminate the brake warning light. That leaves us with 2 things, low fluid switch or e-brake switch.
Interesting - because my disco threw only the BRAKE light recently, the scenario being I tried unsuccessfully to change just the ABS sensor and it ended up being the whole hub. During the week in between wasting my time on just the sensor and getting the new hub the truck would throw just BRAKE until about 30 MPH, then all three. The code was the electrical fault to the sensor when it was just showing BRAKE.
Weird I know, and not documented.
Are you shitting me? Your just going to start throwing wheel speed sensors at this thing until the light goes out? If I wasn't a member here I would pay just to fucking watch.
Do you have any codes at present? Are you listening to anything we are trying to help you with?
In my experience, the sensors don't go bad, the hub is bad either giving the sensor a false reading or physically taking it out.
You have the NT520 now, what codes is it showing?
In my experience, the sensors don't go bad, the hub is bad either giving the sensor a false reading or physically taking it out.
You have the NT520 now, what codes is it showing?
Any single result in a randomized binary sequence is irrelevant. You have no valid point.
Installing new sensors would either solve a problem or it would not. The "a" is important. You do not know what problem will or will not be solved by replacing those sensors.
I'm glad it worked out, but success does not defend the methodology.
Cheers,
Kennith