Hi all,

First post for me.

I've read the FAQ's and through countless threads but I think I've just scrambled my mind now!

I am trying to read the SKC's from a 2002 Octavia and a 2001 golf both with ME7.5 ECUs.

I managed to read the SKC from both the ECU and VDO cluster of the Octavia using VAG K+can commander.

The golf has a RB cluster so I don't want to try reading it with VAG commander having read some horror stories and whilst it opens a channel with the ECU and connects via VAG commander it times out after starting to send and receive.

I have now successfully read the golf eeprom using Argdub's 95040 tool over OBD.

So my two main questions are:

Am I correct that I cannot read the SKC from the bin collected with argdub's 95040 tool over OBD? (When I open the bin file in a hex editor the SKC is FF'd out.) and that I need to read the ECU in bootmode as this is the only way to read the SKC?

Does anyone have any ideas as to why VAG commander timesout? I have tried playing with the settings in the config for time between messages, echo delay etc but it's always the same result. Timeout.

I would be really grateful if anyone can help me with this but understand that we are all busy people. I hope that I have managed to explain myself properly but if I haven't please tell me.

Lastly, thanks to everyone that has posted all the great stuff on this forum. I have already learnt so much more than I did a couple of weeks ago.

Hi.  Did the commander 1.19 work for you?
I have a similar situation with my 2001 Audi A6 2.7t.  I have Commander 1.4 that reads the cluster but won't read my ECU.  I need the ECU PIN to map the cluster to the ECU and then I can match my key with VCDS.   I've downloaded commander 2.5, which I'll try tonight. 
Any help is appreciated?

Unfortunately the old cluster is trashed.  Should have mentioned that.  I sent it off to have the LCD fixed and they ruined it.   They replaced it with a refurbished unit and I'm trying to match it to my ECU.  I wasn't able to try commander 2.5 last night but will tonight.

I'm trying a few versions of commander (1.4, 2.5, 4.5, 5.0) and they aren't reading my ECU but are reading my cluster.  Any other ideas of how to read the ECU through OBD cable?  I'm using a Hex-Can cable from Ross-Tech (old one).   Once I get the PIN from my ECU, I'll be able to adapt with VCDS.  Appreciate any help.

Sorry Zenerdiode, I'm not the original poster for this string.  I was asking if Commander 1.19 worked for their issue.  I have a 2001 Audi A6 2.7t that has IMMO3.  Following Ross-Tech's guide, I need the ECU PIN to match the cluster to the ECU on channel 50 and then match the key through channel 21 of the cluster.   Sorry if I added confusion for adding to the string. 

Hi again all.

I've been really busy over the last couple of months and haven't had much time to play with the golf. Thanks to everyone who has offered some help.

Macxxx: Yes an RB8 cluster in the golf. I took your advice and ran VAG epprom programmer yesterday and after about 45 minutes it connected and retrieved the SKC so thanks very much for that.

Zenerdiode: Your point about immo2 makes sense and the VAG epprom scan of the cluster confirmed this yesterday so no skc in ECU.

I still cannot read the golf ECU with anything but Argdubs tool and the RB8 cluster with anything but VAG epprom but Vag commander 1.4 read both the ecu and the vdo cluster in the skoda Octavia first time.

I now have a load of questions regarding trying to run the golf with the skoda ECU which is immo 3 and remapped but I think it would make sense to start a new topic.

Once again thanks for all your help your replies gave all the answers and I've learnt a little bit more as a result.