ECU module programming guide using FDRS

[Jmeo]

Ah, I’m getting the picture/setup now. Nice garage btw

Thanks buddy, it’s been a long road getting to this point in my life. I am beyond happy with how it turned out.

Sponsored

 

[speedracercjr]

This is why I want to keep the desktop on the workbench. I have a beautiful hutch setup, and a permanently mounted setup would be useful in so many more ways than a portable option that I wouldn’t use very much.

Nice setup!

As for the desktop I would agree, I had one in my basement shop/brewery and mounted the monitor straight to the wall. It was great for having access to Youtube, forums, whatever at all times. I ended up getting a mini PC about the size of a sandwich and mounted it behind the monitor as well so you couldn't see anything. One thing to note is keep an eye on dust, you'll likely need to clean the pc out from time to time.

 

[Snakebitten]

It's not like you wouldn't have tools in THAT garage that would only seldomly be used? ?

 

[tbinmd]

Yes, this is how i operate 90% of the time. Mac laptops into Windows Desktops. Chrome works across all OS

Just download Microsoft Remote Desktop from the Mac app store and you can RDP into the windows laptop.

 

[Jmeo]

Nice setup!

As for the desktop I would agree, I had one in my basement shop/brewery and mounted the monitor straight to the wall. It was great for having access to Youtube, forums, whatever at all times. I ended up getting a mini PC about the size of a sandwich and mounted it behind the monitor as well so you couldn't see anything. One thing to note is keep an eye on dust, you'll likely need to clean the pc out from time to time.

Exactly. The computer I have is one of those small ones you speak of, so it will be great.

The hutch is closed when I’m not doing anything, but you bring up a good point. I will be sure to prevent dust as much as possible

It's not like you wouldn't have tools in THAT garage that would only seldomly be used? ?

Lol, yup. You know how it goes, we spend a lifetime (52 for me) buying and collecting tools. I am a shady tree mechanic, and have been modifying my mustangs and F150’s for 30 years. I also am one of the two mechanics (I have too many hats) at the firehouse, and I work on the apparatus as well, when I’m not running a shift, so I have collected a few

I did not mean to derail this amazing thread, sorry for that to all of you. Now back to your regularly scheduled programs.

Jaime

 

[Ajzride]

Just download Microsoft Remote Desktop from the Mac app store and you can RDP into the windows laptop.

Yes, if you want to take time to configure firewall port forwarding to all of your different Windows Desktops/VMs. I actually have a Remote Desktop Gateway setup and I can hit all of my VMs from anywhere in the world using just Remote Desktop, but based on the post asking questions, I assumed those were all going to be more technical approaches than he wanted to deal with. Perhaps I shouldn't have made that assumption.

 

[roadPilot]

Is there any reason that the Mongoose will not work correctly if I use a USB extension cable with it? I may have available to me, a newer style small desktop computer, and monitor, that I would setup on my workbench. I think I would need to use a 10' USB extension cable to be able to reach the OBDII port.

It should work, but will not be as convenient as sitting in the truck while following on-screen instructions.

 

[tbinmd]

Yes, if you want to take time to configure firewall port forwarding to all of your different Windows Desktops/VMs. I actually have a Remote Desktop Gateway setup and I can hit all of my VMs from anywhere in the world using just Remote Desktop, but based on the post asking questions, I assumed those were all going to be more technical approaches than he wanted to deal with. Perhaps I shouldn't have made that assumption.

No, forwarding required if on the local lan. Just pointing out another option, VNC is could also be since the client is built into the Mac. But that requires a VNC server to be installed on the windows laptop.

 

[Bigjim2]

This guide outlines steps to set up your computer and how to update software in your ECU modules using Ford OEM FDRS software

DISCLAIMER: I have updated many modules using the procedure below without any major issues and literally zero failures. That does not mean failure cannot happen. Flashing ECU modules is a dangerous operation. DO THIS AT YOUR OWN RISK! I will take no responsibility for any damage to your vehicle caused by the below described procedure

