VAG-COM/VCDS EVERYTHING

[ramyhossni]

IMG_1906[1].JPGIMG_1900[1].JPG

Hello All.

hope you all to be fine

i have VAG12.10 cable, it was working fine but after 2 yrs, it was suffering from low response and error msg with interface not found.

i reinstalled the VCDS 12.10.3 lite, but accidentally i connect my laptop to the internet while the cable plugged into USB.

Now i have new error msg

Port status: OK
USB Library Version: 03.01.19
SUB driver Version: 02.04.18
Interface: found!
Type: Ross-Tech HEX-USB
Status: Not plugged into Car!

i tried with another laptop but not working also.

PS. LED working fine, it became green once connect the cable into car.

Hope to get a solution for this issue other than replacing the cable as it's very expensive now for me now .

[alexm1]

Are very important fuse/lock bits?
I am asking this because if you flash Atmega via usb, fuse/lock bits will be not edited.... so it is ok to reflash via usb?

[ramyhossni]

Please, can anybody support me here ??
Thanks

[ramyhossni]

IMG_1906[1].JPGIMG_1900[1].JPG

Hello All.

hope you all to be fine

i have VAG12.10 cable, it was working fine but after 2 yrs, it was suffering from low response and error msg with interface not found.

i reinstalled the VCDS 12.10.3 lite, but accidentally i connect my laptop to the internet while the cable plugged into USB.

Now i have new error msg

Port status: OK
USB Library Version: 03.01.19
SUB driver Version: 02.04.18
Interface: found!
Type: Ross-Tech HEX-USB
Status: Not plugged into Car!

i tried with another laptop but not working also.

PS. LED working fine, it became green once connect the cable into car.

Hope to get a solution for this issue other than replacing the cable as it's very expensive now for me now .

Please waiting for your support

[H2Deetoo]

I would suggest to reflash it (because it got damaged while plugging software to internet).
Check the Kolimer V2 package for which you can find some links some pages back.

You can try to flash over USB using EEWrite tool most likely it isn't supported.
Then reflash with some AVR programmer like USBASP. All info and files is inside the Kolimer package.

[peetr]

Anyone here who know's if the new interface works with kolimers launcher?
http://www.obd2cartool.com/atmega-va...t-skoda-p-1492
Of course they say that it works, but has anyone tested it? What's the effective difference between them, keeping in mind that the new one has a another CAN chip and a K-line chip 9241.
And the big question is: is the Si9241 a real one, or just a fake chip as in many new Delphi DS150e interfaces? I really don't know, but what I know is that the Si9241 chips are not gonna be produced anymore.

I've got the classic one http://www.obd2cartool.com/atmega162...t-skoda-p-1404 and it works with VCDS 17.8 just fine. As the interface has arrived I immediately flashed the firmware files from kolimers package via a USBASP interface and it works perfectly.
But maybe the new interface is better. Kolimer, what do you think?

No matter what, thank you for your work. Without you this wouldn't be possible!

[hid3]

The advertised "HEX-V2" is in fact the same classic interface with old AT162 chip, just with different/modern case and detachable cable. It's not the same as genuine HEX-V2, as it has got different newer chip.

You say that the old/classic interface works perfectly with 17.8 version.
Have you checked UDS cluster adaptation channels, Long Codings, etc? Do those functions work perfectly too?

[peetr]

I used long coding but nothing very big. I played just around and learned how it works in case I need it. I was able to change codings back and forth. Reading fault codes and accessing all modules always worked just fine.
One time I've had a strange behavior with a VW Golf 7. Everytime I connected to the UDS cluster and changed small things like "oil temp reading", the radio made for 3 seconds a high pitched noise. But besides that, I didn't used UDS cluster adaptation channels.

[H2Deetoo]

Try to go to staging adaptation channel and check what it shows. When faulty it shows "xx km" instead of active.

[hid3]

^--- Yep... If it shows anything other than what is expected, then it's very DANGEROUS to use such tool... One wrong value in some random adaptation channel might bring the module totally unusable.

[ramyhossni]

Dear H2Deetoo,
Many thanks for your reply, but it's the first time i will use this tools of reflashing
Please, just if you don't mind and have enough time i need your support to lead me to do it
or please send me the page number that i can find the suitable steps

My VAG ver. is 12.10 and the interface pics below.

thanks again for your support.

.IMG_1906[1].JPG
IMG_1900[2].JPG

[H2Deetoo]

Just go some pages back and read, all info is there.

[peetr]

Today I've tried my interface with a Seat Ibiza 6L and as much as I saw, the values were plausible. Service reset should also work, and I was able to set the coding on the power steering module back and forth without any problem.
The 6L Ibiza just hasn't that much capability.. just a few basic things, but nothing like indicator staging. Yesterday I've read the fault codes from a A6 2.5TDI V6 automatic and this worked just fine. But I know, the problem is in the long coding, not in reading fault codes.
I'm gonna try it with a another Audi A6 2.7T and maybe with a friends Golf 7, but it can take some time till I can test it.
But as long as I just read and don't write anything, I think it should be safe to use.
My interface is a HW 0x46 one

[alexm1]

Which vers. did you use?
17.8 , 17.8.1 or 17.8.10 beta?

[kamine22]

No reason for that at all, but I do attach dumps (hex for flash, eep for eeprom) and fuses screen shots for both 0x44 and 0x46 versions.

thanx ....