Punto '99 1.216V no ECU response

[oz42]

Hi,

with my VAG KKL USB device with FTDI chip I always get "no ECU response". I already tried another laptop with a fresh installed XP SP3, same result.

The connection test is okay.

Do I need to modify the interface? It has 4 connections to the OBD port.

Olaf

[oz42]

Chip is FT232RL

[Alfaeddy]

Hello

Which driver did you use?

Try it once with this driver

http://www.ftdichip.com/Drivers/VCP.htm

Greetings Eddy

[oz42]

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.

[alfa156sarajevo]

Can you connect to some other systems (abs/airbag) on your Punto with that KKL interface?
Does it working with other systems or does not work at all?

[oz42]

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.

[oz42]

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

[Alfaeddy]

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

[oz42]

[*]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://www.ftdichip.com/Drivers/VCP.htm later on
COM port: on WinXP, one COM port appeared; on Win7, I got two. One of the two ports seemed to work.
Latency: set from 16 to 1. I also disabled "serial PnP". I left Baud rate and other settings at default values.
MES settings: I started "scan for interfaces" successfully, after that I did a "latency test" which showed reasonable results.

Perhaps I did something in the wrong order? What I did:
* connect KKL to USB
* connect KKL to car
* ignition on (MAR)
* start MES

Is that correct?

[Alfaeddy]

Hello oz42

Yes, your approach is correct

Your interface is detected?
Thus should a connection can be made to the controller.

One more question.
If your KKL interface is detected!
But should also scan (F11) will work with the existing controllers are detected.
What did you find there?

Greetings Eddy