VAG-COM/VCDS EVERYTHING

**Lolo4321** · 30th September, 2019, 02:13 PM

yes u can run 19.6.1 with Kolimer V9.2 and re-flash. Your cable needs to be plugged in or connected do 12v just follow the pdf guide.

**liviudiaconu** · 30th September, 2019, 02:21 PM

@ hirez: But..you have in fact hw44 cable.

**winamax69** · 30th September, 2019, 05:47 PM

@ hirez
right HW type GAL-AT162 chacked? When GAL connected to the Atmega162, then you have a HW44 type cable.

**hirez** · 30th September, 2019, 05:51 PM

Originally Posted by liviudiaconu

@ hirez: But..you have in fact hw44 cable.

OK, I thought so looking at the PCB, but was not sure. Is that good or bad? But the HWtype tool shows it as 0x46 so I just though that should be right.
Either way the EEflash will auto detect and flash the correct firmware?

**Tib82** · 30th September, 2019, 06:19 PM

Originally Posted by winamax69

@ hirez
right HW type GAL-AT162 chacked? When GAL connected to the Atmega162, then you have a HW44 type cable.

Both type's ATmega162 microcontroller connected to the GAL chip, but the difference is the number of the connected pins. In the case of HW 0x44 type pin 34-35-36-37, while in the case of HW 0x46 type only pin 36-37 are connected to the GAL.

Originally Posted by hirez

OK, I thought so looking at the PCB, but was not sure. Is that good or bad? But the HWtype tool shows it as 0x46 so I just though that should be right.
Either way the EEflash will auto detect and flash the correct firmware?

No worries about it, just plug it into your car and into your laptop, ignition on (for 12V), and run the \/AG(0M_EEWr!teL@ng app

and it will do the rest of the job

**hirez** · 30th September, 2019, 06:48 PM

Originally Posted by Tib82

Both type's ATmega162 microcontroller connected to the GAL chip, but the difference is the number of the connected pins. In the case of HW 0x44 type pin 34-35-36-37, while in the case of HW 0x46 type only pin 36-37 are connected to the GAL.

No worries about it, just plug it into your car and into your laptop, ignition on (for 12V), and run the \/AG(0M_EEWr!teL@ng app

and it will do the rest of the job

Thanks!
I will check the pins. It never hunts to be thorough, and I would rather not break anything.

so... autoflash, run loader9.2 on original fresh 19.6.1, play at will?

Edit: just checked and like the PCB would indicate, the PA0, PA1,PA2,PA3 pins are indeed connected to my PALCE16V8. That is a 0x44 and a good thing?

Also: Does it mean anything important that my PID reads FA20 and not FA24?

**liviudiaconu** · 30th September, 2019, 07:00 PM

Originally Posted by hirez

OK, I thought so looking at the PCB, but was not sure. Is that good or bad? But the HWtype tool shows it as 0x46 so I just though that should be right.
Either way the EEflash will auto detect and flash the correct firmware?

1. For correct functionality must write correct version of Fw and EEPROM.
Must use USB ISP programmer.
2. The response 0x44 or 0x46 is about Fw already wrote in AT162. Not hardware respond 0x44 or 0x46.
So if you have in your Hw44 wrote Fw46 will see "0x46". Not OK.
But, only for test your cable can use EEWriter.

**robinbga** · 30th September, 2019, 07:12 PM

Can't someone come up with a video of how to flash and share it to those who need it like me n hirez, the video should show how to use Kolimer's loader and other flashing tools like eewriter etc.
I would help a lot.
I had the same problem but I ended up using the same loader v1.12.
However, Hires if u contact me, I will share with u what I did to solve mine bcoz I have a similar cable.
I would prefer to use Kolimer's loader v9 due the it functionality, I looked at how it loads vcds and all I can say is its genius.
Keep it up

Cheers
Robin B

WhatsApp: +256752474714
Skype: robin_bga83

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

**Lolo4321** · 30th September, 2019, 07:24 PM

Is your bootloader unlocked ?

**robinbga** · 30th September, 2019, 07:24 PM

Yes

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

**Lolo4321** · 30th September, 2019, 07:32 PM

Ok,
First step:
Plug in the HEX CAN cable into the laptop
Install Ross Tech software downloaded from their site 19.6.1 (HEX CAN must be plugged in during installation)
-( During install accept installation of drivers)
Don't open VCDS after install.
Go into you car and plug in the HEX CAN cable ( Ignition on)

Open Kolimer v9.2 folder
Run VAGCOM_HWType.exe - to confirm that your bootloader is unlocked
After that run
VAGCOM_EEWriteLang.exe
(HEX CAN must be plugged into the car, or supplied 12 V on the bench setup)

after that Open the directory in which u installed Ross Tech software
Copy the loader from Kolimer V9.2 folder into the Ross tech directory
VCDSLoader.exe - Right click on it and -> Send to desktop.
Close all folder, and run VCDSLoader from desktop
enjoy

**robinbga** · 30th September, 2019, 07:37 PM

I tried that at some point and its refused to be detected by 19.6.1.
I did exactly that.
When I opened eewritelang, I selected English I think 0x46 bcoz the original loader said that.
It failed to work

Kess V2 . K-Tag
MiniPro . UPA . VVDI2

**Lolo4321** · 30th September, 2019, 07:41 PM

Originally Posted by robinbga

I tried that at some point and its refused to be detected by 19.6.1.
I did exactly that.
When I opened eewritelang, I selected English I think 0x46 bcoz the original loader said that.
It failed to work

Kess V2 . K-Tag

MiniPro . UPA . VVDI2

Uninstall all software and remove Hex Can from hardware...
Than try again.