There are smart people at Ford and some of them see merit in the present system. We have to speculate what that merit is. Maybe the plan is to send out updates slowly and randomly, and see pushback or error reports come in and thereby avoid the risk of a huge number of vehicles coming in at the me time as an unexpected consequence of an update. Or maybe the perceived merit is something else. It is unlikely that it is the mindless system it seems.

 

Very good point. I also understand they rely on AT&T cellular to deliever these updates which can be quite large. I wonder if AT&T also has some throttles or limitations in place, or maybe Ford's contract with AT&T only allows for so much data to be pushed each period.

Lots of unknowns behind the curtain.

 

I just got an update for bluecruise, lane centering, lane changing, and position within lanes. I have a 2023 F150 Tremor 402a package without bluecruise. I'll probably test it out tomorrow to see what's noticeable.

 

The release notes will include the wording for BlueCruise whether the vehicle has it or not.

 

I had the same download, and I don't have blue cruise. It affect's F150 without blue cruise, not sure how.

 

Because all F150's have an IPMA module whether it has BC or not, so all F150's will get it. Ford should just put better release notes for the OTA's to avoid confusion.

 

Very good point that I had not thought of.

 

I received the BlueCruise 1.4 update the other day and I haven't gotten out on the road yet. I have a 2023 with an active BlueCruise subscription through January of 2026; is there anything I need to do in order to take advantage of the new BC features like lane change, etc?

 

Depends on which OTA you got. There are a few OTA's related to BC 1.4 going around which is confusing some people as to what update does what. If the OTA you got is a Sync update, lane change will not work. If the OTA you got was for the IPMA, then it may or may not work depending on which IPMA update was sent.

 

I don’t see any unique identifier or code associated with this update like I have in the past. Here is a screenshot of the header from the update: