The Complete DIY Guide to Updating Your Mach-E with FDRS

[Mike G]

I pulled the service history for the powertrain ensemble.
Looks like start/finish was ~39 minutes?

Ahh...I had only three this time...the PCM, BECM, and SOBDMC. It depended on how up to date you were previously I think, as to how many modules needed revisions.

Sponsored

 

[Mike G]

So go figure, that I get all set up and ready to do updates, and I am getting the following FDRS error. Anyone have an idea on how to resolve? See attached ?

The server was down for maintenance.....was that way since about 6 CDT this morning from what I can tell. It's up now. I just got in.

 

[Mike G]

Got through them without issue thankfully. Does anyone know if these have the "goodies" for BC 1.4 included in them or will there be some other update that actually activates them?

Nope.

 

[Mike G]

@MrLoganRoss

Try it now...It gave me good results for my own VINs but gave me a 500 error for somebody else's I was checking...so it may not be fully back to normal yet.

 

[Snakebitten]

Just successfully applied the current IPC update, via USB.

@MrLoganRoss, I still had to use the log file to see the URL of each file that FDRS would error out on.
I manually fetched the file and then copied it to the proper location that FDRS would have put it.
Then start the update again and since the file it previously failed on would now exist, FDRS would move on to the next file and error out.

Rinse and repeat for 3 files.

At that point FDRS behaved properly and created the USB package with the necessary file structure and cert. (Der file)

FDRS in stick shift mode! ?

Fingers crossed that you can harvest your updates abroad using a similar technique.

For whatever reason, FDRS on my two laptops has a bug in the file-fetch code for most of the Mach-E updates. Works just fine once the files are available on the hard-drive.

 

[MrLoganRoss]

Just successfully applied the current IPC update, via USB.

@MrLoganRoss, I still had to use the log file to see the URL of each file that FDRS would error out on.
I manually fetched the file and then copied it to the proper location that FDRS would have put it.
Then start the update again and since the file it previously failed on would now exist, FDRS would move on to the next file and error out.

Rinse and repeat for 3 files.

At that point FDRS behaved properly and created the USB package with the necessary file structure and cert. (Der file)

FDRS in stick shift mode! ?

Fingers crossed that you can harvest your updates abroad using a similar technique.

For whatever reason, FDRS on my two laptops has a bug in the file-fetch code for most of the Mach-E updates. Works just fine once the files are available on the hard-drive.

Could you point me to the process for checking error logs?

 

[Snakebitten]

Could you point me to the process for checking error logs?

I believe you have already looked at the FDRS log to decipher where the update is failing?

You simply start a new session in FDRS, and pay close attention to your timestamp as you start an update and it suddenly errors out or fails.

Then grab a copy of the FDRS log file (I don't use the active copy) and scroll to the timestamp that matches the minute/seconds around the moment of failure.
For me, since the failure is almost always during the first file download, the log file will reveal the file/URL that failed.

If you are failing for the same reason, you can do the same. Once you manually download the file in a browser, and then copy it to the appropriate folder for FDRS, restart the update a second time. FDRS will see the first file is already present and will move on to the second file.

It will likely fail as well, and back to the log file again to harvest the URL.

The only confusing part is knowing where FDRS expects to find the file(s)

It's not always the ........\vehiclesoftware\downloads folder.
Sometimes it's the ........\vehiclesoftware\
Sometimes it's ........\vehiclesoftware\strategy\ folder.
Or
........\vehiclesoftware\strategy\downloads folder.

You kind of have to watch your hardrive closely while FDRS is attempting to download the next file and see if it created a folder and has a temporary placeholder of the filename with 0 bytes

See why I hesitated to send anyone down this rabbit hole? Lol

I don't want someone to come along and read this stuff and think it applies to their Mach-E. It'll intimidate and make them hesitate to "take matters into their own hands" with getting their Mach-E updated at least to the point they aren't waiting for the good stuff.

As far as I can tell, very few folks will have this bug. And I'm hoping that Ford discovers it and addresses it in a new FDRS build?

This does NOT affect OTA delivery of an update. I want to be clear about that. It's a bug in FDRS being able to write a file from memory to the disk. And it's not happening with every update. But for my Mach-E specifically, it does affect the majority of the updates.

I'm all caught up after dancing through the IPC today.
And the Powerboost is up to date too.

Both vehicles are fully functional with all the features, including "coming soon" ????

I love my Ford products I currently have. Fantastic engineering. But Ford is tripping all over themselves with the delivery mechanism behind OTA. I just don't choose to live with their stumbling if I don't have to.

 

[MrLoganRoss]

This is super helpful! What if updates themselves don’t appear to be failing? Is it possible they just don’t show up as being available? Of don’t then I am curious as why I don’t have fully updated sync, unless that won’t show up while I don’t update DSP (which I can’t since it is not in the car anymore).

 

[Snakebitten]

Often you will not see the next APIM (Sync4) update available until you have installed all prerequisite updates first.

Look especially for GWM updates.

 

[medriver]

https://www.vncishop.com/wholesale/vnci-vcm3-for-new-ford-mazda.html <-- is this playing with fire?

 

[MrLoganRoss]

@MrLoganRoss

Try it now...It gave me good results for my own VINs but gave me a 500 error for somebody else's I was checking...so it may not be fully back to normal yet.

Just tried and still can’t get in. But if other people are having trouble then I am fine with it. I can try next week when I have more time

 

[Mark Hassa]

https://www.vncishop.com/wholesale/vnci-vcm3-for-new-ford-mazda.html <-- is this playing with fire?

Nobody’s tried one yet. I’m sure there will eventually be some reviews.

 

[Jeff-NoVA]

Got through them without issue thankfully. Does anyone know if these have the "goodies" for BC 1.4 included in them or will there be some other update that actually activates them?

Apparently there are some Forscan tweaks to enable the BC 1.4 features, but they must be state secrets because nobody seems to want to share them ?. OK, that’s not actually fully true. Some kind of people have shared some of the tweaks with me, but I must be missing some other ones.

After applying the most recent round of powertrain updates in FDRS, I've gotten as far in Forscan as getting the new BC features to show in the driver assist menu but I can't get lane change assist to actually function in my '22.

 

[Mike G]

Apparently there are some Forscan tweaks to enable the BC 1.4 features, but they must be state secrets because nobody seems to want to share them ?. OK, that’s not actually fully true. Some kind of people have shared some of the tweaks with me, but I must be missing some other ones.

After applying the most recent round of powertrain updates in FDRS, I've gotten as far in Forscan as getting the new BC features to show in the driver assist menu but I can't get lane change assist to actually function in my '22.

Hmmm, I wonder if comparing the asbuilt values in your IPMA with those of a ‘23 model that came with BC1.2 from the plant might shed some light on whatever differences there might be. Assuming, of course that both cars had all the latest cruise-related module updates. I’ve heard there’s a free program that can compare asbuilt values….

 

[mrlindstrom]

Hmmm, I wonder if comparing the asbuilt values in your IPMA with those of a ‘23 model that came with BC1.2 from the plant might shed some light on whatever differences there might be. Assuming, of course that both cars had all the latest cruise-related module updates. I’ve heard there’s a free program that can compare asbuilt values….

I came across this, not sure how true it is... https://www.macheforum.com/site/thr...in-fdrs-for-over-a-week-now.33226/post-745852

Sponsored