Search results

Well, I don't think Ford ever officially made an annoucement stating this is the case, but I can tell you that it does not work while towing or without wearing the seatbelt and there is no known way to bypass it with a FORScan or any easy method.

It is hard coded that way as a safety measure. Just like the newer IPMA software requires the driver to have their seatbelt buckled in for lane centering and/or Bluecruise to work. Like it or not, that is what Ford decided was the safer route to take and I highly doubt they will change it back...

Got it. Hopefully it works out for you.

If you install that APIM and it is on different software than what your truck has, there will be mismtaching data between the server and the truck and cause issues with the OTA process. What is it that you want to accomplish by swapping the APIM?

This is one of the best investments I have made for my truck. I'll disconnect the battery in my truck 1-2 times a month just for the hell of it even if nothing's wrong. https://www.amazon.com/dp/B0D2K7CV69?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_8&th=1 A 20 minute 12v disconnect does...

@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.

"Not completed" means that particular OTA failed for some reason. It does not mean there is a problem. You just have to wait for the OTA to be resent.

Looks like this is the only way to go. Then you will have to try and go after Ford to get them to reimburse the cost.

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/

What codes is it reporting now? If your Fordpass is connected, message me the VIN and I can check them.

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.

It seems like it reverted one of the IPMA changes on your truck. If lane change doesn't work, lmk. It's an easy fix.

@BSEE SPARKY Have you road-tested BC since you got this OTA to see if lane change and everything is working properly?

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.