ECU module programming guide using FDRS

[rugedraw]

What is the new APIM update supposed to do when it arrives?

See attached.

Sponsored

 

[coadr]

It has been happening 80% of the time when I start my truck.

I'd say it's probably a coin flip over here but by god is it annoying

 

[rugedraw]

Just took my truck out for lunch. When I come back to my truck and start it, touchscreen won't come on. I do the ol' APIM reset-a-roo and the screen stays black. Turned it off, and restarted it and still nothing. Now I see this new code saying my APIM lost comms with the nav display module. Looks I got a fun night of pin-point tests with FDRS ahead of me.

I swear, if @Ford Motor Company comes on here asking me for my VIN, I am going to lose my shit! ?

Good thing I got that ESP. Warranty ran out 6 weeks ago.

 

[RickBullotta]

I had my truck in for some basic service today and asked about the mysterious dealer-only BCM update. The tech said there was nothing for my truck that would suggest it was necessary (no TSBs or other service recommendations), so I'm just going to ignore it.

 

[Kanuck]

It would be interesting to find out exactly what this update was created to correct in the BCM and what TSB it is tied too, if any.

 

[JEB]

Just took my truck out for lunch. When I come back to my truck and start it, touchscreen won't come on. I do the ol' APIM reset-a-roo and the screen stays black. Turned it off, and restarted it and still nothing. Now I see this new code saying my APIM lost comms with the nav display module. Looks I got a fun night of pin-point tests with FDRS ahead of me.

I swear, if @Ford Motor Company comes on here asking me for my VIN, I am going to lose my shit! ?

Good thing I got that ESP. Warranty ran out 6 weeks ago.

In FDRS, there should be a Guided Routine called Sync Touchscreen/Information and Entertainment Display to help you diagnose.

 

[rugedraw]

In FDRS, there should be a Guided Routine called Sync Touchscreen/Information and Entertainment Display to help you diagnose.

Thanks.......I'll start there when I get home later.

 

[Big Dog Daddy]

Started on a new to me 2021 Powerboost in August 2024 with FDRS, tried following all the instructions to get my APIM updated (USB, ethernet, etc), ended up following the "just leave the flash drive in the port for a few weeks" wisdom, pulled it out after a month of no action before a 2 week vacation roadtrip, put it back in with no confidence after, and finally broke the digital dam about a week ago, completely out of the blue.
Bought another 2-day FDRS license and got it up to 23159 version 915. Only thing remaining in the queue is the steering column control update - anybody familiar with that one? I'd really like to be finished with this monotonous journey...

Nice to see another 21 be lifted from its comatose state. There's no reason not to do the SCCM update while you're there.

If you have a blue cruise truck. It's important.

 

[Gord0]

Started on a new to me 2021 Powerboost in August 2024 with FDRS, tried following all the instructions to get my APIM updated (USB, ethernet, etc), ended up following the "just leave the flash drive in the port for a few weeks" wisdom, pulled it out after a month of no action before a 2 week vacation roadtrip, put it back in with no confidence after, and finally broke the digital dam about a week ago, completely out of the blue.
Bought another 2-day FDRS license and got it up to 23159 version 915. Only thing remaining in the queue is the steering column control update - anybody familiar with that one? I'd really like to be finished with this monotonous journey...

To add on to what's above. It looks like you're at least one version behind on sync. Hopefully another series of updates pops up for you.

 

[FirstFord]

I'm a soon-to-be FDRS newbie, on the list to borrow the Mongoose cable. I don't have a clue as to what I'm doing, so I have been reading the Instructional Guides ahead of time in an effort to try to cure some of my ignorance, and I already need clarification on a few points.

