I just changed the lower lambda probe and tried to clear the MIL with my generic scanner. It did not find the ECU... I disconnected the battery and checked all three ECU fuses, they are okay. After reconnecting the battery, my generic scanner found my ECU again. About MES: Multiecuscan / Settings / ...

I disconnected pin 7 and connected the board to pin3. Result: the interface is not detected anymore.

Sorry for the confusion, I meant: I tried MES 1.3 today, not FES. About airbag: I will have to modify the KKL interface before which I won't do today.

Thank you for helping!

Tried FES 1.3 today, still no luck. F11 searches for a while and finds nothing.

On the ECU I read the label ME73 M003 - I think. Old eyes, dm light and tiny characters on the label.
Which of both available ECUs should I select then?

Olaf

[*]Hi Eddy, Hello This interface works with KKL Multiecuscan I think that certain settings are not correct. as driver com port Latency Time Multiecuscan settings Greetings Eddy Driver: I tried http://www.ftdichip.com/Drivers/CDM/CDM20814_Setup.exe (link from your manual) and the driver from http://w...

Does your KKL interface work?

New cable, 2 PCs, 2 OSes (XP and Win7). Still "no ECU response".

Are there KKL interfaces that simply do not work? I have this one:
http://cgi.ebay.de/ws/eBayISAPI.dll?Vie ... 5567292001

Olaf

I only have my Punto to test, my other car has a CAN bus. On the Punto, MES does not find any single module when I click on "scan".

Anyway, the KKL vendor offered to change the interface. I hope that it is defective out of the box, and that the new one will work.

I tried that driver, still no luck. The VAG KKL should work out of the box when I want to read the engine's fault codes, right?

My generic OBD2 scanner (Autel brand) has no problems with the car.

Chip is FT232RL