VAG-COM/VCDS EVERYTHING

**Xaby** · 31st January, 2018, 10:56 AM

VAGCOM_HWType.exe only works if you connect interface to the car or external
12v.
Led is red meaning bad flash in atmega.

**xoom** · 31st January, 2018, 05:18 PM

Originally Posted by Domi

LED flashes red = Bad Flash FW

Or damaged Hardware..

**eliotroyano** · 31st January, 2018, 06:55 PM

Originally Posted by xoom

Or damaged Hardware..

Will be nice to know the possible software issues the interface based in led color or blinks. I have an interface that I repair properly (dumps reflash atmega ftdi) and all the time led blinks in red.

Enviado desde mi Life One X mediante Tapatalk

**alexm1** · 31st January, 2018, 07:27 PM

There is a type of interface with blinking led but still working, is the model without LM7805 (and no GAL/ATF inside). If you connect first on the car and then to pc the led will not blink red, otherwise led will blink until you make the test in vcds.

**eliotroyano** · 1st February, 2018, 02:33 AM

Originally Posted by alexm1

There is a type of interface with blinking led but still working, is the model without LM7805 (and no GAL/ATF inside). If you connect first on the car and then to pc the led will not blink red, otherwise led will blink until you make the test in vcds.

Here are the pics of my interface. HW0x46. ATmega162 + GAL16V8 + FT232RL + 7805. Led blinks red all times. I reprogram ATmega and FTDI several times and result is the same. What can be wrong?

IMG_20180131_211751[1].jpg
IMG_20180131_211844[1].jpg

**Domi** · 1st February, 2018, 07:19 AM

The wire is for what ?!

**alexm1** · 1st February, 2018, 09:14 AM

Who did solder that wire and why?

**hid3** · 1st February, 2018, 09:35 AM

Holy shit, what a mess...

**eliotroyano** · 1st February, 2018, 10:27 AM

Friends wire is for pin #4 of ATmega162. It is reset pin. It is used to locate a header above CAN IC to reflash interface. Glue near ATmega is silicone to avoid wire movement. Sorry if it is not so pretty.

**liviudiaconu** · 1st February, 2018, 10:37 AM

Led blink red and TEST result?

**eliotroyano** · 1st February, 2018, 10:56 AM

Test result is interface not found.

**jakuza** · 1st February, 2018, 01:17 PM

Originally Posted by liviudiaconu

Are you sure 100%?

I read on this thread long time ago.
But there is also some post of mattydr67 on other forum - HERE!

Magadan told that GAL dump are different in 44 and 46 from the one in FT232B and FT232R - I am confused now, all tools are with FT232B or FT232R...

**arturlu** · 1st February, 2018, 02:22 PM

Hello,
I've got clone and it's look like on attached pictures. This is ATMEGA 162 (16AU 1625 H) - invisible on pictures. Other parts are: FT232RL, ATF 16 V8B, MVP2515 and STC 12C2052.
obd_01.jpg obd_02.jpg
Now it works under version 16.8.0.3 with kn32/64.exe (I think it's kind of loader).
I'd like to upgrade to higher version because of missing rod file error for 01-Engine.
VAGCOM_HWType shows 1.96, 0x46, ROSS-USA.
I wonder if it is possible to do some more check before run VAGCOM_EEWrite or running VAGCOM_EEWrite is safe.
1. Is it safe to run VAGCOM_EEWrite when interface is connected to OBD in the car and when ignition is off (as when I run VAGCOM_HWType)?
2. I know that i have to remove R50 but is it possible tu run VAGCOM_EEWrite with working STC only for test purposes?
I would like to do that in that way because I don't want to do any physical modifications to interface (i.e. removing R50) now, but I would like check if I will need to use external programmer (i.e. changed firmware).

Best regards.

**magadan** · 1st February, 2018, 02:46 PM

Originally Posted by jakuza

...But there is also some post of mattydr67 on other forum - HERE!
Magadan told that GAL dump are different in 44 and 46 from the one in FT232B and FT232R - I am confused now, all tools are with FT232B or FT232R...

Mattydr67 didn't study this chip carefully. The public file "*.jed" will work in a cable with a firmware 44 correctly. This file will work in a cable with a firmware 46 too, but in certain cases this file will incorrectly work.
The firmware 46 can use in a cable with a chip of FT232B , and the firmware 44 can use in a cable with a chip of FT232R. Therefore the file "*.jed" doesn't depend on FT232 chip, but this file depends on type (0x44 or 0x46 or etc) a firmware which is programmed in a chip of an atmega.