VAG-COM/VCDS EVERYTHING

[Roma77]

You or another saw this situation VID_0403&PID_0000? Asking because i saw 2-3 times this. But this combination was generated by V(D$ itself, damage AT eeprom and FTDI eeprom. Old versions and before 2.08 FT driver. The rest of times i saw "Not recognized" VID_0000&PID_0000. And this is because of bad China clone FTDI defective after few use, one of +/-/D+/D- desoldered or interrupt, "STC" or "AES" defective, etc.

This is just information and a program that can be used to verify a supplier should not be taken as a panacea for problems. It will be useful to someone, and someone will ruin their scanner, but it was not my fault that I did not put the program in the public domain.

[liviudiaconu]

You understud me wrong. Maybe my english is bad.
I only asked statistics how many times you saw the situation "0403/0000". I'm not saying that application is not useful.
And I said that I only saw 2-3 times that situation but created by "V (D $ .exe", not the driver, sometimes that VID / PID being different (5211/0000, etc).
Most "0000 0000" are due to poorly made FTDI clones.
I did not bring any reproach to anyone. Sorry the date meant something else.

[Roma77]

You understud me wrong. Maybe my english is bad.
I only asked statistics how many times you saw the situation "0403/0000". I'm not saying that application is not useful.
And I said that I only saw 2-3 times that situation but created by "V (D $ .exe", not the driver, sometimes that VID / PID being different (5211/0000, etc).
Most "0000 0000" are due to poorly made FTDI clones.
I did not bring any reproach to anyone. Sorry the date meant something else.

You have nothing to apologize for, our translations into English incorrectly convey thoughts to each other, everything is ok. “0000 0000” is a very bad clone and needs to be replaced; do I often encounter such situations? Yes often, because I myself do them for myself and experiments. All is well, friend, do not apologize, you know that I am very nice to you.

[hid3]

Actually V (D $'s driver is nothing more than a customised FTDI driver. We all know the German man and his philosophy, so... No surprise at all

[jakuza]

Does anyone have a JED file for the ATF HW 46?

Thanks to Elektrik and his hard work for couple weeks on this - yes there is.
It is on this thread, I mean about 100 pages before, so just use search.

[sorinc98]

i have a vcds 18.9 cable . at start works ok, but now i m just getting an error " too many communication errors " i try reinstall but nothing work, what i can do ??

[alexm1]

What you see on "About"? License Status is Invalid or Valid?

[sorinc98]

the cable does not connect to the car and idk why, i try different car but nothing chagen. first work about 5-6 times and now no chance to get it. i try reinstall but no successs1.jpg this say when i connect just the cable to pc but when i connect to thess2.jpg

[alexm1]

Share some pics with both sides of PCB. Pics should be taken close to the pcb and with good resolution.

[Fabio89]

Guys

Anyone know why clone version still doesn't work on New Polo MQB ? It works on Tiguan Mk2, New Jetta GLI 2019, Golf mk7,5 but in New Polo shows messagen of "old interface".

[Domi]

only V2 interface Genuine suport UDS protocol

[FastFast]

Where can I download the HEX-V2 scheme? Or differences from V1.

[azza2]

Loader v9.2 released! It improves compatibility with non English versions and VCDS 19.6.0 version.


http://ge.tt/6I9tkOx2
https://www101.zippyshare.com/v/biPvu9Lt/file.html
https://www.sendspace.com/file/5qr55f
https://uptobox.com/l96rbs2lo9h6


Kolimer ......

Thank Kolimer very much.


I used VCDS 17.1.3 English before. It seems like cable version was 1.96, I am not sure.


Few days ago, I checked cable with the tools and flashed it.
Then I installed VCDS 19.6.1 ZHS downloaded from official website.
It's working fine when I am doing autoscan twice and enter ABS module, clearing fault code.


I got "communitation error" few times when I was clearing fault code in ABS module and entering the module last night. This error appeared when I was trying 19.6.1 ENG first last night.
Then I used ZHS back, no error at my same operation. But, I got the error with ZHS too after that. It's not appeared everytime, occasional. I can use 19.6.1 ZHS to do something successfully still.


Another question btw.
Since I upgraded my Instruments to "L5K D92 087 3" from "5KD 920 870", and upgraded VCDS 10.6.4 to 11.11 12.12 17.1.3, I got a popup message "no rod file found" which is caused by following.
----
Part No SW: L5K D92 087 3 HW: L5K D92 087 3
Component: KOMBI H43 0458
Revision: X0043005 Serial number: 00000000000000
Coding: 170A01
Shop #: WSC **07 0** 104**
ASAM Dataset: EV_KombiUDSMM9RM10 A04709
ROD: N/A
VCID: 4D9B02C11C34B3709AA
No ASAM data for: "EV_KombiUDSMM9RM10" ()
No fault code found.
---


I still got this mesage after I upgraed cable and use 19.6.1 whatever ZHS or ENG downloaded from official Chinese website.


I checked some forums for this. Some guys don't have the "No ASAM data" for this Instruments like following.
---
Part No SW: L5K D92 087 3 HW: L5K D92 087 3
Component: KOMBI H43 0458
Revision: X0043005 Serial number: 00000000000000
Coding: 170A01
Shop #: WSC 00079 790 00000
ASAM Dataset: EV_KombiUDSMM9RM10 A04709
ROD: EV_KombiUDSMM9RM10_VW36.rod
VCID: 4D917A3E1C938276201-8018
---


So, how can I solve this problem?

[kaalis]

Those part numbers could be specific to China market in which RT has no interest. Find someone with geniune cable, scan the car with it and ask him to post in RT forum.

[azza2]

Those part numbers could be specific to China market in which RT has no interest. Find someone with geniune cable, scan the car with it and ask him to post in RT forum.

Some guys got it working which also using ZHS version. See the last part of my last post.

If is there a way to solve that with relpacing rod files. I didn't succeed yet by this way.