Key transponder coding issue. Difficult one.
#1
Key transponder coding issue. Difficult one.
Hello.
I've been working on off style couple of days now with the 2004 xj8. Car worked correctly until owner tried to replace instrument cluster from miles to kilometer -one. That did not work of course without coding. He did not knew this and tried another mile cluster. This time car went totally haywire. When I stepped in he had tried somekind of coding and message center in the IP now displayed CONFIG D R and some other letter. After four completely full day of coding in somewhat correct order all of the car modules back to work I have now in state where only IP, DDM and ECM has config error fault code. And AUD, but that is not snifigant in this matter. Abs unit was shorted and that gave nice difficulty level increase to diagnose why voltages goes down two times every time when key was turned to RUN position. ABS module is now replaced and coded in to the car and it is sorted.
Code in DDM is config error. Propably just because it has keyfobs coded, but no transponders.
Instrument Pack has U1262 SCP bus error. I used oscilloscope with VMM to look it and bus is allright what comes to voltage levels in high and low states. So this tells me that this is consequence fault code what comes when some other device in bus is not working propely(has errors in its own area and yells to bus wrong bits). Car has now propely coded KMH instrument pack and that too shows same U1262 fault code.
ECM has security input P1262 code. That is general pats code. And most likely it is now cause transponder coding does not pass.
The amount of reading about x350 control module coding in tsb and teaching materials is vast. Still ids/sdd gaves me error every time transponders are about to code.
What happends is ids deletes current transponder codes and asks first key to code. I insert it and turn it to RUN position as instruction says. After first key it asks second one and so on. Next it shows result that is Key not programmed. Next screen says that 2/2 keys are programmed. That is clearly wrong
I have measured with an oscilloscope that there is data signal between transponder ring and IP when key is inserted and turnet to RUN position. Verified too with the keyfob tester that has test to this. Replaced the lock, ring and keys with another one and that did now make any difference. Ring is wired straight to the IP. IP reads the key and communicates with the ECM.
We have IDS 118.5, SDD v160, Mongoose, WDS v43, VCM and VMM. Plus other measuring devices ofcourse.
There is a TSB etc where it says something about key not progrmmed because bad connector pin in a footwell connector. I can not find it.
Where to go next ?
Car is 2004 Standard wheelbase 4.2 V8 sold to USA, imported to Finland. Wds finds it as 2003.5 and sdd as 2004.
I've been working on off style couple of days now with the 2004 xj8. Car worked correctly until owner tried to replace instrument cluster from miles to kilometer -one. That did not work of course without coding. He did not knew this and tried another mile cluster. This time car went totally haywire. When I stepped in he had tried somekind of coding and message center in the IP now displayed CONFIG D R and some other letter. After four completely full day of coding in somewhat correct order all of the car modules back to work I have now in state where only IP, DDM and ECM has config error fault code. And AUD, but that is not snifigant in this matter. Abs unit was shorted and that gave nice difficulty level increase to diagnose why voltages goes down two times every time when key was turned to RUN position. ABS module is now replaced and coded in to the car and it is sorted.
Code in DDM is config error. Propably just because it has keyfobs coded, but no transponders.
Instrument Pack has U1262 SCP bus error. I used oscilloscope with VMM to look it and bus is allright what comes to voltage levels in high and low states. So this tells me that this is consequence fault code what comes when some other device in bus is not working propely(has errors in its own area and yells to bus wrong bits). Car has now propely coded KMH instrument pack and that too shows same U1262 fault code.
ECM has security input P1262 code. That is general pats code. And most likely it is now cause transponder coding does not pass.
The amount of reading about x350 control module coding in tsb and teaching materials is vast. Still ids/sdd gaves me error every time transponders are about to code.
What happends is ids deletes current transponder codes and asks first key to code. I insert it and turn it to RUN position as instruction says. After first key it asks second one and so on. Next it shows result that is Key not programmed. Next screen says that 2/2 keys are programmed. That is clearly wrong
I have measured with an oscilloscope that there is data signal between transponder ring and IP when key is inserted and turnet to RUN position. Verified too with the keyfob tester that has test to this. Replaced the lock, ring and keys with another one and that did now make any difference. Ring is wired straight to the IP. IP reads the key and communicates with the ECM.
We have IDS 118.5, SDD v160, Mongoose, WDS v43, VCM and VMM. Plus other measuring devices ofcourse.
There is a TSB etc where it says something about key not progrmmed because bad connector pin in a footwell connector. I can not find it.
Where to go next ?
Car is 2004 Standard wheelbase 4.2 V8 sold to USA, imported to Finland. Wds finds it as 2003.5 and sdd as 2004.
#3
I've done the coding by the vid block pdf. From that I got the coding order information. ETN mode in IP is new to me. Have to try that. Poor pin connection tsb is read but "skipped" as bus is okay and no bus related codes anywhere. Yep it is known that used parts may be difficult to get work. VID Block can be faulty easily. But how it is can be straighen up ? As civilian I bet that I can not sent vid block dump to Jaguar. And hypotetically if that is possible and they sent original back. How I can upload it to ECM ? Wds Engineering mode ?
Last edited by Vauxi; Yesterday at 10:37 AM.
#5
The following users liked this post:
motorcarman (Yesterday)
#6
Additional information about VID Block modification
As a reference here are VID Block Manager related PDF's I have found. Unfor I have not ever got my hands to install floppy. Nor these tell how VID Block is actually sent to car :-( But ... The document "1-186 VID block.pdf" above, Issue 1 - Resolution 2 says constructed VID Block should be possible to be uploaded to car with WDS.
It is also goot to notice about WDS needs newer DLC (OBD2) Cable A-280 (5 meters) or A-259 (3 meters) when VID Block enabled cars are worked with.
It is also goot to notice about WDS needs newer DLC (OBD2) Cable A-280 (5 meters) or A-259 (3 meters) when VID Block enabled cars are worked with.
Last edited by tlindi; Today at 10:21 AM.
#7
Trending Topics
#9
#10
The guide file is too large to upload here.
Gus has it on his site.
Please read
Gus has it on his site.
Please read
688-JAG: Advanced Electrical Systems and Diagnostics
Pages 3-6 to 3-11 for VID block info.
#11
The following users liked this post:
motorcarman (Today)
Thread
Thread Starter
Forum
Replies
Last Post
Currently Active Users Viewing This Thread: 2 (1 members and 1 guests)