Key Coding with AK90 2003 2.5i

[colb]

Not had any luck coding a couple of keys for my one key car, Had a replacement Diamond key and a Flip key cut by a local cutter and set to coding them to the EWS using a new AK90 machine as attempts to code them with a mates AK90 resulted in continual no touch errors. New machine successfully read the ews module and showed 1, 2 and 3 keys ticked in use.
It tells me that the working key I have is No2. Coded the Diamond Key to No3 and the flip key to No4 ensured key status for 4 was ticked and saved the Bin file. I was unable to get the Bin file written back to the EWS module, write error every attempt.
Tried the keys in the car Original works and starts the car, New Diamond key turns ignition on but fails to start the car, same with Flip key 4. Checked keys by reading them on the AK90 and they report OK.
Put BMW Scanner on the car and checked out the live data of the EWS with each key Key 2 the working key passes all tests and shows Fixed , Random and Password OK, the other two keys show wrong Fixed, Random and Password so obviously don't start the car.
I assumed No 3 could be written to the key and that would take over from the original No3, New No 4 would be already programmed into the car as one of the 10 slots available, seems I'm wrong or not doing siomething I should to get the two new keys to work. Must say the AK90 is preety awful to use when reading the processor chip on the board its very hit and miss to get it to read and it won'y write back for me.
You Tube would have you believe its an easy process using the AK90 to do this job, I can't agree there must be a better way,been looking at BMW Editor that plugs into the module socket, anyone use that to do this job?
I would add that the transpondsers in the new keys are PCF7935AA and came supplied with the keys, have tried another transponder in the diamond key but its just the same result.
Also aligned the EWS and DME using BMW Scanner but that didn't change anything with the key function.
Any suggestions, I am in Newport,South Wales, UK.

 

[colb]

Had another go with the AK90+ tonight after talking to IAmOrion on here on another key thread. Re coded the new keys using the saved Bin file and managed to get them displaying the same Vin number as the working key which I havn't managed with all the other attempts I have made to code the new Diamond and Flip keys I had cut. Maybe this is the reason the keys were being rejected with Wrong Fixed, Random and Passwords. Will try them in the car in the morning, heres hoping this will fix the problems I'm having getting them to work.

 

[colb]

Tested this morning, keys don't start the car even though they test ok on the AK90 machine. Checked their status using BMW SWcanner and same old problem. Wrong Fixed code, random code and password all reported on each key. Still left with my original working key. Preety sure I have coded the keys correctly using the saved bin file from the EWS module so am really at a loss to know why I get these keys failing to start. What according to all the videos I have seen on using the AK90 was a simple job has proved to be an absolute pain. Going to have a chat with IAmOrion and let him view how I have been using the AK90, maybe he will spot something wrong. The longer this goes on the more I suspect the EWS module as being duff when it comes to putting new or exhisting keys into it?

 

[colb]

Had an online session with IAmOrion this evening to check out my AK90 and the Bin files and keys. Nothing identified in how I have been coding, suggestion is to get some replacement transponders PCF7935AA ID44 that he uses, keys I have came with these chips but worth trying some new ones as mine have been recoded a few times now and may be duff. Will have another go when I get them.

 

[colb]

Did a fresh read of the EWS and the bin file when analyzed came back with a strange Vin number and showed all 10 slots as used. Now nothing has ever been written back to the EWS and the original first read showed only 1,2 and 3 keys as used.
Something is obviously not right with either the ews module or the AK90. At a loss to spot what is wrong, I am waiting for some new transponders to give it a go again but if the EWS module is faulty I doubt if new keys with new transponders will code correctly with a duff bin file. May be going to an independant who can have a look at whats going on. I don't want to lash out £174 at BMW for a factory key if when I get it it fails to work due to a dodgy EWS. I am supposing that a new BMW supplied key will come coded to slot 4? In all of this my working key showing as Key 2 in AK and Key 1 in INPA works consistantly.

 

[srhutch]

My understanding is it's not the keys that are programmed, it the EWS to the keys. If you havent written anything to the EWS that that will be the issue.

IAmOrion should be able to confirm though.

 

[IAmOrion]

My understanding is it's not the keys that are programmed, it the EWS to the keys. If you havent written anything to the EWS that that will be the issue.

IAmOrion should be able to confirm though.

