VAG-COM/VCDS EVERYTHING

[hid3]

Thank you for your reply. I understand... I will try to repair it just for hobby purposes only (I think I would never use it on a car).

Can you tell me where I find instructions on how to flash it and the binaries for it ? I'm not familiar with this forum

Thanks again!

See this:


http://www.digital-kaos.co.uk/forums...=1#post3219283


and this:


http://www.digital-kaos.co.uk/forums...=1#post3237350

[gerinemo]

Tbh i cant remeber if tour type polo has CAN through to the socket.. Check out pins 6 and 14 of the obd connector... they are the CAN-H AND CAN-L pins

Sent from my SM-G935F using Tapatalk

Just had a look there now and pins 6 + 14 are populated Thanks for your help :-)
in this photo the obd port is upside down so top right is pin 1

Also on my C reader tool it shows protocol as KWP ISO 14230 so this is not connecting over can either
as per photo OBD Port VW Polo 2008.jpgCreader1.jpgcreader2.jpg

[rak183]

Yes a good one

[oddyutza]

Hi,

I do have a VCDS 12.12 and has the following hardware on the PCB
atmega162 16AU 1437H
atf16v8BQL 15su
ftdi ft232RL
MCP2515
VAGCOM_HWType.exe cannot read the cable
Can this cable be updated? how?
If needed i can provide HQ pictures with the interface PCB
regards, and one cold beer on the way

[IJskonijn]

Thanks to all who have contributed to this project and thread. I just finished programming my HQ clone cable. For those of you who may not already have a USBASP or similar programmer. An arduino can easily be used for such purposes. The sketch needed is built in to the examples menu of the arduino IDE software. Just go to File->Examples and select ArduinoISP, then just upload code to your Arduino board.

The following table will show the pinouts for various Arduino boards. I used Duemilanove board. Pin 10 was reset and I used the 5V/GND outputs from the board to power the cable.

Arduino / Genuino Board	MOSI	MISO	SCK	Level
Uno or Duemilanove	11 or ICSP-4	12 or ICSP-1	13 or ICSP-3	5V
Mega1280 or Mega2560	51 or ICSP-4	50 or ICSP-1	52 or ICSP-3	5V
Leonardo	ICSP-4	ICSP-1	ICSP-3	5V
Due	ICSP-4	ICSP-1	ICSP-3	3,3V
Zero	ICSP-4	ICSP-1	ICSP-3	3,3V
101	11 or ICSP-4	12 or ICSP-1	13 or ICSP-3	3,3V
MKR Family	8	10	9	3,3V

I used the following command to program the Atmega162 in my cable:

avrdude -p m162 -c avrisp -P COM5 -b 19200 -e -U flash:w:Flash1.96_HW_0x46.bin:r -U eeprom:w:eepromavr_HW_0x46.bin:r -U lock:w:0x3f:m -U efuse:w:0xf9:m -U hfuse:w:0xda:m -U lfuse:w:0xcd:m

Note: You may have to change "-c avrisp" to "-c arduino" depending on your board. I have seen both mentioned on various sites with respect to programming using an Arduino as the programmer. avrisp worked for my setup though. Also change filenames and fuse settings for your hardware type. My cable was type 46. :-)

Hope this helps someone! My little contribution.

I can confirm that this works, flashed my old VAG106 this weekend with my Arduino.
Thanks guys!!

[hid3]

Hi,

I do have a VCDS 12.12 and has the following hardware on the PCB
atmega162 16AU 1437H
atf16v8BQL 15su
ftdi ft232RL
MCP2515
VAGCOM_HWType.exe cannot read the cable
Can this cable be updated? how?
If needed i can provide HQ pictures with the interface PCB
regards, and one cold beer on the way

It can be updated. The HW you have is type 46. You will need to flash the dumps directly use USBASP programmer or any equivalent (e.g. even Arduino can be used for that, just do some search and reading in the thread).

[oddyutza]

thanks @hid3
Though the thread is so stuffy i`ll try and figure it out i've already ordered an USBASP programmer as my arduino is at home(somewhere)
From what i read so far i could rap this to:
Atmega programming using USBASP
VCDS installation (say 17.X ver)
loader for it
And have fun

[networkers]

Hi,
VAGCOM_HWType.exe cannot read the cable

Connect PIN 16 to +12V and PIN 4 to GND (-) and try again.

[liviudiaconu]

Hi,

I do have a VCDS 12.12 and has the following hardware on the PCB
atmega162 16AU 1437H
atf16v8BQL 15su
ftdi ft232RL
MCP2515
VAGCOM_HWType.exe cannot read the cable
Can this cable be updated? how?
If needed i can provide HQ pictures with the interface PCB
regards, and one cold beer on the way

Put photos with PCB here

[oddyutza]

Hi,
PCB pics here : https://imgur.com/a/70XiolX
I've connected OBD PIN 16 to +12V and PIN 4 to GND (-) and with the cable on the bench powered from a simple 12V source, in VCDS the test is ok, so the dedicate powering is working.

Regards,
Vlad

[liviudiaconu]

Yes but your cable is "44" not "46".
If eewriter say "46" must write first with external AvrUsb programmer with correct versions.

[oddyutza]

Yes but your cable is "44" not "46".
If eewriter say "46" must write first with external AvrUsb programmer with correct versions.

Eh, that's one of the questions as i cannot read the cable with the tools in the loader archive. VAGCOM_HWType.exe states " No interface Found " the same for VAGCOM_EEWriteLang.exe

please advise

[networkers]

please advise

You have installed the proper RT driver for the cable and it is displayed in Windows System/DeviceManager/USB-Conrollers?

[alexm1]

You got your answer: usbasp- external programmer.
See liviudiaconu answer...

[peetr]

Kolimer, I'm using your launcher for a few months for my own cars and it works just fine. I love it, thank you very much!!

I would recommend these:
1) Cheaper version, fully sufficient for your car: http://www.obd2cartool.com/vagcom-16...version-p-1266
2) More expensive version (a bit faster to do Autoscan and a few other functions but essentialy not a miracle with "new style cool look"): http://www.obd2cartool.com/atmega-va...t-skoda-p-1492

Both can be flashed in the future

Nope. The "HEX-V2" is just the look of the modern interface. Internals are basically similar/same to the classic interface. I mean, the functionality is the same.

I'm thinking about to buy a second interface in case my primary one dies but I can't decide which one I should buy today. I like the look of the new interface but:
Is it really just the design and look thats different between them, or has it some advantages that makes it worth paying more money?
The pcb design is just like the real hex-v2 but if it gets the hex-usb+can firmware, does it in fact make any difference? (speed, stability, compatibility with newer cars)
Because VCDS recognizes it as a "HEX-USB+CAN" interface.
Or is it possible that the clone hex-v2 is gonna get an firmware that makes it into a hex-v2?
Which one would you personally buy today?

Don't get me wrong, I really really appreciate for what we get from kolimer! I'm just curious if it's worth investing in the newer interface design.