• From reading some of the threads, I get the impression that the FDRS update process can take 1 or 2 hours, or many, many hours (even days?). So, what is my role during this time? Again, based on some different threads, I get the impression that I need to be present in order to interact with FDRS, to provide responses, yet in other threads, I get the impression that you can walk away and take care of other tasks while FDRS does its thing. I’d like some clarification on this.
• It has been recommended to read TSB 22-2226, which describes the service procedure for using FDRS. In the TSB, it stated, “When prompted, connect the USB flash drive to the FDRS.” This didn't make any sense to me. I assume what was being described was plugging the USB into a laptop that has FDRS running on it?
• The same TSB also states, “When the pop-up stating Restart Required appears on the touchscreen, turn the ignition OFF, open and close the driver’s door, and wait 10 minutes.” I have push-button start. I can't reach the ignition button without opening the door first. Do I need to sit in the driver's seat for all of those hours while FDRS does its thing?
• It also recommends using an Ethernet cable. Is Wi-Fi not suitable/acceptable?
• In the Instructional Guide, it states that your PC/laptop should have a minimum 4GB RAM, but elsewhere I read threads stating 8GB is minimum and 12 is recommended. So, what’s up? Is it actually 8/12GB and the Instructional Guide has not been updated?
• USB size: In one place, I read 32GB is required, and elsewhere I read 64GB.
• Regarding the Mongoose cable itself: It is understandable that the Windows laptop that is to be used would need a driver to run the Mongoose, but in the Installation Guide, when describing the process of installing the driver, it stated: “NOTE: Follow the steps below ONLY if you own the Mongoose-Plus J2534 interface.” So, I won’t need to download a driver for the Mongoose?

 

[SilverPigeon]

I'll turn your bullets into numbers:
1. You'll need interaction when:
- operating FDRS functions like network scan, formatting and creating USB etc.
- when instructed, inserting USB into truck and waiting for it to commence the software update
- when instructed, turning off ignition, leaving door open
- turning on ignition and waiting for the update complete message on SYNC before removing the USB

between these interactions, the time span is usually a few minutes, but some updates can take a very long time. At any time you can check back, but you might find that you've "wasted" some updating time if an update either was very short or had an error.

2. The computer running FDRS. only do this if instructed to do so, otherwise, continue with the next update, remembering to format the USB drive as exFAT between each update.

3. You will find that SYNC may very well instruct you to leave the driver's door OPEN and wait the 10 minutes. I have actually never needed to close the driver's door, for any part of the update process. If you were ever instructed to do this, wind the window down before turning the ignition off.

4. The mongoose is a USB-connected device to the computer and connects to the truck using the OBD port. If your home wi-fi is reliable, operation of FDRS and it downloading files for installation onto a USB drive will be fine. There is a particular issue that may require use of an Ethernet connection into a hidden port in the console (I can't remember which TSB that's in) but only in that particular case.

5. 8GB RAM minimum these days for assurance of proper operation. 16GB RAM preferred and should not be hard to obtain a computer with this at modest cost.

6. 32GB USB drives are very common and have more than enough space. Choose high quality drives like genuine SANDisk drives, preferable USB 3.0 minimum for speed.

6. Install all of the Drew Technologies software referenced in the guide This will also install a program called the J2534 Toolbox. That software will include the driver. You can run the toolbox program and from there check If an updated driver is required. If so, follow instructions (might be as simple as clicking a button to update). Windows might also detect the mongoose needing a new driver when first connecting it to the computer. None of this was necessary in my or most people's cases.

The mongoose full name is "Mongoose-Plus Ford2" or some such. It is what is being referred to there as it is a J2534 interface device.

Always have a constant voltage supply of at least 20A connected to the vehicle for assurance of no power issues during the FDRS session. In most cases, you can get away with a 10A battery charger, but that would make me uncomfortable.

 

[fordtruckman2003]

I'm a soon-to-be FDRS newbie, on the list to borrow the Mongoose cable. I don't have a clue as to what I'm doing, so I have been reading the Instructional Guides ahead of time in an effort to try to cure some of my ignorance, and I already need clarification on a few points.

• From reading some of the threads, I get the impression that the FDRS update process can take 1 or 2 hours, or many, many hours (even days?). So, what is my role during this time? Again, based on some different threads, I get the impression that I need to be present in order to interact with FDRS, to provide responses, yet in other threads, I get the impression that you can walk away and take care of other tasks while FDRS does its thing. I’d like some clarification on this.
• It has been recommended to read TSB 22-2226, which describes the service procedure for using FDRS. In the TSB, it stated, “When prompted, connect the USB flash drive to the FDRS.” This didn't make any sense to me. I assume what was being described was plugging the USB into a laptop that has FDRS running on it?
• The same TSB also states, “When the pop-up stating Restart Required appears on the touchscreen, turn the ignition OFF, open and close the driver’s door, and wait 10 minutes.” I have push-button start. I can't reach the ignition button without opening the door first. Do I need to sit in the driver's seat for all of those hours while FDRS does its thing?
• It also recommends using an Ethernet cable. Is Wi-Fi not suitable/acceptable?
• In the Instructional Guide, it states that your PC/laptop should have a minimum 4GB RAM, but elsewhere I read threads stating 8GB is minimum and 12 is recommended. So, what’s up? Is it actually 8/12GB and the Instructional Guide has not been updated?
• USB size: In one place, I read 32GB is required, and elsewhere I read 64GB.
• Regarding the Mongoose cable itself: It is understandable that the Windows laptop that is to be used would need a driver to run the Mongoose, but in the Installation Guide, when describing the process of installing the driver, it stated: “NOTE: Follow the steps below ONLY if you own the Mongoose-Plus J2534 interface.” So, I won’t need to download a driver for the Mongoose?

