Key transponder coding issue. Difficult one.
Thread Starter
|
Senior Member
Joined: Jul 2019
Posts: 829
Likes: 189
From: Finland
This car is sorted now.Atleast the programming side of it.
Last time car was left on state where it did not accept any key transponders but did accept fobs. Ids/wds/sdd did not give any reason why transponders were not accepted. Instrument cluster were practically only device that gave any giveaway. It gave faultcode about SCP bus being faulty(can not remember the code). To me this fault code especially in case like this may not be the bus itself that is faulty. More like that some of the bus devices screaming wrong bits to it or doesn't talk at all. But to be absolute sure I went in and measured all of the canbus wires except J gate connecotor using TSB XJ413-02a. Only IP055 had some dirt in one pin. Washed every connector what I opened with connector cleaner and ram then in and out couple of times after measurement. There were no issues as it not supposed to be. As the TSB consist only CAN bus.
Next did the same to the SCP bus. Measured mainly only the connectors what could affect to the issues.Measured the wires back and forth with no issues. Cleaned connectors aswell. Any of this job did not have any affect to the scb bus fault. Lastly using an oscilloscope I looked in to the scb bus. Voltage levels were correct, no bad looking data bits nor anything else wrong.
Then it was desided that when bus'es are working physically that the fault can only lie in the programming that is still somehow wrong. We started then program the car completely from the beginning again. Starting from making new session in the wds and making sure that settings absolutely correct in there. Then it meant programming every module as new module from the list down. ECM is done last. Every module were configured manually making sure that the options matches to the car. Found out that America sold car may not have alutomatic headlight levelling even with HID lights. That was weird to us Nordic guys and first big fault in the programming what I did last time. Pretty early came DDM drivers door module time to get programmed. After ddm program, key transponders and fobs were programmed to it. They both went in correctly. Somewhere during programming I noticed that the steering wheel electric lock is not locking nor making any sound. Quick google showed where it shoul be and there wre no lock module. Not so quick goole gave again the same conclusion that America sold car may or may not have steering lock. This was so confusing us. But knowing this before that when car has electric steering lock that does not work correcty. it wil make car non running. Count 1+1 = it will make this car not accept any key. Later on we realized what was the black connector hanging in the breeze and never been used under the IPK. It is the steering lock connector..
Eventually came IPK turn to get programmed. This IPK is already programmed to the car and it is in kmh instead of mls and has correct odometer count. Programming went in fine and it was the manual config time again. In IPK there were setting about the steering lock. That was enabled as default. Turning that disabled gave the feeling that this was it. And it was. After IPK config, keys are again programmed to it as IPK,DDM and RDM has transponder codes sored in. This time IPK accepted the keys ! and wds went further than ever asking steering column barcode numbers. After those were read from the column and inserted IPK was programmed succesfully Eventually it was ECU's turn and after that there were no fault codes found in IPK nor ECM or other necessary modules.
Turned the key to start and starter spins.
Engine does not start though. 6 yo gasoline and jammed fuel pump was quickly diagnosed..
Last time car was left on state where it did not accept any key transponders but did accept fobs. Ids/wds/sdd did not give any reason why transponders were not accepted. Instrument cluster were practically only device that gave any giveaway. It gave faultcode about SCP bus being faulty(can not remember the code). To me this fault code especially in case like this may not be the bus itself that is faulty. More like that some of the bus devices screaming wrong bits to it or doesn't talk at all. But to be absolute sure I went in and measured all of the canbus wires except J gate connecotor using TSB XJ413-02a. Only IP055 had some dirt in one pin. Washed every connector what I opened with connector cleaner and ram then in and out couple of times after measurement. There were no issues as it not supposed to be. As the TSB consist only CAN bus.
Next did the same to the SCP bus. Measured mainly only the connectors what could affect to the issues.Measured the wires back and forth with no issues. Cleaned connectors aswell. Any of this job did not have any affect to the scb bus fault. Lastly using an oscilloscope I looked in to the scb bus. Voltage levels were correct, no bad looking data bits nor anything else wrong.
Then it was desided that when bus'es are working physically that the fault can only lie in the programming that is still somehow wrong. We started then program the car completely from the beginning again. Starting from making new session in the wds and making sure that settings absolutely correct in there. Then it meant programming every module as new module from the list down. ECM is done last. Every module were configured manually making sure that the options matches to the car. Found out that America sold car may not have alutomatic headlight levelling even with HID lights. That was weird to us Nordic guys and first big fault in the programming what I did last time. Pretty early came DDM drivers door module time to get programmed. After ddm program, key transponders and fobs were programmed to it. They both went in correctly. Somewhere during programming I noticed that the steering wheel electric lock is not locking nor making any sound. Quick google showed where it shoul be and there wre no lock module. Not so quick goole gave again the same conclusion that America sold car may or may not have steering lock. This was so confusing us. But knowing this before that when car has electric steering lock that does not work correcty. it wil make car non running. Count 1+1 = it will make this car not accept any key. Later on we realized what was the black connector hanging in the breeze and never been used under the IPK. It is the steering lock connector..
Eventually came IPK turn to get programmed. This IPK is already programmed to the car and it is in kmh instead of mls and has correct odometer count. Programming went in fine and it was the manual config time again. In IPK there were setting about the steering lock. That was enabled as default. Turning that disabled gave the feeling that this was it. And it was. After IPK config, keys are again programmed to it as IPK,DDM and RDM has transponder codes sored in. This time IPK accepted the keys ! and wds went further than ever asking steering column barcode numbers. After those were read from the column and inserted IPK was programmed succesfully Eventually it was ECU's turn and after that there were no fault codes found in IPK nor ECM or other necessary modules.
Turned the key to start and starter spins.
Engine does not start though. 6 yo gasoline and jammed fuel pump was quickly diagnosed..
Last edited by Vauxi; Jul 30, 2025 at 03:22 AM.
Veteran Member
Joined: Dec 2019
Posts: 3,695
Likes: 1,223
Good job recovering it. This is the same method you can use to disable steering lock on a non US car
WDS blue cable has nothing to do with VID block cars. It’s the automatic MS-CAN interface for cars with a CEM/SJB. Only car that needs a blue cable is the 2006.5 New XK
WDS blue cable has nothing to do with VID block cars. It’s the automatic MS-CAN interface for cars with a CEM/SJB. Only car that needs a blue cable is the 2006.5 New XK
Last edited by xalty; Jul 30, 2025 at 02:07 PM.
Thread
Thread Starter
Forum
Replies
Last Post
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)