[macNB]

That's ok
Good luck

Great. Regarding the fuse, lock and security bits, I am a little confused.

For the eeprom, I was going to use fantomel's "vers 6 11.11.5-12.12.0_eeprom 512 rl.hex" file from his collection. Now with PonyProg, is this the correct settings ?

[mattydr67]

I don't know what Fantomel shared in his collection
For 512b words flash its not the right one
For 256b words flash that its the correct one
Good luck

[macNB]

OK. I flashed it successfully (Program, EEPROM and Fuses (256b)).

It successfully installed fantomel's 11.11.5 VCDS s/w (including driver) (while Antivirus is disabled).

Re-start Antivirus and add VCDS.exe to the exception list.

I plug the tool into the USB, installs USB driver and I start VCDS.
Plug the tool into the car OBD port and start Ignition.

"About" button tells me that it's licensed and activated.

Ran the port test and I get this:

Status : Ready
K1: OK
K2: OK
CAN: Not Ready

Cannot to Autoscan ....it says something about CAN function

Tried selecting Engine (address 1) and nothing found.
The only Controller it can find is at Address 2 - the AUTOMATIC GEARBOX.

Tried the tool on both our automatic cars (2010 Polo and 2010 PASSAT).
Same on both

Any ideas what's wrong ??

[mattydr67]

If you plug the tool into your car ( Polo 2010 )
A d then plug the toll to usb
Turn the ignision on
Star the vcds and go TEST
You have the popup windows message tgat you shared it
CAN Not ready
Then SAVE
Go to about and the tool is Valid/Activated
This mean that your CAN BUS in your tool is defective or one or two pins 6 and/or 14 in the OBD plug are connected well
This issue has nothing to do with the dump
My advice is to install the vcds software in a diffrent computer and test a k-line car and then a CAN BUS one before to start repair/fix the CAN BuS in your tool
Good luck

[macNB]

My advice is to install the vcds software in a diffrent computer and test a k-line car and then a CAN BUS one before to start repair/fix the CAN BuS in your tool
Good luck

Thanks for the suggestion.
I measured the resistance between pins 6 & 14 on the OBD connector and its 120 ohm and I traced the tracks back to chip TJA1050 pins 6 & 7 (CAN-L & CAN-H). Either that chip is dead or the MCP2515.

I wish I had a schematic.

It's strange that in both cars, it can scan the auto gearbox controller (which I assume is CAN) but not others.

I don't have access to another car with K-Line.

Time to give up ?

[mattydr67]

Even Engine ECU you can try it if you set to connect by k-line
The engine ECU can also be connected by k-line in a CAN BUS car
But you hae to set it in vcds to be able to do this
Gearbox too

I don't know if its worth for you or not but first step to fx your tool is to change the TJA1050
Good luck

[macNB]

Reading the Engine ECU via K-line may be possible but does not help scan the rest of the CAN controllers.

I am a little surprised that I managed to damage either TJA1050 or the MCP2515 as they are physically mounted on the opposite side of the board to ATmega162 (where I attached the 4 wires).

If I can source the chips, I'll try to fix it otherwise it might be cheaper (and easier) to buy a new one.

Problem is finding decent good quality tools that are easily installed and updatable.

[mattydr67]

Atmega pins ( 1,2,3 ) has direct connection to MCP 2515
No matter that is on the other side of PCB

A HQ clone could be a solution but its not cheap
Good luck

[macNB]

Yes I checked those ATmega162 pin connections to MCP2515 and they are still connected and no shorts.

Should I look for HQ clones based on FT232BL and not RL, or does it not matter ?

[mattydr67]

No mate
I wanted to say that Atmega pins 1,2 and 3 are connected to MCP2515
Maybe it hapend anything there. But if you want my opinion i suppose that the TJA1050 is defective usually.
Vary rare MCP2515 is defective
And all of this only because the car and from time to time because the poor factory quality
As i told you a HQ clone it has a TVS diode on CAN BUS for protection
Good luck