FDRS Jan 8, 2022 updates SOBDMC, SOBDMB, PCM

[louibluey]

Jan 8, 2022 updates SOBDMc, SOBDMB, PCM, running the first one, SOBDMC runs the other two automatically in sequence. Took about 10 minutes.

1 peddlers beware backing out of the garage, it turns off 1PD.

After done, (Dec. 2020 FE), all that remains stuck on my FDRS SW Update list is ABS. I ran ABS again and it did run correctly through all the steps, but is still stuck on the board under my SW Updates (known FDRS bug).

Drove about 8 miles, local and highway, no perceived change. 1PD driving seemed good tonight, but I have not noticed any of the regen level changes others have been experiencing.

First noticed by @KevinS here (I saw it, but could not find that post thread again).

Sponsored

 

[Eric_C_Boston]

Thanks, I noticed the updates tonight. I do not have a SOBDMB update since mine is a RWD.

As always, I wonder what these updates fix. I usually wait until the TSB or SSM comes out.

 

[SnBGC]

Jan 8, 2022 updates SOBDMc, SOBDMB, PCM, running the first one, SOBDMC runs the other two automatically in sequence. Took about 10 minutes.

1 peddlers beware backing out of the garage, it turns off 1PD.

After done, (Dec. 2020 FE), all that remains stuck on my FDRS SW Update list is ABS. I ran ABS again and it did run correctly through all the steps, but is still stuck on the board under my SW Updates (known FDRS bug).

Drove about 8 miles, local and highway, no perceived change. 1PD driving seemed good tonight, but I have not noticed any of the regen level changes others have been experiencing.

Let me guess.....
Updates available only for Job 1 VINs?

 

[phidauex]

Did you already have the 21P22 updates list completed? IE, were there updates to the DCMs, BECM, GSM and RFA as well? Or were these new after you ran those updates before?

I ran all available FDRS updates today, and got the full list from the 21P22 program, but I'm curious if the SOBDMC, SOBDMB and PCM updates are actually a newer version still.

I only took it on a quick test drive, but I noticed that I only hit -60kW of regen, when normally I hit closer to -100kW. I need to try it again with the battery warmed up and some faster speeds.

 

[DevSecOps]

Let me guess.....
Updates available only for Job 1 VINs?

They do not appear for me, so yes, job 1 only

 

[louibluey]

Did you already have the 21P22 updates list completed? IE, were there updates to the DCMs, BECM, GSM and RFA as well? Or were these new after you ran those updates before?

I ran all available FDRS updates today, and got the full list from the 21P22 program, but I'm curious if the SOBDMC, SOBDMB and PCM updates are actually a newer version still.

I only took it on a quick test drive, but I noticed that I only hit -60kW of regen, when normally I hit closer to -100kW. I need to try it again with the battery warmed up and some faster speeds.

yea, I did what became 21P22 back in November 19, enjoyed the higher charge rate above 80% for my Thanksgiving driving.

Until the recent holiday FDRS debacle (where GTs lost Bluecruise with a listed FDRS module update), it was a pretty safe bet to just do anything on your VIN's "SW Update" list.

For two weeks, there was all kinds of bad stuff happening, installing only to get the power off note before anything was actually installed, programs for APIM that were not really normal updates, but repair procedures, like one with a special USB cable, etc. My main problem with that one APIM special cable procedure in my list, 1) it was a not update, it was a repair procedure, closer to a guided procedure (another list), and 2) my VIN did not need it, so it should not have appeared in my SW Update list. My feeling is that (and it was the case before the FDRS debacle), don't put anything in my "SW Update" list that does not pertain to my current version status for my VIN, which seems to be the case again, so all is well

Maybe someone realized the problems, because lately, the weird APIM stuff is gone, and everything for me so far, updates normally again. All that remains is that bug where ABS stays on the list after normally updated.

FDRS shows versions for all modules for a VIN, it is one of the first screens or tabs after GO with a VIN (at least when the passthrough device is plugged into the car OBDII port). I think I remembered to take some screen shots this time before and after ... I will go look and add them here if I have them.

 

[louibluey]

Did you already have the 21P22 updates list completed? IE, were there updates to the DCMs, BECM, GSM and RFA as well? Or were these

This -> new after you ran those updates before?

I ran all available FDRS updates today, and got the full list from the 21P22 program, but I'm curious if the SOBDMC, SOBDMB and PCM updates are actually a newer version still.

