Download Ford Calibration Files

0 views
Skip to first unread message

Ronald

unread,
Aug 3, 2024, 4:13:24 PM8/3/24
to guiworkningre

I installed sensors and added the necessary wiring. Sensors are visible in the Forscan and they are working fine - used PIDs for verification.
So, now have installed on a car EU HID lamps + leveling sensors + US HCM.
Sensors are connected directly to the HCM and are working fine. On the other hand, HCM must have the firmware updated to finish the entire operation.
Unless I missed here something.

I agree with the firmware assessment.
I found this thread from a Polish Ford club about this subject.
[Escape - Kuga USA] Front headlights spacer - Page 10 - Forum Ford Club Poland (fordclubpolska.org)

My keyless Mondeo Mk4 is bricked for almost a month due to TSB 29/2008. The solution would be updating software on KVM/RFA module.
The current (faulty) SW version is: 7S7T-14C104-AG.
Could somebody tell me which patch (calibration file should be used) and ideally send me that file?
Thanks in advance!

Since a 2014 C-MAX did not come with Sync 3, this is a retrofit, I assume. Is the Sync 3 unit that was installed is a Gen 1, part number would begin with G. Since it had the GB5T-14G374-AF Strategy file, this would make sense.

The software is up to date, because I had uninstalled 119 and reinstalled 121 and updated to 121.05. Also, even after I went to DSFM and downloaded the calibration files, which obviously were in fact there, it still did not work. One remaining question, though, is where do I put them? The guidance from Ford is C:\Program Files\Ford Motor Company\Calibration Files\ which is wrong because FJDS is a 32 bit application that resides in C:\Program Files (x86)\Ford Motor Company\ and the calibration files are in C:\Program Files (x86)\Ford Motor Company\FJDS\Vbf (this is one of many places that I copied them to). So, again, it seems like this whole thing is written for IDS, perhaps?

Has anyone ran across this before? I tried (a longshot) creating a directory C:\Program Files\Ford Motor Company\Calibration Files\ but it didn't help, I thought it was worth a try. I could not see anywhere else that contained any *.vbf files that it may be looking for. Are there other files that it needs to download as well? The dialog box that popped up the error message only listed one file, a second dialog box came up for each vehicle for a total of four files and I was able to download them all.

There is a directory C:\Program Files (x86)\Ford Motor Company\FJDS\Calibration Files\ (iirc going from memory on that and it's on the other partition so I can't look at the moment) but there are no .vbf files in there.

COBB Custom Features support was released in Ford Accesstuner Pro version 1.9.1.0-13796 using Ford's latest 2017 Focus RS (GRCK4) ROM. This 2017 ROM strategy supersedes the existing 2016 (GRCK2) Ford Focus RS strategy. As a result the original 2016 ECU definition files have been removed from Accesstuner support. Maps based on the GRCK2 strategy will not load. However, the GRCK2 Focus RS maps can be opened in map comparison view for analysis and import into the new GRCK4 strategy. See details below to migrate existing calibration files from 2016 GRCK2 to the latest 2017 GRCK4 definition file.

can't perform self install as detailed earlier - I am using the same original model TCU, and have it in 2016 MKX. Forscan shows it is "working", but I cannot activate the car from the app, nor does an ESN show up in that area of the SYNC screen. A TCY test in Forscan says "Vehicle conditions incorrect" - I am thinking my TCU is configured differently - here are some forscan particulars:

So to follow up, I posted my issue to the CyanLabs forum where a knowledgable F150 guy there gave me very specific steps to downgrade the TCU, and following that, all is working. I used Forscan and some files he provided to make all of it work. It does seem odd to me that Ford/Lincoln have paused these upgrades. Knowing they are relatively easy to perform, especially when one has the programming tools etc, I wonder if Ford would rather take these older cars "off network" and discontinue supporting them over a new network, rather than completing the upgrade?

It does seem odd to me that Ford/Lincoln have paused these upgrades. Knowing they are relatively easy to perform, especially when one has the programming tools etc, I wonder if Ford would rather take these older cars "off network" and discontinue supporting them over a new network, rather than completing the upgrade?

