VAG-COM/VCDS EVERYTHING

**tricoredc17** · 26th April, 2012, 07:19 AM

Originally Posted by KenshinPT

Yes.

Regards.

Just ask him. You are reading connecting to atmega162? Is the USB port? I think we have the same patent

**matekhr** · 26th April, 2012, 08:08 AM

Originally Posted by mattydr67

That is NEC not ATMEGA
You have bad luck in this case becasue for this kind of tools there's no solution, I mean no dump for NEC
Try to reflash it with MProg maybe you have a littel luck and it will work but in other case you have to buy another tool.
Good luck

Have you any datasheet for this? It doesn't seem to be pin-compatible with Atmega.

(I'll try some other VCDS versions, maybe it will work with some earlier release.)

**mattydr67** · 26th April, 2012, 08:30 AM

Originally Posted by matekhr

Have you any datasheet for this? It doesn't seem to be pin-compatible with Atmega.

(I'll try some other VCDS versions, maybe it will work with some earlier release.)

It is not compatible with Atmega.
It is other Chinese chip and there's no dump for it.
It is working just with VCDS 10.6.0 or if you make a loader will work with other versions too.
But as I told you if you wanna reflash this tool you'll not be able becasue there's no dump for NEC
Sorry for your inconvenience but this is it, you have nothing to do.
Good luck

**matekhr** · 26th April, 2012, 09:10 AM

Originally Posted by mattydr67

It is not compatible with Atmega.
It is other Chinese chip and there's no dump for it.
It is working just with VCDS 10.6.0 or if you make a loader will work with other versions too.
But as I told you if you wanna reflash this tool you'll not be able becasue there's no dump for NEC
Sorry for your inconvenience but this is it, you have nothing to do.
Good luck

Well, my PC recognizes the cable OK (as Ross-tech interface), but after connecting it to car (or 12V) I got the message (something like that):
"Port status: OK, Interface: No"

**bat21** · 26th April, 2012, 09:50 AM

Originally Posted by tricoredc17

Just ask him. You are reading connecting to atmega162? Is the USB port? I think we have the same patent

Is simpler way

**KenshinPT** · 26th April, 2012, 09:56 AM

Originally Posted by tricoredc17

Just ask him. You are reading connecting to atmega162? Is the USB port? I think we have the same patent

Yes... I believe that we have the same method to extract the dump from ori or clone tool.

The only difference in our methods is that I don't ask 500? for that. I just ask for friendship.

Regards.

**mattydr67** · 26th April, 2012, 11:21 AM

Originally Posted by matekhr

Well, my PC recognizes the cable OK (as Ross-tech interface), but after connecting it to car (or 12V) I got the message (something like that):
"Port status: OK, Interface: No"

Plug it into the car do not start the engine.
Then plug it into the USB and check in the Device Manager if it recognized and the VID/PID it is 0403/FA20
Then make an interface TEST and see in the same time if you loose uSB connection.
Or try it to Read it with MProg or use the ept file and try to reflash it.
If it said the it dosen't found the tool this means that FTDI it is broken.
Change it and you have a good tool again. Ovi_dk had same issue
Good luck

**xoom** · 26th April, 2012, 08:57 PM

Originally Posted by matekhr

My old vag-com cable makes me a lot of troubles, so I ordered a new one. It arrived yesterday, didn't work (of course) so I opened it.
Instead of Atmega there's a chip marked D79F8513A (China).
What a hell is that?

Try with older versions of VCDS like 805 - 912..
Also check for solder splashes between chips legs

this is often in chineese stuff

Regards, xoom.

**eliotroyano** · 26th April, 2012, 11:52 PM

Hi friends. I have a weird issue with a Vag10.6 clone cable interface. After a year of usage with almost no troubles, today trying to scan my own car with it, I notice a weird notice from the software indicating me interface detected but car not connected!!!!!. I try every module that I can and I got the same message. I plug and unplug it several times and the result was the same. Also I notice that the interface got hot, touchable but hot!!!!!!. I test my old KKL dumb interface and it reach every module of the car. Anyone had the same issue??? What could be the problem???? I really appreciate your advice friends.

**KenshinPT** · 27th April, 2012, 12:25 AM

Originally Posted by xoom

Try with older versions of VCDS like 805 - 912..
Also check for solder splashes between chips legs

this is often in chineese stuff

Regards, xoom.

You're right.

I had a bad experience in one of my cables.

The FTDI was full of solder flux and that was making a low impedance between pads: Conclusion: bad behaviour.

**eliotroyano** · 27th April, 2012, 04:44 AM

Originally Posted by eliotroyano

Hi friends. I have a weird issue with a Vag10.6 clone cable interface. After a year of usage with almost no troubles, today trying to scan my own car with it, I notice a weird notice from the software indicating me interface detected but car not connected!!!!!. I try every module that I can and I got the same message. I plug and unplug it several times and the result was the same. Also I notice that the interface got hot, touchable but hot!!!!!!. I test my old KKL dumb interface and it reach every module of the car. Anyone had the same issue??? What could be the problem???? I really appreciate your advice friends.

Hi again friends. Here is a pic of the issue that I have.

**mattydr67** · 27th April, 2012, 04:58 AM

What about the LED?
Is it turned on?
If yes in this case you'll need to reflash it.
Good luck

**eliotroyano** · 27th April, 2012, 05:02 AM

Originally Posted by mattydr67

What about the LED?
Is it turned on?
If yes in this case you'll need to reflash it.
Good luck

When the cable was working, just after plug it to the OBD2 port the LED blinks red some times and get green. Now it blinks several times in red and after that it turns off. And when I try to diagnose some car module it starts to get warm and hot but touchable.

**matekhr** · 27th April, 2012, 08:07 AM

Originally Posted by xoom

Try with older versions of VCDS like 805 - 912..

It works with 908

And the firmware is 1.81, but because it's NEC MCU inside instead of Atmege, I suppose it's not upgradeable?

It's not what I expected, because the cable is declared as 10.6, but at least, it works...

Maybe I should update my old cable to higher version - it's 7.04 with FTDI232BL and 93c46 eeprom. What can I do with it?

**KenshinPT** · 27th April, 2012, 09:16 AM

Originally Posted by matekhr

It works with 908

And the firmware is 1.81, but because it's NEC MCU inside instead of Atmege, I suppose it's not upgradeable?

It's not what I expected, because the cable is declared as 10.6, but at least, it works...

Maybe I should update my old cable to higher version - it's 7.04 with FTDI232BL and 93c46 eeprom. What can I do with it?

Hey!!! That's great news!

Regarding the 704 I bet you have a good hardware. If so, you can upgrade it to any available dump

Good luck.