VAG-COM/VCDS EVERYTHING

[hid3]

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

Is this one 0x44 or 0x46?

What's the point in messing with this interface? It's useless.

GAL is needed for proper operation. 0x44 vs 0x46 difference is how it operates with GAL. So no GAL means no difference.

This interface is like a man without a d1ck.

[Baal]

All we need is a firmware dump that will recognize the new interface as a HID device, only then will we see Ross-Tech HEX-V2 Interface in a test window.

Edit:

I've found something else.

https://www.ebay.com/itm/ST-Link-V2-...sid=m570.l1313

https://www.st.com/en/development-to...w-tools-scroll

ARM MCUs are definitely programmable using this thing but someone has to develop firmware for ARM MCUs

[stonecoldro]

why would someone reinvent the wheel? even original R0$$ uses Atmega..

[liviudiaconu]

Originals Hex-CAN use Atmega. Originals HexV2 and NetV2 use STM. More complicated, like a plant.

Clones use Atmega or not but even write on it V2 are Hex-CAN

[Baal]

Yes that's correct but HEX-USB+CAN are slower interfaces than HEX-V2 because of that, HEX-V2 uses USB HID Class and actually needs no driver to run. And yes both of them are using Intel's HEX binary code implementation for programming MCUs, but ARM is faster.

[belkor]

vcds18.2.1 italian and portuguese

[liviudiaconu]

Yes that's correct but HEX-USB+CAN are slower interfaces than HEX-V2 because of that, HEX-V2 uses USB HID Class and actually needs no driver to run. And yes both of them are using Intel's HEX binary code implementation for programming MCUs, but ARM is faster.

ONLY if you reffer at ORIGINAL.

For chinese clones HexV2 is not real. Chinese HexV2 is in fact Hex+CAN. But slowly like HexCAN.
Tested. On the same car, same version of VCDS, Autoscan HexV2 time - Autoscan HexCAN time = 1-3-10 seconds. Depend how many controllers are on car.

[Baal]

ONLY if you reffer at ORIGINAL.

For chinese clones HexV2 is not real. Chinese HexV2 is in fact Hex+CAN. But slowly like HexCAN.
Tested. On the same car, same version of VCDS, Autoscan HexV2 time - Autoscan HexCAN time = 1-3-10 seconds. Depend how many controllers are on car.

On my car autoscan completes in 3.42min using HEX+CAN but genuine HEX-V2 took just 1.36min to complete so there is a difference.

[alexm1]

Your V2 has Atmega inside or ARM?

[liviudiaconu]

He told exactly the same thing i told: ONLY for ORIGINALS.

Most users use china clone. And chineses write like "our clone hexv2 is faster" because this write uwe for original.

I told i tested two clones. And fake-named V2 is in fact Hex+CAN.

I am currious to see from @Baal two PrintScreens:
one from Test-result and one from About screen for his HexV2

[Baal]

Your V2 has Atmega inside or ARM?

It's not mine but it has ARM, it's genuine.

He told exactly the same thing i told: ONLY for ORIGINALS.

Most users use china clone. And chineses write like "our clone hexv2 is faster" because this write uwe for original.

I told i tested two clones. And fake-named V2 is in fact Hex+CAN.

I am currious to see from @Baal two PrintScreens:
one from Test-result and one from About screen for his HexV2

Ahh I just got home, I'll rescan it tomorrow when i get back.

[hid3]

ONLY if you reffer at ORIGINAL.

For chinese clones HexV2 is not real. Chinese HexV2 is in fact Hex+CAN. But slowly like HexCAN.
Tested. On the same car, same version of VCDS, Autoscan HexV2 time - Autoscan HexCAN time = 1-3-10 seconds. Depend how many controllers are on car.

This is true. "Fake-V2" (based on AT162) is in reality several seconds slower in performing Autoscan (for the same car, same PC, same software, same everything) despite the fact that it is supposed to have a faster CAN chip. Looks like the limitation is not there at all

He told exactly the same thing i told: ONLY for ORIGINALS.

Most users use china clone. And chineses write like "our clone hexv2 is faster" because this write uwe for original.

I told i tested two clones. And fake-named V2 is in fact Hex+CAN.

I am currious to see from @Baal two PrintScreens:
one from Test-result and one from About screen for his HexV2

Yeah, again very true. Good news is that the "Fake-V2" (based on AT162) has (almost) identical PCB configuration to the HEX-CAN (aka HEX-PRO v6.1) except the LEDs and USB connector positions, of course. I've heard that the "Fake-V2" (based on AT162) had some its components sourced from the same suppliers the genuine manufacturer has obtained previously.

[RedNix]

Hello, I have VCDS 16.8 which I use on multiple computers. TDI timing graph works on Win 7 but doesn't on Win XP. Anyone knows what might be the issue? Regards

[Jerak]

I just ordered the hid3 recommended cable from obd2cartool.com and have read Info.pdf.
So:
-I install the version provided on CD via their directions
-provide power via OBD, run VAGCOM_HWType.exe > Read
-let's say I get HW 46
-no need to cut trace because of no STC chip
-run VAGCOM_EEWrite.exe

Will it prompt me with everything I need to do?

-with new firmware,upplug and replug, install new drivers?
-install upgrade Vagcom (VCDS) v18.2.0
-run new Vagcom (VCDS), Options > Test

Is this about right? Thank you.

[kaalis]

-run new Vagcom (VCDS), Options > Test
Is this about right? Thank you.

Before this step copy loader, remove shortcuts to vcds.exe and run loader.