ECU module programming guide using FDRS

[rugedraw]

That looks to be the PTS version of what I download from the Motorcraft website. You would click Download File and then open it with a reader like XML Notepad. To save you the trouble, here is your data for the DSP:

<NODEID>
783
<F10A>ML3T-14C656-BJ</F10A>
<F110>DSJL1T-18B849-BP</F110>
<F111>JL1T-14F171-CA</F111>
<F113>ML3T-18B849-BJ</F113>
<F160>061502</F160>
<F161>021902</F161>
<F188>ML3T-14C589-BK</F188>
<F18C>4036645132171528</F18C>
</NODEID>

Your software version is different from mine (-BH) and different from the version currently available on FDRS (-BN) that, for now, fails to install. I wouldn't waste $50 on it until it gets fixed.

Thank you for that. So it does match with what my FDRS history shows. Going back to the SSM you posted, it did install even though I didn't reset the DSP. Has anyone tried resetting the DSP with the new update that just came out for it to see if it goes through?

Sponsored

 

[JEB]

Thank you for that. So it does match with what my FDRS history shows. Going back to the SSM you posted, it did install even though I didn't reset the DSP. Has anyone tried resetting the DSP with the new update that just came out for it to see if it goes through?

I did. No joy. I cut and restored power. Then retried the install. The FDRS prompts said it updated the module to -BN but a subsequent network scan showed that it was still on -BH.

 

[JFR0317]

Even though I had received by OTA and installed 4.3.2 on May 4th, the IPC update that just dropped showed up in FDRS for my truck today and let me install it.

 

[Jesse-Infotainment]

Even though I had received by OTA and installed 4.3.2 on May 4th, the IPC update that just dropped showed up in FDRS for my truck today and let me install it.

The IPC OTA was only one half the update. it updated the calibration. THe FDRS update included a Strategy update also

Those that have not gotten the OTA will do both files.

 

[JFR0317]

Got it! Thanks, Jesse.

 

[Mike G]

I'm going to post on the VIN look up thread to see if any updates show up for my truck in FDRS.

IPC and DSP are showing.

 

[Airborne_Ape]

Anyone that updated the DSP notice the Chimes running through the cluster and not the speakers?

Mine was doing it all the time I had to revert to the old DSP software to make it act normal again.

I have a theory of what the DSP update is supposed to fix which might also explain this.

There's been a persistent bug with the B&O audio system for a while where if the vehicle is put into reverse before the APIM has a chance to fully boot up while an external media source connected with auto-resume enabled and there is a rear obstruction which makes the park aid chime, then main audio channels will be limited to the rear speakers only until the next ignition cycle.

This bug can usually be replicated by leaving a media source connected such as CarPlay, playing a playlist with the ignition on, turning off the ignition without pausing music at the media source, opening the door to simulate getting out without disconnecting audio source, lock & unlock to sleep wake modules, open door again to simulate getting in, turning the ignition on, putting the vehicle in reverse while an object is behind the vehicle before the Sync 4 splash screen has a chance to finish its animation.

I reported this bug in the past, maybe my request didn't go straight into the trash can after-all lol.

Occasionally if a media source automatically resumes while the rear parking aid chime is sounding this bug will persist until the next ignition cycle and the modules have a chance to reboot.

Perhaps the DSP update is meant to fix this by changing the chime strategy. Change logs would help, but that's too-wishful thinking.

 

[Snakebitten]

^ Great post. Very well explained.
And I think I have experienced just such a glitch once or twice.

But normally I am so slow and deliberate when getting into the truck and doing my "pre-check" before takeoff that I rarely experience the kind of glitches that would result from interrupting the trucks boot-up sequences?

I'm actually kind of stunned that Ford can get the "Ready" light on the instrument cluster so quickly. I wonder if they would slow it down just a couple of seconds, and write into the code a bit wider window of time for all the handshakes between modules, if these trucks (Powerboost especially) might be less buggy?

 

[JEB]

I have a theory of what the DSP update is supposed to fix which might also explain this.

There's been a persistent bug with the B&O audio system for a while where if the vehicle is put into reverse before the APIM has a chance to fully boot up while an external media source connected with auto-resume enabled and there is a rear obstruction which makes the park aid chime, then main audio channels will be limited to the rear speakers only until the next ignition cycle.

This bug can usually be replicated by leaving a media source connected such as CarPlay, playing a playlist with the ignition on, turning off the ignition without pausing music at the media source, opening the door to simulate getting out without disconnecting audio source, lock & unlock to sleep wake modules, open door again to simulate getting in, turning the ignition on, putting the vehicle in reverse while an object is behind the vehicle before the Sync 4 splash screen has a chance to finish its animation.

