VAG-COM/VCDS EVERYTHING

[subzdarg]

tested on a 2010 a4 no issues an 2004 t5 transporter no issues also a 2018 leon no issues an my own leon 2014 mqb no issues scaning a 2019 golf later

[liviudiaconu]

VCI= Connect, 1-Read ver (nothing, only few hexa) 2 Go Boot, 3 FILE (.dat needed). Where is the file?

[subzdarg]

20200715_204604[1].jpgi got this an a 1kb .dat file from it but the hex code just kept goin an goin maybe it needs dumping with usbasp or something there is a few programming pins on the pcb if anyonenhas any ideas hownto dump let me know

update tested 2019 golf an 2020 leon flawless an mk5 golf and 2011 a4

[boomfunk]

I got the same output with VCIUPDATE, however the hex code had a few numbers different as mine has an older version 2020.01.13.

My cable still has trouble connecting to most modules, it works on 01-Engine but will not connect to ABS or Instrument Cluster, K-Line init failed error. Trying to get a response from the seller. Perhaps its a hardware issue.

[ersin58]

Hello I'm new here and come from Germany. I am looking for a v9.2 drump, I would appreciate your help
Hello I'm new here and come from Germany. I am looking for a v9.2 drump, I would appreciate your help

[ersin58]

Hello I'm new here and come from Germany. I am looking for a v9.2 drump, I would appreciate your help

[Mario6]

Hello I'm new here and come from Germany. I am looking for a v9.2 drump, I would appreciate your help

Hi.
Find and read post # 8692.

[dreevo]

hey guys,
So i have a vcds interface with error (interface not found)
So i'm trying to flash EEPROM using VAGCOM_EEWriteLang.exe but i'm facing the interface is not in bootloader mode problem
I have the PDF file explaining the procedure of dealing with the no bootloader mode interface but since i'm a newbie i couldn't really understand the electronic stuff.
Does any one have any clue how this is done or have has anyone tried fixing this before ?
Here is the whole board zoomed in, as i said i can't see anything saying ATmega so i guess it's bootloader disabled.
116155010_313134899732118_6920424698814187447_n.jpg

[kaalis]

You don't have atmega162, so Kolimer loader is not for you.

These utilities support only interfaces based on ATmega162 chip. NEC, ARM or others are not supported!

[dreevo]

You don't have atmega162, so Kolimer loader is not for you.

So there's no way this interface can be fixed ?

[kaalis]

Use software and version supplied with the cable when you bought it.

[razvan2005]

Hello guys,


It's my first post here but i read a lot of posts and i like very much what you do. Congratulations you all !
I don't own a vag car (my wife does ) and i don't work in a close domain. Electronics is my hobby and programing it's my job. So please take me as a begginer.


I'm encountering some issues with a cable. About 2 years ago i bought one cable from china v17.1 with the following configuration: FT232RL, ATMEGA162 and ATF16V8B.
I didn't used it because i managed to kill it from the first usage (didn't used the crack ).
Then after few months i bought another cable. This was 17.8 with FT232RL, ATMEGA162 and PALCE 16V8H (it worked that time).


These days i had some time and i wanted to update them.
I have updated both cables atmega with v9.2 loader hardware 0x44 with verification and everything went fine.
Next step was to check the ftdi chip. I reprogrammed them to 0403 / FA24.


On the workbench (only power applied) i tried to test using HWType tool. None was working.
One cable had green light on (v17.1) and one was blinking red(v17.8).


I've checked the green light one and i found that the FTDI chip was broken, so i have replaced it, reprogrammed it and it's done.


Next i wanted to find out what was happening with the red blinking cable (17.8). I did and electrical check (joints and voltage) and everything seems to be fine. When it's connected to the power supply it drains about 220 mA current. It's like always trying to boot and restart. As i saw on the working one the current of 220 mA is drained when you connect it till it "boot" (red light dissapears and green appears), then the current stays at ~ 70 mA.
I suspect that PALCE chip is doing something weird and probably it doesn't like the v9.2 loader. Did someone encountered such an issue ? Is there a specific dump for PALCE to work with v9.2 ?


I will attach some pictures with both PCB and printscreens.

This is the working ATF cable:
20200723_012615.jpg

And the HWType results for it:
hwt.jpg

And this is the dead one (in the picture the FTDI chip is not present). It behave the same with and without FTDI chip on pcb:
20200723_005857.jpg

20200723_005930.jpg

Thank you in advance !

[liviudiaconu]

1. dumps posted here 1-2 years ago. Must search in this thread.
2. PALCE is a producer. Her 16V8 was named PAL 16V8
Not PALCE 16V8. This is chinese. Big consumption.
Find a GAL 16V8 or ATF 16V8 and try programm with "44" dump for 16V8
3. remove that ~~~~ed jumpers J1/J5 or, better remove J1/J5 and AES chip. Is possible after can make a test.

Red blink= bad communication on K-lines. That is 9637, 16V8 or anything between Atmega and 7/15 OBD2

But for first, ROSS-USA? is not a 9.2 serial.

[razvan2005]

Hello Liviu,

Thank you for fast reply and for clear answer.
I will order and replace the PAL chip and program it soon also remove the jumpers and AES chip

Regarding ROSS-USA ... you're right... good notice. The archive in the kolimer's v9.2 loader had a directory called: "Projects TL866+Progisp". Here were the binaries for TL866 programmer, which i use, and surprising this file: "VCDS HW 0x44 LB v2.mpj" contains ROSS-USA in AVR instead of ROSSTECH as it is in "eepromavr_HW_0x44.bin". I will use the binaries in the root folder to solve this issue.

I will come back with feedback after i will receive the order for ftdi and gal chip.

Thank you once again and have a nice day!

[obdcarsale]

who can update HEX-V2 STM32F415 ARM ITEMS? and need Russian version, thanks

4.jpg
5.jpg

I can pay for it