ECU module programming guide using FDRS

[JEB]

According to his profile, he doesn't have a 2021 truck yet, although he might and hasn't updated yet, kinda like Ford?

I'd be willing to PayPal him for his 48 hour FRDS license if it would FIX his broken truck and bring him good cheer!

Already complaining about a truck he doesn’t even have yet? Good grief. Snakebitten, you are a far nicer guy than I am. Where’s the head shaking in disgust emoji?

Sponsored

 

[azDcab21]

Does this manual update on Job1 year trucks get you to the Job2 builds software status? i.e. BC, cameras on at speed, etc... I've read though the thread and am debating to take the dive. I'm currently at: Sync4: 21146 Revision 145 with a Job1 truck. Not sure what I get going the manual route vs. waiting. I've gotten 2 OTA since owning the truck so i'm not sure if i'm in the "stuck" mode that others has mentioned.

 

[iceman77]

Iceman. I don’t remember where you posted about bad behavior with the adaptive cruise control, but something weird happened on my 4-hour drive this morning. When I tested my setup after your first post, I configured the cruise control to recognize speed signs. Like your system, mine also didn’t keep the setting past one ignition cycle. But I never actually used the cruise control or set it back to default. Multiple days and ignition cycles later, when I used cruise control for the first time this morning after updating my APIM, it worked exactly like it was supposed to. The adaptive cruise control changed the speed setting according to the changing speed limit signs. When I went into the settings, however, it still looked like cruise control was off. Not just the “smart” part but the entire function. So, at least on my system, it did work as I configured it a few days ago. The display just didn’t show the settings accurately past one ignition cycle.

I’m not sure if this is a better or worse result. But there it is.

Yes, the APIM settings are messed up. Not the ACC. If “I set it and forget it” it works as expected. The issue arises when you restart your truck and you purposely go to SYNC Settings -> Features -> Cruise Control. That’s when it messes it up. It does not just deactivates the Speed Sign Recognition but the Cruise Control mode itself is messed up (no CC mode is selected):

When you tap "Adaptive Cruise Control" it will show that your "Speed Sign Recognition" is deactivated. But if fact, it deactivates this feature right when you enter this menu. So as long as you re-activate it and don’t enter this menu it works!

It seems to me, that the APIM software has a bug, where it does not retain this setting in its EEPROM and when you enter this AAC menu, default values are loaded. I believe this bug was introduced when their developers moved the SSR under AAC menu

 

[JEB]

Yes, the APIM settings are messed up. Not the ACC. If “I set it and forget it” it works as expected. The issue arises when you restart your truck and you purposely go to SYNC Settings -> Features -> Cruise Control. That’s when it messes it up. It does not just deactivates the Speed Sign Recognition but the Cruise Control mode itself is messed up (no CC mode is selected):

When you tap "Adaptive Cruise Control" it will show that your "Speed Sign Recognition" is deactivated. But if fact, it deactivates this feature right when you enter this menu. So as long as you re-activate it and don’t enter this menu it works!

It seems to me, that the APIM software has a bug, where it does not retain this setting in its EEPROM and when you enter this AAC menu, default values are loaded. I believe this bug was introduced when their developers moved the SSR under AAC menu

Yeah, I guess I didn’t completely understand what was happening. But, at least there might be a workaround—set it how you want it once and then don’t look at it again. Only look when you want to make changes, at which point you’ll need to start over.

 

[iceman77]

Yeah, I guess I didn’t completely understand what was happening. But, at least there might be a workaround—set it how you want it once and then don’t look at it again. Only look when you want to make changes, at which point you’ll need to start over.

That's exactly my philosophy! Set it and forget it! My issue was, that I initially entered this menu each time I started the truck (just to verify if it retained the previous value). Then I learned, that this action actually deactivated already active SSR. So I reactivated it, and I left it alone. I just don't enter this menu section, until Ford developers fix this. And ACC with SSR works just fine!

 

[Ajzride]

Got mine all updated today. One thing that I ran across I haven't seen mentioned yet, is that both of my USB updates failed the post-upgrade check. I had to re-run the verification (not re-run the update) twice to get it to pass.

 

[Ajzride]

Working on updating all the modules for the Mach-E while I have my two day license. I updated the BCM and now all of the TPMS sensors need to be paired to the car again. The tool to pair them is cheap, but not available locally. Make sure you have the TPMS pairing tool before you do the BCM or you will be making a trip to the tire store to have it fixed since your two day license will expire before you get a training roll delivered.

 

[jcaspar]

Does this manual update on Job1 year trucks get you to the Job2 builds software status? i.e. BC, cameras on at speed, etc... I've read though the thread and am debating to take the dive. I'm currently at: Sync4: 21146 Revision 145 with a Job1 truck. Not sure what I get going the manual route vs. waiting. I've gotten 2 OTA since owning the truck so i'm not sure if i'm in the "stuck" mode that others has mentioned.