What sync version do you have?

If you are thinking of doing the complicated process to force broken update with the TSB, first try USB.

Several here have successfully got their truck unstuck by driving around with USB stick in the truck for 2-4 weeks. Downside is you need multiple FDRS sessions. Once to create the USB, and again after it finally installs to continue updates. This is more likely to succeed than the forced process with network cables in the TSB.


Additional things to know:
Turn off non essentials before you begin.
Turn off automatic wipers, HVAC system, I turn off the radio too. If you do not turn off automatic wipers your wipers will run continuously when the truck is in "update mode."

Button is same as key.
Key on, engine off is just pushing button in accessory mode.
Key off is pushing button to off, then I open driver door and wait for center screen to go off.

When directions tell you to START the vehicle, you don't need to do that.
Key on, engine off is enough to get updates going on the sync screen over USB.
Then key off, exit for 5-10 minutes when prompted.
(This will not work if you are on the broken sync versions that need USB plugged in for a month.)

USB updates I sit in driver seat until they install. It can take up to 10 minutes for update to start. You'll see messages at top of screen and you can tap on that to see progress. For USB updates I turn the radio on because they can install normally while driving and I get bored sitting in silence. I turn it back off for whatever is next that isn't USB.

 

[Big Dog Daddy]

What sync version do you have?

If you are thinking of doing the complicated process to force broken update with the TSB, first try USB.

Several here have successfully got their truck unstuck by driving around with USB stick in the truck for 2-4 weeks. Downside is you need multiple FDRS sessions. Once to create the USB, and again after it finally installs to continue updates. This is more likely to succeed than the forced process with network cables in the TSB.

@FirstFord has a 2022 his truck should be fine. The only trucks that could have been stuck with the bad update were 2021 Job 1 trucks, and those were produced prior to 7/8/2021.

 

[graves1907]

About to start a fun day of updates! Just confirming that the first page is still the latest and greatest walkthrough, haven't done this in 2 years....

 

[FirstFord]

@SilverPigeon and @fordtruckman2003 - THANK YOU! VERY informative! I'm going to copy your answers and add them to my FDRS prep folder that I've got going. The bad news is that more than likely, I'll have more questions still to come.

I'm going to follow up on some of the answers:

Button is same as key.
Key on, engine off is just pushing button in accessory mode.
Key off is pushing button to off, then I open driver door and wait for center screen to go off.

I will fully admit that I'm an ignoramus on this stuff, but even I know that the ignition button is the same as the ignition key. ? What I was trying to get at - and still don't quite understand - is the actual physical movement to achieve the instructions: "turn off the ignition then open the door." I don't understand how that can be done unless you are sitting in the driver's seat throughout that stage of the process. What I mean is, if my truck had a physical key ignition on the steering column, I could reach through the open driver's window and turn off the ignition, then open the door - as instructed. But with a push-button ignition, there is no way I can reach through an open window and reach that button, meaning I have to open the door first to reach the ignition button. So, what has just dawned on me - and I apparently missed this in the answers provided - is that I was coming from the perspective of being outside the truck during this and trying to reach in. It is just now dawning on me that at the particular stage where the ignition switch is off/on and the door is open/closed is a stage where you are already sitting in the driver's seat to interact with FDRS. Correct?

What sync version do you have?

If you are thinking of doing the complicated process to force broken update with the TSB, first try USB.

Sync version 23291, revision 1049. I don't know for sure, but I don't think my version is one that is "stuck" because I just got an OTA day before yesterday (although it appeared to be a repeat OTA). I have mentioned in a different thread that I do seem to get updates - but not all of them, based on @rugedraw 's sheet (and maybe I'm not supposed to get ALL of them). I don't really have a complaint regarding the OTA process - the purpose in going through the FDRS exercise is to get the latest IPMA update so that I can make one last desired change in FORScan.

Sponsored