The Complete DIY Guide to Updating Your Mach-E with FDRS (Alternative to Forscan)

[Mike G]

Oh very cool. I had the license for only 2 days so didn’t get to play much. But good to know for the next time that there is an event log. So in this case when the procedure was unsuccessful, would you have gotten an error message because the next event makes it look like it just finished the procedure.

The text should have alerted the operator that things didn't go as planned.

Mike

Sponsored

 

[Jambler]

If you successfully completed all updates yourself via FDRS and Blue Cruise is working great, is there any way to get rid of the CSP 22B08 notice that keeps appearing on Ford Pass and on the Ford recall site?

 

[Mike G]

If you successfully completed all updates yourself via FDRS and Blue Cruise is working great, is there any way to get rid of the CSP 22B08 notice that keeps appearing on Ford Pass and on the Ford recall site?

It's just a notice...it doesn't really apply to me because my APIM or TCU aren't "stuck" and unable to get updates. It's just a notice like the one (21G01) that says I'm entitled to get BlueCruise installed at a dealership...but I already have BlueCruise up and running...so...I ignore it.

Mike

 

[Arjan]

I did the updates that were pending, only module that keeps coming back is OBCC. Is this cleared after driving ?

 

[Mike G]

I did the updates that were pending, only module that keeps coming back is OBCC. Is this cleared after driving ?

Some have reported that you need to log out of FDRS completely and then log back in and do a network scan to clear it.

Your version should then show up as -AN.

I'm about to do this one myself in a few minutes.

Mike

 

[walla2]

Some have reported that you need to log out of FDRS completely and then log back in and do a network scan to clear it.

Your version should then show up as -AN.

I'm about to do this one myself in a few minutes.

Mike

Ran this yesterday and this did it for me. Not sure I even logged out - I may have just closed and restarted FDRS.

 

[Mike G]

Ran this yesterday and this did it for me. Not sure I even logged out - I may have just closed and restarted FDRS.

Yeah, it took more than that for me. I tried logging out and in twice.

I then just shut everything down and went for coffee. Came back after 15 mins and it had cleared and was now the -AN version and the engineering PN had also changed to -AP.

So I think the car had to go to sleep before the A/B switch happened.

Mike

 

[pouyafrankie]

Do we have a dedicated post with a list of things to do when troubleshooting programming failures via FDRS? For example, my SOBDM module kept failing until I unplugged the car from my EVSE charger. I'm sure this is covered somewhere in the thread/forum but the search function wasn't very helpful.

 

[Neil4Real]

Do we have a dedicated post with a list of things to do when troubleshooting programming failures via FDRS? For example, my SOBDM module kept failing until I unplugged the car from my EVSE charger. I'm sure this is covered somewhere in the thread/forum but the search function wasn't very helpful.

No, but it’s not supposed to be on the car charger when doing any updates. Just the 12v should be on a charger.

 

[GrumblesTheDog]

Out of curiosity, are people still getting OTA notices even if they brought their car fully up to date with FDRS? I think I recall someone mentioning they get an OTA failed status message through the widget, but then it sounds like some people are still getting update notifications? The Ford website JSON trick has been blank for me now for several months - no queued, failed or anything.

I'm not particularly worried about missing anything (for now), it's more that I hope everything is working smoothly once the HVBJB recall software updates get pushed...

 

[RonTCat]

Out of curiosity, are people still getting OTA notices even if they brought their car fully up to date with FDRS? I think I recall someone mentioning they get an OTA failed status message through the widget, but then it sounds like some people are still getting update notifications? The Ford website JSON trick has been blank for me now for several months - no queued, failed or anything.

I'm not particularly worried about missing anything (for now), it's more that I hope everything is working smoothly once the HVBJB recall software updates get pushed...

It is possible. An OTA can possibly report a "success", even though it really did zero updates since the updates were already applied.

 

[generaltso]

It is possible. An OTA can possibly report a "success", even though it really did zero updates since the updates were already applied.

Early on, OTA updates would try to install on my car and fail if the modules were already updated with FDRS. But now it seems like the OTAs aren’t even queued if the affected modules are already up to date, which is a much better strategy. I assume that was an intentional change?

 

[Mike G]

It is possible. An OTA can possibly report a "success", even though it really did zero updates since the updates were already applied.

I have updates set to enabled with a daily scheduled time in the middle of the day when I'm most likely to be driving downtown. My car is completely up-to-date. I don't ever recall getting the notification that I had an update pending during any times I've spent in the downtown area. I suspect that because all my updates are done using FDRS that I'm no longer offered any.

ETIS still thinks I should visit my dealer for the 21G01 and 22B08 programs. I don't know why.

Mike

 

[BMT1071]

ETIS still thinks I should visit my dealer for the 21G01 and 22B08 programs. I don't know why.

Mike

Probably because a dealer did not complete them and file a warranty claim.

 

[Eric_C_Boston]

I ran into a nasty problem in the middle of the current PCM update that also has SOBDMc, SOBDM, and BECM updates. The PCM and SOBDMc went okay. The SOBDM and BECM failed because I got a security access violation error when FDRS tried to download the firmware from the Ford server. I got the same error when I retried.

Any idea how to fix this?

I captured the old version numbers before I updated and I should have the old versions of PCM and SOBDMc firmware. I saw some information about using a special version of FordScan to restore the old versions in the PCM and SOBDMc?

Sponsored