VAG-COM/VCDS EVERYTHING

[networkers]

use Kolimer's v6.3 or v7.0

v7.0 did I miss something?

[kaalis]

• The v1 and v2.7 contains only 1 eeprom for 0x44 and 1 for 0x46 and the v4 and v6.3 contains eeprom for each languages. Is it means that the v1 and v2.7 are multi langs?
• Can somebody tell me which version of \/€Đ$ use the v1, v2.7 and v4 packages?
• Is there any way to check a BIN/HEX files about it's supported \/€Đ$ version?

1. Kolimer added languages later. You can flash any loader version, install vcds language of your choice and see does it work. Definitely faster than 2 days waiting for answer.
2. You can start with 17.1.x and test each of them going to more recent version while you got licence lost. Had it written down somewhere but can'f find it now.

Leave old versions in history. Some had coding bits shifted, etc.
I understand you are searching for version combination that works in every language. Don't want to dissappoint you.

my new clone vcds hex v2

Looks like fake v2 by looking at device manager and port test

[Tib82]

Why do you keep diggin up old versions? Have you tried Windows 98? LOL. Forget about the previous versions. Each Kolimer's version is a significant improvenet over the old one; once new one is out, the previous ones should be forgotten.
Having said the above, use Kolimer's v6.3 or v7.0 with any VCDS version, starting from 17.1.3 till 18.2.1 and enjoy.

What OS I'm using is depends what is the hardware inside the PC. So in a rare case yes, I can use Win 98

For myself 18.2 Eng is quite good. So why I diggin up old versions?! Maybe because I need an older version for a specific case As I wrote previously I need 2 specific languages (German and Hungarian) in the same time and with 6.3 it's not available. So if an earlier version could work with fully multi lang (in the same time), the 17 is still quite enough for a 10 yrs old car. So can you help me about my questions above?

Another question:
Is the v7.0 out? Now is it supports the 18.2.1 English version? Where can I download this?

[belkor]

Looks like fake v2 by looking at device manager and port test

I know it´s vcds hex can with other design

[hid3]

v7.0 did I miss something?

Actually no. It's for alpha/beta testers.

2. You can start with 17.1.x and test each of them going to more recent version while you got licence lost. Had it written down somewhere but can'f find it now.

Leave old versions in history. Some had coding bits shifted, etc.
I understand you are searching for version combination that works in every language. Don't want to dissappoint you.

^^ Yeah, this one.
Hints:
V2 Loader + 17.1.3 = MultiLanguage on one EEPROM
V6.3 Loader + VCDS 17.8.0/17.8.1/18.2.0 = Two languages (Your and English) on one EEPROM

[Tib82]

Hints:
V2 Loader + 17.1.3 = MultiLanguage on one EEPROM
V6.3 Loader + VCDS 17.8.0/17.8.1/18.2.0 = Two languages (Your and English) on one EEPROM

Because I was sure that previously I met with a 17.8.1 multi lang cable, I flashed and tested several EEPROM + Loader versions, and I got the followings:
v6.3 EEPROM + v6.3 Loader >> 17.8.1 and 18.2.0 with max 2 languages
v2.7 EEPROM + v2.7 Loader >> 17.8.1 multi lang

Different versions of EEPROM + Loader combo (e.g.: v2.7 EEPROM + v4 Loader) makes "Interface: Not Found!"
So yes, the multi language \/€Đ$ is possible with ATmega162, but only the 17.8.1 and eariler versions can work like this.

[Resko]

Are you sure, that you have written the right FTDI file? Check what kind of FTDI-Chip is on PCB. I guess you need to write "ftdi_mprog_BMBL.ept" with mprog.

Then you will get:

USB VID=0403
USB PID=FA20

Manufacturer=Ross-Tech
Product=Ross-Tech HEX-USB

Hello i have the FTD2323BL chip and i used BMBL ept file with mprog. I dont see any issues when programming with mprog. Here is what i get when i take read and parse in MPROG:
mprog.jpg

[hid3]

Tib82, please do not re-invent the wheel.
Firstly, I am not sure what actually you mean by v2.7.
Kolimer has never released such version.
But I assume you mean V2.
Trust me, 17.8.x will NOT work correctly with V2 (amd multi-lang). Been there, done it, proved that.
17.1.3 is the maximum what will work with V2 and multi-language setup.

PS: "license is valid" does not mean you have a fully and correctly working interface at all!

[belkor]

Hello i have the FTD2323BL chip and i used BMBL ept file with mprog. I dont see any issues when programming with mprog. Here is what i get when i take read and parse in MPROG:
mprog.jpg

seems to be ok
run now VAGCOM_EEWriteLang as admin choosing your language and with AV and/or Windows Defender off
after all ok, run vcds from VCDSLoader that you previously placed in vcds instalation folder

[adicristi]

This is my interface. Is broken. From what I saw ...I have missing pieces.

Sent from my Mi A1 using Tapatalk

[alin 151]

This is my interface. Is broken. From what I saw ...I have missing pieces.

Sent from my Mi A1 using Tapatalk

Clean with alcohol isopropyl rewrite and will work.
Missing pieces is not important.... aes.

Sent from my SM-J530F using Tapatalk

[kaalis]

Firstly, I am not sure what actually you mean by v2.7.

He have read archive extension as part of version number.
VCDSLoader_v2.7z

This is my interface. Is broken. From what I saw ...I have missing pieces.

Who sold you this?

[adicristi]

China - aliexpress .
1. When I write the interface sometimes I have FT_Write I/O error...
2. For the first time after flashing it, it works. But if I disconnected from USB and I connect again will not work. "Interface not found."
3. What shroud I check on PCB ?

[Tib82]

...
Trust me, 17.8.x will NOT work correctly with V2 (amd multi-lang). Been there, done it, proved that.
17.1.3 is the maximum what will work with V2 and multi-language setup.

PS: "license is valid" does not mean you have a fully and correctly working interface at all!

What I checked: After flashing my interface with the v2 single-EEPROM content + using v2 Loader, the 17.8.1 English, German, Hungarian, Romanian softwares recognised my cable as "Valid / Activated" and I reach many modules in my car and I easily recoded them.

I don't know what does it mean "NOT work correctly". I don't know how the loader works. Maybie it's bit more than just pair the fake cable SN with the software. But tf the cable recognised as a valid cable, how can it works incorrecly? "Been there, done it, proved that." No worries, I trust you. I just would like to understand what is wrong with 17.8.1 + v2 loader, what was the exact problem what you saw.

He have read archive extension as part of version number.
VCDSLoader_v2.7z

It looks a possible reason my misunderstood Thanks for the correction

[belkor]

China - aliexpress .
1. When I write the interface sometimes I have FT_Write I/O error...
2. For the first time after flashing it, it works. But if I disconnected from USB and I connect again will not work. "Interface not found."
3. What shroud I check on PCB ?

plug in the cable and run as admin VAGCOM_HWType and report