Hi, I replaced my 2002 XK8 with a 2007 XKR convertible.
Trying to fix a tcm and body control module while learning to use IDS was not much fun.

I decided to familiarize myself with the SDD software before I needed to use it.

The convertible roof was working fine before I used SDD but now will not communicate with the FTCM.
yellow question mark on scan

When trying to reconfigure it I get this error message

Error - CSA_Comms Operation 'SetDiagnosticSession'
Argument : strModule FTCM
Argument : m_nChannelType 1
Argument : nSessionID Default Session
Argument : nDriverLevel 1
DefaultSessionLocked returned UNKNOWN 2CF


I've been working on this/reading forums for 4 days, learning lots but not this!

Any idea how to enable communication again?

 

Have you tried doing a hard reset by disconnecting a battery cable and then try SDD again?

 

Yes,
hard reset, cable disconnected and shorted for a minute.
Tried a soft reset from SDD as well, no luck with either.

Using a 40 amp dc power supply set to 13.6 volts, good battery (12.7 volts after resting overnight)

using V130 SDD and clone mongoose

 

Gbellefo,
Does the folding top work and the problem is SDD reporting or is there a problem folding the top?

If the top folds normally and SDD communications is the problem, try re-running the "license". If that fails, reloading the SDD software may be necessary.

If the folding top function does not work, suspect a water incursion, if parked outside during inclimate weather.

keep us posted.

 

Hi Bill,
the roof worked fine before I touched SDD, but does not work now.
I had to close it manually to get to the battery to do a hard reset.

