PDA

View Full Version : Bluetooth OBDII Problems



Strop
10th February 2024, 04:58 PM
Hi all,

I come here seeking help acknowledging that I know nothing.

I am having some electrical problems with my D5. It is a massive parasitic draw that flattens the battery within hrs. I have been able to track down eventually to when it occurs but I can not explain it. First the issue.

It has been diagnosed as the Alternator not shutting down properly and continuing to draw power from the battery. I have been told that it needs to be replaced - still waiting on that one though. The unusual thing is that when I leave the dealers the problem disappears - I am assuming they have done a system reset or something similar. I still can see that the battery is never being fully charged though - they acknowledge that is part of the problem. Anyway - drive out of the dealers go home, turn the car off and the alternator doesn’t draw power. Will continue like that till I do the following. I have been slowly adding things back and doing things to try and find a cause.

I can see that if I plug in my OBDII reader and drive around nothing happens to the car. Alternator is not triggered after shutdown.

If I connect to the OBDII reader with my phone and connect to the reader then stop the car the issue reappears. I am using a VEEPEAK bluetooth dongle and the software I am using is Car Scanner ELM OBD2. I do not use the dongle to alter anything just read data - actually purchased it so I could monitor transmission temps while towing. Anyway I select Land Rover and generic OBD2 during setup.

I have no idea why this could be happening and any help would be appreciated.

Pedro_The_Swift
12th February 2024, 06:08 AM
Disconnect the dongle, its probably polling the car every couple of minutes..
I run a Gap tool in my RRS 365 days a year.

Strop
14th February 2024, 08:54 PM
I disconnect it and remove the dongle and it the issue still exists. Like it starts the problem and if a disconnect the battery to do a ECU reset the issue goes away till I use the dongle again.

Dongle works fine on my other cars and doesn’t cause any issues I am aware of.

shack
15th February 2024, 09:56 AM
It's quite possible there's a fault with the dongle.

It's also quite possible that CarScanner has issued an incompatible request and put the ECU into some kind of loop.

I would either try changing the dongle or select a different connection profile, I think it has listing specifically for D4, I'd try that one.

The generic ones are a bit so so.