Your help is requested: I'm working to retrofit XF X250 Blind Spot Monitoring to a 2011 (2007-15) XK/R.

I would appreciate a copy of the XF IVSAsbuilt file for an XF X250 with BSM.
File name should be <VIN> MODULE_RECORDSET.
2012 is preferred but 2010+ should work.
Objective is to coordinate the hardware and software part numbers.

Thanks in advance for your help.

best regards,
Bill

 

Hi Bill,

I need to retrofit TPMS into Evoque 2016 and I got it installed but now I need to modify module_recordset.xml to add the below entry as I think:

<module gmrdb_acronym="TPM">
<node_id>0x751</node_id>
<part_set>
<part did="0xF112" gmrdb_name="ECU_ASSEMBLY_PN">
<part_number type="WERS">FW93-14F012-BF</part_number>
</part>
</part_set>
</module>
would that work?


TPM for JLR

 

Hi Bill,

I need to retrofit TPMS module in Evoque 2016. by your post above I think I need to modify <VIN> MODULE_RECORDSET.xml file.

I came up with the below. Is that okay?

<module gmrdb_acronym="TPM">
<node_id>0x751</node_id>
<part_set>
<part did="0xF112" gmrdb_name="ECU_ASSEMBLY_PN">
<part_number type="WERS">FW93-14F012-BF</part_number>
</part>
</part_set>
</module>

 

also how can I make sure that the node_id is correct. I'm afraid that SDD applies the software on a different module than the TPMS one.

 

I had a similar issue where I wanted to get <VIN> MODULE_RECORDSET. for vehicles with TPM. I ended up looking at websites where they sell used cars (like drive.com.au, etc.) and Picked up a few VINs, downloaded using SDD and then got the one that had the TPM module record.

 

Hello APIguy,
If I understand correctly, you are retrofitting / adding Tire Pressure Monitoring on a 2016 Evoque.
I assume that the Pathfinder software functions similar to SDD. If so, you will need to do the following:
1. Install the required hardware
2. Edit the module record set, Note that the file is double entry: "As-Ordered" and "As-Built". Edit both.
3. Edit the Central Configuration File (CCF) to enable the TPMS
4. Program the TPMS module.
5 Drive 5 minutes to allow the wheel sensors to respond to the TPMS signal.

You are no doubt aware that the TPMS inniator signal is provided at each wheel antenna.
The wheel sensor signal/data is received via a central antenna integrated into the TPMS module.

I don't know pathfinder but:
Using SDD, the module record_set is compared to a master copy held within the hidden Program_Data folder (Typical for WIN7).
If there is a difference, the master copy will replace the working copy (your edits). You should be able to avoid that issue by using properties/read-only.
Pathfinder should be similar.

For those using SDD V150 or earlier, IVSAsbuilt files for every applicable JLR vehicle maufactured through the date of your SDD is found in the hidded Program_Data folder.

best regards,
Bill

PS: Use a proper XML editor such as XML Copy Editor. Makes life so much easier.

 

Thanks Bill,

I use SDD 162.00 v.345. With TPMS config in CCF. do you know what it means by WBL, DLS, HSPA, etc.? also for the node_id, I did some research and found that the node_id for TPM is 0x751. Is there a risk that I could upgrade a different module than the one I intend to upgrade which is the TPMS module? I mean how SDD know exactly which module to upgrade? is it node_id? I attached the error I got below when I tried to configure new TPM module using the as built file without modification. While editing the record set xml file to add the TPM element, should I add it at the end or following alphabetic order or anywhere really doesn't matter? I attached the modification I have done in 2 screen shots below.



TPMS CCF Config



ERROR I got when I tried to configure new module TPMS while using the original as built file.



TPM As Built in recordset xml file



TPM As Ordered in recordset xml file

 

Disclosure: I'm doing similar work with Blind Spot Monitoring (BSM) and IDS_SDD V150 or below. All vehicle data files (VDF) are available within the programs that I use.

The requirement to on-line/download (resolve) the module file(s) may or may not complicate the process. It may be that failure to "resolve" the software part is that the software has not been made available.

The SDD program (V150 and below) includes "qualifiers" that may interfere with our efforts to add non-standard modules. This is true for my XK BSM effort because BSM was never an option. There is no such issue with BSM retrofit for the XF because BSM is native to the XF.
It may be that access to on-line vehicle data files is qualified/restricted per the OEM as-built record. (speculation)
Can you access the on-line TPM software files (secondary boot loader and data) and put it on your computer in the "hidden file" location?
Look in Program_data\JLR\sessions\as_built or something similar. I'm going from memory, so be creative.

I don't know the abbreviations that you asked about except NAS is north America specification.
Remember that not all CCF items are pertinent to any one vehicle. There are likely entries by the same or related name that DO NOT apply.
You could benefit from seeing the CCF for a similar Evoque (or the LR equivalent) with TPM. Alternatively, you are stuck guessing.
Try asking for help with TPM CCF on this or a LR forum?

PPS: There is a way to view the CCF "resolution" but I'll have to search for it, if you need it.

Please keep us posted on your progress.
Bill

PS: consider a new thread on the Evoque forum? If so, invite me.

 

Thanks Bill,

I did modify and I got the below success and choices. I have a feeling may be the update of the recordset file WERS was not with the correct software part number may be. May be the TPMS Module is dead? Is there a way to test the module independently whether it is dead or not? Do you have a mapping between Hardware Part Number and Assembly Part Number?



Success messages as the TPM Part Number was resolved. Not sure that the WERS I put in the recordset file is the correct one but it was copy and paste from a vehicle that has the same module installed.



That is the screen where I had the choice that I couldn't understand. The hardware part number I installed is FW93-14F012-BF not the ones on the screen above.



