Anyone had an issue like this?
Today, my car is totally freaking out. Its throwing every code known to man. I get config e error, I have no rpm gauge, I have no temp giauge, I get parkbrake error, I get gearbox fault, I get restricted performance, no DSC. Just about anything the car can throw it is throwing.

The last thing I worked on, was replacing a rear brake caliper on left, and pads on both rear sides, and brake hose on the rear right side. The car was fine before that and not throwing any of this. I dont see how any of this could be related.
I did run the battery down, but have since recharged it. Its not that old and is fully charged. I unhooked the battery for a while to clear everything, but it is still doing this.

Could I have somehow done something to the ecu connection? where is that? Anyone have this before? Makes no sense.........

Thanks for any ideas to fix.

 

Does the car start, & stay running?
Do you have a Jaguar specific reader?
If so, just clear the codes.
Have seen mine do this before.

 

Yes it does start and run, can drive it. Dont have a jag specific reader, i Have an ODB II that I use for clearing codes.
I did pull battery cable once, and cleared codes once.
I have left battery unhooked for the last 4 hours so I will post if that helped or not.....
Thanks for the reply.

 

1. From Robert rawle u k Britain South Wales this problem happened to me had the front brake disks and pads changed on my jaguar xjr x350 2005 all messages came up took it to a jaguar specialist they found that the abs cable was jammed behind the bolt holding the caliper on they took the ecu out had to have a programme made to reset it put it in changed the abs sensor because the bolt had cut through the sensor worked perfectly
   

 

Thanks! I will look at that. I had the right rear ABS disconnected while I was working on the wheel bearing a few weeks ago. Possible that maybe that has a kink or a frayed section, I will inspect.
That would make sense that there is a short in the system.

I left my battery off for afternoon. Car started and ran normal, guages worked etc. Then, I hooked my code reader up, and everything went haywire again. So maybe a short somewhere would cause this behavior.

 

"Then, I hooked my code reader up, and everything went haywire again."
I had very similar experience, plugging in cheap OBD BT reader. Just when I got my car, it hooked up my OBD reader that worked fine on 2006 Toyota, 2014 Honda; 2019 Subary and 2016 BMW. On my 2004 X350 the message center come up with all messages you can think off! I brought car just 3 weeks ago and drove it 300 miles home, then another 500 miles on trip to NYC, car was working great! I just plugged damn $10POS in out of curiosity, than anything else. Nothing was touched on the car!. Car was still working fine, if reader is not plugged in! I ordered Carsoft reader that reads Jaguar proprietary codes, some of them.
I keep $10 stuff just to help friends an neighbours! It does not come anywhere close to Jaguar!.

 

My code reader was not a cheap one...it was like $125 and I have been using it on my jaguar without issues for 5 years now, never any problem. Used it to read, clear codes and always has worked fine until now. I think I have a short in the wiring most likely the ABS sensor wire. Will look tonight.
Thanks for the input though! Always appreciated and useful.

 

I would check your earths before doing anything drastic. There are 4 ,I think, behind the front headlights plus more scattered around the car. I had one of mine snap off just as I got home and I had all the error codes then. Get a spanner on the nut and give them a gentle tighten, a rotten one will fall off easily.

 

So, I checked the front ground points anyway, don't know where the others are. They look very good, no corrosion or weakness. My car has very little rust or corrosion anywhere.
I pulled both wheels off, and inspected the ABS lines. They are in place, and no sign of breakage or excessive wear. I disconnected both and reconnected.

Upon firing up the car, now I have different code. Now my guages work, and I am getting a "config b" instead of everything else I was getting.
I looked up config b, and either folks did a reflash, or after 3 or more tries of hard resetting the ECU, it finally went away. So I have unhooked both battery cables and will let it sit all day while at work and see if its better later.

Fingers crossed.

 

WOW! AMAZING! I Can't believe it.

I left my battery disconnected all day yesterday and all night, with the cables touching each other.
This morning, I start the car. every single code and problem is gone. Took it for a few miles drive. No codes. Runs great.
Shut it off when I got back. Restarted. Still good. Moved some cars around, started it and moved it. No issues.

I can't believe that fixed it, but I am confident enough it is reset that I will drive the car to work today. I'm so happy it worked!

 

Car is still good.
None of the codes have come back after a week + of driving.
Just wanted to follow up with the result.