IDS_SDD Deep Dive - IDS\XML\IVS-AsBuilt
Hello SDD fans, fellow computers nerds and wanna-bees,
I'd like to share some SDD deep dive experience. I find it interesting and hope that some of you do too!
SDD scans your vehicle when it is "connected", and stores a copy of the "as-built" and "as-ordered" module and software inventory on your laptop.
The location is ProgramFiles\JLR\IDS\XML\IVS-asbuilt (or just IVS in newer versions). The file name is (your_VIN).xml.
Since it is an .xml file, it can be opened and examined using windows explorer. Just exit without saving unless you are intending to make a change.
The file lists module anconyms, CAN node IDs and software for each module in the target vehicle.
Acronyms with module names for a typical 2011 XK follow, XKRs are similar, as are other Jaguars of similar vintage.
AAM = Audio Amplifier Module node_id>0x784 part_number type="WERS">7W8M-18C808-AB
ABS = Anti-lock Brake System node_id>0x760 part_number type="WERS">8W83-2C405-CC
ACM = Audio Connectivity Modulenode_id>0x784 part_number type="WERS">8W83-18C815-AC
APIM = Accessory Protocol Interface Mod node_id>0x784 part_number type="WERS">8X23-18C941-BA
BCM = Body Control Module node_id>0x726 part_number type="WERS">8W83-14B476-AD
BCMB = Body Cont Mod “B” node_id> Mod0x7B7 part_number type="WERS">8W83-14D628-AD
DACMC = Digital Audio Control Module C (HD Radio) node_id>0x784 part_number type="WERS">7W93-19C034-AE
DDM = Driver Door Module node_id>0x740 part_number type="WERS">BW83-14B531-AA
DSM = Driver Seat Module node_id>0x744 part_number type="WERS">8W83-14C708-BC
FACP = Integrated Control Panel node_id>0x7A0 part_number type="WERS">9W83-18C858-BA
FCDIM = Front Control Display Interface Module (Touch Screen Display) node_id>0x784 part_number type="WERS">9W83-10E889-AB
GSM = Gear Selection Module node_id>0x732 part_number type="WERS">8W83-7E453-BE
HCM = Headlamp Control Module node_id>0x734 part_number type="WERS">8W83-13K031-AD
ICM = Infotainment Control Module node_id>0x784 part_number type="WERS">9W83-19C059-BA
IPC = Instrument Panel Cluster node_id>0x720 part_number type="WERS">9W83-10849-AE
MRCM/FTCM = Movable Roof Control Module node_id>0x787 part_number type="WERS">8W83-13B524-AB
NCM = Navigation Control Module node_id>0x784 part_number type="WERS">AW83-10E887-AB
PAM = Parking Aid Module node_id>0x736 part_number type="WERS">9W83-15K866-BB
PBM = Parking Brake Module node_id>0x756 part_number type="WERS">8W83-2C496-AC
PCM = Powertrain Control Module node_id>0x7E0 part_number type="WERS">8W83-12A650-YAF
PDM = Passenger Door Module node_id>0x741 part_number type="WERS">BW83-14B533-AA
PSM = Passenger Seat Module node_id>0x7A3 part_number type="WERS">8W83-14F316-BC
RCM = Restraints Control Module node_id>0x737 part_number type="WERS">9W83-14B321-BG
RFA = Remote Function Actuator (KVM) node_id>0x731 part_number type="WERS">AW83-19G481-AA
SARM/SRM = Sat Audio Radio Mod node_id>0x784 part_number type="WERS">8W83-18C963-AD
SCME = Driver Climate Seat Module E node_id>0x776 part_number type="WERS">9W83-14F268-AB
SUMB = Adaptive Damping Cont Mod node_id>0x786 part_number type="WERS">8W83-18B008-AG
SODL = Side Object Detection Left node_id>0x7C4 part_number type="WERS">9X23-14D455-CD
SODR = Side Object Detection Right node_id>0x7C6 part_number type="WERS">9X23-14C689-CD
TCM = Transmission Control Module node_id>0x7E1 part_number type="WERS">9W83-7Z369-FA
TEL = Bluetooth Telephone Module node_id>0x784 part_number type="WERS">9W83-10D893-EC
TPM = Tire Pressure Monitoring Module node_id>0x751 part_number type="WERS">9W83-1560-AB
Z-RCCM = Restraints Control Module node_id>0x733 part_number type="WERS">9W83-18D493-AD
Correction: SODL/R were added to the OEM XK file. Typical for XF/XJ, it is not normally found in the XK.
If you would like to know more or share what you know about the inner-workings of IDS-SDD, lets hear from you.
Bill
I'd like to share some SDD deep dive experience. I find it interesting and hope that some of you do too!
SDD scans your vehicle when it is "connected", and stores a copy of the "as-built" and "as-ordered" module and software inventory on your laptop.
The location is ProgramFiles\JLR\IDS\XML\IVS-asbuilt (or just IVS in newer versions). The file name is (your_VIN).xml.
Since it is an .xml file, it can be opened and examined using windows explorer. Just exit without saving unless you are intending to make a change.
The file lists module anconyms, CAN node IDs and software for each module in the target vehicle.
Acronyms with module names for a typical 2011 XK follow, XKRs are similar, as are other Jaguars of similar vintage.
AAM = Audio Amplifier Module node_id>0x784 part_number type="WERS">7W8M-18C808-AB
ABS = Anti-lock Brake System node_id>0x760 part_number type="WERS">8W83-2C405-CC
ACM = Audio Connectivity Modulenode_id>0x784 part_number type="WERS">8W83-18C815-AC
APIM = Accessory Protocol Interface Mod node_id>0x784 part_number type="WERS">8X23-18C941-BA
BCM = Body Control Module node_id>0x726 part_number type="WERS">8W83-14B476-AD
BCMB = Body Cont Mod “B” node_id> Mod0x7B7 part_number type="WERS">8W83-14D628-AD
DACMC = Digital Audio Control Module C (HD Radio) node_id>0x784 part_number type="WERS">7W93-19C034-AE
DDM = Driver Door Module node_id>0x740 part_number type="WERS">BW83-14B531-AA
DSM = Driver Seat Module node_id>0x744 part_number type="WERS">8W83-14C708-BC
FACP = Integrated Control Panel node_id>0x7A0 part_number type="WERS">9W83-18C858-BA
FCDIM = Front Control Display Interface Module (Touch Screen Display) node_id>0x784 part_number type="WERS">9W83-10E889-AB
GSM = Gear Selection Module node_id>0x732 part_number type="WERS">8W83-7E453-BE
HCM = Headlamp Control Module node_id>0x734 part_number type="WERS">8W83-13K031-AD
ICM = Infotainment Control Module node_id>0x784 part_number type="WERS">9W83-19C059-BA
IPC = Instrument Panel Cluster node_id>0x720 part_number type="WERS">9W83-10849-AE
MRCM/FTCM = Movable Roof Control Module node_id>0x787 part_number type="WERS">8W83-13B524-AB
NCM = Navigation Control Module node_id>0x784 part_number type="WERS">AW83-10E887-AB
PAM = Parking Aid Module node_id>0x736 part_number type="WERS">9W83-15K866-BB
PBM = Parking Brake Module node_id>0x756 part_number type="WERS">8W83-2C496-AC
PCM = Powertrain Control Module node_id>0x7E0 part_number type="WERS">8W83-12A650-YAF
PDM = Passenger Door Module node_id>0x741 part_number type="WERS">BW83-14B533-AA
PSM = Passenger Seat Module node_id>0x7A3 part_number type="WERS">8W83-14F316-BC
RCM = Restraints Control Module node_id>0x737 part_number type="WERS">9W83-14B321-BG
RFA = Remote Function Actuator (KVM) node_id>0x731 part_number type="WERS">AW83-19G481-AA
SARM/SRM = Sat Audio Radio Mod node_id>0x784 part_number type="WERS">8W83-18C963-AD
SCME = Driver Climate Seat Module E node_id>0x776 part_number type="WERS">9W83-14F268-AB
SUMB = Adaptive Damping Cont Mod node_id>0x786 part_number type="WERS">8W83-18B008-AG
SODL = Side Object Detection Left node_id>0x7C4 part_number type="WERS">9X23-14D455-CD
SODR = Side Object Detection Right node_id>0x7C6 part_number type="WERS">9X23-14C689-CD
TCM = Transmission Control Module node_id>0x7E1 part_number type="WERS">9W83-7Z369-FA
TEL = Bluetooth Telephone Module node_id>0x784 part_number type="WERS">9W83-10D893-EC
TPM = Tire Pressure Monitoring Module node_id>0x751 part_number type="WERS">9W83-1560-AB
Z-RCCM = Restraints Control Module node_id>0x733 part_number type="WERS">9W83-18D493-AD
Correction: SODL/R were added to the OEM XK file. Typical for XF/XJ, it is not normally found in the XK.
If you would like to know more or share what you know about the inner-workings of IDS-SDD, lets hear from you.
Bill
So can you change the SDD and add things like headlamp steering? Mine accidently booted up with that enabled last year and I about wrecked turning onto my street because I was watching the lamp swiveling instead of the curb.
If you run the network integrity test (begin a diagnosis session and enter electrical/network/bus fault [iirc]) found in recommendations "module information - Network integrity test" you can obtain a lot of information about each module including software and hardware WERS #'s, module serial #'s and whether a module stores the VIN.
Last edited by hafren; Nov 8, 2022 at 05:18 PM.
Lindsay,
Thanks for bringing up Integrity Test and presenting in Excel.
That reminds me that I what to find detailed info on the WERS format.
I think combining the information will make and interesting read.
Thanks for bringing up Integrity Test and presenting in Excel.
That reminds me that I what to find detailed info on the WERS format.
I think combining the information will make and interesting read.
Hi Bill, wondering if I could pick your brain.
I'm trying to retrofit adaptive cruise control ACC to my car which from factory did not come with this.
I have sourced the module but it's from a newer year car. SDD throws an error saying configuration not compatible when I try to configure it as a new module in the CCM (due to newer firmware being on the module?)
Now I have read (on a Russian forum translated to English) that if the As built xml file is modified then SDD will recognise the module and allows the correct software to be downloaded and hence programmed.
My question is do you know where this As built xml file is located in the JRL folder?
Also will it matter where in the xml file I make the additional on the CCM/ACC 'new' module? So putting it at the end would be fine will is the list of module in a chronological order?
Much obliged.
I'm trying to retrofit adaptive cruise control ACC to my car which from factory did not come with this.
I have sourced the module but it's from a newer year car. SDD throws an error saying configuration not compatible when I try to configure it as a new module in the CCM (due to newer firmware being on the module?)
Now I have read (on a Russian forum translated to English) that if the As built xml file is modified then SDD will recognise the module and allows the correct software to be downloaded and hence programmed.
My question is do you know where this As built xml file is located in the JRL folder?
Also will it matter where in the xml file I make the additional on the CCM/ACC 'new' module? So putting it at the end would be fine will is the list of module in a chronological order?
Much obliged.
Trending Topics
Hi Bill,
Really good stuff!!
Question -
I don’t see CCM (Climate Control Module) listed ( not common?)
Can you talk about this a bit more? Is the VIN programmed on it? I was told the VIN is etched on a chip. True or fairy tale?
Thank you
Really good stuff!!
Question -
I don’t see CCM (Climate Control Module) listed ( not common?)
Can you talk about this a bit more? Is the VIN programmed on it? I was told the VIN is etched on a chip. True or fairy tale?
Thank you
Got a link?
It talks about Range Rover but same modules can be used in Jags as well. Just different software needed to be flashed.
https://www.drive2.ru/l/561310307780136026/
Hi Bill, wondering if I could pick your brain.
I'm trying to retrofit adaptive cruise control ACC to my car which from factory did not come with this.
I have sourced the module but it's from a newer year car. SDD throws an error saying configuration not compatible when I try to configure it as a new module in the CCM (due to newer firmware being on the module?)
Now I have read (on a Russian forum translated to English) that if the As built xml file is modified then SDD will recognise the module and allows the correct software to be downloaded and hence programmed.
My question is do you know where this As built xml file is located in the JRL folder?
Also will it matter where in the xml file I make the additional on the CCM/ACC 'new' module? So putting it at the end would be fine will is the list of module in a chronological order?
Much obliged.
I'm trying to retrofit adaptive cruise control ACC to my car which from factory did not come with this.
I have sourced the module but it's from a newer year car. SDD throws an error saying configuration not compatible when I try to configure it as a new module in the CCM (due to newer firmware being on the module?)
Now I have read (on a Russian forum translated to English) that if the As built xml file is modified then SDD will recognise the module and allows the correct software to be downloaded and hence programmed.
My question is do you know where this As built xml file is located in the JRL folder?
Also will it matter where in the xml file I make the additional on the CCM/ACC 'new' module? So putting it at the end would be fine will is the list of module in a chronological order?
Much obliged.
Hooray! Someone else is looking into manufacturer level OEM module integration!
Unfortunately for me, I've been distracted for a while and must go from memory.
Matters worse, possible pneumonia, so thinking is requiring extra effort...
but here goes:
It sounds like our Russian friends are editing the vehicle data file that is downloaded from the vehicle to your laptop when first connected.
That file is hidden. I explain access to the hidden file for Windows Xp and Win7 in one of the IDS/SDD Deep Dive posted on this forum.
TOXO also explains in his post about adding BSM to the XF. (I apologize for this indirect answer, more when I get my brain back.)
The Russian hack that works for the LR may be deceptively simple: It may be model specific. And it may not work for Jaguar X150 without additional effort.
When SDD "resolves" the software for a given part number, it is working with a sub-routine that is specific to your model.
The allowable part numbers are listed. If your part number (including allowable variants) is not on the list, the software will not resolve.
That is part of the genius, to prevent dealer techs (and us) from making "mistakes".
The SDD file is an .exml file and may be edited if you have the software from our Russian friend "Smartgauges".
It is available on GitHub.
I'm very interested in what you are doing and have some of the parts for that upgrade.
I need a bit of time to think but more than happy to collaborate.
PS: I'm still working on a BSM/CTA solution for those interested.
Please keep us posted.
Last edited by Bill400; May 13, 2026 at 03:04 PM.
@Bill400 Thank you for your prompt response! Hope you start feeling well very soon!
So we (my brother in law and myself) are trying to do this retrofit project on 2 cars a 2016 XJ and a Range Rover Sport 2014.
We have sourced a FPLA module which came off a 2016 range rover. For some reason range rover modules seem more readily available and cheaper than jag modules.
The plan is to do the retrofit on the range rover first (as we already got all the parts needed for this project) before investing in the parts for the jag (pending successfully doing the range rover)
Unfortunately there isn't much info regarding xml edits etc on range rover forums. They tend to use a GAP tool rather than SDD for this retrofit.
Anyway after doing some (long) research, I came across this Russian forum (I have linked it above). The challenge is the translation to English in order to be able to understand it. Chatgpt seemed to provide a more coherent translation. My understanding from it is that the FPLA module is backwards compatible but for it work on older cars the xml needs to be altered to a DPLA module. Correct me if I'm wrong/you understand of it is different.
There seems to be a chap who is in the same position and asked the question further down the same thread. Unfortunately you need a Russian phone number to make an account on that forum otherwise I would have tried to got more info from the writer of the post.
The points I need help with are
1. Looking at the JRL folder I can see a xml and an exml files that have as built information in them. I am unsure which one needs to be altered.
2. When doing the altering do you need to have opened SDD and started a session? Complete the alterations then start new season in SDD or can you make the alterations in the xml/exml file prior to firing SDD up?
3. The Russian forum mentions DPLA needs to be in the as built file for the FPLA module to work on a 2014 model. Will I need to find a 2014 car that has native ACC and extract the information from it's as built and copy that into my car's as built file?
Again many thanks for the help.
So we (my brother in law and myself) are trying to do this retrofit project on 2 cars a 2016 XJ and a Range Rover Sport 2014.
We have sourced a FPLA module which came off a 2016 range rover. For some reason range rover modules seem more readily available and cheaper than jag modules.
The plan is to do the retrofit on the range rover first (as we already got all the parts needed for this project) before investing in the parts for the jag (pending successfully doing the range rover)
Unfortunately there isn't much info regarding xml edits etc on range rover forums. They tend to use a GAP tool rather than SDD for this retrofit.
Anyway after doing some (long) research, I came across this Russian forum (I have linked it above). The challenge is the translation to English in order to be able to understand it. Chatgpt seemed to provide a more coherent translation. My understanding from it is that the FPLA module is backwards compatible but for it work on older cars the xml needs to be altered to a DPLA module. Correct me if I'm wrong/you understand of it is different.
There seems to be a chap who is in the same position and asked the question further down the same thread. Unfortunately you need a Russian phone number to make an account on that forum otherwise I would have tried to got more info from the writer of the post.
The points I need help with are
1. Looking at the JRL folder I can see a xml and an exml files that have as built information in them. I am unsure which one needs to be altered.
2. When doing the altering do you need to have opened SDD and started a session? Complete the alterations then start new season in SDD or can you make the alterations in the xml/exml file prior to firing SDD up?
3. The Russian forum mentions DPLA needs to be in the as built file for the FPLA module to work on a 2014 model. Will I need to find a 2014 car that has native ACC and extract the information from it's as built and copy that into my car's as built file?
Again many thanks for the help.
Hi Bill, wondering if I could pick your brain.
I'm trying to retrofit adaptive cruise control ACC to my car which from factory did not come with this. ....
.... My question is do you know where this As built xml file is located in the JRL folder?
Also will it matter where in the xml file I make the additional on the CCM/ACC 'new' module? So putting it at the end would be fine will is the list of module in a chronological order?
Much obliged.
I'm trying to retrofit adaptive cruise control ACC to my car which from factory did not come with this. ....
.... My question is do you know where this As built xml file is located in the JRL folder?
Also will it matter where in the xml file I make the additional on the CCM/ACC 'new' module? So putting it at the end would be fine will is the list of module in a chronological order?
Much obliged.
You are looking to edit the .xml file in the hidden folder to match the edited file that is not hidden. @toxo explains how SDD will change the file if not done properly.
See: Side Object Detection / Blind Spot Monitoring Retrofit - Page 3 - Jaguar Forums - Jaguar Enthusiasts Forum Post #26 and #47.
Save yourself grief by using an .xml editor. TOXO also explains that the order does not matter.
If the specific/correct part is available for the vehicle that you are attempting to modify, save yourself additional grief and use that part.
What version of SDD (or alternative) are you using?
Your retrofit deserves its own post. Please post a link here.
All SDD files are encrypted and I don't know of anyone nor any place that has access to any decryption software. If YOU know of a way to obtain necessary software, I know of a LOT of people who would love to get their hands on the stuff. Like me.
Thread
Thread Starter
Forum
Replies
Last Post
hafren
XJ XJ6 / XJ8 / XJR ( X350 & X358 )
5
Aug 18, 2015 10:46 AM
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)








