VAG-COM/VCDS EVERYTHING

**liviudiaconu** · 23rd January, 2018, 07:28 AM

I only one with BL tested on V5. Worked fine. (17.8.0 only, not tested with 17.8.1). So..is possible to be an issue with your cable? Or something in your OS?

**xoom** · 23rd January, 2018, 07:59 AM

Did you checked your VID/PID of cable? maybe its FA20.. and hw write cant "see" it

**liviudiaconu** · 23rd January, 2018, 09:04 AM

Asking me?
FA20 and worked.
I will try again this afternoon or tomorrow.

But not used Writer, always used external programmer.

**hid3** · 23rd January, 2018, 04:09 PM

Are you able to pst the PCB of the interface which is having problems?

**xoom** · 23rd January, 2018, 05:13 PM

Originally Posted by liviudiaconu

Asking me?
FA20 and worked.
I will try again this afternoon or tomorrow.

But not used Writer, always used external programmer.

No.. The post before you

And Yes it doesn't matter if you use ISP

**alexm1** · 23rd January, 2018, 05:20 PM

What about fuse/lock bit?
I saw that they are changed only with external programmer, with Writer will remain the same as before reflash.
So, is important to change them or not?

**xoom** · 23rd January, 2018, 06:34 PM

Originally Posted by alexm1

What about fuse/lock bit?
I saw that they are changed only with external programmer, with Writer will remain the same as before reflash.
So, is important to change them or not?

They are not that important (as they are already set to hardware type)

if you use Writer ... then bootloader writes FW inside and no need to touch fuses

i allways leave my Fuses same

and Lock Bits 0xFF (unlocked)

**vaicekas** · 23rd January, 2018, 07:12 PM

Originally Posted by Vet

Loader V2 with 17.1.3En works fine from the first look: description of bits and adaptation channels are fine. But if I try to work with program a little bit longer (10-15 min), I’m starting to get “Communication lost with control module” massages. For example, if I start “Auto-Scan” procedure it’s in 100% cases never have been complete. Auto-Scan process always interrupts with massage “Communication lost”. And, that is most scared, during auto-scan process, program is messing with order of scanned control modules! It starts from 01 (Engine CM) than after some address (let’s say 19)program, instead of next control module, proceed querying 01 address ones again!

P.S. May be anybody have any idea, how to solve “Interface not found” answer on my cable with V5 Loader version???

Your problem is a poor quality adapter. Probability of bad FT232. I had a problem like “Communication lost” I replaced the FTDI from another cable and got it all up. Sometimes MCP2515 crashes.
I have several adapters with FT232BL and with FT232RL. I tested them all with Loader v5, I did not notice any problems.
Try re-writing BL.ept to FTDI (FT232BM is the same as FT232BL) and then try the Loader v5

**Vet** · 24th January, 2018, 02:21 AM

Thank you all guys – you make me believe my BM-cable should work with V5 Loader also! And finally “Interface is found”!

This is what I did (just for the case, if somebody gona get in my trap):

1) I flashed ones again by USBASP-programmer ATmega162 with “VCDS HW 0x44 LB v2.prj” project file. – No luck (Interface: Not Found)
2) Then I flashed ones again by MProg FTDI chip with “ftdi_mprog_BMBL.ept” – No luck (Interface: Not Found)
3) Then, after reading XOOM’s post once again (

Originally Posted by xoom

Did you checked your VID/PID of cable? maybe its FA20.. and hw write cant "see" it

), I thought: If I have bootloader in my cabele (cable is already flashed by programmer with the firmware which has bootloader), why don’t to try reflash it in “lucky mode” by “VAGCOM_EEWriteLang.exe”. So I stared it, changed PID from 0xFA24 to 0xFA20, pushed write button and cable was reflashed one’s again to custom firmware (according to manual).
4) To my surprise cable past test in 17.8.0 program!
5) I had to agree with proposed firmware update from 1.95 to 1.96. And now 17.8.0/17.8.1 are seeing my cable smooth and perfectly!

Tomorrow I will test it in the car. Hope everything will past fine..

Thank you all guys, ones more!

**flavyus1987** · 24th January, 2018, 08:36 AM

Everytime before program it, check PID in device manager.

**mikroel** · 24th January, 2018, 02:35 PM

Does anybody can share GAL16V8 dump for VCDS with FTDI RL chip?
It look like different then for VCDS with FTDI BL?

**alexm1** · 24th January, 2018, 02:46 PM

I din not tried yet... Gal/Atf dump
Link in the doclink.doc

**Vet** · 24th January, 2018, 11:44 PM

Confirm! V5 loader indeed fully functional with 17.8.0_En and 17.8.1_En !!!

At least 2 hours on two cars (with UDS protocol control modules) : Auto-Scan, Fault Erasing, SRI Reset, coding bit and adaptation channel description – everything smooth and perfect! I’m more than a happy!

**liviudiaconu** · 25th January, 2018, 07:34 AM

Originally Posted by alexm1

I din not tried yet... Gal/Atf dump
Link in the doclink.doc

Is for old cables only.

**tucano79** · 25th January, 2018, 07:11 PM

Hi guys I have a problem with my vag 16.8.4. I think it is W46 and has got atmega162. I attach photo. I tryed to program this Vag com with upa programmer and loader V2. Using lock and fuse bit. The problem is that after Program when I connect the vag com to obdII it don’t works because the led is off. So if I try to disconnect from obd and reconnect more times and then the led turn on green and the cable works correctly. But when I disconnect the vag com from obdII if I try to reconnect it doesn’t work. Every time I have to connect and disconnect the vag many times then the Len turn on. Can you help me?