|
Title: SKC for new key - failure Post by: Rsicks on May 24, 2013, 07:33:55 PM First off, I am a new member to this awesome website and have been reading like mad. A lot to retain ;D
Well I am trying to create a new key for my 03 Audi A4. I cannot for the life of me find the SKC - and not because I do not know where to look... my car is not letting me. I apologize if I do not have all the info on the first post - if you need anything please let me know. So for starters I gave 95040 a shot... Quote C:\Program Files\Nefarious\NefMoto>ME7EEPROM --OBD -b 9600 -r -p 2 95040.bin ME7_EEPROM v1.40 COM: 2, Baud Rate: 9600 Opening COM2 ... OK Initiating communication ... FAIL. (error=0x50001) Closing COM2 C:\Program Files\Nefarious\NefMoto>ME7EEPROM --OBD -r -p 2 95040.bin ME7_EEPROM v1.40 COM: 2, Baud Rate: 10400 Opening COM2 ... OK Initiating communication ... FAIL. (error=0x50101) Closing COM2 C:\Program Files\Nefarious\NefMoto>ME7_95040 --OBD -r -p 2 95040.bin Ver: 1.31 Com Port: 2 Baud Rate: 10400 Opening COM2 ... OK Initiating communication ... FAIL. (error=0x01) Closing COM2 And when I try to use Nefmoto in general... Quote Standard... Reading all ECU info. Starting diagnostic session. Unable to properly start diagnostic session, attempting to continue with current undefined session. Negotiating communication timings. Successfully changed to new communication timings. 0% complete. 20% complete. 40% complete. 60% complete. 80% complete. 100% complete. Read 5 ECU info entries: 0x92, System Supplier ECU Hardware Number: 0261208346 0x94, System Supplier ECU Software Number: 1037368621 0x91, Vehicle Manufacturer ECU Hardware Number: 0x0D, 8E0909059 , 0xFF 0x9B, Calibration Date: 8E0909559R , 0020, 0x0300416F, 0x0B832378, 0x5658, 3.0L V6/5V , G 0x9C, Calibration Equiment Software Number: 0x00010100 Restoring Windows sleep mode. Quote Programming.... Reading all ECU info. ECU reports programming session preconditions have been met. Negotiating communication timings. Successfully changed to new communication timings. Starting diagnostic session. Start diagnostic session failed, ECU reports security access is required. Reading all ECU info failed. 100% complete. Restoring Windows sleep mode. It seems like ECU reports security access is required happens a lot. In Programing, in Logging... I cant seem to win. The ECU will not allow me in, let alone be able to get the SKC out of it. I am using a KII cable of off ebay and can use VCDS without any problems. And when I run Vag Commander it gives me a error saying cannot automatically detect EEPROM. I would rather stay away from taking the ECU out. I'm not real comfortable with benching it. So any help in getting Nefmoto or the 95040 would be amazing!! Title: Re: SKC for new key - failure Post by: k0mpresd on May 24, 2013, 07:56:19 PM if you are uncomfortable with benching an ecu then you have acquired the wrong hobby.
Title: Re: SKC for new key - failure Post by: Rsicks on May 24, 2013, 08:15:58 PM You have a good point. ;D
I think its only because its new to me. I have been reading more and I'm starting to feel better about it. I will need to do a lot more reading before I start benching comfortably though. Title: Re: SKC for new key - failure Post by: Rsicks on May 27, 2013, 01:03:56 PM I was able to pull the dump from the RB4 cluster with Vag Commander and it looks the same as the dumps found when I searched Google for other examples. Unfortunately like others have stated the program does not come up with the correct PIN inside the GUI.
Is there a way to find a SKC in the cluster dump like you can with an EEPROM dump? I've been looking for duplicates but there is none in mine nor any of the other dumps I have found for other A4's. The cluster dumps have been pretty uniform in the location of the VIN and IMMO3 serial numbers... so there should only be a couple places that it could be located in. |