Hello all, I am acquiring all the parts to complete this 4G upgrade on a 2016 MKX and 2017 MKC. For those interested the 4G antenna that is part of Fords official upgrade kit is P/N: NL1Z-19A390-A , I can confirm that this is the white flexible antenna pad with a Male Fakra D lead coming off of it as pictured in the ford bulletin and the dealer sells these for about $50 CAD. In order to connect this to the TCU you will require a Fakra D (purple ends) or Fakra Z (water blue ends) female to female extension cable. Both the TCU and Fords antenna have male ends. The Fakra Z type cable is universal and will plug into any Fakra type end, the Fakra D will only plug into the ends on the TCU and antenna. These cables can be found on eBay or Amazon and you will need to order which ever length you require for your specific application. For the MKX a 12" (1 Foot) cable should be sufficient if using the suggested locations listed in the ford procedure located Here . Both the antenna listed above and the TCUs are made by continental. Also as others have stated it is definitely easier if you can find a TCU out of the exact same model you are trying to upgrade, however this isn't required. That said you will require a paid version of Forscan in order to change the firmware in the TCU to match your application and will also require it in order to downgrade the firmware. If those who have completed this upgrade could post the firmware versions that worked on their specific applications as well as the as-build data that would be very helpful for those wondering what files they will need or should show once they connect. A few have posted successes but not what files they used to get there. I will be attempting to use a TCU from a 2018 F150 and one from a 2019 Edge. Though the prefixes and suffixes are different than the ones that come out of an MKX or Nautilus once installed I should be able to reflash the firmware to the correct versions that would apply to an MKX and MKC and load the factory as-build data from 2018 versions of each. These files are still available from ford and FORScan will also have them. Waiting on my extension cables before I get started, but once I do I will post exactly what needed to be done in order to get these to work.

Finally got all my parts together to complete this 3G to 4G upgrade and I can say it worked out well for both my 2016 MKX as well as my 2017 MKC. The parts I used are below and should apply to any one upgrading from 3G to 4G, the only difference would be the length of the antenna extension cable. In the MKX the TCU is located in the right rear quarter panel just to the left of the subwoofer as shown in earlier posts in this thread. The MKC TCU is located under the center console, accessible from the passenger side foot well area. These were both installed following the guidelines setout in the ford bulletin HERE. Hopefully this plus all the other info out there can help someone else get this feature working again. This can be done for much less than what dealers are charging just for labor, provided they are willing to do it or know anything about it. Total costs for this upgrade was around $200 CAD per vehicle, TCUs were $130, antennas were $52 and extension cables were $20.

Step 1: Remove old TCU located to the top left of the subwoofer in the right rear quarter. Should be noted that the original module electrical connections faced the rear of the vehicle and the new/repurposed TCU faces the front of the vehicle (per the guide). For me this caused the wiring harness to be too short to reach without cutting back the taped main harness and pulling the TCU wiring out a bit more. It will reach but it was tight.

Step 2: Temporarily Plug the factory harness into the new/repurposed TCU, connect FAKRA type I (beige) bypass plug (if not using wifi hotspot), connect the 4G antenna and extension harness. This will all be kind of just dangling as you verify functionality. Make sure everything works as expected before going through all the effort of finishing the install.

Step 3: Connect to vehicle using FORScan. I didn't reuse a previous profile, I just connected as if it were the first time and allowed FORScan to scan for all modules. The TCU should get recognized during the scan. After the scan is completed open the PID tab on the left and select the TCU from the menu at the bottom, then add all available TCU functions to the monitor. This will allow you to see signal strength and the status of the module among other things. You can push play and see what the status of these are which will allow you to see that everything is reading, once everything is good push the stop button as you can't run 2 functions at the same time (next step). Ensure you have decent cellular strength or the authorization steps may not work. (mine was around 175-180).

Step 4: Open the configuration tab on the left and scroll down to the TCU module asbuild data section and run it. Once open we will be changing the last character of the first block on the first line 754-01-01. The code will be xxxX-xxxx-xxxx. We will be changing the "X" from what ever it is (Likely a 2) to a 3 and clicking on write. After this has been written and the prompts followed we are going to go and change that 3 back to what it was previously and click write. This forces the TCU to reprovision itself. You can now stop this function and go back to the PID section and monitor the TCU again. This time you will see "Unprovsioned mode" and the other values will be zeros. Let this run until it reads "Waiting for authorization". The TCU is now waiting for the request to come from the phone app.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages