Multiecuscan

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 AlfaDiag Demo, VAG-Com, Unidiag and OBD2 Scanmaster to see which one is working. Everytime i have switched to another software i have had to turn ignition off and back to MAR. After trying OBD2 Scanmaster (which hasn't worked) i have turned ignition back to MAR and got lots of error messages on my car panel ( Error VDC, ABS, Airbag, Turn off car, got to workshop ). When i have tried to connect with Multiecuscan i have got the following message 'Invalid Iso Code" and the corrupted 'Info' data.



I have to admit that my car battery went down shortly after that.

Overnight i disconnected the battery and recharged it. Fortunately today the errors are gone and the car works again ( PUUUHHH, had a bad sleep over this).

Reconnecting with Multiecuscan shows my the same error 'Invalid Iso Code' like yesterday. AlfaDiag shows the following ecu info.


Do i have to worry about this ? Is the ECU Data somehow corrupted?

Hi!

With interface are you using with AlfaDiag?

Standard USB KKL Interface.

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

Hi,

i m think your problem come from you com settings in windows. Don't miss to set the latency to 1 (and not 16, the default value). Check the HOWToUse link.

I have the same mistake (Invalid ISO code) and now with the correct setting, the error disapear.

You can found more information on my car test here :

http://www.alfanatiques.com/forum/odb-m ... 17193.html

Fred

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 works ( Cooling Fan, etc.)

But after my multiple error messages and battery problem, i always get the "Invalid ISO Code" message.
If i ignore the message, i can use some actuators, but parameters don't show plausible values, or the values are freezed an do not change.

Today i have tried 1.5.0, trying with setting for 166 JTD 03 2.4 JTD 20V with CF3 and CF4 ECU but no luck.
Even tried a different notebook with latest FTDI Drivers. No change.

I did a connect with Unidiag showing the following messages.


Version 1.5.0 no shows


I also sniffed the serial communication of Version 1.5.0:

Sorry for the poor log. blue (sent by PC), red (received by PC)

HI,

I see where the problem is. I will add a fix for your problem in the next version.
Thanks for this information.

One more note - according to the ISO Code on the images your ECU is EDC16/CF3.

Yani

OK. Thanks.

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.
But the value change on my 20min test drive seems right.

Hi,

I already answered that I know where the problem is. It is fixed in the new version. You just need to wait a few days...

Yani