Power-Up 2.3.0 OTA rolling out

[Snakebitten]

I have not. But I'm assuming that I probably never will because the Ford cloud database has my truck listed as "uptodate"?

(Thanks to you in no short way lol)

Sponsored

 

[SouthernGuy]

IF you have an iphone...

The "easiest" way, is to grab tonesto7's FordPass widget. It is great. Once installed, just go to Widget Settings -> Debug Menu -> View OTA API Info. You will see a bunch of great info, including the status of the last attempt to update. It does not give you individual module versions, but it will tell you the "Power-Up" version.

There is a whole thread on it, including how to install it:
https://www.f150gen14.com/forum/threads/fordpass-scriptable-widget-ios-ipad-macos.7444/

But, the short answer is to go get it from here:
https://github.com/tonesto7/fordpass-scriptable

Anthony is currently working on v2.0 of the script which looks to be fantastic. Infinitely better than the "FordPass" app itself!

Hope this helps.

Thanks for the reply. What about non-iPhone users?

 

[iceman77]

Has anybody who has used FDRS to update the APIM and TCU manually gotten 2.3.0 anyway? So far, I haven’t—it would be redundant. But I was wondering if Ford would still push it out for its own record keeping, particularly for future OTA updates.

Your truck periodically reports software revisions of all your modules to the mothership. You can see that yourself in your AB data. If your OTA targeted modules are deemed up to date, there is no reason for them to push it down.

 

[JediNut]

Thanks for the reply. What about non-iPhone users?

There is another thread about the OTA information being hidden in the headers from the Ford site. It's not as clean and pretty as Anthony's app, but you should probably be able to grab the info there.

Check out this thread:
https://www.f150gen14.com/forum/threads/ota-status-hidden-in-the-ford-website.7464/

 

[JJ_Tex]

It looks like mine is trying to do the update to 1.7.1 and it expires tonight at midnight.

The truck is parked in the garage within wifi range, is there anything I need to do to ensure it installs before the packet expires tonight?

 

[speedracercjr]

It looks like mine is trying to do the update to 1.7.1 and it expires tonight at midnight.

The truck is parked in the garage within wifi range, is there anything I need to do to ensure it installs before the packet expires tonight?

Pray to the mechanical gods that your truck doesn't get stuck on 1.7.1 like some of us.

 

[TJSparky]

SpeedRacer is right!!!
1.7 HELL

 

[JEB]

Your truck periodically reports software revisions of all your modules to the mothership. You can see that yourself in your AB data. If your OTA targeted modules are deemed up to date, there is no reason for them to push it down.

Yeah, that’s what I figured. It would be pointless. But Ford is a bureaucracy and I wouldn’t put administrative ticket-punching past them.

 

[Jus Cruisin]

I received the notice the truck got 2.3.0. Not connected to wifi.

The Ford assistant doesn't work.... I don't think it does..?? Not sure where to find the adaptive cruise control settings to turn on the speed sign recognition.

Oh well...

 

[iceman77]

I received the notice the truck got 2.3.0. Not connected to wifi.

The Ford assistant doesn't work.... I don't think it does..?? Not sure where to find the adaptive cruise control settings to turn on the speed sign recognition.

Oh well...

SSR is located in Features -> Cruise Control -> Adaptive Cruise Control

 

[msokad]

First time poster, long time lurker.

My truck tried install 2.3.0 the other day. but I received a message it failed. The next day, the ford website said "all set" but when I looked at the Update Status on my truck, it shows 2.1.1 was installed again.

I did the steps in another post to see what the status is and see this. Now I'm even more confused.

Asking the more knowledgeable, any Ideas?

1. additionalConsentLevel: 1
2. communicationPriority: "High"
3. deploymentCreationDate: "2022-02-01T21:39:33.347+0000"
4. deploymentExpirationTime: "2022-02-08T21:39:33.347+0000"
5. deploymentFinalConsumerAction: "General Failure Will Retry"
6. deploymentId: "34c168ca-f74a-4362-a76f-c2e9663a18d8"
7. inhibitRequired: false
8. latestStatus: {aggregateStatus: "failure", detailedStatus: "OTAM_E1016",…}
9. oemCorrelationId: "FLARE-PRD-SOFTWARE-FNV2-479518-507905"
10. otaTriggerExpirationTime: "2022-01-18T23:04:43.778+0000"
11. packageUpdateDetails: {,…}
12. tmcEnvironment: "PRD"
13. triggerType: "SOFTWARE"
14. type: "REGULATORY"

 

[Jus Cruisin]

SSR is located in Features -> Cruise Control -> Adaptive Cruise Control

Thanks!

 

[Zeromarine]

I have had failed a bunch of times but never has it yet said failed on the truck or ford pass. This is for 1.7. Anyone have the same thing ?

 

[AutonomousHybridF150]

What's so strange is that if we purchased 10 pc's of the same make/model, and then proceeded to prepare all 10 for deployment, we would almost guaranteed have identical out-of-the-box experiences, including getting them all updated to the latest build/updates.

Yet with our trucks, I can stick the USB stick in with the truck running and it will only take seconds to recognize what is on the stick and initiate the update.

The next truck will act like nothing has happened.

Then my truck will get stuck in the "restart to finish" loop, only to instantly overcome the loop by me REMOVING the stick against instructions.

While the next truck doesn't get stuck in the restart loop.

The inconsistencies doesn't make sense in the normal ones & zeros digital realm.

But I do admit it makes for some adventure for those determined to do this themselves

I have seen this on high end vehicles with a lot of electronics when trying to re-flash the PCM. The more electronic crap that is firing up when you flip the key on, the more possibility of interference. I have also seen some really weird things happen when wires get shorted out, etc, somewhere else in the system. Isn't there some TSB for pinched wired on the 2021 trucks? Lol.

Just saying. Those old "tap the PCM AFR wire" air fuel "light show" gauge have caused a lot of issues for tuners back in the day before we really knew we needed a wide band sample to be proper "SMH". A little resistance on an unknown wire in an unknown loom or volatile system voltages due to all the little things turning on can cause the issues you speak of.

 

[shalabama]

I have had failed a bunch of times but never has it yet said failed on the truck or ford pass. This is for 1.7. Anyone have the same thing ?

Same here. Mine choked on 1.7.1 but no alerts or notifications. My updates and schedulers are in zombie mode. Fingers crossed we eventually get an update either OTA or thru dealer to correct.

Sponsored