This is the hardware I installed. FW93-14F012-BF

 

APIguy,
Ok, I understand that we are discussing LR. (I knew that I was a bit off!) SDD function remains the same.

The progress report confirms that SDD found the correct software part for the specified module. Hurray!!!
The FW93-14F012-BF appears to be suitable for 2012-18 Evoque per ebay search. (Not definitive but usually reliable.)
Since the module communication is suspect, try a module scan using SDD.

Module part number should match the "software parts to be downloaded window" in your second image above.
The engineering part numbers on the part and internal/SDD are not required to match. (Confusing, I know.) SDD even renames one of the BSM modules so it can tell left from right. Some SDD magic. (In the military, a lifetime ago, we referred to it as FM.)

Please report the module scan results. I'm guessing that your CAN connection may be at fault.

Talking about CAN connections, keep in mind that CAN is RF, radio frequency, and connections are very sensitive to reflections. Connect to the main bus, not a branch. Emulate the OEM CAN bus wiring configuration. Double check that both CAN hi and lo are properly oriented. Tap connectors are a bad idea for CAN. Lengthwise twist and solder is good.

However, If the module scan performs properly, wiring is probably OK.

The simple module check is SDD vehicle scan. If you have a CAN bus adapter and software, you may test the individual module. power the module, connect the CAN reader/laptop and read CAN startup signals. don't forget a 120 ohm resistor for that test setup.

Keep us posted.

Bill

 

I did the scan but it didn't detected the TPM module installed. I suspect 2 things:
1. The module is connected to the car but the connector has that isolation substance they put on it at the factory (as the module is not connected). Is there a way to check if the connector actually delivering Power, CAN_L, CAN_H and Ground to the module? like a tester I can connect instead of the module
2. I'm not authorised to do it as I found errors in the session report. Will send you the report in a private message but the errors are as per the below:



SDD Exception Error

SDD Log:

[2023-01-1618:54:49,666] ERROR [btpool0-7] [com.jlr.sdd.exceptions.SddExceptionInterceptor:48:logException] com.jlr.sdd.tools.ids.actions.GetGatewayStatusActi on: java.lang.NullPointerException: null
java.lang.NullPointerException: null
at com.jlr.sdd.core.actions.SddAbstractAction.isAutho risedRepairer(SddAbstractAction.java:461) ~[app.jar:na]
at com.jlr.sdd.core.actions.SddAbstractAction.isGcmEn abled(SddAbstractAction.java:453) ~[app.jar:na]
at com.jlr.sdd.tools.ids.actions.GetGatewayStatusActi on.setGcmImageAndTip(GetGatewayStatusAction.java:5 84) ~[app.jar:na]
at com.jlr.sdd.tools.ids.actions.GetGatewayStatusActi on.updateStatusData(GetGatewayStatusAction.java:36 8) ~[app.jar:na]
at com.jlr.sdd.tools.ids.actions.GetGatewayStatusActi on.updateDeviceStatus(GetGatewayStatusAction.java: 163) ~[app.jar:na]
at com.jlr.sdd.tools.ids.actions.GetGatewayStatusActi on.execute(GetGatewayStatusAction.java:143) ~[app.jar:na]
at sun.reflect.GeneratedMethodAccessor45.invoke(Unkno wn Source) ~[na:na]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Un known Source) ~[na:1.6.0_26]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.6.0_26]




SDD Scan Results. No TPM

 

Is your vehicle pre-wired for TPM? What connectors/wiring are existing?
CAN hi and low may be tested using a multi-meter to confirm basic connection.
Be careful to not damage or stretch connectors when probing:


Use the Multi-meter to check for B+ power and ground also.

 

Thanks Bill,

It is pre-wired for TPM and here is a screen shot: Will have to remove the roof liner and may be order a new module (in case current one is faulty) and get back to you.



TPMS connector in Evoque 2016 (Roof Liner)


C9MC39 is the TPMS connector as I think FW9T-14489-AA/LR070487

 

Did you ever solve this?
I am trying to do the same thing, retrofit climate seats. The climate seats run a different module. Sdd keeps trying to flash the as built module.

 

I was successful to get around the as built thing with help from Bill but the wire from the roof liner had no power and I had no electrical experience. But now gaining that.

adam.alinsky@outlook.com.au

 

OK good to hear. I am confused on this part, from Bill. Where is the module record_set edited?

"2. Edit the module record set, Note that the file is double entry: "As-Ordered" and "As-Built". Edit both."

 

If you can email me, we can setup a meeting or send you detailed instructions how I did it.

i need someone I can team up with so that we can help each other closely. Bill is the best but he is in US and too advanced. Trying to get at a level where I can work with him. If we team up we can all benefit.

adam.alinsky@outlook.com.au

 

Adam,
Thank you for the compliment but I'm just sharing what I've learned from others and by digging around in IDS/SDD for years.
I would encourage you to continue your discussions on the open forum whenever possible to provide that spark of inspiration to others.

Keep up the good work.

Bill

 

I am looking for asbuilt file for my jaguar 2013 2.2d. Had to bring car to service for battery replacement, but people there did not know about the procedure so it ended up no key/no ignition status. They do not have tools and do not know how to get it back on track so I brought it on myself to fix it. Tried to configure existing cjb module, but received asbuilt files missing. Need help with the file, will pm a vin number. I am using offline 160 sdd jlr version.

 

I am not for sure but i think the last version to contain as built and calibration files was 148 or 150. I have some files for 131 and 138 i think on google drive. I will look. Dont know if they will mesh with 160. I have 160 on a hard drive. Your car may be too new for 131. Maybe motorcarman or clubairth or someone else will know. Best i can offer. Sorry. Just looked. I will be of no help. I do not have the as built files seperate. Sorry to waste your time