ECU module programming guide using FDRS

[RickBullotta]

Been a while… work gets in the way unfortunately. Anyone with a license and a spare minute mind checking if I have any updates? I have a ‘21 powerboost with the power release and close tailgate, I know about the BCM issue.

1FTFW1ED0MFB66211

Also, does anyone know if the BCM update shows up for everyone or just those with power release only and no power close tailgates?

My truck has power open/close, but the update did show up in FDRS for me (and bricked my truck). Be careful!

Sponsored

 

[abd79]

My truck has power open/close, but the update did show up in FDRS for me (and bricked my truck). Be careful!

Yeah I won’t be doing that update until Jessie says it’s good to go.

 

[Jesse-Infotainment]

Been a while… work gets in the way unfortunately. Anyone with a license and a spare minute mind checking if I have any updates? I have a ‘21 powerboost with the power release and close tailgate, I know about the BCM issue.

1FTFW1ED0MFB66211

Also, does anyone know if the BCM update shows up for everyone or just those with power release only and no power close tailgates?

Yes it shows for all. You have the BCM update only.

 

[abd79]

Yes it shows for all. You have the BCM update only.

Thanks, I’ll be leaving that up date right where it is too.

 

[Jesse-Infotainment]

Thanks, I’ll be leaving that up date right where it is too.

Yeah. I would for now. I looked and it seems they did fix it now. I made a post I deleted explaining the update called for the wrong file. SO after doing more research it seemed to be not all the powerboost but most had the wrong file called for.

JEB for example has ML3T-14F390-CBA The update called for that file again. It should be calling for CAJ. Since its the ECU calibration file it caused the BCM to brick since it was incompatible with the new files.

This happened to a guy a while back that had a ABS update that bricked his truck and it couldnt start. THe udpate only installed the 188 file and not the ECU. SO they werent compatible and crashed his truck out. I was bale to load the old file and get him back to running.

There were a few trucks that did have the correct file called for. I can see the update files. I can see what is states is the file it should be. SO I wasnt sure if it was stating the right file but calling for the wrong one in the update. It seems that it was stating the wrong file and calling for the worng file.

So it seems now they have assigned CAJ to all powerboost.

In reality Im sure that porn was the reason for all the guys bricking the BCMs. Oh and looking at youtube videos. We stand to learn much form this guy

 

[abd79]

Yeah. I would for now. I looked and it seems they did fix it now. I made a post I deleted explaining the update called for the wrong file. SO after doing more research it seemed to be not all the powerboost but most had the wrong file called for.

JEB for example has ML3T-14F390-CBA The update called for that file again. It should be calling for CAJ. Since its the ECU calibration file it caused the BCM to brick since it was incompatible with the new files.

This happened to a guy a while back that had a ABS update that bricked his truck and it couldnt start. THe udpate only installed the 188 file and not the ECU. SO they werent compatible and crashed his truck out. I was bale to load the old file and get him back to running.

There were a few trucks that did have the correct file called for. I can see the update files. I can see what is states is the file it should be. SO I wasnt sure if it was stating the right file but calling for the wrong one in the update. It seems that it was stating the wrong file and calling for the worng file.

So it seems now they have assigned CAJ to all powerboost.

In reality Im sure that porn was the reason for all the guys bricking the BCMs. Oh and looking at youtube videos. We stand to learn much form this guy

?

 

[Jesse-Infotainment]

So the update is fixed. I can now say I was 100% correct the update called for the wrong file

So this is the same truck

Aug 15 they were attempting a PMI to bring the BCM back

F16C is downloading CBA

Now same truck Yesterday at 11

F16C is now CAJ

So the timing was impeccable. Yesterday around 11 they sent out the fix maybe earlier.

 

[Jesse-Infotainment]

Well now I found this in there.. so maybe someone at Ford was looking at things they shouldnt have.

 

[JEB]

So the update is fixed. I can now say I was 100% correct the update called for the wrong file

So this is the same truck

Aug 15 they were attempting a PMI to bring the BCM back

F16C is downloading CBA

Now same truck Yesterday at 11

F16C is now CAJ

So the timing was impeccable. Yesterday around 11 they sent out the fix maybe earlier.

As you pointed out, Ford’s software versioning makes no sense at all. CBA ==> CAJ looks like it should be a downgrade. Boobs.com, however, is a huge upgrade.

 

[BHunted1]

Happy to say all 3 modules (GSM, WA and BCM), updated ok.
Saved BCM for last. Whole process less that .5 hrs.
Took out for a run, no issues....

 

[wayfarer556]

I’m hoping I didn’t use up all my luck, I leave for Vegas at 2:30 tomorrow. I’ll preface this by saying I likely won’t use the correct acronym for something but I have a lot of experience In this general area albeit on Deere and Caterpillar equipment. This experience has also created a lack of fear of these situations because In the case of Deere and Cat if the module is still on the CAN then you can program that sucker. You might need a 900$ Adapter that looks like Clark Griswolds Christmas lights in storage, but bricked has never been a word I’ve had to use in those industries.

So what I can pass along wether it was a factor I’ll leave that up for discussion:

