ECU module programming guide using FDRS

[JEB]

How can we revert back? Any easy way?

Before reverting back, you might want to give a revised programming procedure a shot. In the past (e.g., SSM 50739), the DSP was reprogrammed by first cutting power to the DSP to perform a hard reset and then updating the software:

SSM 50739 - 2020-2021 Various Vehicles - Audio Inoperative - No Sound From Audio Speakers -No Communication With ACM Or DSP - DTC U1084, U0237 And/Or U0238
Some 2020-2021 Escape vehicles and 2021 F-150/Mustang Mach-E/Expedition/Explorer vehicles built on or before 22-Nov-2021 may exhibit a concern of the audio inoperative, no sound from audio speakers, chimes default to coming through the Instrument cluster, no communication with audio control module (ACM) or digital signal processor (DSP) module, and/or DTC U1084, U0237 and/or U0238. This may be due to the software in the DSP. To correct this condition, perform a hard reset of the DSP by disconnecting the 12-volt battery. Reprogram the DSP module using the latest version of the appropriate Ford diagnostic scan tool. For claiming, use causal part 18B849 and any applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

The newest procedure to correct the pop/static (SSM 51663) omits the hard reset step. I wonder if that was a mistake on Ford’s part. I haven’t had the chance yet to try updating the DSP using this older procedure to see if it clears the FDRS queue and revises the software version. When I do, I will either pull fuse 28 or pull the power plug on the DSP directly. Disconnecting the battery won’t work on a Powerboost.

It’s interesting that a malfunctioning DSP can cause a host of odd problems, including having chimes misdirected to the instrument cluster. I didn’t have that problem myself after the most recent update which may or may not have installed correctly.

Sponsored

 

[rugedraw]

Before reverting back, you might want to give a revised programming procedure a shot. In the past (e.g., SSM 50739), the DSP was reprogrammed by first cutting power to the DSP to perform a hard reset and then updating the software:

SSM 50739 - 2020-2021 Various Vehicles - Audio Inoperative - No Sound From Audio Speakers -No Communication With ACM Or DSP - DTC U1084, U0237 And/Or U0238
Some 2020-2021 Escape vehicles and 2021 F-150/Mustang Mach-E/Expedition/Explorer vehicles built on or before 22-Nov-2021 may exhibit a concern of the audio inoperative, no sound from audio speakers, chimes default to coming through the Instrument cluster, no communication with audio control module (ACM) or digital signal processor (DSP) module, and/or DTC U1084, U0237 and/or U0238. This may be due to the software in the DSP. To correct this condition, perform a hard reset of the DSP by disconnecting the 12-volt battery. Reprogram the DSP module using the latest version of the appropriate Ford diagnostic scan tool. For claiming, use causal part 18B849 and any applicable labor operations in Section 10 of the Service Labor Time Standards (SLTS) Manual.

The newest procedure to correct the pop/static (SSM 51663) omits the hard reset step. I wonder if that was a mistake on Ford’s part. I haven’t had the chance yet to try updating the DSP using this older procedure to see if it clears the FDRS queue and revises the software version. When I do, I will either pull fuse 28 or pull the power plug on the DSP directly. Disconnecting the battery won’t work on a Powerboost.

It’s interesting that a malfunctioning DSP can cause a host of odd problems, including having chimes misdirected to the instrument cluster. I didn’t have that problem myself after the most recent update which may or may not have installed correctly.

Interesting. I applied the update with FDRS a while ago, but I never reset the DSP by cutting the power, and I've had the pop/static issue happen to mine. I am going to try that to see if it happens again or not.

 

[JEB]

Interesting. I applied the update with FDRS a while ago, but I never reset the DSP by cutting the power, and I've had the pop/static issue happen to mine. I am going to try that to see if it happens again or not.

No joy for me. I cut and restored the power and tried to reinstall the update. Same result. FDRS says that it successfully updated the DSP software from -BH to -BN but a rescan of the module shows that it’s still on -BH. The installer is messed up.

I’d be curious to see if you get different results.

 

[Mike G]

No joy for me. I cut and restored the power and tried to reinstall the update. Same result. FDRS says that it successfully updated the DSP software from -BH to -BN but a rescan of the module shows that it’s still on -BH. The installer is messed up.

I’d be curious to see if you get different results.

I did this DSP update on my Lightning and *thought* it had done all the programming properly and now suspect that as you say, nothing was accomplished. I took a look at the JSON XML for the package and even though I'm like a hog lookin' at a wristwatch when it comes to some of the update packages it still looks like it was written wrong. I checked my dealer's mannequin and it's still on the same rev for the DSP that my truck is on ("-AJ"), and I know the mannequin hasn't been updated. So I suspect mine was never really updated either.

 

[rugedraw]

No joy for me. I cut and restored the power and tried to reinstall the update. Same result. FDRS says that it successfully updated the DSP software from -BH to -BN but a rescan of the module shows that it’s still on -BH. The installer is messed up.

I’d be curious to see if you get different results.

