VAG-COM/VCDS EVERYTHING

[liviudiaconu]

CAN Gw 2005+ or 2006+ appear like CAN OK, for older cars appear CAN NR Try on a 2006-2007 car to made a test.

IF your VCDS is BL you can use a version of eeprom like accept VCDS 11.11.5 EN OEM (no loader needed)

[mesterel]

I have a Vag Com 11.11 atmega 162, gal16 I hope the dumps are OK.

[MacNB]

@liviudiaconu

,

Both my cars are 2010 model (Polo & Passat) and they have CAN.

My VCDS is BL and the version of VCDS s/w & eeprom is from Fantomel's collection 11.11.5. I don't think it's OEM as Antivirus complains that it's malware and I have to exclude it from scans. Can't find "VCDS 11.11.5 EN OEM"

The BL eeprom and 11.11.5 should have no effect on the CAN function not working.

[liviudiaconu]

With vcds arrived CAN=OK? If yes, something wrong on your work. If not, maybe your tool is deffective (HW)

[MacNB]

With vcds arrived CAN=OK?

Sorry I do not understand what you are asking.

I plug the cable into the Car OBD, start VCDS 11.11.5, start Ignition, click test port.
Interface is found, Port test is OK but "CAN: Not ready"

I can only scan the Auto gearbox controller since it is not CAN but K-Line.

Yes, I think there's a h/w problem. I am going to replace the CAN Transceiver chip (TJA1050).

[liviudiaconu]

Sorry for my bad english.

When you bought the cable, arrived with a CD with soft. With that soft the "test" appear with CAN=OK?
If yes, and now, with 11.11.5 not, can be a soft problemm or can be HW, too (simple coincidence).

If never worked with CAN=OK, HW problemm.
1. resolder all pins for CAN from Atmega, MPC2515, MPC2551/TJA1050 etc
2. if not, replace one by one CAN components 2551/1050 ..2515.etc

The total price...depends from country to country...

[riha]

Didn't find with search: i have chinese vagcom 12.1 with nec+ft232rl. I used aminebot patched vcds 908 but it said that its not registered. Which vcds version i should to be used?

[alexm1]

If it is with NEC, you can not make it work, dumps are available only for Atmega. Do not waste your time, buy another one and this time make sure it is with Atmega

[liviudiaconu]

Didn't find with search: i have chinese vagcom 12.1 with nec+ft232rl. I used aminebot patched vcds 908 but it said that its not registered. Which vcds version i should to be used?

Use MProg for rewrite .ept file. Try the version from your CD. 99% from times NEC interfaces didn't erase dump, only destroy FT232 settings.
Or, like Alex sed, buy another with Atmega.

[MacNB]

Sorry for my bad english.

no problem.

When you bought the cable, arrived with a CD with soft. With that soft the "test" appear with CAN=OK?
If yes, and now, with 11.11.5 not, can be a soft problemm or can be HW, too (simple coincidence).

If never worked with CAN=OK, HW problemm.
1. resolder all pins for CAN from Atmega, MPC2515, MPC2551/TJA1050 etc
2. if not, replace one by one CAN components 2551/1050 ..2515.etc

The total price...depends from country to country...

Yes when i first got the cable, it all worked fine....Autoscan, long coding, etc. It came with 11.11.0...and was registered/activated
Then, one day (many months later), I must have forgotten to turn off the Wifi and the autoscan would not work and got unregistered.

So, I refreshed the FR232BL with one of fantomel's EPT file for BL chip.
I attached 4 wires to the ATmega162 (pins 1,2,3,4) and built a parallel port programmer.
Then I flashed the Atmega and the EEPROM using PonyProg2000.
All looked OK until I plugged it to the car....got "CAN: Not Ready"

I replaced the TJA1050 with MCP2551 and tested it the car...same..."CAN: Not Ready.
Next I replaced the MCP2515 and tested it the car...same..."CAN: Not Ready.

I started to get "CAN: Not Ready" after I attached the 4 wires to the ATmega162 chip and re-flashing.
Unless the new flash is not programming the CAN Controller correctly, or some other h/w damage has occurred.

I have tried three different versions of VCDS 11.11.0 (that came with the cable), 11.11.5 and 12.12.0 and all give the same CAN error

[riha]

Use MProg for rewrite .ept file. Try the version from your CD. 99% from times NEC interfaces didn't erase dump, only destroy FT232 settings.
Or, like Alex sed, buy another with Atmega.

Just reset this adapter, install vcp FTDI drivers and it work with vagcom 409.
Another question: how i can use my adapter with vag k-line commander?

[liviudiaconu]

[...]

I started to get "CAN: Not Ready" after I attached the 4 wires to the ATmega162 chip and re-flashing.
Unless the new flash is not programming the CAN Controller correctly, or some other h/w damage has occurred.

I have tried three different versions of VCDS 11.11.0 (that came with the cable), 11.11.5 and 12.12.0 and all give the same CAN error

Q=16MHz try to replace.
3 of that 4 Atmega's pins are wired to MPC2515. Maibe when you soldered the 4 wires you made "short circuit" between 2 pins.
Try to use more "flux" and a good iron and remade the solder of 4 pins. If not, try (if you have IR station or hot air flow station) to desolder Atmega and resolder again without "shortcircuits".

If after this still not..and as you say, replaced 2515, Atmega 162 can be damaged. But until now i never destroyed an Atmega.

[MacNB]

Q=16MHz try to replace.
3 of that 4 Atmega's pins are wired to MPC2515. Maibe when you soldered the 4 wires you made "short circuit" between 2 pins.
Try to use more "flux" and a good iron and remade the solder of 4 pins. If not, try (if you have IR station or hot air flow station) to desolder Atmega and resolder again without "shortcircuits".

If after this still not..and as you say, replaced 2515, Atmega 162 can be damaged. But until now i never destroyed an Atmega.

Thanks for your suggestions.
Someone else (Matty) suggested replacing the 16Mhz crystal too.

I have checked all the traces between mcp2515, mcp2551 and the ATmega162 (against a generic circuit diagram) and there are no shorts and they are connected correctly.
If the ATmega was destroyed, then surely VCDS would not pass the test and display v1.92 ?

For now, I think I am going to give up and look for a new tool.

[liviudiaconu]

Thanks for your suggestions.
[...]
I have checked all the traces between mcp2515, mcp2551 and the ATmega162 (against a generic circuit diagram) and there are no shorts and they are connected correctly.
If the ATmega was destroyed, then surely VCDS would not pass the test and display v1.92 ?

For now, I think I am going to give up and look for a new tool.

Can be a little short between (let say) pins 4 an 5..
Because of that i say to desoder and cleanely resolder Atmega.

Atmega can be destroyed at one in/out pin only, that mean Test on K1, K2 is OK. Is not like 7805 (+5V appear or not correctly, so is good or destroyed).

[MacNB]

Atmega can be destroyed at one in/out pin only, that mean Test on K1, K2 is OK. Is not like 7805 (+5V appear or not correctly, so is good or destroyed).

Ah OK I understand -- so one of the I/O lines could be dead.
Problem is I do not have good tools like hot-air guns to remove and re-solder quad-line packages like ATmega. I managed to remove MCP2515 without a hot-air gun but I think that's my limit.
Thanks for the suggestion.