I reported this bug in the past, maybe my request didn't go straight into the trash can after-all lol.

Occasionally if a media source automatically resumes while the rear parking aid chime is sounding this bug will persist until the next ignition cycle and the modules have a chance to reboot.

Perhaps the DSP update is meant to fix this by changing the chime strategy. Change logs would help, but that's too-wishful thinking.

Newest DSP software is to address a loud pop followed by static upon start-up in the B&O systems, not misdirected chimes.

SSM 51663 2021-2023 F-150/Expedition - Pop Noise And/Or Static In Speakers At Start Up

2021-2023 F-150/Expedition may exhibit a pop noise and/or static in the speakers at start up that cannot be turned down or off using the audio system controls. To correct the condition, reprogram the audio digital signal processing module (DSP) to the latest software level using the Ford Diagnosis and Repair System (FDRS) diagnostic scan tool. For claiming, use causal part 18B849 and applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

 

[abd79]

Is there any update to Ford fixing the CMR update where it fails on security?

 

[RickBullotta]

Newest DSP software is to address a loud pop followed by static upon start-up in the B&O systems, not misdirected chimes.

SSM 51663 2021-2023 F-150/Expedition - Pop Noise And/Or Static In Speakers At Start Up

2021-2023 F-150/Expedition may exhibit a pop noise and/or static in the speakers at start up that cannot be turned down or off using the audio system controls. To correct the condition, reprogram the audio digital signal processing module (DSP) to the latest software level using the Ford Diagnosis and Repair System (FDRS) diagnostic scan tool. For claiming, use causal part 18B849 and applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

F*cking Ford does it again. I installed this DSP update, and like everyone else, it is still showing in FDRS - but that's not the bad part. Just yesterday I had the rear speakers cut out when on CarPlay, which has NEVER HAPPENED BEFORE until this sh*tty update. Someone needs to fire their entire software team. This new guy from Apple doesn't seem to have fixed a damn thing with the quality of their OTA process.

 

[JEB]

F*cking Ford does it again. I installed this DSP update, and like everyone else, it is still showing in FDRS - but that's not the bad part. Just yesterday I had the rear speakers cut out when on CarPlay, which has NEVER HAPPENED BEFORE until this sh*tty update. Someone needs to fire their entire software team. This new guy from Apple doesn't seem to have fixed a damn thing with the quality of their OTA process.

I don't know for sure whether you can blame the software itself this time. For me and at least one other person (@Mike G) it looks like the software failed to install. FDRS says it was supposed to update the software to -BN but it stayed at the same level (-BH for me, -AJ for Mike) after the update. Going through the downloaded files from FDRS, something looks hinky with the bootloader. Usually, the bootloader file starts with M for me (M=2021) but this time it started with an F, which makes no sense.

So, use FORScan, FDRS or the as-built data and verify if your DSP software updated to -BN. If it didn't, the software failed to install and your issue could be for reasons other than the software. Perhaps just the act of resetting the DSP during the install attempt threw something off. Try a forced module reset or cut the power to the DSP, give it some time to power down and then power back up and see if that does anything.

 

[RickBullotta]

I don't know for sure whether you can blame the software itself this time. For me and at least one other person (@Mike G) it looks like the software failed to install. FDRS says it was supposed to update the software to -BN but it stayed at the same level (-BH for me, -AJ for Mike) after the update. Going through the downloaded files from FDRS, something looks hinky with the bootloader. Usually, the bootloader file starts with M for me (M=2021) but this time it started with an F, which makes no sense.

So, use FORScan, FDRS or the as-built data and verify if your DSP software updated to -BN. If it didn't, the software failed to install and your issue could be for reasons other than the software. Perhaps just the act of resetting the DSP during the install attempt threw something off. Try a forced module reset or cut the power to the DSP, give it some time to power down and then power back up and see if that does anything.

Currently it's ML3T-14C589-AJ.

 

[JEB]

Currently it's ML3T-14C589-AJ.

Your update failed to install, which also explains why it didn’t clear the FDRS queue. You’ll need to wait until Ford fixes it, which might take awhile. It took several months for them to get the GSM right—a little less time for the ABS. Hopefully not as long this time. The pop and static is unsettling and dangerous.

What B&O system do you have? I don’t recall ever updating my DSP software in the past so I can’t figure out why I’m starting with a higher version than you and @Mike G.

 

[Jesse-Infotainment]

Currently it's ML3T-14C589-AJ.

That is the old one. The new one Is

ML8T-14C589-AB

It doesnt reflect in FDRs that the new one is installed that is why it doesnt go away in the updates

Sponsored