@b.go Obviously, I'm sorry to hear this happened and also happy to hear no one was hurt.
It would be intereting to see if it reported any codes before it went offline due to the fire. If your Fordpass was connected at the time it happened and you don't mind, message me the VIN. My curiosity is...
The chance of this happening is extremely rare. Even then, it would have to be an update to one of the Sync related modules where the data gets screwed up and creates a bottleneck for future updates. In the case of a failed BCM update, there would not be any "block" on the server side for future...
Message me the VIN. I can check the OTA history and we can talk off the forum. But no; you cannot initiate the OTA trigger yourself. You may have gotten the same OTA sent twice and it failed the second time which is why you are seeing that message about not completed.
The problem with this method is that putting in a TCU that doesn't belong to the vehicle can cause issues with the back end server data. If the TCU that gets swapped in is not the same part number or has different firmware on it, it will cause issues with future updates via OTA or FDRS. The...
Got your message, but posting here so anyone else can provide insight. There are a bunch of codes, but they're mostly stored codes caused by the root problem. These are the problem codes:
As we all probably already suspected, I don't think this is an easy fix that a battery disconnect or...
You can borrow one of mine. Let me know if you want me to add you to the list. Details are below:
https://www.f150gen14.com/forum/threads/community-mongoose-reprogramming-vehicle-interface-lending-thread.13145/
Check what you have in this location in your APIM:
If whatever value you show there has DRLCF disabled, then change it to enable it, reboot the APIM and check again.
The OTA version of the update us 10.3.0 and it updates several modules.
https://www.f150lightningforum.com/forum/threads/ota-software-update-10-3-0-powertrain-battery-parking-brake.24247/post-469128
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...