VAG-COM/VCDS EVERYTHING

**poilodo** · 1st February, 2022, 08:26 PM

Originally Posted by borg123

Guys I have problem with my interface, it seems dead.
I used @mepsnet picture as it is the same, circled red what is burned.
Can it be fixed?
What is that component and what is the right part number for replace?
Thanks!

Attachment 864720

it is an MCP2562.
see page 17 on this link : https://www.yumpu.com/en/document/re...sheet-semitron

**comin** · 3rd February, 2022, 10:36 AM

Originally Posted by sumi1

Tested vcds wiit atmega -loader 9.2-vcds 21.9 working well for windows 10 64 bit and windows xp

VCDS 21.9 ENG + cable made in china Atmega 162
does not work with cars year 2019
Someone was checking on the 2019 car ?
U78bfe168ad27430fac53147534f2335f0.jpg

**liviudiaconu** · 3rd February, 2022, 02:41 PM

try 19.6, maybe have more luck. If not..ARM version

**ganobi** · 3rd February, 2022, 07:20 PM

Originally Posted by comin

VCDS 21.9 ENG + cable made in china Atmega 162
does not work with cars year 2019
Someone was checking on the 2019 car ?
U78bfe168ad27430fac53147534f2335f0.jpg

Atmega 162 no longer supports this year.

**alin 151** · 4th February, 2022, 08:28 PM

Hi!
I need the ept file for the V2 interface taken from flyfvdi.
VCDS Hex-V2 with main chip STM32F405VGT6
I have 2 interfaces V1 with Atmega and V2 with ARM.
I accidentally took V2 and rewrote the ftdi with the ept from V1 and now VIIPlus Loader no longer recognizes it..
Thanks in advance!

**nextor** · 4th February, 2022, 09:06 PM

Originally Posted by alin 151

Hi!
I need the ept file for the V2 interface taken from flyfvdi.
VCDS Hex-V2 with main chip STM32F405VGT6
I have 2 interfaces V1 with Atmega and V2 with ARM.
I accidentally took V2 and rewrote the ftdi with the ept from V1 and now VIIPlus Loader no longer recognizes it..
Thanks in advance!

The ARM interface doesn't use FTDI for USB anymore. The STM32F405/415 chip has integrated USB support.

**alin 151** · 4th February, 2022, 09:19 PM

Seriously?
I did not know.....
Do I still have a chance to fix it?
I used Mprog to read it and now I have VID 0403 and PID FA24

**nextor** · 4th February, 2022, 09:24 PM

Originally Posted by alin 151

Seriously?
I did not know.....
Do I still have a chance to fix it?
I used Mprog to read it and now I have VID 0403 and PID FA24

This is the PID/VID used by the Atmega interface (HEX-CAN)

**alin 151** · 4th February, 2022, 09:40 PM

I noticed...
I compared it to V1

**bg17aw** · 5th February, 2022, 10:17 AM

Originally Posted by mepsnet

That is not the only difference look this photo which I made

Attachment 864574

I have the exact same two, can anyone explain which one is better to keep?

**nextor** · 5th February, 2022, 11:07 AM

Originally Posted by bg17aw

I have the exact same two, can anyone explain which one is better to keep?

The one with the big electrolytic capacitors is better.

**bg17aw** · 5th February, 2022, 02:00 PM

thanks. Care to explain why?

**alin 151** · 5th February, 2022, 02:05 PM

Would you like to read yor V2 interface with Mprog and post the ept file?
I really need to fix this cable.
How is this cable recognized in Device Manager?
Thanks!

**nextor** · 5th February, 2022, 02:11 PM

Originally Posted by bg17aw

thanks. Care to explain why?

Read 3-4 pages back and you'll understand why.

**nextor** · 5th February, 2022, 02:12 PM

Originally Posted by alin 151

Would you like to read yor V2 interface with Mprog and post the ept file?
I really need to fix this cable.
How is this cable recognized in Device Manager?
Thanks!

I'm not at home and I don't have the interface with me.