Hi,
I have been trying to resolve a dead ignition problem with my 2007 XKR convertible.
There is no ignition even with the key inserted into the SCU.
SDD offers to take over the ignition and it seems to work the first time, every time.

Rescanning typically results in SDD going through the motions, but the ignition never turns on, dash is dead throughout process.

Today I tried configuring the BCM, ICM as new. No luck, either communication error, unknown error or target writing error.
After the last failure SDD threw the error message, "Failed to control the vehicle ignition".
I'm guessing this might explain the programming failures.

I pulled the 3 relays in the front BCM, popped the covers off and cleaned the contacts, but they were in great condition and all bench tested fine, no real load test though).

Any ideas? Ever had this error message?

 

Hello Gene,

I'm responding on the forum to bump your post and share with others.
See: RFA/KVM replacement | Jaguar Forum and scroll down a few posts.
Poster says that the KVM rarely fails. Likely true.

Also see the last XK 150 section (PATS) in the 688-training manual, which I think that you have.
Principle of operation is on page 12-60. ( JF won't upload the document, says wrong extension, it's .pdf !)

Since SDD will enable the ignition, it appears that the CJB is sending an immobilization deactivation request to the instrument cluster via MS CAN and the instrument cluster deactivates immobilization.
If the encrypted data exchange with the ECM (via HS CAN) is successful, fueling and ignition are enabled. The Aux JB activates the B+ power supply to the FPDM (does it?)
If all of the above functions are enabled at start-up of SDD, look at what SDD bypasses:

Quote from page 12-60:
"When the CJB receives a hardwired ‘start button pressed’ signal, a valid key request message is sent from the CJB to the KVM via the MS CAN bus. • The KVM activates all 3 interior LF antennas to out put LF signals, which activates the Jaguar SmartKey (in the vehicle). • The activated Jaguar SmartKey transmits an RF security code signal to the RF receiver. • The RF receiver transmits the security code signal via dedicated serial data line to the KVM. • The KVM checks and validates the security code and communicates a ‘SmartKey validated’ message to the CJB via MS CAN."

If SDD was recognizing your KVM, I would look at the actual start button on the center console. The pre-facelift XKs start buttons are subject to collecting dirt in the face-up position. (See the XK stickies if you have that problem.)

Since SDD does not recognize the KVM module, try to reprogram it.
This will entail reprogramming key fobs. If memory serves, two key fobs are required.

If no joy, verify power and MS CAN at the module connection.

If still no joy, remove the module for inspection and cleaning of circuit board with contact cleaner and (clean) toothbrush.
Reconnect and try again.

If still no Joy, replace the KVM, reprogram.

Also see Service Bulletin SSM63477: Version of SDD makes a difference!

Keep us posted.

 

Hi Bill,
the XK RFA/KVM must be very reliable. There certainly aren't many references on the web.
I'm sure the issue is with my SDD operating skills, or lack of!

Thanks for the pdf info. The file 688-JAG: Advanced Electrical Systems and Diagnostics is a treasure trove of information.

The 2007 does have the pats system. Unfortunately the module as well as the instrument cluster module, is missing the vin. ?????? or blank

My confidence in my hardware, clone mongoose and VXdiag are at an all time low. I bit the bullet and ordered the DA-dongle.
I'm hopeful a fresh install and the proper hardware make the difference.

Have you noticed a recurring theme in the various rectification processes, involving removal and reinsertion of the fuse just prior to downloading?
I assume it is an attempt to catch the module during its boot cycle. In my previous attempts I did not pay attention to the time frame required, 10 seconds.
That might be the key.
(I also tried a battery disconnect instead of just the modules fuse, no luck that way.)

The other "tip" that keeps coming up is pressing the start button, whether it works or not. Because it is wired directly to the CJB, SDD knows the button has been pressed. SDD notes this in some functions but not others.

Ford owned Jaguar at the time so I am going to see what I can find on their version of IDS.
I read on another forum that the Ford IDS removal program works on SDD. Might be worth a try if I need to changes versions.

Haven't checked the FDPM module to see if it is getting power. Nice easy check to see how far along the start signal is getting!
Scoped the Can Buses, both are clean.

Any idea if you can use SDD on a single module, or pair of modules?
I bought used modules to replace the none communicating ones in my car.
It would be nice to program them outside the vehicle so I don't do more damage.
Wire them up on the bench together, can bus and power, and dtc connection point for SDD?

Service Bulletin SSM63477 was enlightening. I have been using v130 and v138, and have switched back and forth between the two.
I may have to stick with v138, but I know it was v130 that got me into the trouble initially, by using the "campaigns session".

Lots more reading to do!





I

 

The switch itself works reliably, the car consistently acknowledges that it was pressed, when trying to start.
Smart key message comes up. I didn't realize the switch was an issue though. I'll keep that in mind when I'm trouble shooting.

The 2007 XK needs a min of a 25 amp power supply, I've got it hooked up to a 30 amp with a clean output.
Good idea to check the power supply output, my power supply had a noise filter on the switch that was bad. Spewed noise so I cut it out and all is good now.

 

Do you have two key fobs?

Keep us posted.

Bill

 

I do have 2 keys programmed now.
Also have a few new aliexpress ones to try to add at some point.

 

I read that an invalid key would automatically be ejected by the SCU socket.
It works, my original key stays in but the unprogrammed one gets ejected.

Can we assume that this is proof of a valid key?

 

Yes but you should run the SDD "start authorization routine" to verify this and check for any other start fault conditions.

 

I'll run it next.
Thanks for the attachment. There are other issues so this report should help a lot.

 

The start authorization won't run, communication error.

Not all bad news though, got ignition control again.
Running Immobilization after programming the RFA as new and using the rectification process, pulling and replacing the module fuse as software download started worked. I had to try it a few times but it got there in the end.

Once I had ignition control I attempted to program the ICP module as new to resolve its communication errors.
The instructions were to erase the existing keys first, which I did.

Programming the cluster module failed, so the keys never got reprogrammed.
I now have ignition control with the key fob but the SCU (fob slot) now rejects the unprogrammed key.
Reprogramming the keys failed as well.

I'll dig into it tomorrow but I'm happy to have ignition control again!

 

My car started today for the first time in months, thanks to this forum and it's great members.
Bill400 was a great help. His SDD posts and tips helped me begin to understand how IDS/SDD works.
(and how little I knew when I started!)

There are still a some issues to work through but there is light at the end of the tunnel.