Post here if you have an active FDRS account and are willing to look up info for others

[rugedraw]

Thank you for the lighting quick reply Javier! The car sat at the dealer until I bought it in mid-March, and it hasn't been driven a ton since I bought it either. Is it possible that's why those modules haven't "phoned home" in a while? It will be replacing my company car on July 1st, so it will see more use soon. As for FORScan, I am aware (and am handy with both cars and tech) of it but haven't had the occasion to use it yet. Do I need to use the PC version of the app or will FORScan Light for Android do the trick? Looks like you're referring to the PC version, but just checking.

Not driving the car for extended period can prevent updates from installing, but not from them being sent to you. I do not know what causes the vehicle to phone home nor do I have an explanation as to why some modules have reported themselves and other haven't. As far as not getting any updates since March: It could be your VIN is just not part of an active OTA roll-out plan and you simply just have to wait for the next round to be pushed to you.

I have never used the Android version (although I have been curios to try it), so I am not sure it you can reset the modules with it, but a module resent is a fairly simple script, so I would assume you can do it with the phone version, but honestly, I am not sure. It won't hurt to do it. Lmk when you do and I will check the VIN again and see if anything changed.

Sponsored

 

[gtb75]

Not driving the car for extended period can prevent updates from installing, but not from them being sent to you. I do not know what causes the vehicle to phone home nor do I have an explanation as to why some modules have reported themselves and other haven't. As far as not getting any updates since March: It could be your VIN is just not part of an active OTA roll-out plan and you simply just have to wait for the next round to be pushed to you.

I have never used the Android version (although I have been curios to try it), so I am not sure it you can reset the modules with it, but a module resent is a fairly simple script, so I would assume you can do it with the phone version, but honestly, I am not sure. It won't hurt to do it. Lmk when you do and I will check the VIN again and see if anything changed.

Thanks again for the quick reply - and understood on all points! I have been driving it at least weekly, and the main battery usually is somewhere from 60%-80% state of charge. The 12V battery is currently at 97% according to the Ford website (never gets to low from what I've seen), so that should be good as well. I ordered an OBDLink EX from Amazon to use with FORScan for PC - gets delivered tomorrow. I will post when I get the APIM, GWM and TCU modules reset. I have known about FORScan for years (have owned multiple Fords), just never needed to mess with it. But I figured it's good to have the hardwired OBD adapter if I ever explore the basics beyond just clearing codes and resetting modules.

Lastly, I also scheduled a visit to the dealer next Wednesday to get TSB 24-2141 addressed, and asked them to look at the outstanding software updates when it's there. Assuming the module resets don't change anything hopefully they can push them while it's there for the TSB.

 

[devmach-e]

I just had my car in for the HVBJB recall (thankfully, not a forced replacement, but dealer-initiated). Would like to know what they did other than just the HVBJB related programming. Paperwork given doesn't indicate anything useful.

VIN 3FMTK3R75NMA02321

*bump*

 

[Mike G]

*bump*

What day was this?

The last time any programming was done on this VIN according to FDRS was 1 December 23.

Other than that it's been somebody looking up the VIN and connected vehicle tab in PTS to check the status of the car.

There is no warranty repair history saying 23S56 was completed..in fact it's still an outstanding field service action for this VIN.

Here's the list of available software showing in FDRS today:

 

[devmach-e]

What day was this?

The last time any programming was done on this VIN according to FDRS was 1 December 23.

Other than that it's been somebody looking up the VIN and connected vehicle tab in PTS to check the status of the car.

There is no warranty repair history saying 23S56 was completed..in fact it's still an outstanding field service action for this VIN.

Here's the list of available software showing in FDRS today:

Thank you for checking. The recall work was done this week: Wednesday, June 5th. Do I need to go back to the dealership and complain that nothing appears to have been done? I was under the impression that the SOBDMC would be updated at the very least.

 

[0CO2]

If you'd be kind enough to run my VIN (is going in to service on Monday), much appreciated!

3FMTK3SU3MMA06124

 

[Mike G]

Thank you for checking. The recall work was done this week: Wednesday, June 5th. Do I need to go back to the dealership and complain that nothing appears to have been done? I was under the impression that the SOBDMC would be updated at the very least.

You can't just update one of the powertrain modules without doing all of the other ones showing in FDRS. They are scripted to be completed as a coordinated set...Well technically you could just pick one...and then cancel out of the rest of them I suppose...but that's not supposed to be the way they are done. You currently have a PCM, ABS, BECM, and SOBDMC that would normally get updated as a function of completing 23S56 HVJB recall. Also in FDRS there are tool functions for filling and bleeding the battery pack after it's been reinstalled following a HVJB replacement. I don't see any evidence that anything like that happened.

Here are the session logs from FDRS for the 4th and 5th showing that someone simply looked up your VIN in PTS. No programming took place...or any filling and bleeding....at least not using FDRS at any rate. So I don't know what to tell you . I guess it might be a good idea to get an explanation from the service manager.

 

[devmach-e]

You can't just update one of the powertrain modules without doing all of the other ones showing in FDRS. They are scripted to be completed as a coordinated set...Well technically you could just pick one...and then cancel out of the rest of them I suppose...but that's not supposed to be the way they are done. You currently have a PCM, ABS, BECM, and SOBDMC that would normally get updated as a function of completing 23S56 HVJB recall. Also in FDRS there are tool functions for filling and bleeding the battery pack after it's been reinstalled following a HVJB replacement. I don't see any evidence that anything like that happened.

Here are the session logs from FDRS for the 4th and 5th showing that someone simply looked up your VIN in PTS. No programming took place...or any filling and bleeding....at least not using FDRS at any rate. So I don't know what to tell you . I guess it might be a good idea to get an explanation from the service manager.

I've called. They claim they did the HVBJB hardware side of thing, but for whatever reason, the car wouldn't take the software update, but felt it was okay to give me the car back. They can't explain why it was okay to give me the car back without doing the 4 module updates.

Yeah, I'll be speaking to the service manager on Monday when I bring the car in to have the software updates done. They claim it will only take an hour. Why do I get the feeling that is not the case. I have to wonder if they didn't do the software updates, did they actually do the HVBJB replacement, too.

 

[Mike G]

I've called. They claim they did the HVBJB hardware side of thing, but for whatever reason, the car wouldn't take the software update, but felt it was okay to give me the car back. They can't explain why it was okay to give me the car back without doing the 4 module updates.

Yeah, I'll be speaking to the service manager on Monday when I bring the car in to have the software updates done. They claim it will only take an hour. Why do I get the feeling that is not the case. I have to wonder if they didn't do the software updates, did they actually do the HVBJB replacement, too.

First double-check the VIN to make sure I wasn't looking up a different vehicle altogether...cause I find it remarkable that this combination of events even happened, to be honest. I just want to make sure we are talking about the same car.

Powertrain updates are called out for several different FSA campaigns ( 21G01, 22S29, 22S41, 23B50, and 23S56).

For reasons that I'm not clear on, the only program that requires powertrain updates, but that is currently on hold for techs to perform, is the 23B50 (stuck charge cord). What's hilarious is it's the same module updates that would need to be updated for all the other programs I listed above, including the 23S56 HVJB that your car was ostensibly in the shop for. So there's no reason they couldn't have legitimately done it.

This car has never had the HVJB replaced according to the service history, so that can't be a reason they just decided to skip it.

The other thing is...this is a Safety Recall which has associated legal requirements and ramifications for non-compliance. So in essence they gave you back the car half-done? Or not really done at all? Cause if the shop is using FDRS there should have been evidence. I mentioned the bleed and fill routine in FDRS...but there's no evidence showing anybody looked up how to discharge the HV battery, and remove the pack, or any other work packages that I see routinely being accessed in PTS (it's all listed in FDRS when they do that).

