I have searched a number of threads and not been able to find my issue where no OBD2 readers will connect to my XKR 2013. I attached a new ELM327 OBD2 WiFi reader to my XKR 2013 then I turned on the ignition without starting the car, since I was in my underground car park I was not able to see if my iphone was connecting so I turned off the ignition and removed the ELM327. I started the car and drove out. In the daylight I turned off the ignition and I attached the ELM327 and started the car again. The car showed error messages in the instrument pod that had never shown before. "gearbox fault", "E-Diff failure" and others flashed in the instrument panel. The orange engine error light also showed. I turned off the ignition and removed the ELM, then started the car again - it started normally and the faults still flashed in the instrument panel. I drove away in "D" but the auto box would not change gear. I was able to change gear with the paddles in both "D" and "S". I turned the engine off and on a few times on the way home, but no change. After being home for a good few minutes I started the car again and there were no faults showing in the instrument pod. I have taken the car to a Jag specialist to have the stored codes cleared. His reader (which has connected previously) will not connect to the car. There is power to the OBD2 port under the dash, so the fuse has not blown, and the earth is good. We have done a hard reset by disconnecting the battery and joined the cables. The error messages have not shown since. All the pins on the car's port appear intact. We can't get any other OBD2 readers to connect. The car drives normally with no faults showing in the instrument pod. There has been a comment that there could be a gateway module that connects the car's OBD2 port to the rest of the car. Also, even though here is power to the port, could the fuse be compromised to not be letting enough power to the port? Any one have any suggestions?

 

If the fuse isn't blown then that side is OK - OBD tools use very little power.

 

Thanks for your input - Bruce

 

All the faults you listed are nearly always a result of a Low Battery Voltage situation. Like, 99.3% of the time.
Check your battery, it needs at least 12.6 volts after sitting unmolested for several hours.
Dozens of threads address this issue. Do a quick search for Low Battery. Tons of information.

 

OBD port connects directly to the bus - no gateway "module"

 

Thanks to everyone who replied to my question. There were a couple of issues. My Jag Guy tested the fuse (central Junction box) to the OBD2 reader socket having first assumed it was good when he thought the Black cable was earth in the socket - the earth is actually brown. Even with the fuse replaced - couldn't get any signal as the reader socket's wires were loose which didn't come to light until he wiggled his reader to get a signal. So 3 x hours labour later.............. The only bright side was that the battery was replaced as it showed as faulty. I wouldn't have known that if this OBD2 issue had not come up.

At the end of the day it looks like the ELM327 was responsible for blowing the fuse. I'm not trying it again.

 

I know many keep their ODBII readers connected while driving their vehicles. The one time I did that resulted in a “dynamic” configuration change. I’ll not ever do that again.
The fact that the liberally scoped fuse was blown also gives me no confidence.

 

One thing you might wanna look at is what shape the OBD two connector in the vehicle is in. I had a situation where my S type R when I first started messing with it would connect to my mongoose and I can get into all the modules and do whatever I wanted.

but then I started having issues where it wouldn’t connect it would say no communications. I went out and got one of those cheap OBD two breakout boxes end it wasn’t showing any activity coming out of the car. So I dismounted the OBD two connector from the vehicle instead of looking at the pins and I noticed that there was a lot of broken plastic on the connector itself around the pins So I started removing the pins from the connector and I noticed that many of them had a little wiper tang part of the connector socket look like it had been pushed away from the center of the connector pin. This can happen when you’ve connected to that socket too many times and it starts getting loose

So I depinned the entire connector and replaced the connector body that I got from one of the electronic parts supplier houses you find online and then I used a small pick like tool to reposition those wiper tangs back into position in the sockets- like where they should be originally and woe and behold I was able to connect to the car and communicate with the modules again.

so you might have a problem with your connector pins. Maybe you have something similar which is causing a higher than normal current draw which is blowing the fuse.

I’d recommend getting one of those OBD two breakout boxes that I talked about and just hook it up without your scanner attached and see if You get any bus activity on the little LED lights on the break up box. If you do see some activity hook up the scanner again and see what happens

 

Hello;
I see where you have owned a 2007 XKR. I recently bought a '07 XK Conv. Can you recommend a OBD reader?
Thanks in advance for your help.
rsdmitch