Tools you will need:

- Windows PC with 4GB RAM or greater, running Windows 10 or Windows 11
- VCI Interface preferably Mongoose-Plus J2534 (can be purchased from Amazon here)
- USB Flash drive 32GB or larger (must be formatted to exFAT)
- 12V Automotive Battery Charger/Maintainer (I used this one from Amazon)

Software you will need:

- Driver software for your VCI interface
- Ford Diagnostic & Repair Software (commonly known as FDRS)

Installation and Setting up Mongoose-Plus J2534 VCI interface:

NOTE: Follow the steps below ONLY if you own the Mongoose-Plus J2534 interface

1) Download the OPUS IVS driver for your Mongoose-Plus device from here.
2) Connect your Mongoose-Plus device to your PC and launch the installer. You should be presented by the following screen:

3) Hit Install to start the installation process, when prompted, activate the device!

FDRS Software Installation

1) Download and install FDRS software from here. You will need a license to run this software and can be purchased here (2-day FDRS license cost $50)
2) Launch FDRS, you will be prompted to enter the license that you have just purchased.
3) Register an account (if you don't have one) on Motorcraft website here.
4) Log into FDRS using your Motorcraft credentials. Make sure you select Non-Dealer Motorcraft as User Type

5) Connect your VCI device to your truck's ODBII port and connect the USB cable to the PC running FDRS. Once FDRS Device Manager pops up, make sure you select Other Device, in the drop-down dialog:

Select Drew Technologies Inc. - Mongoose-Plus Ford2 if you own the Mongoose-Plus VCI device

After this you should be greeted with this screen, meaning you are ready to go!
The icons at the bottom should be all green with battery voltage shown

Running Network Test (Initial Scan)

1) Turn Ignition On, Engine Off
2) Click Read VIN from vehicle
3) Click Go to initiate Network Scan

Once completed a new tab called Toolbox will appear at the top of your FDRS screen:

On the left hand side you will see all modules detected on your truck. The ones that responded positively will be marked green. On the right hand side notice the SW Updates tab. Head over here to see all available SW updates for your modules.

Module SW Update Procedure

1) Head over to SW Updates tab in the FDRS Toolbox window.
2) If there are updates available, hit the Download button. The tool will download the necessary tools needed for the module update.
3) Once download completes the button turns green with a text "Run".

IMPORTANT: Before you proceed to the next step, connect your truck to external power supply (a good battery charger/maintainer as one listed above will do the job). DO NOT connect the negative (black) charger clamp directly to the battery monitoring sensor, it must be connected to an engine or chassis ground in order to bypass the BMS circuitry (see example here). Do not proceed unless you have solid 12.5V or more showing on your ODBII port.

4) Run the SW Update procedure and follow the on-screen prompts very carefully

Be patient, some modules take long time to update. This is especially true for IPMA module which takes almost 3 hours to complete. Therefore, it is very important to have your truck connected to external power supply (battery charger/maintainer)

NOTICE FOR FORSCAN USERS: FDRS will knock out your recent FORScan changes from your modules you are updating. It reloads your As-Built (AB) data at the end of the SW update procedure. Make sure you back-up your FORScan changes and load them back after you are done with SW updates. By time your FORScan changes get propagated to your AB data set on FORD servers, so this would not be an issue. This would only affect users performing FORScan changes and running module SW udate within short period of time. I am suspecting, that receiving OTA shortly after FORScan changes would have same effect.

If you have any questions or concerns feel free to reach out to me over DM. If I don't reply in time, reach out to other experts including, but not limited to @Jesse-Infotainment , @Bob_Mac, @JEB or @Snakebitten.

Also, I would strongly suggest to follow @Bob_Mac document, outlining the latest updates and shared knowledge related to this process. You can access his guide here.

Hi Iceman, You are the best! I did all the above on my 2021 Job1 502a and did over 7 modules...took me longer because I has to wait until I was at 80% full battery for the GEM (twice updated).

