VAG-COM/VCDS EVERYTHING

[IJskonijn]

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

I had to scratch away the R50 line before the HWType worked. (The PDF has more info on this)

[alexm1]

No STC on that PCB...no need to cut/remove anything...

[liviudiaconu]

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

Nope.
1. cable not answer to HWType - Write with AVR Programmer.
2. Cable answer and can write with EEpromwriter but display 46 and cable is in fact 44 or vice-versa - Write with AVR Programmer.
3 cable can be write with EEpromWriter and display correct version (44 or 46)..use EEpromWriter

[IJskonijn]

No STC on that PCB...no need to cut/remove anything...

I didn't say anything then ;p

[Hadgee]

Hi again,

I have a 17.1 from odb2tuning that with help from this site I have tried to fix as the 'can:not ready' Has earlier messages it has been reflashed to kolimer great firmware/ loader. Still no can.

My friend has bought the same cable is it possible to download the firmware from my friends and put back onto mine in case I can send it back to the supplier.?

Thanks in advance

[alexm1]

You did not say if on your friends cable CAN=ok

Atmega is protected for reading...so I do not think dump it is your problem... I do not remember if you shared pics, but I tried kolimer dumps on different harware and all have a CAN -READY.

[Hadgee]

Hopefully test friends lead tomorrow.....its just arrived.

I did full kolimer flash was all ok except can. Kind people on here came to the conclusion that possibly can chip maybe faulty after trying many things.

If can't do a dump no problem.....see if somebody wants a non can lead with kolimers 17.8 on.

Thanks for the reply

[hid3]

The real question is does your car (which you are testing the cable on) actually support CAN?
Pics of the PCB would also help

[Hadgee]

The real question is does your car (which you are testing the cable on) actually support CAN?
Pics of the PCB would also help

Hi,
Yes it does 2012 VW Passat. It works ok with another friends 12.12 (non atmega) lead. Pics are way back in the forum, I will look for pics and put up for you.

Ok page 385 for pics

Thanks

[Hadgee]

You did not say if on your friends cable CAN=ok

Atmega is protected for reading...so I do not think dump it is your problem... I do not remember if you shared pics, but I tried kolimer dumps on different harware and all have a CAN -READY.

Hi

Friends lead is can:OK, I suspect mine was faulty from the start.
My pics are on page 385 if interested.

Thanks

[peetr]

On the real hex+can-usb and hex-v2 interface there are protection diodes between the CAN-high and CAN-low lines to ground. They are there to protect the CAN-transmitter from voltage spikes but on our clone interfaces they are missing.
It works without them but I think it is a good idea to put these diodes in there, but which ones are the best for this application? Simple 30V Zener diodes?
Or better one of these ones: https://assets.nexperia.com/document...t/PESD2CAN.pdf but incl. shipping they are a little bit expensive: https://www.ebay.com/itm/192183800321

The first two pictures are our clone interfaces with missing diodes in the red circle and the third picture is the original interface with the protection diode.

[hid3]

Hi,
Yes it does 2012 VW Passat. It works ok with another friends 12.12 (non atmega) lead. Pics are way back in the forum, I will look for pics and put up for you.

Ok page 385 for pics

Thanks

Today I reflashed one interface (a simple "classic" one from OBD2cartool's shop, looks like exactly as yours).
The Test showed K1&K2 being OK while it CAN was not ready, despite the fact that it was connected to a car with CAN available/working.
However, since I had to do some things on the car, I proceeded. Surprisingly, everything worked fine and via CAN protocol.
Is this the same in your case?

[hid3]

On the real hex+can-usb and hex-v2 interface there are protection diodes between the CAN-high and CAN-low lines to ground. They are there to protect the CAN-transmitter from voltage spikes but on our clone interfaces they are missing.
It works without them but I think it is a good idea to put these diodes in there, but which ones are the best for this application? Simple 30V Zener diodes?
Or better one of these ones: https://assets.nexperia.com/document...t/PESD2CAN.pdf but incl. shipping they are a little bit expensive: https://www.ebay.com/itm/192183800321

The first two pictures are our clone interfaces with missing diodes in the red circle and the third picture is the original interface with the protection diode.

Well, if you want as good interface as the original one, then why not to buy the original one?
E.g. let's say this one:
http://www.obd2tuning.com/vcds-kabel...at-p-2749.html

[Hadgee]

Today I reflashed one interface (a simple "classic" one from OBD2cartool's shop, looks like exactly as yours).
The Test showed K1&K2 being OK while it CAN was not ready, despite the fact that it was connected to a car with CAN available/working.
However, since I had to do some things on the car, I proceeded. Surprisingly, everything worked fine and via CAN protocol.
Is this the same in your case?

No, the can protocols did not work. I specifically wanted 22 for the AWD so checked many times. K lines are fine on older cars. The only protocol that worked was the auto gearbox.

[hid3]

Then return it for a refund or exchange. Not worth bothering further with it.