I did this DSP update on my Lightning and *thought* it had done all the programming properly and now suspect that as you say, nothing was accomplished. I took a look at the JSON XML for the package and even though I'm like a hog lookin' at a wristwatch when it comes to some of the update packages it still looks like it was written wrong. I checked my dealer's mannequin and it's still on the same rev for the DSP that my truck is on ("-AJ"), and I know the mannequin hasn't been updated. So I suspect mine was never really updated either.

You guys know a lot more about this than I do. According to PTS FDRS history back in September of last year when I first manually updated my truck:

Audio Digital Signal Processing Module (DSP) - Software Update

8:07:10 PM

Module software has been updated to - ML3T-14C589-BK

Button Pressed : OK

How do I check what my truck actually has?

 

[Jesse-Infotainment]

You guys know a lot more about this than I do. According to PTS FDRS history back in September of last year when I first manually updated my truck:

Audio Digital Signal Processing Module (DSP) - Software Update

8:07:10 PM

Module software has been updated to - ML3T-14C589-BK

Button Pressed : OK

How do I check what my truck actually has?

If you ran the update it updated.

The issue is with ford submission.

Two possible issues.. One they havent added the software to the acceptable software list

Two they have a shitty vehicle submission system. Im leaning towards two as its been an issue with PCM updates for the power boost for a while now. Iceman has had the PCM update showing now for a month or two since it was released and installed.

I dont know why Ford cant get the submission to work worth a flip.

 

[rugedraw]

If you ran the update it updated.

The issue is with ford submission.

Two possible issues.. One they havent added the software to the acceptable software list

Two they have a shitty vehicle submission system. Im leaning towards two as its been an issue with PCM updates for the power boost for a while now. Iceman has had the PCM update showing now for a month or two since it was released and installed.

I dont know why Ford cant get the submission to work worth a flip.

If that's the case, then the update does not fix the pop/static issue because I have had it happen twice since I applied that update.

Edit: As a matter of fact, it never happened to me until after I applied that update. I remember when it happened to me the first time, I texted you a video of it as it was happening.

 

[RickBullotta]

If that's the case, then the update does not fix the pop/static issue because I have had it happen twice since I applied that update.

It might just be "the power of suggestion", but after applying the DSP update it *seems* like the maximum volume out of the audio system is louder.

 

[Jesse-Infotainment]

If that's the case, then the update does not fix the pop/static issue because I have had it happen twice since I applied that update.

You can look in forscan also. Select the car icon. Click configuration. Scroll to DSP and see what the strategy shows.

 

[rugedraw]

It might just be "the power of suggestion", but after applying the DSP update it *seems* like the maximum volume out of the audio system is louder.

I did hoping it would fix the bass roll-off issue on my aftermarket subs, but it didn't help with that, either.

 

[JEB]

If that's the case, then the update does not fix the pop/static issue because I have had it happen twice since I applied that update.3

Edit: As a matter of fact, it never happened to me until after I applied that update. I remember when it happened to me the first time, I texted you a video of it as it was happening.

You probaby applied a different update than the one I’m talking about. It only dropped onto FDRS last week. So, if you applied it more than about a week ago, it’s a different update.

As for checking which software version you currently have, you have a couple of options. First, you can download the as-built from the motorcraft website onto a windows laptop and then open in up with a simple app, like XML Notepad (or you can have someone do this for you if you provide your VIN). Second, you can view the software version from the main screen in FDRS. Third, you can look at the software version after a vehicle scan with FORScan or FORScan lite.

 

[Jesse-Infotainment]

IPC update has been released to FDRS for the 2021 Job 1 Lariat and up trim.

 

[rugedraw]

You probaby applied a different update than the one I’m talking about. It only dropped onto FDRS last week. So, if you applied it more than about a week ago, it’s a different update.

As for checking which software version you currently have, you have a couple of options. First, you can download the as-built from the motorcraft website onto a windows laptop and then open in up with a simple app, like XML Notepad (or you can have someone do this for you if you provide your VIN). Second, you can view the software version from the main screen in FDRS. Third, you can look at the software version after a vehicle scan with FORScan or FORScan lite.

I'm going to post on the VIN look up thread to see if any updates show up for my truck in FDRS. Is the as-built data in PTS what I need as in the attached picture? I'd hate to have to give Ford another $50 just for this, but if it does solve the pop/static issue, it would be well worth it.

Either way, I will most likely look into this tomorrow after work. Today is game 1 of the NBA Finals and I'm going to be watching the Heat hopefully pull off a miracle. I know I'm not going to touch my truck tonight. lol

 

[RickBullotta]

IPC update has been released to FDRS for the 2021 Job 1 Lariat and up trim.

Installed flawlessly. I tried re-running the DSP update - it didn't re-do the install but did try to update the database on the Ford side, but it still shows up as an available update.

 

[JEB]

I'm going to post on the VIN look up thread to see if any updates show up for my truck in FDRS. Is the as-built data in PTS what I need as in the attached picture? I'd hate to have to give Ford another $50 just for this, but if it does solve the pop/static issue, it would be well worth it.

Either way, I will most likely look into this tomorrow after work. Today is game 1 of the NBA Finals and I'm going to be watching the Heat hopefully pull off a miracle. I know I'm not going to touch my truck tonight. lol

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.

Sponsored