VAG-COM/VCDS EVERYTHING

**kaalis** · 10th February, 2018, 06:12 PM

Originally Posted by obd2cartool

There is really helpful for learning VAG, but I found most friends got VAG cable which not support reprogramming,That is will waste time to do it! We have one DIY VAG 16.8.4 cable with update hole,support reprogramming any version and language by your dumps. chip with 16V8B+ 2*L9637D +ATMEGA162 +FT232RL +MCP2515 +A1050. so if you want to change version you need check your cable PCB whether could support reprogram.

Hello, can you tell how to get back to firmware what it was before using loader? I don't know how to ask it the right way.

And what is purpose of 2 jumpers on PCB?

**kolimer** · 12th February, 2018, 10:07 AM

New loader for 18.1.0 V6.1
Special thanks to my friends for testing.

Original installer:
http://dltemp.ross-tech.com/VCDS/dow...-Installer.exe
SHA256 cba53d02a51014b3937938b7bc44edda9ec9354d135c178155 512dae9d021b9e

Loader:
http://ge.tt/7zLlAZo2
https://www.sendspace.com/file/1k82p4

Enjoy ...

**dj2d** · 12th February, 2018, 10:54 AM

Thanks Kolimer for your work ! Will test and report

**dj2d** · 12th February, 2018, 11:42 AM

Tested on a previous interface that was down due to V5 loader and 18.1 VCDS
Used external programmer, writing OK

Test on Golf Mk5, coding OK, autoscan OK, clear DTC OK, licence valid.

Rewriten it with USB write, all OK.

So far so good

Do you have a way to "lock" it, I mean VCDS can't rewrite with unvalid licence or modify as with V5 and lock the eeprom? Fuses maybe?

**spoon63** · 12th February, 2018, 09:05 PM

Hi, do I need to update the firmware after 17.8 with VAGCOM_EEWriteLang? or simply put the loader in the folder 18 vcds

**xoom** · 12th February, 2018, 09:55 PM

Originally Posted by spoon63

Hi, do I need to update the firmware after 17.8 with VAGCOM_EEWriteLang? or simply put the loader in the folder 18 vcds

Update Firmware supplied with V6 Loader

**mikroel** · 12th February, 2018, 11:10 PM

so far everything passed well

**xoom** · 13th February, 2018, 10:33 AM

Yep, so far so good:
lcn9uKY.jpg

**kolimer** · 13th February, 2018, 04:23 PM

Updated loader to V6.1 (fixed not starting for the first time)
Updated post http://www.digital-kaos.co.uk/forums...=1#post3213188

**dj2d** · 14th February, 2018, 12:13 PM

A little bug to report with V6 loader :

After autoscan if you choose manually an ecu it will close right after opened. Only way to open it is to close the software and launch it again.

Same issue several time. Will try 6.1 and report.

**dj2d** · 14th February, 2018, 12:27 PM

Update : With V6.1 issue solved. Autoscan > Clear DTC > connect to any ECU > works well, ecu doesn't close. Thanks !

**jakuza** · 14th February, 2018, 01:06 PM

Does anyone tried 17.8.1 on other languages than English with v6.1 - any report?

**eliotroyano** · 14th February, 2018, 01:20 PM

Friends I have a doubt. Does exist any type of hardware or firmware difference that allows an old interface (V704 HW0x44 ATmega 162 + Gal16V8 + FT232BL + MCP2515 + transistors) works slowly with CAN based modules (starts good after some seconds becomes to be slow until it loose controller connection - I release connection starts again, and operation continues with the same behavior)) than K-line based ones?
I ask because I have updated this old interface with various tested dumps of this thread and the result is always the same. Any comments or tips are welcome.

Sent from my Android Smartphone

**vaicekas** · 14th February, 2018, 02:52 PM

Originally Posted by eliotroyano

Friends I have a doubt. Does exist any type of hardware or firmware difference that allows an old interface (V704 HW0x44 ATmega 162 + Gal16V8 + FT232BL + MCP2515 + transistors) works slowly with CAN based modules (starts good after some seconds becomes to be slow until it loose controller connection - I release connection starts again, and operation continues with the same behavior)) than K-line based ones?
I ask because I have updated this old interface with various tested dumps of this thread and the result is always the same. Any comments or tips are welcome.

Sent from my Android Smartphone

Try replacing the new MCP2515. She is responsible for the CAN protocol

**xoom** · 14th February, 2018, 03:42 PM

Originally Posted by eliotroyano

Friends I have a doubt. Does exist any type of hardware or firmware difference that allows an old interface (V704 HW0x44 ATmega 162 + Gal16V8 + FT232BL + MCP2515 + transistors) works slowly with CAN based modules (starts good after some seconds becomes to be slow until it loose controller connection - I release connection starts again, and operation continues with the same behavior)) than K-line based ones?
I ask because I have updated this old interface with various tested dumps of this thread and the result is always the same. Any comments or tips are welcome.

Sent from my Android Smartphone

Can be PLD chip (GAL16V8) draws excess current and 8705 gets HOT.. Maybe you have dropping voltage.. (ATF16V8BQL) draws way less current..