Multiecuscan

I don't know the answer.
But because i use the interface on a Volvo V70 as well, i have built in the switch, to have whatever connection of 1-3-7-9 i want to.
Safety First

I cannot reproduce the AlfaDiag Init of the COM Port. I always get the ISO error. Anyhow data connection is quite stable. I have done some data logging on my way to work for about 20min, with no connection drops. Odometer value seems wrong, it show something like 22000km but the cars about 130000km....

You can cut K-Line on the 4-PIN Connector to the board exactly like on the image.

@Jerry 159: I also use the cable with other cars, so i don't want to link the PINs.

Check attachment.

I pinned PIN 1-7-9 to a 4-position switch and then to the cutted k-line.

PIN 3 is not connected at the moment but would be possible.

OK. Thanks.

I have a 156 2.4 JTD 20V Facelift 2 (EDC16C9), Built in 11/2003. As i thought it is one of the first ones with 20V engine. Is there really a 20V built in 2002, meaning Facelift 1 ? I know that there are 1.9JTD 16V in Facelift 1. @Yani: Can you add an entry for the "156 2.4JTD 20V" build in 2003 and ...

Settings of FTDI COM Port are correct. Latency is set to 1. It worked the first time i tried 1.4.1 that means: - No Invalid ISO Code message - No Strange Info Data - Read Errors and Clear worked - Parameters could be read ( Battery voltage, Gas Potentiometer, etc. ) with plausible values - Acuators ...

Standard USB KKL Interface.

This one to be exact:
http://cgi.ebay.de/VAG-COM-409-1-USB-Di ... 5885695de9

Hello there, I tried Multiecuscan yesterday with selecting 156 02' 2.4 JTD 20V. I got a connection, showing no error messages. On the Info screen the Information seemed to be correct and reading Errors worked perfectly. Since i have used my USB KKL Interface for the first time i have also tried Alfa...