VAG-COM/VCDS EVERYTHING

**Tib82** · 25th September, 2020, 05:21 AM

Originally Posted by j8y

Attachment 747474 Attachment 747471 Attachment 747472 Attachment 747473Hi guys I’ve got what I bought and was advertised as a hex v2 cable. I need it to work with 2020 cars. When I plug into and use the interface vcds reports it as a hex-usb interface not v2.

Can I update? I’ll attach pics that might help

It's a HEX-CAN in a V2 case, that's why it is recognised as a HEX-USB-CAN. You cannot "update" it into HEX-V2.

**ppjose** · 26th September, 2020, 10:47 AM

Hi all,

I have read some posts in the thread but there are many pages ... so i hope a little understanding

i have this vagcom v12.12 atmega162 interface but VCDS says the license is invalid from the first use despite following all instructions carefully

Is there a way to activate the license or I have to throw it away and buy another one? (see attachments)

this interface is a good one?
ATMEGA162+16V8+FT232RL / firmware 1.96 / hardware x46 / bootloader enabled / VCDS v20.4.1
( https://i.imgur.com/jFRQUzW.png )
I think that it not has L9637D chipsets, not sure, it is important¿? with bootloader enabled i can flash it by software in case of license problem, right?

thank you very much!!!!

best regards

**hid3** · 26th September, 2020, 07:15 PM

Unfortunatley your interface is useless.
Give it as a gift to neighbour kid or donate it to me as parts donor.
For your own use, you must get a normal, full PCB interface.

**temusr** · 28th September, 2020, 03:38 PM

Hello ,
Would any one be kind and help me with my Chinese clone HEX-v2 cable.
I have programmed the atmega 162 controller's flash and eeprom and worked fine with loader for vcd 16.8.0.
When I try to test the cable on version 19.6.0 which I need for cars in my garage or higher version is better of course, VCD gets banning the cable and corrupts it.

I need a dump 1.96 firmware + eeprom that works with vcd version 19.6 or 20 and a loader; can any one point me to liks or solution?
with full appreciations

TE

**temusr** · 28th September, 2020, 03:50 PM

Helllo,
have you tried the Kolimer.zip tools and dumps to program your cable?

if not then from my trial I can tell you about some tips to save you time and maybe of help;

Try to program your atmega 162 controller both firmware and eeprom according to your hardware type. You can use USBASP device ( cheap and effective) or using arduino with avrdude command (read about it on previous pages on this forum)
if you need to program the ftdi (usb controller on cable) do it using mprog.exe all tools are found in kolimer.zip I can upload it to you if needed or send on email it is 5.5MB and test

you also may save your current flash and eprom before doing any achanges.

Thanks TE
ppjose

**ppjose** · 28th September, 2020, 09:53 PM

Originally Posted by hid3

Unfortunatley your interface is useless.
Give it as a gift to neighbour kid or donate it to me as parts donor.
For your own use, you must get a normal, full PCB interface.

yes, user jan4 has helped me by private message and I am going to buy a new interface in obd2cartool

Originally Posted by temusr

Helllo,
have you tried the Kolimer.zip tools and dumps to program your cable?

if not then from my trial I can tell you about some tips to save you time and maybe of help;

Try to program your atmega 162 controller both firmware and eeprom according to your hardware type. You can use USBASP device ( cheap and effective) or using arduino with avrdude command (read about it on previous pages on this forum)
if you need to program the ftdi (usb controller on cable) do it using mprog.exe all tools are found in kolimer.zip I can upload it to you if needed or send on email it is 5.5MB and test

you also may save your current flash and eprom before doing any achanges.

Thanks TE
ppjose

thanks for your help but I don't think my interface has the bootloader enabled (I have to check it yet) so I need to buy an USBASP programmer and it's not worth it in my case i think. I have the v9.2 kolimer package already downloaded

**hid3** · 29th September, 2020, 06:10 PM

Originally Posted by ppjose

thanks for your help but I don't think my interface has the bootloader enabled (I have to check it yet) so I need to buy an USBASP programmer and it's not worth it in my case i think. I have the v9.2 kolimer package already downloaded

Mate, even if you had USBASP on your desk it wouldn't help.
Your cable doesn't have GAL chip, which makes it neither 44 nor 46 hardware. Trying to resurrect such cable is the same as trying to drive a car which doesn't have wheels and steering wheel by design. If a car doesn't have wheels and steering wheel, means it's a house, not a car. Same with your cable.

**kwat** · 29th September, 2020, 09:07 PM

Please link to the interface programming package in Polish version 20.4.1.
Thank you.

**Mario6** · 30th September, 2020, 08:36 PM

Originally Posted by kwat

Please link to the interface programming package in Polish version 20.4.1.
Thank you.

KOLIMER

https://www.digital-kaos.co.uk/forum...light=vag+vcds

**dixonSRB** · 1st October, 2020, 07:08 PM

Hi guys, thank you so much for all these pages of discussion about fixing VCDS interfaces, but I am little bit confused.

I use VCDS 19.6.1 with HEX V2 cablec it is not original, it is clone. Everything worked normally, coding, fault readings... But today it just stopped working and I receive error it failed to communicate with interface. How can I fix it so everything works normal?

PLEASE help me, I don't have idea how to fix problem...

**kamilo1409** · 2nd October, 2020, 08:38 AM

Hi, i have kabel and software 20.4.1. Now i have problem with my kabel.
So, i have program VAGCOM_EEWriteLang.exe to repair (version 19.6), but i dont know if I can use or no.

Can you help me? Maybe have you VAGCOM_EEWriteLang.exe verion 20.4.1?

**kaalis** · 2nd October, 2020, 11:07 AM

Just use loader 9.2 version. There is no loader for every subversion of vcd$hit

**DODBCA** · 6th October, 2020, 10:10 AM

Originally Posted by ppjose

yes, user jan4 has helped me by private message and I am going to buy a new interface in obd2cartool

thanks for your help but I don't think my interface has the bootloader enabled (I have to check it yet) so I need to buy an USBASP programmer and it's not worth it in my case i think. I have the v9.2 kolimer package already downloaded

What interface was recommended to you? I am looking at these two and do not understand the difference.

https://www.obd2cartool.com/diy-vag-...t-skoda-p-1317
https://www.obd2cartool.com/diy-vag-...hipping-p-1388

**kaalis** · 6th October, 2020, 01:53 PM

20.9 beta released. As always, not for hex-can.

**obdcarsale** · 7th October, 2020, 12:40 AM

Beta 20.9 works only with Ross-Tech's current HEX-NET and HEX-V2 interfaces.
It will not work with any of our older, legacy interfaces.
Support for legacy interfaces will be included again in the next Release version.
HEX-NET and HEX-V2 interfaces must be set to the Beta channel using VCIConfig.
CB v0.4529 or higher is required to use this version of VCDS.
Beta channel for your interface can be selected on the Advanced tab in VCIConfig.
Updating your interface will not affect compatibility with previous versions of VCDS.
Default installation location is C:\Ross-Tech\VCDS-Beta\
If allowed to install to its default location, it will not overwrite or interfere with the use of Release 20.4.