Not sure which update enables the 500A charging, but due to recent cybersecurity changes, I can no longer check for pending module updates. I still have PTS access, but it was nerfed by Ford so I am not able to see everything I used to be able to see with my login.
However, anyone that buys the...
I am guessing the mothership thought your truck still needed the config to be enabled, so it sent you that update as a blanket cover. In your case, it made no difference to your truck since you enabled those things yourself.
@Jesse-Infotainment I have his VIN.
@BSEE SPARKY The OTA you got was the one that enables the config, but I assume you already did that when I sent you the FORScan changes. There are two IPMA OTAs needed for BC 1.4 to work. The first one will install the software itself, and the second one will...
The OTA you got was for the APIM and it did enable the buttons for lane change assist etc in your touchscreen, but you are missing another config-only OTA update for the IPMA that would enable the features themselves. If you go to your driver assist menu and then cruise control, you will see the...
Even if that is the one you are waiting on, doing all the other updates will help the cause. If you only have one module with a pending update, when your VIN comes up in the OTA lottery, you'll get that one instead of another one that may preceed it. Any vehicle that has fallen behind for...
Unfortunately, that one can no longer be done with FDRS without a dealer login. Assuming the goal of updating the modules is to get WAL, that is the only one you are at the mercy of the OTA process (or dealer) for.
Unless FDRS downloads the files before it gets to the screen where it asks you...
Updates on vehicles (with the exception of maybe Tesla) do not work the same way they do on your phone or typical electric consumer device. This is not a Ford thing; you cannot force an OTA for outdated module(s) on any vehicle. They get sent when they get sent. While I understand this method is...
I have his VIN. His IPMA is now on the BBC strategy that we have. This IPMA update has been available for all trucks since December of 2024 regardless of what Sync version the truck is on as long as you have FDRS. However, to receive the OTA, the truck would need to be somewhat current in the...
Ford recently changed their cybersecurity methods. Using a VPN in another country no longer works. It is a waste of time and money to attempt to use FDRS in a country where it is not supported.
Do you have FORScan or any kind of code scanner to see what codes it is reporting now? We are going off of codes it reported 2 months ago. Ideally, FORScan would be best in case Jesse has some troubleshooting tips he can suggest to pin-point whether the TCU or the GWM is the culprit here.
Got your message. Code history is stored on the cloud for 60 days at a time. On 11/21, the truck reported these codes below and has not reported anything since. The BCM and CMR codes can be ignored as those are stored codes. However, that TCU code cites a component failure and the GWM codes...
If the modem is truly not working, it will not be reporting any codes to the cloud I can see with the VIN, but message me the VIN and I can check to see if I see anything obvious. If it is not reporting codes to the cloud, you would need FORScan or a code scanner to post any codes it is...
To do this, it requires more than programming. From convos I have had with people much more knowledgeable than myself, the TCU needs to be converted from ESIM to SIM on a bench. I know a guy that does it, but he is not on this forum. I believe he is in Poland. You would need to remove the TCU...
Interesting. I also experienced the predicitve speed kicking in after I turned it off with the beta release that didn't have the seatbelt requirement. Maybe they fixed that for the official release.
That is predictive speed assist. It can be turned off in the driver assistance > cruise control menu.
I have found that even if you turn it off, it still does it, but you can fully disable it with FORScan using the change @PJnc284 mentioned. Before BC 1.4, that value was a 0, but changing it to...