Did you get anywhere with this? I've got someone who's contacted me directly with the same issue but it didn't happen on my car so I'm not sure how to figure it out. I was thinking that because the SODR module is responding properly and has been flashed/updated with the vehicle VIN etc, to swap the modules over so the working one is then SODL and reflash SODR, learn the VIN etc?

Also, where did you get the mirrors from?

 

not yet, to be honest, not had the time,

still have an orange fault light in the RH mirror glass indicating the fault

also still have the comms issue to the left module

this could be a comms issue, or could be a power or grounding issue of the module, as it its' dead ' it will have a comms issue.....

so still investigating, and have tried several modules , genuine pairs from donor cars, and refreshing, still no joy till i have another go

if you find the issue i would love to know, i feel its a simple issue to be honest

BB

 

Got it. You need to edit your as built XML file and add the SODL/SODR info in there. SDD can address the right hand module as that uses a real part number but the left hand module has a dodgy one so that it gets the left hand data written to it. SDD won't be able to resolve that part number properly unless it's in your as built file.

I can write that bit up tomorrow if you've got no idea what I'm talking about. But it does mean you don't need to take your rear bumper off again!

 

fantastic !!!!

that would be a great help if you could,
i am confident in CCF stuff, but some of the other XML alterations i have not yet atempted

so a step by step would be invaluable for me and others

really appreciate the help

BB

 

thinking about it , this might be what's holding off my AHB modification , all the hardware is there, and can be seen but the system doesn't seem to work though i can select on the screen

BB

 

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.

 

many thanks

will give it a go in the next few days while off work

BB

 

I'll see if I can find the right XML to add to your as-built file if you send me the VIN of the car you're working on, that should make the process easier for you. Unless it's a 2010 X250!

 

have messaged it , cheers

BB

 

Post is updated with the 3 different options I can find for different age X250s, that should do you.

 

Would these settings work with the x260
I hate asking as I spend a lot of time looking and reading instead of being drip fed but cannot find anywhere on the net that has done it to the x260 this thread is by miles the closest I have found and don’t wanna brick the modules any pointer would be great

 

I know very little of the X260, but I do know that JLR moved away from having many customisations of the loom towards more standardisation. So it's more likely the wiring will all be there, even in the mirrors. You also probably won't need to modify your as-built file - the X260 XML files I have here all have the SODL and SODR definitions in them. I guess you won't know for sure unless you try it though!

Pretty sure you aren't going to brick anything over and above the risk you run of bricking anything with SDD

 

there isn’t any wiring under my bumper not worried as can sort that

but I have read my as built file that I got and no mention of the sodl or sodr in there anywhere mate
under as built or as ordered for my vin at least

 

Just at a loss as to what part number I should add for the x260 to the as built file

 

I can get that for you tomorrow - if you have SDD just unzip the zip file for all the X260 XML files built at the same time as yours and search for SODL in the files and copy/paste the section into yours.

 

that would be so nice of you thank you so much

 

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.

 

Yes mate 8 pin ones mate thank you so much

 

cannot find any zip file with all the x260 files in it looked everywhere

 

Where in sdd would this zip be