NefMoto

Hello, I am trying to build a bench setup to read and flash EDC15 out of a MK4 1.9 TDI jetta.

I have the OBD2 connetor and ECU 81 pin pug from out of the 2003 donor car.  I have done lots of searching and readingand have the following wiring setup:

ECU (Can-H) pin 7 <---> OBD pin 6
ECU (Can-L) pin 6 <---> OBD pin 14
ECU (K-line) pin 16 <--> OBD pin 7
ECU (power) pin1&2 <---> 12+
ECU (ground) pin 4&5 <--> Ground
OBD pin 16 <--> 12+
OBD pin 4&5 <--> Grown

When I start up nefmoto (v1.9.3.2) it finds my VAGKKL cable.  However, whenever I try to connect I get Error "Failed to read test echo from FTDI device. Make sure the cable is in dumb mode and connected to the OBD port."

If I go to KWP200 Settings and unselect "Should Verify cable in Dumb Mode" and try to connect it still fails.

Can someone please point me in the right direction, is my bench setup wrong or is there an issue with my cable?

Power light on my VAGKKL cable is on so its getting OBD2 power.

keep your head up. impossible is nothing.

-can high/low are totally not needed for obd2 reading/writing. these are drivetrain communication wires
-also +12v wires are in the wrong place, need ecu pin 2 and 37, add a switch between wire to 37 to simulate ignition
see scheme. edc15vm+ connects the same way as edc15p+ btw.
http://mhhauto.com/attachment.php?aid=68953 (http://mhhauto.com/attachment.php?aid=68953)


and test it with vcds or something first...

Nefmoto will not flash anything other than ME7.

oh OK thank you PRJ any suggestion on what software I should use to download and flash for an EDC15?

Also, I did make some progress by switching to getting VCSD-lite working first.

Turns out that the Blue "KKL Vag-Com" cable does not work under Windows 7 with the latest FTDI drivers  (CDM v2.12.10).  I had to go into device manager and delete all the device and click delete associated drivers, then reboot.  Once I did that I could go into device manager and select the device under other and let windows 7 search for new driver online.  Once the driver was installed I had to go into the COM port to COM4 and under advanced set the "latacy timer" to 2 as noted on the VCDS website.

After doing all this and adding a switch as suggested to simulate ignition I can kinda connect, however, I am still getting errors with VCDS-lite, when I test the COM port the latency is poor and when I try to connect to the ECU it trys an trys and then gives an error that "to many communication errors occurred".

So I am closer but still not there, anyone have suggestion on resolving latancy issues under windows 7 for the blue vag-com cable?

mpps v13 does these fine. sometimes need to write in bootmode, sometimes not

But your bench harness wont work, as i mentioned earlier