some USB-serial adaptors have issues when using with diagnose interfaces - it's better to buy a "native" usb interface

There is nothing wrong with using a netbook. I'm using an EEEPC 701 (only celeron 900 and 1g of ram) and after setting the latency to minimum - it works ok. It was a little sluggish with only 512k of ram - but with 1G seems to work ok. edit: with the odometer - are you 100% sure the car wasnt tamper...

Thanks again Yani - that was the solution. I've reinstalled .net framework - this time version 3.5 (instead of 2.0) and it worked perfectly - same laptop, same interface, same car - managed to read all live data, and do some graphs.

madkat
alfaclub.ro

Thanks - i'll try - the .net is 2.0 afaik - i'll check and see.

any thoughts about my problem?

With version 1.6 i read the parameters of a 2004 156 jts - cleared errors, turned on/off actuators - with the setting for 156 jts selespeed (gb is manual though) and ecu "nonEU type" strange enough after two weeks i couldnt read realtime parameters - only error codes and actuators. Same ca...

Hello first ost here. tried scanning a 156 2.0 jts (man gearbox) with version 1.6 of multiecuscan. Hardware ibm T23 with vagcom kkl (normal). Got the ISO message (as the oster above) - selected continue (Y) - and managed to scan the ecu, erase errors, get real time arameters, etc... two weeks ago - ...