ECU module programming guide using FDRS

[Mike G]

No it’s not than I’m missing out on any as I update manually but it’s not seeing any change whatsoever in PTS on the status of OTAs. One would think that since the truck has moved past 1.7.1 that if a new OTA was pushed and I hadn’t updated manually yet it would have at least tried.

I still show 1.7.1 as failed in the scriptable widget and none of my dates for deployment, expiration etc have changed.

Oh okay.

I see the same thing with the widgets on both my F-150 and the Mach-E but since I live way out in low cell coverage country and since I'm not expecting any OTAs to ever show up for me anyway I never thought about it.

Mike

Sponsored

 

[abd79]

Oh okay.

I see the same thing with the widgets on both my F-150 and the Mach-E but since I live way out in low cell coverage country and since I'm not expecting any OTAs to ever show up for me anyway I never thought about it.

Mike

Low cell signal may be my issue as well, I only get 1-2 bars of service at my place but I do have it connected to Wi-Fi all the time when home. May try and get a booster for home and see if anything changes other than better reception for my cell phone at home.

 

[Mike G]

Low cell signal may be my issue as well, I only get 1-2 bars of service at my place but I do have it connected to Wi-Fi all the time when home. May try and get a booster for home and see if anything changes other than better reception for my cell phone at home.

OTAs don't ever come over wifi.

Regardless of what Ford tells you.

They are only pushed using the TCU. And it's likely that if you do get one you'll be driving in a large metropolitan area with good cell coverage. That seems to be the only time it ever happens. When you're 'out-and-about' in a downtown area.

Mike

 

[F150 John]

Quick question about this. Do I need to download just FDRS or do I need the VCI software as well? I have the Mongoose-Plus on the way and trying to get everything set ahead of time.

 

[redduke916]

^have they successfully done any others?

yes

 

[Mike G]

Quick question about this. Do I need to download just FDRS or do I need the VCI software as well? I have the Mongoose-Plus on the way and trying to get everything set ahead of time.

Yes

 

[JEB]

Quick question about this. Do I need to download just FDRS or do I need the VCI software as well? I have the Mongoose-Plus on the way and trying to get everything set ahead of time.

No. VCI (Vehicle Communication Interface) software is only for the VCMM, VCMII or VCM3 interfaces. The Mongoose is a J-2534 pass-through device. You should, however, download and install the J-2534 Toolbox from Opus for the Mongoose diagnostics.

 

[Mike G]

No. VCI (Vehicle Communication Interface) software is only for the VCMM, VCMII or VCM3 interfaces. The Mongoose is a J-2534 pass-through device. You should, however, download and install the J-2534 Toolbox from Opus for the Mongoose diagnostics.

Okay, my bad. I did install that software as well as the toolbox software because I thought it was required (must re-read the first post I guess).

Regardless..it hasn't hurt anything or kept me from successful programming.

Mike

 

[JIMFOUNTAIN]

Previously reported success in March with complete update. Bluecruise etc. working. Turned OTAs off.

Turned OTA back on a few weeks ago after hearing about new updates being available. Nothing happened for a while so "reported" OTA issues. OTA then pushed 2.8.2 and then 2.8.3 to me. Not sure what was in them since I already had Bluecruise+. Saturday (4 days ago) got the TRM update via OTA. Recall is still showing as incomplete....

1) TRM update said I would have split screen capability now in the trailer backup guidance screen. Not working for me. Anyone have this working?
2) Anyone had the TRM update via OTA and get the recall marked as complete?
3) Any ideas what showed up in 2.8.2 and 2.8.3 since I already had Bluecruise???

No current FDRS access. VIN is 1FTFW1ED5MFB13052.

 

[abd79]

Previously reported success in March with complete update. Bluecruise etc. working. Turned OTAs off.

Turned OTA back on a few weeks ago after hearing about new updates being available. Nothing happened for a while so "reported" OTA issues. OTA then pushed 2.8.2 and then 2.8.3 to me. Not sure what was in them since I already had Bluecruise+. Saturday (4 days ago) got the TRM update via OTA. Recall is still showing as incomplete....

1) TRM update said I would have split screen capability now in the trailer backup guidance screen. Not working for me. Anyone have this working?
2) Anyone had the TRM update via OTA and get the recall marked as complete?
3) Any ideas what showed up in 2.8.2 and 2.8.3 since I already had Bluecruise???

No current FDRS access. VIN is 1FTFW1ED5MFB13052.

How did you “Report” OTA issues?

 

[speedracercjr]

How did you “Report” OTA issues?

In Sync there's a place to send Feedback, I think from the main Settings page.

 

[RellIk&5]

In Sync there's a place to send Feedback, I think from the main Settings page.

I've had been using that function on a daily basis prior to doing my own FDRS updates and never saw a single OTA as a result.

 

[Foxtrot150]

Hey all,
Brought my 2021 Job 1 truck in 2 days ago to the dealership to attempt to get OTA's updating (and perform recalls 22B08 and 22S17) and just got it back. They ended up replacing the GWM as well as successfully performed the APIM recovery (TSB 22-2150 I believe). Been an issue since October when the dealership attempted and update and broke it - updates were greyed out and was stuck on 1.7.1.

Two questions:
1. What version am I on now (21146_Product Revision 145)? I get confused with how it aligns with https://en.m.wikipedia.org/wiki/Ford_Power-Up_Version_History.
2. Typically how long before I receive an OTA after the fix or am I still stuck?

Before:

After (today):

 

[FordConvert]

Hey all,
Brought my 2021 Job 1 truck in 2 days ago to the dealership to attempt to get OTA's updating (and perform recalls 22B08 and 22S17) and just got it back. They ended up replacing the GWM as well as successfully performed the APIM recovery (TSB 22-2150 I believe). Been an issue since October when the dealership attempted and update and broke it - updates were greyed out and was stuck on 1.7.1.

Two questions:
1. What version am I on now (21146_Product Revision 145)? I get confused with how it aligns with https://en.m.wikipedia.org/wiki/Ford_Power-Up_Version_History.
2. Typically how long before I receive an OTA after the fix or am I still stuck?

Before:

After (today):

You should start receiving updates, timing is up to the Ford mothership. You're quite a ways from being totally up to date, but they fixed the main problem. BlueCruise is revision 364, and now I think current is 415.

 

[Mike G]

You should start receiving updates, timing is up to the Ford mothership. You're quite a ways from being totally up to date, but they fixed the main problem. BlueCruise is revision 364, and now I think current is 415.

@Foxtrot150

Sync 421 is the latest.

Strange they didn't even update you to the point where you could schedule OTAs for more than one day a week. Kindof a dick move IMO.

Screengrabs of your FDRS config showing weirdness on your APIM software version...as well as a list of software updates FDRS says you need. After doing the GWM module the APIM or TCU may pop up again with a new update. This is normal "whack-a-mole" behavior until you're all caught up.

I wanted to add....don't expect OTAs to download using your home wifi. Empirical evidence suggests they are only downloaded using the vehicle's TCU modem while driving in a metropolitan area (city) with good cell coverage (more than two bars of AT&T). There is no evidence to suggest that they have ever been downloaded using the customer's wifi despite Ford's suggestion to connect your vehicle to your home network.

Sponsored