ECU module programming guide using FDRS

[dnand]

I haven't tried it with FDRS and the Mongoose cable but tried it previously with Forscan and the Vlinker cable and could never get it to work. Kept running in to driver issues between the Mac and the VM software. If you're running Bootcamp though that might eliminate some of the complexity.

And its entirely possible that with the Mongoose cable/drivers it works just fine. As @Snakebitten said, one way to find out.

**Edit to add that I do recall hearing someone able to successfully use Forscan on a Mac with Windows so its entirely possible (likely?) that it was user error on my part.

Thank you! I'll report back once I give it a try!

Sponsored

 

[dnand]

I haven't tried it with FDRS and the Mongoose cable but tried it previously with Forscan and the Vlinker cable and could never get it to work. Kept running in to driver issues between the Mac and the VM software. If you're running Bootcamp though that might eliminate some of the complexity.

And its entirely possible that with the Mongoose cable/drivers it works just fine. As @Snakebitten said, one way to find out.

**Edit to add that I do recall hearing someone able to successfully use Forscan on a Mac with Windows so its entirely possible (likely?) that it was user error on my part.

So, I just tried installing and activating and it kept failing at activation. Safe to say, it is not worth taking the chance to use the Macbook.

 

[21PlatinumF150]

Hi all,
This forum helped me get my 21 Job 1 unstuck about a year ago. Thanks again.

Been watching all along. Over the past couple months, I’ve successfully received OTA updates. This week, I am getting errors during attempts to install Power-Up 4.3.2. According to Tonesto’s site, this update requires a Vehicle Inhibit. I’ve let it try to update on its own and have tried to initiate it manually. All attempts have failed. Could it be caused by a low battery state of charge?

Does anyone have a way to check my VIN for additional info/insight?

Thanks in advance.

VIN = 1FTFW1E82MFB93459

 

[tbinmd]

I don't have a PC but have a Macbook with Windows on it. Would this work for FDRS?

I use a MacBook Pro for my FDRS updates. This is running on an intel MacBook Pro that is running boot camp. You need to boot directly into windows and not run it as a VM. I've found running as a VM can cause issues since the VM is not directly controlling the USB ports.

 

[RickBullotta]

@Jesse-Infotainment - is there a way to see the actual files downloaded by FDRS for a specific update? I'm going to be watching the files for that DSP update to see when they actually change, so I know when to re-attempt the install. Thanks!

 

[rugedraw]

Hi all,
This forum helped me get my 21 Job 1 unstuck about a year ago. Thanks again.

Been watching all along. Over the past couple months, I’ve successfully received OTA updates. This week, I am getting errors during attempts to install Power-Up 4.3.2. According to Tonesto’s site, this update requires a Vehicle Inhibit. I’ve let it try to update on its own and have tried to initiate it manually. All attempts have failed. Could it be caused by a low battery state of charge?

Does anyone have a way to check my VIN for additional info/insight?

Thanks in advance.

VIN = 1FTFW1E82MFB93459

PTS shows the reason for failure as "OTA conditions not met" "errorCode":"204". I do not know what that means. Your truck is not recording any low battery voltage DTC's, so I doubt SOC is the reason it is failing.

 

[TJSparky]

I would also like to know if the DSP update is fixed. I know at one point Jesse mentioned it changed the sound to come out of the cluster rather than speakers.

 

[robry]

my 2023 tremor keeps getting deep sleep notifications. I did a BMS reset because I accidentally put the charger on the battery terminals (Which I recall causing BMS issues). It went away for a few weeks but now it's back. I haven't gotten anything since 4.2.2.2 as well. Any thoughts? The damn thing is 6 months old and has battery issues already, seems wild.

 

[21PlatinumF150]

PTS shows the reason for failure as "OTA conditions not met" "errorCode":"204". I do not know what that means. Your truck is not recording any low battery voltage DTC's, so I doubt SOC is the reason it is failing.

Thanks for the prompt reply. Since I usually make short trips, was hoping that connecting a battery charger /power supply might solve it. I’ll wait and see if it loads. If not, might have to get a 2 day license to overcome this one.

 

[rugedraw]

Thanks for the prompt reply. Since I usually make short trips, was hoping that connecting a battery charger /power supply might solve it. I’ll wait and see if it loads. If not, might have to get a 2 day license to overcome this one.

No need to be in a rush for this update. I got that update sent the same day you did and it failed for me, too, but for different reasons. This update only preps the truck for future updates, so no need for FOMO at this point. Save the $50 for a decent bottle of Scotch or your poison of preference.

 

[RcFlyer330]

my 2023 tremor keeps getting deep sleep notifications. I did a BMS reset because I accidentally put the charger on the battery terminals (Which I recall causing BMS issues). It went away for a few weeks but now it's back. I haven't gotten anything since 4.2.2.2 as well. Any thoughts? The damn thing is 6 months old and has battery issues already, seems wild.

how often and how long do you drive the truck? also it wouldn't hurt to go get the battery tested.

 

[robry]

how often and how long do you drive the truck? also it wouldn't hurt to go get the battery tested.

Several times a week but not daily. Usually short trips like 10-15 miles round trip (I generally try to remote start it and let it warm up a little before driving so I can get the oil nice and hot).

 

[RcFlyer330]

Several times a week but not daily. Usually short trips like 10-15 miles round trip (I generally try to remote start it and let it warm up a little before driving so I can get the oil nice and hot).

Charge the battery then go get it tested at your local autoparts store (it should be free) and see if they can give you the calculated cca. I believe +-100 cca is still a good battery. you can also take it to your local ford service department (good luck) and have them test it and possibly warranty it. lastly you could just replace the battery yourself hopefully it fixes the issue.

 

[robry]

Charge the battery then go get it tested at your local autoparts store (it should be free) and see if they can give you the calculated cca. I believe +-100 cca is still a good battery. you can also take it to your local ford service department (good luck) and have them test it and possibly warranty it. lastly you could just replace the battery yourself hopefully it fixes the issue.

I'm taking it in in a month for an oil change, tire rotation, the usual before I take it on a 1600 mile trip for vacation, I'll bug them about it then.

 

[Jesse-Infotainment]

@Jesse-Infotainment - is there a way to see the actual files downloaded by FDRS for a specific update? I'm going to be watching the files for that DSP update to see when they actually change, so I know when to re-attempt the install. Thanks!

It downloads and installs the new FIles. The vehicle submission fails to updates ford end so the update remains as available even though it did install. The update is Installing. It just doesnt update on Fords emd. this happens all the time with Ford updates.

18 Speaker

188 - ML3T-14C589-BN
F10A - ML3T-14C656-CD

8 Speaker

188 - ML8T-14C589-AB
F10A - ML3T-14C656-AJ

Sponsored