VAG-COM/VCDS EVERYTHING

[Shanewazere]

Hello there new here anybody any experience with this cable
or can point me to a better one on obd2cartool thanks https://www.obd2cartool.com/vagcom-1...8sagh3pkaghhs4

[dodiss]

hi, no problem with smd soldering Flashing too. Never tried to read VCDS atmega, but don't think it a miracle

[dodiss]

Yes you can if your cable was built with chip ATMEGA162.
It would be a little bit difficult if you don't have any experience in firmware upgrading or even soldering.
However the cable is dead already, why not try to do something?

hi, no problem with smd soldering Flashing too. Never tried to read VCDS atmega, but don't think it a miracle

[Maitreya]

TRY
1. uninstall current version V(D$ and remove the directory where it was installed.
2. Download 19.6.2 from the official site and install it to your PC. During the installation the cable should NOT be connected to the USB. Do NOT to uncheck ""Run V(D$ at once" before click OK button at the last step of the installation.
3. Connect the cable to the USB port. If lucky the driver will be installed automatically. If failed to load the driver try to install it manually.
4. If the cable is identified and driven properly it should work. Google "V(D$Loader" you should find the 9.2 version. Download it and copy the file "V(D$LOADER.exe" to the directory where V(D$.EXE is located. Run the loader and try testing the cable.
5. If the cable cannot driven by the 19.6.2 driver, or the 19.6.2 software cannot identify the interface even the device is properly driven, you may need to refresh the firmware. That would be another story.

[Maitreya]

hi, no problem with smd soldering Flashing too. Never tried to read VCDS atmega, but don't think it a miracle

then it should be easy for you.
google "V(D$ loader" and follow the link "V*** Loader 9.2 Kolimer Automatic Installer", download the second link in that post, then you will have everything except the hardware.

[dodiss]

then it should be easy for you.
google "V(D$ loader" and follow the link "V*** Loader 9.2 Kolimer Automatic Installer", download the second link in that post, then you will have everything except the hardware.

Thank you

[Maitreya]

Besides, if the cable cannot be recognized by Windows with any version of driver (your old one or the 19.6.2 version), that means the FT232 chip was modified ("locked").
To solve this problem you need to refresh the FT232 chip.
First download the generic FT232 driver from http://www.ftdichip.com/Drivers/CDM/...0Certified.zip. Unpack it.
Check your USB device VID & FID by:
Open the Device Manager of Windows -> right click the cable (should be ross-tech something with a yellow icon showing that the driver doesn't work) -> Properties -> "Detailed Information" Tab -> "Hardware ID"
You will find something like this:
捕获.JPG

Then open the "ftdibus.inf" in the dirctory of the FTDI driver with notepad, replace all string "VID_0403&PID_6001" with what your find in the device manager (in this exapmle "VID_0403&PID_FA24").
Now manually install the driver and have windows install it from the FTDI Driver directory.
Once the driver is installed and working, you can use MPROG35 to refresh the FT232 chip:
Run Mprog;
"Read and Parse" to load current FT232 flash. "Save as" to save it as backup.
"Open" to open the flash file that will be written to the FT232. The file has .ept suffix and can be found in the "V*** Loader" package.
捕获.JPG

*Use "ftdi_mprog_BMBL.ept" if your chip is FT232B* or "ftdi_mprog_RLRQ.ept" if your chip is FT232R*.
Write.
After that the generic driver would be useless.
Disconnect the cable.
Install 19.6.2.
Re-connect the cable. The USB driver should be loaded automatically.
Then you can proceed. The following procedures require a 12V DC power to the boad of the cable. Could connect +12V to the pin 1 of 7805 and zero to the head sink of the 7805.
Run "VAGCOM_HWType.exe". Press "read".
If the status of "boot loader" is "Enabled" you are lucky. Use "VAGCOM_EEWriteLang.exe" to automatically refresh the chip.
If the boot loader is disabled you will have to refresh it manually. A USBASP/ USBISP device is required - very very cheap. Follow the instructions. Be careful with the differnet board versions 0x44 or 0x46. Be careful with the fuse bits!

[Vagsura]

Hi everybody! Few days ago i received two VAG HEX-V2 units from China, to test them and start learning about Vagcom. Why i bought two? Because i knew i was going to break one of them hahaha.

And that´s why im here. I got one of them bricked, and no idea about where to start to fix it

This is how it looks like:

[alexm1]

If you find on the other side the famous Atmega 162 AU...you migth have some luck and you could make it work as new ....after reflash. You better share more pics from both sides.

[Maitreya]

Hi everybody! Few days ago i received two VAG HEX-V2 units from China, to test them and start learning about Vagcom. Why i bought two? Because i knew i was going to break one of them hahaha.

And that´s why im here. I got one of them bricked, and no idea about where to start to fix it

This is how it looks like:

Should have clearea pictures for both sides of the PCB to identify the chips.

[pocinas]

Hi lads.

It is someone here who use Well clone quality vcds with china vcds loader 1.1x ?

I bouht one.. all looks nice, inside as well.

I requested with seller for activation to my vcds loader and i got it.. loader is activated..

I got problem because vcds work me with FRN and ADP (FRN - think French ADP is Polish), i prefer use ENG but doesnt with Eng vcds 19.6.2... tried 19.6.1 as well.. dont recognize interface.

Seller dont replay my at the moment for my message about problem with eng version which i prefer to work and try sort out problem here, if possible.helps..

Any sugestion.

Anyone can help with this?

[Maitreya]

Update: I manually flashed it with 1.96 0x44 without changing anythingelse. It ......works as well.
So it can work with both 0x44 and 0x46 firm wares......Then what's the difference?

Hello Friends.
I have an old USB VAG COM cable with ATMega162 and FT232RL. Firm ver 1.84 and VCDS ver 11.11.2.
I wanted to upgrade it for using with my new audi A3.
Before flashing I read quite a few posts and dowloaded all neccesary resouces.
First I ran the VAGCOM_HWType.exe. It reported "Interface not found". However the driver of the cable was OK because VCDS 11.11.2 worked well.
Then I tried to program the FT232 chip by writing "ftdi_mprog_RLRQ.ept" to the FT232RL. Succeeded. Then I installed the new driver successfully.
Now trying VAGCOM_HWTye.exe again and it reported:
Attachment 669736

Glad to see that the boot loader was enabled but the HW version "0X46" confused me, because I learned from various places that if the pin34/35 of ATMEGA were connected to the PLD(ATF16V8), the HW version should be "0X44", which is exactly my case:
Attachment 669739

Anyway I proceeded. Successfully refreshed the avr162 with one-click tool "VAGCOM_EEWriteLang.exe" —— with flash & EEPROM for "0x46" HW.
The cable seems working with 19.6.1 on my old fabia but I'm still a little worring. Does any one know if I did something wrong?

[TESTASTRETTA]

does anybody try HEX V2 from www.obd2cartool.com ? is it real HEX V2? thx

[papuc]

does anybody try HEX V2 from www.obd2cartool.com ? is it real HEX V2? thx

Seems like they have now the STM32F415 variant now as well at the low low price of $119.99. They only had 5 and someone bought one from Belgium two days ago. They show PCB so pretty sure that's HecksV2 clone.

Edit: And seems like there's another listing for $109.99 there too.

[grantius]

I have a great working VAGCAN Pro cable with a FTDL 245R - is there any version of VCDS that'll work with this?