This is all somewhat astonishing.

 

[Mike G]

@devmach-e

One final note.....a message, bulletin, email was sent to dealers authorizing them to update all outstanding available software updates showing in FDRS at the time of programming software updates for program 23S56...on Ford's dime. So they could have completely updated your car and charged the labor to Ford. I guess they didn't mention that.

 

[Track9979]

Hey All, hoping someone can look up what modules updates i have available in FDRS and if there's anything on OTA. I went to a dealer to do a bunch of updates due to sync/couldn't activate modem issues. They did a bunch, and it's working, but flaky. PAAK not working, fordpass app isn't always responsive. OTA/Fordpass team says more updates are needed (that would maybe fix the issue, or maybe not) and of course are trying to send me back to the dealer. I'm hoping I'd get some over OTA instead of wasting time at a dealer, but if not, at least to go there with more definitive info. VIN: 3FMTK4SE3PMA28420

Also, i got a new l2 charger installed, and a charge fault/no charging when it was supposed to start at midnight (via car scheduling). Plugging in charger and manually starting seems to be fine. FORSCAN code is SOBDM: P0D28:00-68 and i can't really find much about it online. Is there info on troubleshooting this in PTS? Thanks!

 

[rugedraw]

Hey All, hoping someone can look up what modules updates i have available in FDRS and if there's anything on OTA. I went to a dealer to do a bunch of updates due to sync/couldn't activate modem issues. They did a bunch, and it's working, but flaky. PAAK not working, fordpass app isn't always responsive. OTA/Fordpass team says more updates are needed (that would maybe fix the issue, or maybe not) and of course are trying to send me back to the dealer. I'm hoping I'd get some over OTA instead of wasting time at a dealer, but if not, at least to go there with more definitive info. VIN: 3FMTK4SE3PMA28420

Also, i got a new l2 charger installed, and a charge fault/no charging when it was supposed to start at midnight (via car scheduling). Plugging in charger and manually starting seems to be fine. FORSCAN code is SOBDM: P0D28:00-68 and i can't really find much about it online. Is there info on troubleshooting this in PTS? Thanks!

This is what the codes looks like in PTS. The codes reported by your CMR qualify for the attached SSM. You are showing pending updates for both of those module, but I can't say with certainty that the code in the SOBDM will be resolved by an update.

 

[chiendat]

Can I have another check with my car: 3FMTK4SX9PMA04656? I presented the SSM-52574 to the dealer and they said there is nothing for my car to be updated. I see that I have 5.1.1 in my car so it’s definitely not the latest.

Just bumping this up the stack in case it was missed

 

[seanp123]

Can you look up 3FMTK4SX8MME01979?

 

[carbonizedbrett]

I would appreciate if somebody could look up 3FMTK3SU0MMA27089 and provide an update.

It went in for a number of recalls on 4/1 which I thought were completed by 4/17 but for Reasons (long story) I only had the car from 6/25 to 5/5 before it went back from 5/6 to 6/4 for collision repairs. Updates should have been completed before the problematic 4/26 - 5/5 window and in the unlikely even they did additional updates after they got the car back in May, that should have been after the window.

And yet I got the " 1Pedal Drive fault - Press brake pedal to reduce speed" issue this morning, after only having the car since Tuesday.

Sponsored