The SDD software appears to be working on all other modules, just not the roof module.
(It did recognize the roof module when I started SDD, I remember seeing it. At some point it lost communication and now I can't read the hardware number on it to reconfigure it in SDD.)

Car has been stored inside. I pulled the rear seats, no signs of water getting in.

I'm sure it is my own incompetence with SDD that caused the problem.
Nothing was physically touched and the car did not move, just me and SDD!

 

To the best of your recollection, what did you do when connected to SDD?

 

I was running the campaign section.
Maybe I updated something incorrectly.

The doors stopped responding but i just had to reconfigure existing and they both worked again.

No luck with the roof module though.
I was able to see it in SDD, but at some point it would no longer see the module to pull the hardware number.

 

Gene,
Please confirm that you did not physically alter, remove/replace any modules between being able to see the FTCM and not being able to see it on SDD.
Since you were running the campaign and updating software, did you intentionally update the FTCM?
Did you alter or open the CCF, Central Configuration File?
Does your SDD V130 have complete VDF, Vehicle Data Files?

When a module does not report on SDD you may suspect:
1. No power to the module
2. Defective module
3. Broken CAN branch wire between the loop and the module
4. CCF corrupt/disabled module(s)
5. Module software corrupt
6. SDD software unstable
7. Vehicle Communications Interface, VCI unstable

Based on what I think that you have said/done, items 1, 5, 6 & 7 are a good bet.

Start with power to the module: Confirm the fuse, power at fuse and at the module.
(If you don't have a wiring diagram, there are lots of options.).

Next, SDD has a system reset that may be invoked separate from module reprogramming.
Try that.
Module programming is designed to be foolproof. The active program is moved to memory; a new program is loaded and checked and only then is the previous program cleared.
This sequence requires turning the ignition on and off several times. If the process is not completed properly, the original program is reloaded by default.
It is possible/very likely that the "defective" module is stuck mid-program rather than "bricked".
A reset and ignition cycle may return the module to its previous program.

How did you get here?
Items #6 and #7 are reasonable possibilities.
Unstable SDD V130 is a good bet.
PM if you would like to pursue that avenue.

Bill

 

I am working on it again today.

(Please confirm that you did not physically alter, remove/replace any modules between being able to see the FTCM and not being able to see it on SDD.)
No, nothing was physically touched during the entire process.

(Since you were running the campaign and updating software, did you intentionally update the FTCM?)
I did not see one for the FTCM, but it may have been included in one of the others. I definitely saw a reference to it during the process.

(Did you alter or open the CCF, Central Configuration File?)
I did, after the problem occurred. I have loaded the as built configuration, loaded and all back ups green.

(Does your SDD V130 have complete VDF, Vehicle Data Files?)
They do appear to be there, I checked using file explorer and there are a lot.
I am using the British Diagnostics kit, V130. It was the only one I found that IDS worked properly on.


(When a module does not report on SDD you may suspect
(1. No power to the module) power confirmed for power relays and communications, fuses 30, 32, 8 in the rear seat junction box
(2. Defective module)
(3. Broken CAN branch wire between the loop and the module) wires are good, 62.5 ohms on circuit, tested at module
(4. CCF corrupt/disabled module(s))
(5. Module software corrupt)
(6. SDD software unstable)
(7. Vehicle Communications Interface, VCI unstable)

(Based on what I think that you have said/done, items 1, 5, 6 & 7 are a good bet.)

Start with power to the module: Confirm the fuse, power at fuse and at the module.
(If you don't have a wiring diagram, there are lots of options.).

(Next, SDD has a system reset that may be invoked separate from module reprogramming.
Try that.
Module programming is designed to be foolproof. The active program is moved to memory; a new program is loaded and checked and only then is the previous program cleared.
This sequence requires turning the ignition on and off several times. If the process is not completed properly, the original program is reloaded by default.
It is possible/very likely that the "defective" module is stuck mid-program rather than "bricked".
A reset and ignition cycle may return the module to its previous program.)

(How did you get here?
Items #6 and #7 are reasonable possibilities.
Unstable SDD V130 is a good bet.
PM if you would like to pursue that avenue.)

I have tries the SDD vehicle reset, hard resets, ignition cycles, no luck so far though.

A few months ago I installed the remote roof kit from Jagwrangler.
I never paid much attention when I installed it, but the can bus wires are cut during installation, fed to their control unit.
I thought this was the issue but removing the kit and wiring the can bus back the way it was makes no difference.
Perhaps it played a part in not being detected at some point?

 

If it all worked before, can you re-open the older session prior to doing a campaigns? Campaigns aren't always applicable to your vehicle. If you can open the session prior to that, it should reset.

 

Tried that this morning but no luck.
Is there a way to force it?

 

do you have power at the module? Fuse OK? Is there a TSB that indicated your model needed an update?

 

Yes, fuses are good and there is power on the module and the feeds for the motors.
No, no tsb, just me doing something foolish, running the campaign programs in case the dealers never did.

It's a painful lesson!

 

Yes not all campaigns apply to our car, model. In fact most don't. Enough said.


If it were me and I was unable to restore/return to a previous session, I would first I would check error codes. I'm betting there are some and those should give you next steps. Run a network check and see if it sees the part. Failing that, I would check the CCF and see if it shows the module fitted. If it is, and there are no DTC codes thrown, I'd try following the "replacement of an existing module procedure." But I assume that won't work because the car doesn't recognize the module. Then I would try installing a new module procedure, but I assume all verts come with the module so that won't be an option to select from. When you follow either procedure, the module stays connected until SDD tells you to replace the module. Following the order is important.

 

There are error codes now, that I didn't have when I started.

CCF show it as an optional fitment, not detected

Tried reconfiguring as existing, and as a replacement, error on both.

 

what are the codes? and what steps is it telling you to follow for each code?

 

There are a few dtc codes, SDD highly recommends, pin point tests for can bus, power, grounds, presumably because it cant see it.
The measurements are all good. no issues with the can bus or power.

I'm going to try a different version of SDD and hardware, see if I have any better luck connecting.

 

Don't know if this will help but Jaguar has a SDD best practices document that gives you another method to get a sleepy/lazy module back up and running.
It might not work but do take a look.

Here is the interesting part;




It's a way to "fool" SDD into seeing and/or programming a module.
.
.
.

 

Thanks,
I've been doing a lot of reading the last few days.

I did try this a few times, no luck though.
just gives a FAILED error

 

Have you replaced the FTCM yet?