OBD2 Gauge killing battery
I can't remember if I've already tried this or not, but I recall that one YouTuber (Sal's Garage) said that he simply unplugged the dongle wherever he parked the car.
Might give it a try (again?) at some point. Not gonna hold my breath.
Might give it a try (again?) at some point. Not gonna hold my breath.
thanks, will attempt this during the weekend and report back. I’ve never tried just removing it but worth a try…but this also failed during emissions testing so assuming it doesn’t work.
My guess is that won't work. On my 2017 SVR if I plug anything into OBD then remove it, the system doesn't fully shut down and it drains the battery. Emissions testing, pulling codes etc
Also note on mine the annual 'service required' indication comes on the Jag app on my phone but never appears on the car's instrument cluster...
Also note on mine the annual 'service required' indication comes on the Jag app on my phone but never appears on the car's instrument cluster...
This OBD-2 battery killing appears to be fairly widespread on other JLR vehicles and seems be caused by the IPC (Instrument Panel Cluster) failing to sleep.
From the SSM for some Land Rover models linked below:
“Cause:The issue occurs when the instrument panel cluster
sees a functional request for a diagnostics service it
doesn't support & then it will not be able to go to sleep”.
https://static.nhtsa.gov/odi/tsbs/20...68925-0001.pdf
There is also a related TSB for Land Rover vehicles.
https://static.nhtsa.gov/odi/tsbs/20...72155-0001.pdf
Here is a thread from a Land Rover forum. It would be amazing if our issue isn’t the same.
https://landroverforums.com/forum/ne...solved-117524/
No doubt the fix is trivial if JLR could be bothered to get off their ***, but I’ll not hold my breath. Anyone with this issue visiting their JLR should bring this up and try to get a straight answer.
A solution from the other end might be to figure out exactly what the “functional requests for service” the IPC doesn’t support are and stop the OBD-2 dongle from sending these.
This issue is a bummer, I’d really like a set of proper gauges.
From the SSM for some Land Rover models linked below:
“Cause:The issue occurs when the instrument panel cluster
sees a functional request for a diagnostics service it
doesn't support & then it will not be able to go to sleep”.
https://static.nhtsa.gov/odi/tsbs/20...68925-0001.pdf
There is also a related TSB for Land Rover vehicles.
https://static.nhtsa.gov/odi/tsbs/20...72155-0001.pdf
Here is a thread from a Land Rover forum. It would be amazing if our issue isn’t the same.
https://landroverforums.com/forum/ne...solved-117524/
No doubt the fix is trivial if JLR could be bothered to get off their ***, but I’ll not hold my breath. Anyone with this issue visiting their JLR should bring this up and try to get a straight answer.
A solution from the other end might be to figure out exactly what the “functional requests for service” the IPC doesn’t support are and stop the OBD-2 dongle from sending these.
This issue is a bummer, I’d really like a set of proper gauges.
There won't be a 'fix' from JLR, as the official stance is to not put unsupported devices on the vehicle, which means anything you plug in to the OBD2. I agree it's stupid, but most aftermarket devices poll things on the network to get data, and while those modules are seeing a device asking them for info, they stay awake. Some modules ignore it and go to sleep anyway, but not all of them, and that creates a draw when the module stays up, and keeps the networks up, which keeps other modules talking as well.
I’d be happy if they just fixed connection to required emission equipment but not counting on it. May look into installing one of those quick battery disconnects, not for the OBD2 device but for emissions.
There won't be a 'fix' from JLR, as the official stance is to not put unsupported devices on the vehicle, which means anything you plug in to the OBD2. I agree it's stupid, but most aftermarket devices poll things on the network to get data, and while those modules are seeing a device asking them for info, they stay awake. Some modules ignore it and go to sleep anyway, but not all of them, and that creates a draw when the module stays up, and keeps the networks up, which keeps other modules talking as well.
Thread
Thread Starter
Forum
Replies
Last Post
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)