My question is on Forscan. On Forscan, I did backup all my As-Built before the FDRS updates. With all the updates and changes in the modules, if I simply restore these backup ASB, would it create an issue? I was thinking (likely incorrectly) the ASB might change and my restoring them could create an issue. Is it better to go back into each module and change what I had changed before my FDRS?

Thank you again for all your great work! Jim

 

[XLT22]

There can be configuration changes with those updates so it's best to keep track of them and re-do them manually IMO. Eventually the changes will show up on the Motorcraft site but I'm not aware of the timetable for that. I ran a network scan in FDRS after making my last changes to help it along.

 

[JEB]

Hi Iceman, You are the best! I did all the above on my 2021 Job1 502a and did over 7 modules...took me longer because I has to wait until I was at 80% full battery for the GEM (twice updated).

My question is on Forscan. On Forscan, I did backup all my As-Built before the FDRS updates. With all the updates and changes in the modules, if I simply restore these backup ASB, would it create an issue? I was thinking (likely incorrectly) the ASB might change and my restoring them could create an issue. Is it better to go back into each module and change what I had changed before my FDRS?

Thank you again for all your great work! Jim

Probably not a good idea just to reload your FORScan backups. Some module updates actually add new lines of code to the as-built data. If you try to reload your FORScan backup, there willl be a mismatch and FORScan will throw an error code. I agree with @XLT22 . Probably safest to just check your FORScan settings after the updates and manually change the ones that were overwritten.

Might not be too onerous. If you made your FORScan changes awhile ago, some of them might have already been uploaded to the Motorcraft servers and you will still have them.

 

[Bigjim2]

Probably not a good idea just to reload your FORScan backups. Some module updates actually add new lines of code to the as-built data. If you try to reload your FORScan backup, there willl be a mismatch and FORScan will throw an error code. I agree with @XLT22 . Probably safest to just check your FORScan settings after the updates and manually change the ones that were overwritten.

Might not be too onerous. If you made your FORScan changes awhile ago, some of them might have already been uploaded to the Motorcraft servers and you will still have them.

Thank you! That's what I was thinking too.

I might have misread Iceman's directions on backing up Forcan. I was thinking these modules would have updates (vaules) that weren't in there before my foreskin edits and mess up the whole deal.
Much appreciated!

 

[Jmeo]

Well, I took the dive today and got all my updates done. This did not come without a couple headaches, but I believe it was more to do with the Motorcraft website itself.

What was confusing is that I made a username and password on the Motorcraft site. Then, when I tried to purchase the FDRS license, the link brought me to a new page that kept asking for my username and password, but it kept saying it was incorrect. What I did not notice for quite some time is, now you HAVE to create a NEW account at this step, for the IDS link in order to go any further. Anywho, I finally figured it out.

I only had 4 modules that needed updating, which were PCM, ABS, WACM, and APIM. I updated the first three, then went on to use the recommended USB drive to update the AIPM without issue.
After I got those done, I now had an update waiting for the TCU. This one also needed the USB to complete. Following the footsteps laid out for us to follow, I was even sure to reformat the USB after each module update.

For me, both times I update via USB, I did not see the "remove the USB" notification. I just waited twice as long as recommended, and continued like I saw it. I was able to see that they had in fact updated when I went back to the software update tab.

Using the recommended battery charger set to 20 amps, the truck's voltage never dropped below 13 volts, so I also highly recommend getting one.

Thanks to the pioneers for blazing the trail, we are all fortunate to have you in this forum.

 

[Jmeo]

Oh, I was thinking, perhaps now I should replace my saved As-Builts with new As-Builts, now that everything has been updated? That way if I ever need to resort back to factory in the future, I will go back to today (after updates)?

 

[m_bt54]

Thank you! That's what I was thinking too.

I might have misread Iceman's directions on backing up Forcan. I was thinking these modules would have updates (vaules) that weren't in there before my foreskin edits and mess up the whole deal.
Much appreciated!

I‘m not usually the spelling police but I can’t let this typo go

Sponsored