22S41 Recall Software - Server Deployment Issue

[DevSecOps]

@DevSecOps perhaps you could check my VIN, maybe it says something in there?

I can't do VIN checks today. I'm trying to brick my HVBJB by going over mountains and DCFC.

Sponsored

 

[WyldStallyn]

I just had the recall performed on my 2021 Job 1 SR AWD this past Saturday. One of the things I remember noticing on the paperwork which seemed strange was that it mentioned 22S41B or 22S41-B instead of just 22S41. Would it be possible that this would be a tweaked version of the recall software? I will check the paperwork when I get home and update this post with a photo.

@DevSecOps perhaps you could check my VIN, maybe it says something in there?

You can send it to me. I have FDRS open right now.

 

[Mathington]

I can't do VIN checks today. I'm trying to brick my HVBJB by going over mountains and DCFC.

No worries, I look forward to hearing how it goes!

 

[scoopman]

I can't do VIN checks today. I'm trying to brick my HVBJB by going over mountains and DCFC.

You should be playing some kids music, that's important.

 

[WyldStallyn]

I just had the recall performed on my 2021 Job 1 SR AWD this past Saturday. One of the things I remember noticing on the paperwork which seemed strange was that it mentioned 22S41B or 22S41-B instead of just 22S41. Would it be possible that this would be a tweaked version of the recall software? I will check the paperwork when I get home and update this post with a photo.

@DevSecOps perhaps you could check my VIN, maybe it says something in there?

Same situation as @agoldman . They connected with FDRS, 22S41 updates were not available, so they closed out the recall without updating anything.

BECM: NJ98-14C197-AB (AE is 22S41 version)
SOBDMC: LJ98-14G069-AXG (AXH is 22S41 version)

 

[DevSecOps]

Same situation as @agoldman . They connected with FDRS, 22S41 updates were not available, so they closed out the recall without updating anything.

BECM: NJ98-14C197-AB (AE is 22S41 version)
SOBDMC: LJ98-14G069-AXG (AXH is 22S41 version)

Such a mess ... I wonder how many people will have closed recalls without the software actually on the vehicle and if the OTA system will catch it.

 

[Mathington]

Well, I have to say… “Made it”! Was getting quite worried with all these stories but no issue. One dcfc was in 111 degree heat per the car sensor. No issues.

How were your battery other temps after DCFC and driving in such heat? Were you running CarScanner to check your temps and Amperage being pulled by the car during driving?

 

[DevSecOps]

How were your battery other temps after DCFC and driving in such heat? Were you running CarScanner to check your temps and Amperage being pulled by the car during driving?

During DCFC the car will do it's best to keep the battery at 95. It should have been able to in 111.

 

[Mathington]

Same situation as @agoldman . They connected with FDRS, 22S41 updates were not available, so they closed out the recall without updating anything.

BECM: NJ98-14C197-AB (AE is 22S41 version)
SOBDMC: LJ98-14G069-AXG (AXH is 22S41 version)

WTF, really? Damnit, that means I have to go in again or hope for an OTA before my road trip in 3 weeks. The dealer didn't mention any of that to me when I picked up the car

Thanks for checking this for me @WyldStallyn !

 

[Mathington]

I have a feeling that we're gonna see the updates return today / tomorrow.

Then we're gonna have to figure out what changed...

I'm gonna guess it's a persistent DTC now.

This should *in theory* help owners get the service and parts replaced instead of dealers just clearing the codes and sending people on their way.

 

[DevSecOps]

This should *in theory* help owners get the service and parts replaced instead of dealers just clearing the codes and sending people on their way.

Yes, but I have no confirmation that's the change. It's purely my guess. I'm certain they changed something and given the quick turn around I assume it's something small. It could also be tolerances but I would assume that would have a lengthier testing process.

 

[Mathington]

Yes, but I have no confirmation that's the change. It's purely my guess. I'm certain they changed something and given the quick turn around I assume it's something small. It could also be tolerances but I would assume that would have a lengthier testing process.

Yea, that makes sense.

 

[BillPitman]

Strange ... First I've seen of that. Are you sure? Mine still shows up:

https://www.nhtsa.gov/recalls

Yes, it is there today….. Bill P

 

[generaltso]

Such a mess ... I wonder how many people will have closed recalls without the software actually on the vehicle and if the OTA system will catch it.

Yeah, this is going to be quite the mess to untangle. Now there will be cars with closed out recalls that never actually got the updates AND cars that had the updates applied but don't have the recall closed out because they were applied DIY. Ford should probably just start over with their recall database by pulling current versions of the modules for every car from whatever database FDRS uses.

 

[Kamuelaflyer]

Yeah but we were comparing modules on one VIN and I didn't recognize that version so I asked him and Wyld if they had seen it before. Either way it's not the recall version but the problem was that we only had a tooltip to go on so only those who keep track of tooltip versions and their associated modules would likely know.

I’m way behind on the thread Dev. Thanks for the clarification.

Sponsored