Other way around You read in the EWS, which saves a bin file... you then use that bin file to code a key to the EWS (Picking one that's "Unused") or you can replace a known lost key if desired. When I first started, I was ticking the "used" box in the EWS data, and then writing back to the EWS (You can write back to an EWS3 module but not an EWS4) - however I have come to learn that this is NOT required. The EWS / other modules in the car will mark a key slot as "used" when it detects the new key being used.

As mentioned to [ref]colb[/ref], I suspect it's a case of wrong blank transponders and so have suggested buying the same blank key that I've always ordered for all the people that've come to me for keys (Standard diamond shape) and giving that a go... I've done 40-50 keys and never had a problem with the keys/transponders. (I did get caught out with newer EWS4 modules and had some issues, but after sorting out an adapter for the AK90+ It's all good and working)

 

[colb]

Awaiting delivery of some new transponders at IAmOrions suggestion to replace the ones already used in the new keys I had cut, also been talking to a local Auto Locksmith who reckons he can code the keys but has to get a cable, planning on doing it through the eeprom in the module. Will report back when we get around to doing it.

 

[colb]

Sorted, at last, called on the services of a mobile auto lockie, he coded my new diamond key using a Zed-Full coding machine, read the eeprom on the EWS board and then coded new key to slot 8, that failed to crank the car so he recoded to slot 3 which is a known used slot that I do not have the key for. Success, cranked first go. Confirmed its operation using BMW Scanner and viewed key status andm live data when using the key. Passed Fixed, Random and Password and viewed the rolling code changing when key used. All is well, now got two working keys and the new flip key as a spare which can have the chip from Key 3 popped in if needed.
Will be attempting to return the obviously duff AK90 machine, wouldn't want to use that again after my experience with it, amazed others who use it have success, if I ever want to have another go I would try the BMW Editor kit, more expensive but that uses the same method as the lockies Zed-Full machine to read the eeprom, uses the pinouts on the module and a touch probe on a solder joint on the reverse of the board to prompt it to read and write to and from the module.
Charged me £120 even though I had my own key cut but having seen what he had to pay for the Zed-Full machine and his travel on top it was still cheaper than a BMW supplied key, that not knowing the key history of the car may well have been no crank if they had supplied a key for slot 4 which shows up as the next unused key.
If anyone in South Wales wants any keys doing pm me and I will pass his detail to you, he will code keys supplied or cut and code keys for you.

 

[mickcheshire55]

I’ve got an 04 plate and have been having the exact symptoms you have. Even down to the EWS showing 3 keys, the random vin number etc etc.. what is very interesting I also have another car an it coded a key for that 1st time no issues. I’ve even tried running the AK90+ on Windows XP.. still the same. All writes to the EWS fail...that has to be the issue I can’t see any other reason, it must have a communication breakdown somewhere along the way.. I have 2 keys, key 1 and key 2 according to the AK90. I even tried to tell it the new key was key 2 and it accepted it and said it was programmed...needless to say it wasn’t and my original key 2 still works fine. It’s really odd as the new key shows as correct when read in the AK90 just won’t crank the car.. something else that’s very odd. I believe you can only programme the pcf7935aa once...yet it you programme it as say key 2 it accepts that and shows as it’s done but then you can rewrite it as key 3 and it does the same..very strange.

 

[colb]

As I said I gave up with the AK90 and got a local mobile Locksmith to sort it, took him twnety mins to code my key but he read the EWS board eeprom chip not the same one as the AK90. Coded the key with the data he downloaded on his machine. First attempt he coded it to slot 8 but that didn't work. Since my EWS showed it had 3 keys registered my working key was number 2 so he recoded the new key to slot 3 using the same transponder in the key. Popped the EWS back in the car and we were in business, cranked ok and remembered the key, rolling code all working as it should. I also had a flip key cut but rather than shell out for him to code that decided it was just as easy to change the transponder over if I ever need to use it. as both keys are easily opened. Still don't know why the AK failed to code when other have managed fine, I found the AK was hit and miss connecting to the chip on the board even with clean pins.

 

[mickcheshire55]

I noticed when you read the EWS it randomly puts mistakes in the vin (pretty much a different error each time you read) I opened a saved bin file and corrected the errors in the vin and told it to write back to the EWS... even tho the EWS was not even connected at that time...it went through the process as if the EWS was connected but it was not so it obviously said write failed at the end of the process, but the bizarre thing is when I then wrote to the key it corrected the vin error there too.. still no luck with it working tho...I’m beginning to wonder if it makes the errors in the vin, if it also makes errors in the codes when reading and then writing to the 7935 chip..and that’s maybe why the EWS does not accept it..

 

[colb]

Tried all that when I had a go, as well as the wrong Vin numbers displaying it also put in the build factory as Oxford where the Mini line is.
You really dont or shouldn't need to write the bin file back to the EWS after coding a key. It is supposed to code the key to your chosen slot which should be the next unused key slot as the position is already coded in the EWS to accept a key to that new position, the key just needs coding from the bin file the Ak90 has read from the processor on the ews board. Thats where mine all went wrong it would not code correctly in that it coded the key and also read the key when checked on the Ak90 however the EWS didn't recognise the key so would not crank the car. Tried recoding to a few of the other unused slots but got the same results.

 

[mickcheshire55]

I’ve also got an 03 plate. What is really odd it has no bother programming a new key for that one. I’ve done a 2nd previously and now a 3rd key for that after all the failures on my 04 plate..it is really strange..straight through the process no issues. As you say no need to write back to the EWS. Still made the vin number errors but these correct themselves after the key has been used and the mileage updates on the new key..

 

[mickcheshire55]

Out of interest did your locksmith programme one of the keys/chipsyou had previously attempted to programme with the AK90 or did he use another virgin chip?