ECU module programming guide using FDRS

[MikeYQM]

My battery charger was DOA so I didn’t get all of the updates done yet. I had 3 odd issues afterwards. 2 only occurred the first time I drove it after the updates. The last issue is this running board issue.

Message came on that backup brake assist wasn’t available backing out of the garage. Next 2 times in the truck and backing up with no error.

The truck wouldn’t run on battery. I checked the power flow and it showed this message. It was 66 degrees out and I’ve been driving over 7 miles at this point. After we stopped for ~45 mins and left it was back to normal.

If it helps anyone here are the updates I ran last night.
Door module (DDM)
Audio (DSP)
Gearshift (GSM)
Battery Energy Control (BECM)
Anti-Lock Brake System (ABS)
Secondary On-Board Diag module C (SOBDMC)
Power train Control Module (PCM)
Driver Front Seat Module (DSM)
Door Module (DDM) - showed up again and disappeared after this update. 2 updates maybe. Both were successful.
Trailer Module (TRM)

I had mine forget it was a hybrid after the insulation recall repair. I believe they drained the HEV and for a drive cycle it wouldn’t go into EV mode. I don’t recall if it fixed itself or if I charged the battery, but it did correct itself and I believe it was caused by low battery.

it’s possible yours Is related to doing updates without a charger and it will fix itself.

 

[nicholsbradley]

Why after the updates does the power up versions not change? The sync does but not the update details page

 

[abd79]

Why after the updates does the power up versions not change? The sync does but not the update details page

Mine still shows the failure of 1.7.1 as well and I’ve been updated for over a week now.

 

[nicholsbradley]

Mine still shows the failure of 1.7.1 as well and I’ve been updated for over a week now.

Do you have BC and the new camera features?

 

[Snakebitten]

Just a theory, but FordPass and Sync update screens are probably designed to reflect OTA activity.

We are basically bypassing the TCU route for all these updates. So maybe that module plays a role in triggering notifications?

 

[abd79]

Do you have BC and the new camera features?

Yep

 

[Platinum Peasant]

After talking a bit with @Jesse-Infotainment, the issue appears to be with my APIM. I have a 21 Platinum fully loaded. Would anyone with a 22' Job 2 fully loaded and updated to rev 364 (either 3.5 or 5.0, not powerboost), be willing to share their *updated* as built file for the APIM? Please PM me directly if so. Many thanks!

 

[Ajzride]

So I've been very vocal in my criticism of Ford this week for how hokey the FDRS update process is. I spent 4 days furious that they wouldn't give me the next set of APIM and GTW updates in FDRS even though I had completed everything in the queue. Thanks to @Bob_Mac I was finally clued into the fact that my IPC was corrupt. It wasn't the kind of corruption we saw with the Nano where there were a bunch spaces or junk characters in the data, but my IPC had one part number (F120) that was updated, and the second part number (F188) was still at the old rev, and corrupted by one letter. This was why the updates wouldn't come through. @Jesse-Infotainment was able to help me work around FDRS to load the F188 file and bypass FDRS. Within five minutes of getting the IPC part numbers to show up correctly FDRS offered me the next APIM update.

So long story short, pay attention to what the guys here advise you to do, and if your updates are not showing up, there is probably a reason, dig into the details.

As for Ford. I'm sorry I called you snakes who were holding back my updates just to get another 2 day FDRS license sale from me. But your update system is still clunky and confusing, and I pity your dealership techs who have to deal with it.

 

[Snakebitten]

So...... You aren't going to trade it for the new Tundra? ????

You should know that I privately didn't judge you during your rant(s). And you aren't the only one who has arrived venting. Lol

I rather enjoyed watching the whole story unfold for you.

And yes, it's a little unfair to expect dealerships that are built on what is fast appearing to be a legacy service model, to master this brave new SaaS vehicle approach. Lol

Ford is becoming a software company that also manufacturers cars/trucks.

 

[abd79]

Just testing the water here but is everyone that’s updating since the TSB having their OTA info also update to reflect not being stuck?

Is anyone who was updated prior to the TSB have their OTA info reflect being unstuck

Just wondering so I know whether or not to keep my case open with Ford OTA or close it. My info still shows I’m stuck even though I’m updated and everything appears to be ok.

 

[Ajzride]

To be fair, I said I was impressed with the Toyota Safety Sense 2.5+, not the Tundra.
The TSS was way better than Fords equivalent, but the same things I hated about my 4Runner they have not addressed in the new Tundra. The seats are hard and flat, the leather is stiff, the steering wheel rim is skinny, the interior surfaces feel cheap, and the whole thing is underwhelming. Toyota or not, at $65k they need to borrow some materials from their Lexus group to make it feel worthy of the sticker price.

 

[iceman77]

Folks, finally I got my truck back from the dealer and I had a chance to test out my Mongoose cable. All went flawlessly, no corruption during network scan, and what I noticed, that the Network Scan runs much faster than using the VCX Nano. I want to also point out, that I did not run any diagnostic on the device using the "Toolbox" tool as @Bob_Mac and others mentioned. Just clean driver install and I was good to go! I could not test the device itself for any module programming, as my 2022 F-150 model that is up to date with all updates and BC is activated by factory.

On another note, I am really glad how this community grew, just on this thread, and how many folks were able to fix their trucks with failed 1.7.1 OTA, followed by BC activation via FDRS tool! I am really impressed!

I know I haven't been much active on this thread lately, I am in the midst of another battle with Ford and a botched part, that affects hundreds of owners of hybrid trucks, with no resolution from Ford in clear sight, so I had to take matters into my own hands again. If you need my personal assistance, feel free to DM me, I will do my best to help you out!

 

[abd79]

Folks, finally I got my truck back from the dealer and I had a chance to test out my Mongoose cable. All went flawlessly, no corruption during network scan, and what I noticed, that the Network Scan runs much faster than using the VCX Nano. I want to also point out, that I did not run any diagnostic on the device using the "Toolbox" tool as @Bob_Mac and others mentioned. Just clean driver install and I was good to go! I could not test the device itself for any module programming, as my 2022 F-150 model that is up to date with all updates and BC is activated by factory.

On another note, I am really glad how this community grew, just on this thread, and how many folks were able to fix their trucks with failed 1.7.1 OTA, followed by BC activation via FDRS tool!

I know I haven't been much active on this thread lately, I am in the midst of another battle with Ford and a botched part, that affects hundreds of owners of hybrid trucks, with no resolution from Ford in clear sight, so I had to take matters into my own hands again. If you need my personal assistance, feel free to DM me, I will do my best to help you out!

Appreciate everything you and the team here have done to help enable us to update our own trucks. Appreciate the teams knowledge and willingness to help out a fellow member. Thanks for everything!

 

[Snakebitten]

Iceman,
Great to hear you have that sweet (but leaky) truck back home. And I know you are using that relentless brain of yours to once again "take matters into your own hands"

You deserve any success you achieve.

 

[FordConvert]

Sponsored