When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I am guessing they are the 8 pin/square plug sensors part FW93-14F152-BD but I will get that info out of SDD as you'll need the part number for both sides to stop them conflicting with each other.
sensors I brought are fk72-14f152 it said they are from a xe but my car will not see them once I connect them I still have a orange question mark on them still just as if they wasn’t connected and no faults showing for them as they not even in the fault list
So I'm guessing due to the changes in protocols and software used in the X260 the information isn't sorted in SDD in the same way. The relevant XML files are encrypted when not in use, although some as-built information is stored in the .currentsession file this doesn't include the WERS part numbers.
[QUOTE=toxo;2459569]So I'm guessing due to the changes in protocols and software used in the X260 the information isn't sorted in SDD in the same way. The relevant XML files are encrypted when not in use, although some as-built information is stored in the .currentsession file this doesn't include the WERS part numbers.[/QUO
so what do you think then to get them to be seen by the car
Just a thought - you said there was no wiring behind your rear bumper - does that mean your car doesn't have reversing sensors? It's the same loom on the X250. If so you might need to put a fuse in the rear park fuse slot as the blind spot sensors and the parking sensors share the same positive feed.
You may be able to resolve your BSM communication issues by programming with SDD in Engineering mode: Copy of thread below:
reggraham 20-05-14, 07:06
SoftwareDownload is in C:\Program Files\JLR\IDS\Runtime\ just double click it enter the last six characters of the VIN and press the tick, you'll be presented by an engine selection screen before selecting the engine size/type click on the icon that looks like two people and select 'engineering' this allows full control over the CCF file and is the equivalent to asking Jaguar for the unlock code from the main SDD session screen. Be careful as this does allow anything to be changed updated, as this is the program that gets called by the the main SDD session when you select recommendations and car configuration update etc.
I have played with this program a lot now and use it more than the main SDD screens... End of copy.
SDD Engineering mode for XF 1 SDD Engineering mode for XF 2
Good luck!
Bill
Last edited by Bill400; Nov 5, 2021 at 12:36 AM.
Reason: correction
Runtime is a folder there must be something else after mate
Originally Posted by Bill400
SoftwareDownload is in C:\Program Files\JLR\IDS\Runtime\
Although for what it's worth that has never worked for me - in my experience SoftwareDownload craps out the second it actually tries to talk to the car with a communications error. I know it works for many other people.
I feel like your issue with your sensors must be something basic - if they are powered and are connected to the right canbus (the X260 has 4 busses unlike the X250 which has 2) then at the very least the right hand one should show up and report stuff.
I very much appreciate your sharing your knowledge & experience retrofitting the XF BSM. Post #26 should help in my quest to add the feature to my 2011 XK.
Seeking to understand the difference between the XML edits, I notice that the 8x edit uses 9X part numbers with different extensions. Is that intentional?
Using 9X sensors for the XK, I'll try the pre-facelift version first.
"Engineering Mode" works quite well for many of us and was necessary for the pre-2012 XK reverse/back-up camera retrofit.
Yes, it's intentional. I lifted that directly from as-built configuration files for XFs of the appropriate age. I'd suggest you do the same for the XK as the part numbers in the XML will be slightly different. The XML I have provided above is almost certainly only suitable for X250s.
To get the right XML for your XK, take a look in: C:\ProgramData\JLR\IDS\Sessions\SOFTWARE_MANAGEMEN T\SM_AS_BUILT
Unzip an X150 zip file that's the same year as yours, and search in the extracted XML files for SODL. One of the cars the same era as yours will have had the options fitted and you can copy and paste the SODL and SODR definitions into your own as-built XML as per my earlier instructions.
Many editors have a 'find in files' search function, like Notepad++ or Textpad. Or you can use findstr or grep on the command line to search in all the files at once rather than having to do it by hand.
Although for what it's worth that has never worked for me - in my experience SoftwareDownload craps out the second it actually tries to talk to the car with a communications error. I know it works for many other people.
I feel like your issue with your sensors must be something basic - if they are powered and are connected to the right canbus (the X260 has 4 busses unlike the X250 which has 2) then at the very least the right hand one should show up and report stuff.
have fitted the correct ones now and show up with a green tick for each but shows fault on dash
so need to re configure existing right and left modules I think
toxo,
BSM was not an option for the XK (all years) and as far as I know, not been retro-fitted yet.
Since the XK and XF are kissing cousins, the retro-fit should be do-able.
I'm in over my head at the moment but will over-come through self-study and sharing by generous folks as yourself.
Well my retrofit of the 2016 XF sodl and sodr is done and works perfect for both blind spot and reverse object detection
i will write a post up at some point with the parts required wiring and the asbuilt module numbers
Supermans1,
Congratulations!
What was the hang-up?
Bill
needed the correct part numbers for a start
finding sodl and sodr to add to my asbuilt and then reprogram them
I had to reprogram the left first then the right on the x260 unlike what toxo said about right first
oh and they have to go up the right way otherwise the warning light just keeps comming on on the mirrors for no reason
Hopefully the forum won't time me out while I write all this... obviously you do this at your own risk and it's not my fault if you brick your car.
When you first try to do anything involving the modules on the car, SDD connects to the internet and downloads a zip file full of as-built XML data into the folder C:\ProgramData\JLR\IDS\Sessions\SOFTWARE_MANAGEMEN T\SM_AS_BUILT. Broadly speaking it gets the file for the model of car and the production week that car was in, so for example a zip file for all X250 chassis built in week 50 of 2010. In this zip file is an XML file for every VIN number detailing what modules were in that car when it was built, what the part numbers are and what the CANBUS message IDs are. When you go to work with the modules SDD references this XML file to make sure it downloads the right firmware and configuration. So, you need to edit this file and add the module info in for SODL and SODR.* These are the steps that I took to fix this.
Fire up SDD, open a Diagnostics session with the car. Go into the symptom selection screen and navigate through Electronics -> Driver Aids to one of the side object detection symptoms, e.g. LED illuminated, and press continue. SDD will then list your DTCs and will highlight the DTC stored on SODR about communications failure. Click the icon that looks like a signpost next to it, and it will take you to a table of possible solutions, the only one of which is to read about left module failure/replacement. Click Run or View or whatever on that line item, but then cancel out of it and go back to the list of solutions. You should see an 'Extras' tab has appeared at the top. Click this and you will see 2 options, "Configure existing side object detection module - Left" and "Configure existing side object detection module - Right". Click to run against the item for Right. This will overwrite any stored VIN in the SODR module with your VIN. According to the docs doing this with the usual "Configure new side object detection module" task under Recommendations will not work if there is an existing VIN in the module, i.e. if it came from another car.
Note that if you run the task for the Left module at this point, it will fail saying that it was unable to resolve the module.
Once that is complete open up File Explorer and go to C:\Program Files\JLR\Common\XML\IVSAsbuilt. Edit the file that is called YOUR_VIN_NUMBER_MODULE_RECORDSET.XML. It's got no line breaks in it, so it is not easy to read, but you want to position your cursor between the tags somewhere on the 2nd line of the file where you can see
"</module><module"
So place your cursor between > and < and paste in the following for a pre-facelift X250 using the 9X sensors.
Facelift X250 using 9X sensors:
If you are on an older car with the 8X sensors:
Paste this same text on the last or second-to-last line of the file, again inbetween 2 module tags. This is because there are 2 sets of config in the file - as built and as ordered - with the data all compressed into a few lines it's not obvious to see, but doing this will make sure you have put the module data in both sets of config. You can double-click before and after your edits to open the XML file up in Internet Explorer to view it and make sure it looks right and the structure is good. The order of the modules in the file is not important. Save and close the XML file. Right-click the file, click Properties and go to the Security tab. Edit permissions and put a tick in Deny against Everyone -> Write. If you don't do this, SDD will get the as-built XML file out of the ZIP file when it starts the process of talking to your modules, and it will overwrite your changes.
Repeat the SDD steps above, but run "Configure existing module - Side object detection - Left".
That should be everything done!
* A bit more info. My understanding is that SDD can address the SODR module with its correct part number out of the box, because it talks to that unit and has a match in the parts database for the part number. However the SODL module reports a different part number, which does not exist. This is because the part number is the firmware filename, and the SODL module needs to be updated with different firmware settings to the SODR module. Although they inherit whether they are SODL or SODR on the CANBUS network via the resistor in the mirror, that would not determine which firmware they get as that is based solely on part number. In effect SODL lies about its part number to get the right firmware.
It might be a lot or too much to ask too but I think it would be helpful if you could take a snapshot of where specifically in the XML you placed the added code. I ask because I may follow @Bill400 in an attempt to retrofit these to my XK. (after he's done of course:-)
Hopefully the forum won't time me out while I write all this... obviously you do this at your own risk and it's not my fault if you brick your car.
When you first try to do anything involving the modules on the car, SDD connects to the internet and downloads a zip file full of as-built XML data into the folder C:\ProgramData\JLR\IDS\Sessions\SOFTWARE_MANAGEMEN T\SM_AS_BUILT. Broadly speaking it gets the file for the model of car and the production week that car was in, so for example a zip file for all X250 chassis built in week 50 of 2010. In this zip file is an XML file for every VIN number detailing what modules were in that car when it was built, what the part numbers are and what the CANBUS message IDs are. When you go to work with the modules SDD references this XML file to make sure it downloads the right firmware and configuration. So, you need to edit this file and add the module info in for SODL and SODR.* These are the steps that I took to fix this.
Fire up SDD, open a Diagnostics session with the car. Go into the symptom selection screen and navigate through Electronics -> Driver Aids to one of the side object detection symptoms, e.g. LED illuminated, and press continue. SDD will then list your DTCs and will highlight the DTC stored on SODR about communications failure. Click the icon that looks like a signpost next to it, and it will take you to a table of possible solutions, the only one of which is to read about left module failure/replacement. Click Run or View or whatever on that line item, but then cancel out of it and go back to the list of solutions. You should see an 'Extras' tab has appeared at the top. Click this and you will see 2 options, "Configure existing side object detection module - Left" and "Configure existing side object detection module - Right". Click to run against the item for Right. This will overwrite any stored VIN in the SODR module with your VIN. According to the docs doing this with the usual "Configure new side object detection module" task under Recommendations will not work if there is an existing VIN in the module, i.e. if it came from another car.
Note that if you run the task for the Left module at this point, it will fail saying that it was unable to resolve the module.
Once that is complete open up File Explorer and go to C:\Program Files\JLR\Common\XML\IVSAsbuilt. Edit the file that is called YOUR_VIN_NUMBER_MODULE_RECORDSET.XML. It's got no line breaks in it, so it is not easy to read, but you want to position your cursor between the tags somewhere on the 2nd line of the file where you can see
"</module><module"
So place your cursor between > and < and paste in the following for a pre-facelift X250 using the 9X sensors.
Facelift X250 using 9X sensors:
If you are on an older car with the 8X sensors:
Paste this same text on the last or second-to-last line of the file, again inbetween 2 module tags. This is because there are 2 sets of config in the file - as built and as ordered - with the data all compressed into a few lines it's not obvious to see, but doing this will make sure you have put the module data in both sets of config. You can double-click before and after your edits to open the XML file up in Internet Explorer to view it and make sure it looks right and the structure is good. The order of the modules in the file is not important. Save and close the XML file. Right-click the file, click Properties and go to the Security tab. Edit permissions and put a tick in Deny against Everyone -> Write. If you don't do this, SDD will get the as-built XML file out of the ZIP file when it starts the process of talking to your modules, and it will overwrite your changes.
Repeat the SDD steps above, but run "Configure existing module - Side object detection - Left".
That should be everything done!
* A bit more info. My understanding is that SDD can address the SODR module with its correct part number out of the box, because it talks to that unit and has a match in the parts database for the part number. However the SODL module reports a different part number, which does not exist. This is because the part number is the firmware filename, and the SODL module needs to be updated with different firmware settings to the SODR module. Although they inherit whether they are SODL or SODR on the CANBUS network via the resistor in the mirror, that would not determine which firmware they get as that is based solely on part number. In effect SODL lies about its part number to get the right firmware.
This is great write up … thanks so much. It looks like you were working on a RHD car, right? The SODR module needed to be configured first. I wonder if the order the modules needs to be reversed for LHD cars? Does anyone know?
This is great write up … thanks so much. It looks like you were working on a RHD car, right? The SODR module needed to be configured first. I wonder if the order the modules needs to be reversed for LHD cars? Does anyone know?
