Fault Diagnostics with VAGKKL
Fault Diagnostics with VAGKKL
Hi.
First time using MultiECUScan with my Alfa 156 2004 2.0 JTS.
1) MultiECUScan finds my VAGKKL at COM2
2) I select model version 156 '02 JTS 2.0
3) I use the Settings/Interfaces/TEST button
see result in attached picture.
Result ends in
Testing timer with 250ms
The operation has timed out.
4) Ive tried to lower speed on Com Port
5) I've put Recieve and Transmit Buffer to low but no improvement.
6) Tried a WIN8 machine instead of XP but with same result.
Conclusion.
Can I somehow rule out that my VAGKKL cable is faulty? (Its a cable with CH340 chip, downloaded the latest driver from manufacturer site) Not the best chip when I do a google on it.....
Any more settings to try?
Is the model version correct? Anyone who has connected to a 2004 2.0 JTS?
All help higly appreciated.
/Peter
First time using MultiECUScan with my Alfa 156 2004 2.0 JTS.
1) MultiECUScan finds my VAGKKL at COM2
2) I select model version 156 '02 JTS 2.0
3) I use the Settings/Interfaces/TEST button
see result in attached picture.
Result ends in
Testing timer with 250ms
The operation has timed out.
4) Ive tried to lower speed on Com Port
5) I've put Recieve and Transmit Buffer to low but no improvement.
6) Tried a WIN8 machine instead of XP but with same result.
Conclusion.
Can I somehow rule out that my VAGKKL cable is faulty? (Its a cable with CH340 chip, downloaded the latest driver from manufacturer site) Not the best chip when I do a google on it.....
Any more settings to try?
Is the model version correct? Anyone who has connected to a 2004 2.0 JTS?
All help higly appreciated.
/Peter
- Attachments
-
- TEST_result.JPG (179.84 KiB) Viewed 5148 times
-
- Posts: 180
- Joined: 18 Dec 2013, 18:22
- Location: Guarulhos/SP - BRAZIL
Re: Fault Diagnostics with VAGKKL
Hello Peter
It may seem strange, but I also have a CH340 and the Multiecuscan (under Windows XP) sees TWO interfaces in TWO COM ports (one real and one "fake") at the same time and only works if you configure both. It would be your case? Preferably the interface is connected to the ECU.
I have no time now to show, but if you look through my posts you will find what I say before I get to the forum tomorrow.
Good Luck
Walter
It may seem strange, but I also have a CH340 and the Multiecuscan (under Windows XP) sees TWO interfaces in TWO COM ports (one real and one "fake") at the same time and only works if you configure both. It would be your case? Preferably the interface is connected to the ECU.
I have no time now to show, but if you look through my posts you will find what I say before I get to the forum tomorrow.
Good Luck
Walter
Re: Fault Diagnostics with VAGKKL
Hi Peter
Just try this driver and provide only the Latency Time to 1
http://www.ftdichip.com/Drivers/VCP.htm ( use 2.10.00 )
Greeting Eddy
Just try this driver and provide only the Latency Time to 1
http://www.ftdichip.com/Drivers/VCP.htm ( use 2.10.00 )
Greeting Eddy
-
- Posts: 180
- Joined: 18 Dec 2013, 18:22
- Location: Guarulhos/SP - BRAZIL
Re: Fault Diagnostics with VAGKKL
Dear Eddy and Peter, already warning that the CH340 does not accept FTDI drivers.
Re: Fault Diagnostics with VAGKKL
So no need to try FTDI driver on CH340 chip?
I downloaded the FTDI driver but do not know how to upgrade the driver so my KKL uses it. Tried to do it using COM Port properties and update driver and choosing the *.inf file but got error message. Also installed using exe file but do not know where the drivers end up in WIN XP.
I downloaded the FTDI driver but do not know how to upgrade the driver so my KKL uses it. Tried to do it using COM Port properties and update driver and choosing the *.inf file but got error message. Also installed using exe file but do not know where the drivers end up in WIN XP.
Re: Fault Diagnostics with VAGKKL
Waltomatic wrote:Dear Eddy and Peter, already warning that the CH340 does not accept FTDI drivers.
Hi Walter
The warning of the CH340 chip's really
but has apparently been canceled.
But as a precaution I therefore advise for older drivers (02.10.00)
Greeting Eddy
-
- Posts: 180
- Joined: 18 Dec 2013, 18:22
- Location: Guarulhos/SP - BRAZIL
Re: Fault Diagnostics with VAGKKL
I have tested all versions of FTDI in my CH340. I believe that only a newer version (but there is no longer 340) could accept these drivers.Alfaeddy wrote:Waltomatic wrote:Dear Eddy and Peter, already warning that the CH340 does not accept FTDI drivers.
Hi Walter
The warning of the CH340 chip's really
but has apparently been canceled.
But as a precaution I therefore advise for older drivers (02.10.00)
Greeting Eddy
Greetings!
Re: Fault Diagnostics with VAGKKL
Hi Walter
May very well be
Well you've tested the driver
I also wanted to do but I did not have the time
Greetings Eddy
May very well be
Well you've tested the driver
I also wanted to do but I did not have the time
Greetings Eddy
Re: Fault Diagnostics with VAGKKL
Hi. Should I read your posts so that ITS possible to use FTDI together with CH340?
Thanks for your assistance!
Thanks for your assistance!
-
- Posts: 180
- Joined: 18 Dec 2013, 18:22
- Location: Guarulhos/SP - BRAZIL
Re: Fault Diagnostics with VAGKKL
No, it's not about using FTDI drivers with CH340, this is IMPOSSIBLE! But to read about configuring TWO interfaces on Multiscuscan.PAN wrote:Hi. Should I read your posts so that ITS possible to use FTDI together with CH340?
Thanks for your assistance!
Go to my profile and click "Search user's posts"...
But I already did it for you... viewtopic.php?f=5&t=1493&p=15018#p15018