ECU module programming guide using FDRS

[Fordphanatic]

1007 is a quick update, unless your battery is very low it should be fine. It took my Lariat PB about 15 min.

Why does the hood need to be closed? I have done many updates via FDRS and had the hood open and battery connected to charger for all of them. Never had an issue with hood open.

Sponsored

 

[Jesse-Infotainment]

Why does the hood need to be closed? I have done many updates via FDRS and had the hood open and battery connected to charger for all of them. Never had an issue with hood open.

I think they have an OTA pending.

 

[Ford4Ever]

Why does the hood need to be closed? I have done many updates via FDRS and had the hood open and battery connected to charger for all of them. Never had an issue with hood open.

It is one of the OTAs that require the vehicle to be secured. No doors, hood or tailgate open.

 

[Kanuck]

It's actually under the hood latch. ?

Thanks.... I just have to flip the latch down.....

 

[Kanuck]

1007 is a quick update, unless your battery is very low it should be fine. It took my Lariat PB about 15 min.

My truck has been sitting for a couple of days. I had the update fail a couple of times when I selected update now. I figured the battery was low. The charger showed 11.9 volts. Had to have the truck all closed up. Again it failed. Tried again and this time locked the doors. Charger under the hood. And it worked, but Ford Pass never said the lock the truck, just all closed up.....PINA

 

[speedracercjr]

It is one of the OTAs that require the vehicle to be secured. No doors, hood or tailgate open.

FWIW I did both of those "priority" updates with the hood open and truck on the charger. I did lock the truck doors though, and both successfully installed

 

[Ford4Ever]

FWIW I did both of those "priority" updates with the hood open and truck on the charger. I did lock the truck doors though, and both successfully installed

IDK, mine wouldn't kick off until I closed the hood (just left the charger cable dangel from the closed hood). I've never had to lock the doors for the OTAs to install.

 

[Mike G]

And 12 days from the previous update on Feb 16 there's this....

 

[Txmade]

And 12 days from the previous update on Feb 16 there's this....

is there anything really new with this is update , I am curious what it says about the FSAs for 21G01 @rugedraw is this new info?

 

[Mike G]

is there anything really new with this is update , I am curious what it says about the FSAs for 21G01 @rugedraw is this new info?

It's been saying that same thing for months on the front page. I don't know what the actual changes were since they don't really provide details. The update is always free so I've found it's best to keep it updated rather than get surprised during some programming adventure when something goes horribly wrong...and I might later find out it's because I didn't update.....

I bought a shiny new 2015 Lariat and was one of the first people to take delivery here in Alabama. During the first two weeks I discovered the now infamous Intelligent cruise ghost issue that would cause the truck to hit the brakes when overtaking a certain type of 18 wheeler with a certain type of shiny sided trailer, as well as sometimes doing the same thing when approaching an overpass. So it went to the dealer service department and I got it back without a working cruise control for literally the next six months, until I took it to another really big dealer about 30 minutes away and they fixed it.

Turned out my original dealer's tech just hadn't bothered to update his laptop and was several versions behind...and his system didn't recognize the intelligent cruise module or components on this brand new 2015, and so it just left them disabled.

 

[rugedraw]

is there anything really new with this is update , I am curious what it says about the FSAs for 21G01 @rugedraw is this new info?

As of today, PTS still asks dealers not to perform 21G01. While we see regular people with a Mongoose performing BC updates themselves almost everyday, Ford is still seeing something there that has them shook.

 

[Mike G]

As of today, PTS still asks dealers not to perform 21G01. While we see regular people with a Mongoose performing BC updates themselves almost everyday, Ford is still seeing something there that has them shook.

I understand it's to do with the IPC not being able to be programmed.

While we're on that topic....there are several service advisors out there that if the words BlueCruise are spoken (even at a great distance) their immediate response is "shields up!"....followed immediately by "Ford says we can't....." etc.

There's a problem with that though. The moratorium is supposed to be on program 21G01, which is intended to apply to vehicles that were equipped with the necessary hardware at delivery, but never got the software updates to make it work (either by the long promised OTAs, or FDRS either one).

What this moratorium is not supposed to be about is preventing vehicles that had working BlueCruise from the plant ('21 J2 and beyond) from getting repaired when it stops working. But that seems to be what's happening in many cases. Say the word "BlueCruise" and immediately you're informed by a very knowledgeable service manager that "BlueCruise is on hold". When that's not really the case.

They apparently don't get the nuances and they probably don't care. Reading is fundamental.

 

[Snakebitten]

"They don't care" trumps everything else they might be lacking.

Nothing can overcome that obstacle.

 

[jober03]

New to the forum here.

I have a ‘21 XLT PB 302A with quite a history. It’s a Job1 truck built in March ‘21. I took delivery in July ‘21. A few weeks after taking it, I noticed the connected services didn’t work. The dealership applied a software update which fixed the connectivity issue… but disabled my heated seats and rear defrost. That became a 5 month saga that ended with a Lemon Law suit, a check from Ford, and a repaired truck (the software they applied for the connectivity issue was for an Ecoboost power train, not PB).

Fast forward another several months and I discovered it wasn’t receiving any updates. Took it to another dealership (we moved), and they diagnosed it as a bad APIM. They replaced it, and while it was in the shop, I got an app notification about the update. That was May ‘22.

On to now: I am still not receiving updates. My truck shows software version 21223_PRODUCT, while PTS shows a previous version. I recently updated all modules wit FDRS/Mongoose.

Everything worked except the APIM. I was able to create the USB. It begins Updating, but eventually I get a Code_0 USB error. Sometimes the error comes up in about 3 minutes, sometimes 20 minutes, or somewhere in between. I’ve tried 2 flash drives from 2 manufactures.

I’ve heard there may have been some bad APIMs from last year. Could that be the case?

1FTFW1ED0MFB41289

 

[Mike G]

New to the forum here.

I have a ‘21 XLT PB 302A with quite a history. It’s a Job1 truck built in March ‘21. I took delivery in July ‘21. A few weeks after taking it, I noticed the connected services didn’t work. The dealership applied a software update which fixed the connectivity issue… but disabled my heated seats and rear defrost. That became a 5 month saga that ended with a Lemon Law suit, a check from Ford, and a repaired truck (the software they applied for the connectivity issue was for an Ecoboost power train, not PB).

Fast forward another several months and I discovered it wasn’t receiving any updates. Took it to another dealership (we moved), and they diagnosed it as a bad APIM. They replaced it, and while it was in the shop, I got an app notification about the update. That was May ‘22.

On to now: I am still not receiving updates. My truck shows software version 21223_PRODUCT, while PTS shows a previous version. I recently updated all modules wit FDRS/Mongoose.

Everything worked except the APIM. I was able to create the USB. It begins Updating, but eventually I get a Code_0 USB error. Sometimes the error comes up in about 3 minutes, sometimes 20 minutes, or somewhere in between. I’ve tried 2 flash drives from 2 manufactures.

I’ve heard there may have been some bad APIMs from last year. Could that be the case?

1FTFW1ED0MFB41289

@Jesse-Infotainment

Sponsored