GuydLV

Hi, I have the code C1165 code showing up for 'Wheel speed rear right input - circuit failure'. It apparently triggers the limp home mode. A quick swap with the left rear wheel speed sensor followed by a reset and another read still shows the issue on the right side. I am now trying to troubleshoot the wiring: RR2-1 and RR2-2 connectors from the sensor should arrive at FH103-43 and FH103-32 respectively by the DSC box. Unfortunately a multimeter test gives negative results. So I guess it means something is wrong in between. As the wiring diagram shows that RR2 connectors reach FH103 going through FH1, FH1 has become my next port of call. The same diagram shows FH1 somewhere in the door panel, but I am not too sure where. Am I proceeding the best way to troubleshoot the fault? If so, would anyone know how to reach that FH1 connector? Thanks

Thanks Graham I have just tried adding more RAM. It was initially installed it with 1024 MB to be in line with the specs. But even with 2048 MB I still have the same problem. For the moment, I managed to read the DTC's using testman. Apparently I have faulty front and rear right ABS sensors. I have even been able to use datalogger to read the speed from the four wheels to double check the indications provided by the DTC. So testman works but it is not really ideal using it that way, and I cannot seem to find all the features apparently available in tabman. For example, that part of the application you can use to pair keys. Guy

I performed a fresh install of Windows and of SDD/IDS over a clean installation of XP Pro. No licence issue anymore but still no luck! IDS initialization stops for some reason after the initial IDS launching screen. Very frustrating! I have investigated further and it seems that the launch of IDS is actually linked to the opening of an exe file called "tabman.exe" found in C:\Program Files\JLR\Runtime. This does not work either if I launch it directly from here. However - I think that from the logs - I saw that this "tabman.exe" in turns calls a programme called "testman.exe". This one starts properly in my case and I can select .app files that takes me to similar screens as some of the ones seen on the video. This is not really usable this way, but it gives an idea on what part of the IDS programme does not work. I will keep on searching although it would be of great help if anyone could share a working image of SDD/IDS... 🙄

I managed to get a VIN reading so I think loading the drivers that came with the cable helped rather than using the one that came with SDD. However the launch of IDS is still aborting for some reason and there is no error message at all. Just to show what happens, I have filmed that part and put it here on YouTube. Could it be because of that icon on the top right corner saying "activation required" that IDS does not launch properly?

Hi, yes I removed already the network interface.

Thanks Joe, indeed I installed it on XP Pro. I can go successfully through the various stages you mention. It is just the launch of IDS that seems to halt for an unknown reason. I go as far as 1:23 in the video, then the IDS launch window and the small browser window on the top left corner both close and nothing happens. I will reinstall the driver, as someone suggested I used the Mongoose driver from the DVD I got and not from the SDD 1.30 install pack. But if you have any other ideas, they are more than welcome.

Mangoose/Mongoose cable now received, SDD v1.30 installed on XP, Mongoose cable detected but this is as far as I can get. As I am trying to connect to a 2002 S-Type, the SDD software reports that no symptoms map are available and I am invited to launch the legacy IDS tools. Which is fine so I click on the link. An IDS window appears along with another web browser pop up but then both disappear and nothing happens. I have tried to look for the application file of the legacy IDS in the installation folder but I could not find it. I have seen reports of similar problems on the web but no solution mentioned. Has anyone experienced anything similar? can this be solved or worked around easily? Thanks

Hi Steve, thanks for the comprehensive answer. The car was indeed left without being used by the previous owner. And I have good reasons to think he left it outdoor exposed to the elements and animals. I am following the strategy you recommend. I am just waiting for my Mangoose interface to be delivered so that I can confirm codes raised and then erase them to start from scratch. I have also started to check the various connectors on the bus between the various modules, so far nothing to report but I still have quite a few to check. The only possible sign of pest is in the insulation that is found below the bonnet, below that plastic cover at the base of the windshield. It was crumbling but not sure if it was for mice or just because it's old. Good point about the speed sensors, I will check the rear ones as well... as soon as the snow and the wind will be gone!

Hi Martin, thank you. I am glad to know the S-Type can prove to be a reliable car. I had to sell my Ducati before moving to the UK, but these are great bikes. Lucky you if you happen to own more than one! Guy