- truck is an early build platinum powerboost 4x4 with every option except I think the safe
-I plugged in fired up FDRS and started updating modules in a totally random order based on me picking ones that sounded non critical and quick first since I was new to the software
- truck was hooked to a snap on battery charger that has a flash reprogram feature that keeps voltage Constant on I think 14.4
-I’d made a ton of changes in forscan a while back after I realized Ota updates weren’t working. I had some stuff turned on that wouldn’t work but I wasn’t getting any codes or error messages and I hadn’t went back and changed it due to and incident with that cheapie interface and my girlfriends French bulldog.
-after the initial update attempt failing and a second attempt doing the same, I disconnected charger and battery took my computer back to the house, drank crown royal on the rocks and updated some ford software that they say is irrelevant when using mongoose (ids I believe) Restarted computer twice leaving mongoose connected to usb. Turned off everything windows defender related.
-went back to truck, reconnected battery and cussed loudly when it was still in its comatose state. I signed out of and back into FDRS server side and played around with other modules self tests, ran a BCM self test etc if I thought any of what I was doing had the slightest chance of being successful I would have paid more attention to what I was doing. I didn’t think the module was going to have to be replaced I just figured I needed the dealer level tool and direct software package sent from Ford.
- after my screwup I did some googling and read something about this possibly being related to a tailgate safety issue and my truck had two procedures for some tailgate release showing to be done. Before I did the PMI I ran one of them the other one it wouldn’t let me do I think it’s for just a power release tailgate or something. The reason I tell you this is because when the PMI finished it told me to print something out and give to myself about the tailgate as a supplement to the operators manual. I did not satisfy that request.
- I updated some other module, wish I could remember which one but i wanted to see if I had a single module issue or if I needed to start mixing mortar (brick dad joke)
- then I ran the PMI, it was my first official PMI, and like many firsts it was much quicker and much less memorable than I’d anticipated. -I was able to do all the other updates and APIM fix over Ethernet easily once I got over this hurdle.
-I’ve always been an Apple guy. I had to get a new windows based PC for a few select programs such as Cat ET and some machining software I run. All the windows computers I’ve had before got painfully slow quickly so I’ve avoided internet browsing or installing any programs that weren’t absolutely necessary. This computer has Never seen social medial. This computer has never seen a boob. Not a single one. Now that I think about it I feel really sorry for it


I’m certainly not typing all this out here as an encouragement for anyone to do this themselves. I consider the owner of my local small family dealership a friend and if I had really screwed this thing up he would’ve gave me something to drive end head warranty cover it no problem. He’s been short on techs for this type work is the only reason gave it a whirl.

You both scare and intrigue me. You remind me of tech support people I’ve worked with before. Their best works were not done while they were sober.

 

[Snakebitten]

Question for the gurus...

I had a fella ask me to look up his VIN because he was notified of a 2.8.2 failure.

First I explained how if it were me I'd get a charger on the battery and make sure the trucks battery management system was going to vouch for the truck on the next OTA attempt for 2.8.2 ?

But then I checked FDRS and found far fewer available updates than expected for a 2021 Raptor that was waiting on 2.8.2

Maybe my memory is fading since it's been a few months for me and my previous 2021 Powerboost, but wasn't 2.8.2 fairly hefty? Surely it included an APIM module update?

Is it possible that an OTA first-failure, since it's not deemed a permanent failure (yet), removes the updates from the FDRS queue until its deemed a permanent failure?

Fella claims that he has never received an OTA and this failed 2.8.2 was the first OTA activity his Raptor has ever shown him.

I sure wouldn't want to give him incorrect feedback.

 

[Jesse-Infotainment]

Question for the gurus...

I had a fella ask me to look up his VIN because he was notified of a 2.8.2 failure.

First I explained how if it were me I'd get a charger on the battery and make sure the trucks battery management system was going to vouch for the truck on the next OTA attempt for 2.8.2 ?

But then I checked FDRS and found far fewer available updates than expected for a 2021 Raptor that was waiting on 2.8.2

Maybe my memory is fading since it's been a few months for me and my previous 2021 Powerboost, but wasn't 2.8.2 fairly hefty? Surely it included an APIM module update?

Is it possible that an OTA first-failure, since it's not deemed a permanent failure (yet), removes the updates from the FDRS queue until its deemed a permanent failure?

Fella claims that he has never received an OTA and this failed 2.8.2 was the first OTA activity his Raptor has ever shown him.

I sure wouldn't want to give him incorrect feedback.

All raptors are Job 2 so they shipped at levels of software jobs ones were trying to get to. So the job 2 had updates but way fewer than the job 1.

Sorry made a mistake. Even I get messed up
2.8.2 has been different for job 2 what’s funny is they now have the same gateway and apim version as job 1 where they didn’t before.

The updates in that list I have not seen in any OTA package

 

[Snakebitten]

All raptors are Job 2 so they shipped at levels of software jobs ones were trying to get to. So the job 2 had updates but way fewer than the job 1.

Sorry made a mistake. Even I get messed up
2.8.2 has been different for job 2 what’s funny is they now have the same gateway and apim version as job 1 where they didn’t before.

The updates in that list I have not seen in any OTA package

Always on top of things for me Jesse. Thanks.

So looking at that Raptors FDRS snapshot above, whatever updates are included in the failed 2.8.2 OTA, they ARE in that FDRS list?

In other words, just because Ford IS attempting to update his Raptor via OTA, Ford hasn't removed the various updates from the FDRS list. Some portion of that list in the snapshot is what makes up his trucks 2.8.2 package.

 

[Jesse-Infotainment]

Always on top of things for me Jesse. Thanks.

So looking at that Raptors FDRS snapshot above, whatever updates are included in the failed 2.8.2 OTA, they ARE in that FDRS list?

In other words, just because Ford IS attempting to update his Raptor via OTA, Ford hasn't removed the various updates from the FDRS list. Some portion of that list in the snapshot is what makes up his trucks 2.8.2 package.

To me they look like they are not. If you can send me the vin and I can show you what is in it

Sponsored