Smart Car of America Forum banner

Resurrecting Bricked W451 ED3, OBD2 Trouble

206 Views 3 Replies 3 Participants Last post by  Geeman
Hello all. I've been reading up lots on this forum and I recently attempted to resurrect a bricked 2013 Electric with the assistance of Bill Kichman. I unfortunately ran into some trouble after test fitting my refurbished battery; the OBD2 port doesn't appear to work!

I've confirmed that fuse 15 is installed and intact, as well as confirming that pins 4 and 16 of the OBD2 socket are at 12 volts nominal. I've attempted to communicate with the car using two different diagnostic readers; a BlueDrive bt wireless smartphone dongle and an Innova 3130lat wired reader. Both appear to detect power from the port but are unable to establish communication; the BlueDrive is completely unresponsive save for a power light and the Innova returns an "unable to connect" error. I know that both scanners are at least partially functional because I can get them to work with my 2008 Toyota Prius.

What causes the OBD2 port to act up like this? Is there something wrong with the CAN bus? Thank you all in advance!
1 - 4 of 4 Posts
I also own an ED3 and BlueDriver dongle and know for a fact that the car is not supported. I’d check and see if the other dongle supports the car.
It's disappointing to hear that a supposedly universal scanner won't work on a car I need it most for. After doing some additional digging, it looks like the Mucar V06 is the way to go, as salty as the price tag appears to be.
Firstly, a couple of questions.
You mention OBD pin 4 & 16 are at 12V nominal but pin 4 should be a ground, it might just be me being daft as you also say you have leds illuminated on your interface.
Is the 'P' illuminated next to the shift lever when the ignition is on at any time?
If it is on the CAN bus is normally active.

I think if you are resurrecting an ED3 battery pack you need to look at the Xentry / Vediamo combination with Tactrix type J2534 Passthru OBD interface already discussed on the forum or at least the Arduino based Battery Diagnostic tool, I think both can give valuable information for an ED3 in this condition.

The 'universal' scanners I have seen either don't work at all or produce confusing messages because the P codes from the the defective ED3 HV system are not typically seen by a 'universal' scanner.
It is hard enough interpreting the P codes using Vediamo which translates the original factory message to English with some German thrown in but it works well once you get used to it.
Xentry on a virtual machine works well and is the same software as the dealer uses and allows you to view various signals and clear most codes.

I also gibbered on about Xentry/Vediamo/J2534 method in previous posts and it is also where someone also mentioned using a Mucar Vo6 with an ED3 'add-on' but I have not used it :-
See less See more
1 - 4 of 4 Posts