Reviewing all the codes I think I can rule out the ones related to battery fault and also the ones reporting faults which I am not seeing as the ones related to headlamps or lighting. Ruling out: B1246, B1317, B1318, B1470, B1681, U1752. This leaves me with: CAN related DTC's: U1752, U1900, U2521 A/CCM DTC: B1262 (which I can live with) Unkown DTC's: B1352, U1751, U2195, U2197, U2200 The CAN's ones worry me as I don't know how to address them. But I think that what I will is to focus on solving the real problems, hoping that the warnings will go away after clearing the codes. I have an issue with the braking, as the pedal has to be pushed very hard in order to brake as if the car would never stop. The other one is with the performance as if the car had no power at all although the engine starts smoothly and on all the cylinders (apparently). I'll investigate this and share my findings.

Hi Joe, thanks for retrieving these descriptions. I will look at them in detail. Yes, I did charge the battery and its voltage looks ok. But I guess the code then need to be cleared using a software or will they clear on their own if the fault is gone? By the way, I know I have a genuine braking issue but that's all I was expecting in terms of warning.

Hi, a series of warnings started to appear on my dashboard: the engine light and the ABS are on, and there are messages that say there is an 'ABS fault', 'DSC is not available' and vehicle has 'restricted performance'. I entered the self test menu for the lack of a proper JLR diagnostic tool and retrieved a total of 15 DTC's. I then tried to decode them following the guidelines below, but even then I am only able to match 9 of them with DTC's listed in the workshop manual. I have attached the DTC's reported by my S-Type. Guideline for DTC decoding: 1XXX relates to Enhanced (manufacturer specific) codes P1 9XXX relates to Body Enhanced (manufacturer specific) codes B1 AXXX relates to Body Enhanced (manufacturer specific) codes B2 DXXX relates to Undefined (manufacturer specific) codes U1 EXXX relates to Undefined (manufacturer specific) codes U2 Obviously I would like to find out the meanings of these codes separately but I am hoping they could share a common cause as the car was left parked for 8 months without being driven at all and then suddenly reports all these issues at once. My current leads: Someone told me it was the DSC module that needed to be repaired by that a service like this one. The brake booster could be ko. I did do the usual tests and although I am not fully convinced by its behaviour , I am not sure wheter a faulty brake booster would trigger that many alarms. Speed sensor ko: I have checked the driver side one at the front, and it looked ok visually all clean. Alarms need reset: would it be possible that some of the DTCs like the ones related to the battery just need clearing? this would allow to tell apart the relevant DTCs. Would you have any ideas on the decoding of these codes and why I could not find reference to some of those? or any similar experience?

Glad you found another one!

Hi, I don't know about the compatbility with a slightly different part number but isn't this one the same as yours: https://www.ebay.co.uk/i/202233595663?rt=nc ?

Hi Peter, thank you. I still need to cover more miles with mine but indeed S-Type's seem to be great cars. The manufacturers always look at the past at some point and revive some old series, so we may well see a re-edition or a tribute to the S-Type of some sort... although the new market and the trend is really on the side of the SUV's and crossovers.

I would not go for the chrome naturally but it combines nicely with this shade of blue. I realized that I always have as much chrome on my S-Type, except for the headlights... Here is what I was referring to on mine, there is a relatively big gap between the chrome and the window which is filled with dust and moss. The car had been parked for a few months before I bought it, so I guess it did not help. But still, it seems weird to me to see such a huge gap which I assume is not present without the chrome additions.

Hi, I also recently found out about the bolt retaining the battery located below the car. Just about the best place to get rusty and not the best design when there are more user friendly solutions. Have some of you considered removing the bolt, filling in the hole and holding the battery from within the boot?

Thanks Ron! It looks like your S-Type also has the chrome around the windows as mine. But on mine it seems to have been fitted in such a way it just collects dust, water and moss. It makes me wonder if this is a standard part or if that was fitted as an accessory later on. Do you have the same problem on yours?

Hi Everyone Thanks for letting me join the forum. Coming from the other side of the channel, I thought I could never truly live the British experience without having: played golf once (check), enjoyed an afternoon tea (check) and owned a RHD Jaguar (check, but still to be enjoyed). So I have recently bought a 2002 2.5 L V6 S-Type, the X202 I believe. It looks and works nicely although it came with a lot of questions. I also happen to work as a volunteer at the British Motor Museum in Gaydon where we also look after the Jaguar heritage collection. So a true Jaguar enthusiast! That being said I have owned for 10 years a limited edition of the Peugeot 406 coupé which never disappointed me. Looking forward to exchanging with you on the forum. Guy