My truck is the same as yours, Job 1 (1/21 build) with 21146 Rev 145 as latest update. I did the three line change in Forscan here and now have bed/360 and hitch camera at speed. Worth a try before going the FDRS route if the cameras are what you want. I do not think anyone has been able to activate BlueCruise with an FDRS update as it is a subscription item for us Job 1 trucks. Hopefully from Ford soon!

 

[Ajzride]

Do you actually need FDRS to complete the APIM update after the USB stick is built? I've seen several post saying it took a couple of days to kick off. By then a 2-day FDRS license would have expired. I know when I did mine the APIM kicked right off and completed no problems, and then FDRS validated the files and cleared a bunch of DTCs. I'm wondering if people with stubborn APIMs are going to be on the hook for a second license purchase just to wrap up the APIM update.

 

[azDcab21]

My truck is the same as yours, Job 1 (1/21 build) with 21146 Rev 145 as latest update. I did the three line change in Forscan here and now have bed/360 and hitch camera at speed. Worth a try before going the FDRS route if the cameras are what you want. I do not think anyone has been able to activate BlueCruise with an FDRS update as it is a subscription item for us Job 1 trucks. Hopefully from Ford soon!

Thanks. Sounds like a good reason to go the forecast route for cameras at speed plus other goodies and wait for ford on bc.

 

[speedracercjr]

Got a whole bunch of off brand usb sticks in yesterday afternoon, of course none of them worked. Ice, Jesse, JEB and everyone else I appreciate your help but I don't know what else to do. I guess I'm stuck waiting for this miracle 1.7.1 fix to come down from the heavens (FORD) and fix my truck.

 

[iceman77]

Do you actually need FDRS to complete the APIM update after the USB stick is built? I've seen several post saying it took a couple of days to kick off. By then a 2-day FDRS license would have expired. I know when I did mine the APIM kicked right off and completed no problems, and then FDRS validated the files and cleared a bunch of DTCs. I'm wondering if people with stubborn APIMs are going to be on the hook for a second license purchase just to wrap up the APIM update.

No! Once APIM update completes the update from the USB flash drive it will report the new version files to the mothership.

 

[JEB]

Got a whole bunch of off brand usb sticks in yesterday afternoon, of course none of them worked. Ice, Jesse, JEB and everyone else I appreciate your help but I don't know what else to do. I guess I'm stuck waiting for this miracle 1.7.1 fix to come down from the heavens (FORD) and fix my truck.

I’m really sorry this isn’t working for you. Before throwing in the towel, there might be two other things you can look into. First, when you say you have tried multiple kinds of flash drives, what do you mean by that? Are you creating new drives directly from FDRS or are you just copying the files from drive to drive? If you are doing the latter, my concern is that you might be missing hidden files on the original drive that essentially make it bootable. I would try making a new drive from scratch from FDRS and if you want to try different drives after creating a new master copy, clone it so you know subsequent copies are exact copies.

Second, you might want to reach out to Jesse to see if the PMI procedure might work. Using this route, you would be treating the whole software process the way you would if you installed a replacement module and needed to program it for the first time. Maybe that will get you over the hump by overwriting the existing software on your APIM instead of just updating it.

 

[speedracercjr]

I’m really sorry this isn’t working for you. Before throwing in the towel, there might be two other things you can look into. First, when you say you have tried multiple kinds of flash drives, what do you mean by that? Are you creating new drives directly from FDRS or are you just copying the files from drive to drive? If you are doing the latter, my concern is that you might be missing hidden files on the original drive that essentially make it bootable. I would try making a new drive from scratch from FDRS and if you want to try different drives after creating a new master copy, clone it so you know subsequent copies are exact copies.

Second, you might want to reach out to Jesse to see if the PMI procedure might work. Using this route, you would be treating the whole software process the way you would if you installed a replacement module and needed to program it for the first time. Maybe that will get you over the hump by overwriting the existing software on your APIM instead of just updating it.

By different flash drives I mean different brands, and different sizes (8GB, 16GB, 64GB, 128GB & 256GB) and I even went on a tear when formatting of trying different allocation unit sizes. I made three "master" usb drives directly from FDRS and then only cloned them. The only action I can get is from formatting as FAT32 which throws an error on the truck. I did that just to verify it was actually reading the port.

I'm gonna guess that needs FDRS, oof I should have just signed up for the month long access at this point. @Jesse-Infotainment aren't you in Dallas? I live in Houston and travel up there about once a month or so. Tacos and beer payment????

 

[Jesse-Infotainment]

By different flash drives I mean different brands, and different sizes (8GB, 16GB, 64GB, 128GB & 256GB) and I even went on a tear when formatting of trying different allocation unit sizes. I made three "master" usb drives directly from FDRS and then only cloned them. The only action I can get is from formatting as FAT32 which throws an error on the truck. I did that just to verify it was actually reading the port.

I'm gonna guess that needs FDRS, oof I should have just signed up for the month long access at this point. @Jesse-Infotainment aren't you in Dallas? I live in Houston and travel up there about once a month or so. Tacos and beer payment????

No payment needed bud.. come up here and we will do whatever we need to get you up to date.

Ill take the tacos though.. I know a few good spots!

Sponsored