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.
@Supermans1 I agree that having the correct VIN in the module is unlikely to affect the performance of the modules, but in the unlikely chance that it does, I'm willing to give it a try.
I’m new in here so first of all hello to everybody
I’m struggling with my Fpace that I’ve bought. The Sodr sensor got replaced by the previous owner and I spent at least 30h, trying to get this module working
maybe anyone in here can help me.
I got myself SDD v164 and tried to configure new module.
I get through the configuration process but the software parts to confirm are unknown or not available.
I’d be happy if anyone could tell me, if I’ve got the wrong software or maybe there is a special function hidden for my problem.
Welcome to the forum. Be sure to post a message on the new member sign-in.
Also, add your vehicle detail to your signature for ease of assistance.
A hearty double welcome to a member willing to do the work (30hr) before asking!
Competent with SDD through MY2015, I will offer what I know/think:
Pathfinder would be the correct diagnostic software for the F-Pace.
If the correct .VBFs were available, it might be possible to program an early (2016?) F-Pace using SDD, haven't heard of anyone trying.
An "off-line" version of SDD beyond V150, does not have the VBF, (vehicle binary file) archives, so that is another problem.
Pathfinder is understood to require a new VCI, If you are using a MongoosePro JLR, that may be a problem using Pathfinder.
Once you have the correct VCI and download Pathfinder, consider signing up for a day or two of Topix.
Finally, the HK part numbers are not consistent with the FW parts found. An incompatible part is a possibility.
I would expect four FW93 software part numbers: secondary boot loader and data file, right and left.
Ok I tried it with two different FW93 14f152 BD Modules and both are not from an FPace - the VIN says, that one of them was from an RR Evoque and the other one was from an XF X260.
My FPace ist from 2017 - is it even possible to program a module with SDD in a 2017 car? Because you said - "if it is a 2016" .
I Bought myself today a Module from an FPace with fitting numbers (FW93-14F152-BD & HK83-14D453-AB) in the UK.
Now I'm waiting for the Module and will keep you updated.
I'm bored in lockdown (where I live is still under lockdown now) and so I got tinkering and ended up retrofitting blind spot detection to my XF-R. I wrote up a guide on it - I'm still refining it but here is the link so far. I'd welcome comments etc. Turns out it was pretty easy to do! I don't think I would have bothered without having so much time on my hands but it was a fun job.
"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."
The xml file should be edited to include the information of the module that's found in a car of the same year and model and not the information of the actual module (part number etc.) that is being retrofitted which maybe from a different car or a later year car. Is this correct?
When editing the xml file, does SDD needs to be running first and you have already started a session? Or can you edit the As built xml file prior to running SDD? (like a few days before or something)
When editing the xml file, does SDD needs to be running first and you have already started a session? Or can you edit the As built xml file prior to running SDD? (like a few days before or something)
Thanks
@Mrdude Ok. You question here reveals that you are in a bit over your head. That is fine. You will get there if you learn a few things that you don't know - that you don't know.
First order of business: Start a new thread. Title it "Adaptive Cruise control Retrofit" or whatever best describes your intention. Stop posting your questions all over the forum. That's bad form.
Go back to the previous posts (like this one) and provide a link to the new thread so that anyone interested may follow. This discussion isn't just about you. Someone else may learn from this discussion next year or ten years from now.
Your new post: Give us all the information up front.: Vehicle Make, year, model. Give the part number information that you know. Radar sensor module: correct part number, part number that you propose to use and from what vehicle.
Provide a narrative of what you propose to do and what you know and what you have gleaned from various sources.
Tell us what software tool that you are using: Are you using SDD? Online or off-line? What version?
SDD "resolves" (looks for/selects) software for a given part number. The version of SDD may allow more/different versions of part numbers.
You have stated that our friends on the Russian forum say that parts may be forward or backward compatible. That can be vehicle and SDD version specific.
Your project is very interesting. I want to see you succeed. The easiest way is to use a radar distance module from a similar/same make/year/model.
However, if you do start your own thread with the necessary information, I will try to dig out a list of compatible part numbers from a specific version of SDD.