I only took it on a quick test drive, but I noticed that I only hit -60kW of regen, when normally I hit closer to -100kW. I need to try it again with the battery warmed up and some faster speeds.

I some how missed PCM before, but here are the SOM... updates before and after and PCM after:
Not sure why there are two columns?

SOBDMB, C before (11/19/22, what become 21P22) and SOBDMB, C after 1/8/22 update

PCM after (missed the before shot)

 

[generaltso]

I just ran through the PCM, SOBDMC, SOBDMB updates along with a DSP update that also appeared for my car. Those all updated fine, but before I started I saw a DTC for the GWM reporting that there was an Ethernet failure with the IPMA. After the updates, I cleared and retested but I'm still getting that same DTC. Anyone else seeing that?

 

[Eric_C_Boston]

I some how missed PCM before, but here are the SOM... updates before and after and PCM after:
Not sure why there are two columns?

SOBDMB, C before (11/19/22, what become 21P22) and SOBDMB, C after 1/8/22 update

PCM after (missed the before shot)

Ford uses a number of part numbers for different elements of a module. Forscan and FDRS pick up on different ones or calls them by different names.

Forscan reads an Assembly Part Number at PID F113. This seems to be the Factory Assembly Part Number of the module. It is what got installed at the factory. It seemingly never changes through the life of the module.

FDRS reads the Engineering Assembly Part Number at PID DA01. This number changes with software updates, so I assume it is the part number of the module with the current level of firmware/software.

Both Forscan and FDRS reads PID F188. Forscan calls it Strategy, which appears to be the original Ford name for module firmware. FDRS calls it Software Part Number.

Since I have a RWD, I have different part numbers. I have not done any of the recent updates. My car's PCM has a Engineering Assembly of MJ98-12A650-BDF and a Software PN of MJ98-14C204-BDF. The SOBDMC has LJ98-7P120-BDE and LJ98-14G069-BDE.

It appears -BDx are RWD versions and -BBx are AWD versions. I would not be surprised if GTs have yet another versions.

Your car's previous PCM numbers are likely MJ98-12A650-BBF and MJ98-14C204-BBF.

 

[louibluey]

I just ran through the PCM, SOBDMC, SOBDMB updates along with a DSP update that also appeared for my car. Those all updated fine, but before I started I saw a DTC for the GWM reporting that there was an Ethernet failure with the IPMA. After the updates, I cleared and retested but I'm still getting that same DTC. Anyone else seeing that?

Mine cleared to all green. I think FDRS keeps some history, next chance I get, I will see if I can find a similar recent error. (will edit this post if I find anything).

Okay, just checked. On power up, I had a GFM dtc, but it cleared first time. I do not see anything about GWM or Ethernet. (FE, Dec 2020 build date)

 

[KevinS]

I just ran through the PCM, SOBDMC, SOBDMB updates along with a DSP update that also appeared for my car. Those all updated fine, but before I started I saw a DTC for the GWM reporting that there was an Ethernet failure with the IPMA. After the updates, I cleared and retested but I'm still getting that same DTC. Anyone else seeing that?

i have had the same experience. I’m going to wait a few days and see if it clears on its own.

 

[Texas-E]

i have had the same experience. I’m going to wait a few days and see if it clears on its own.

Same for me.

 

[generaltso]

i have had the same experience. I’m going to wait a few days and see if it clears on its own.

I hope it clears because I would think that connectivity from the GWM to the IPMA will be important for the BlueCruise update.

 

[louibluey]

i have had the same experience. I’m going to wait a few days and see if it clears on its own.

I saw your post, but could not find it again. Thanks for posting (I just added a credit in the original post).

Soon enough, this thread will go away too, the official notes always start a new thread. I try to put the date and modules or some identifier in the title, so we can find the initial searches, well with search

 

[KevinS]

I just ran through the PCM, SOBDMC, SOBDMB updates along with a DSP update that also appeared for my car. Those all updated fine, but before I started I saw a DTC for the GWM reporting that there was an Ethernet failure with the IPMA. After the updates, I cleared and retested but I'm still getting that same DTC. Anyone else seeing that?

Just an update that I have checked the car again today after clearing DTCs and it continues to throw this error. I'm going in tomorrow for the windshield recall and will try one more time to resolve it and will otherwise let the techs know.

Sponsored