VAG-COM/VCDS EVERYTHING

[pocinas]

Hi There folks.

After broke my 2 VCDS one HEX+CAN (0x44) 2nd HEX v2 (0x46) (using probably wrong number vcds and wrong loader) both cable was recognized (detected) but shows NOT PLUGGED INTO A CAR (off course OBD2 plug was connected to car).

So i start procedure reflash ATMEGA162..... older VCDS HEX+CAN (0x46) back to life (reflash using Programmer TL866 Plus) tested with car and at the moment work fine.

the same firmware but for 0x44 i tried wrote to 2nd vcds HEX v2, flashing ATMEGA 162 finally was OK, but VCDS 17.8 (17.1.3) still NOT PLUGGED INTO A CAR and both LEDS not light.


Can anyone tell me firmware for HEX V2 and HEX+CAN shoul be diffrent on is the same to both cables?

If is diffrent someone can share firmware or link where i can find, on this forum or nuber post ( i tried find but without result)

[liviudiaconu]

You said your Hex+CAn is 0x44 but you said wrote 0x46. So? Post here photos good resolution with both sides of PCBs.

For 17.x.y-18.z.w version Firware is 1.96. 0x44 or 0x46, like HW-type

[pocinas]

You said your Hex+CAn is 0x44 but you said wrote 0x46. So? Post here photos good resolution with both sides of PCBs.

For 17.x.y-18.z.w version Firware is 1.96. 0x44 or 0x46, like HW-type

Apologize if i confused... the same firmware means file from the dame package, finally Like hex-can hw is 0x44 because pin 34 and 35 is connected with GAL chip... so wrote 0x44 file then Hex v2 pin 34 and 35 is NC so i used files 0x46. But for both vcds firmware from the same package, just diffrent 0x44 or 0x46.

I thinking maybe for Hex V2 is totally diffrent firmware from.diffrent package, because in description Hex v2 is faster then older Hex-Can and Hex v2 can support UDS/ODX.

So this is why was my question.

[alexm1]

For this hardware without GAL/ATF how can we "see" the type of the hw?

Is this one 0x44 or 0x46?

[Bregu]

Hello there,

i´ve figured that my cable have an ARM chip, so useless.

thanks for your help

[jan4]

only atmega 162 can be adapted......................
yours has an arm processor .

[Bregu]

Thank you.

I´ll try to buy a better one.

[Baal]

I have but one question, does this work on 2018 VAG cars?

[kaalis]

Even originals works only partly with latest years. Check rosstech forum.

[Baal]

Even originals works only partly with latest years. Check rosstech forum.

So basically it doesn't make difference if I'm using cloned interface, it works as good as the original?


I have this one HEX+CAN

HW: 0x44
FW: 1.96
PID: FA20
Upgradable via USB using VAGCOM_EEWriteLang.exe

[kaalis]

Post autoscan of your 2018 car.

https://www.briskoda.net/forums/topi...terface-error/

[Baal]

Post autoscan of your 2018 car.

https://www.briskoda.net/forums/topi...terface-error/

It's not mine it's my customers car, I have HEX V2 interface too bought from obd2cartool.com but i haven't had any time to get it running yet. Will my HEX V2 work as good as the original?

[kaalis]

If you have no Vbat in port test result, then you have fake V2.
Check device manager for cable name/title. Is it under usb or hid devices...

[Baal]

Yes I know I have a clone from obd2cartool.com but that was not my question.

My question was will this interface work as good as the original.

[liviudiaconu]

[...]
Is this one 0x44 or 0x46?

Is a petard.

[...]
I thinking maybe for Hex V2 is totally diffrent firmware from.diffrent package, because in description Hex v2 is faster then older Hex-Can and Hex v2 can support UDS/ODX.

So this is why was my question.

Tested "HexV2" and "Hex+CAN" in the same car in "autoscan".
The faster HexV2 is slower than Hex+CAN.
And, most important, "HexV2" is, in fact, a "Hex+CAN".