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

[rugedraw]

Spent the last day doing updates and I am left with the following. Any advice apprecieate.

thx

GVMS error blocking ACM (I clicked on the ACM module button but nothing really happens) Did I do the right thing? What are the next steps, notifications, length of time to wait, etc? Is it blocking more than just the ACM? I have a day left on my current license.

APIM DTC error 87 missing message, which looks like something to do with Sirius, which I don't use at all. Anything I should do with it?

As far as the GVMS warning, once you submit a request for them to look at it, it can be cleared quickly, or can take longer than what you license is good for. No way of knowing really how quickly they get around to looking into it. Being the ACM, it is not a big deal IMO and I wouldn't stress it.

I also would ignore the APIM DTC, but that's just me. I've learned not to let codes ruin my day anymore. If there is no tangible problem that is affecting your ownership experience, I would ignore it.

Sponsored

 

[BlueDragon]

Thanks @rugedraw. I assume they look at it manually and then unblock and new things will show up in FDRS, correct?

 

[rugedraw]

Thanks @rugedraw. I assume they look at it manually and then unblock and new things will show up in FDRS, correct?

Correct. However, that ACM is not the gatekeeper for any other updates, so there is no need for FOMO if you can't do it before your license expires.

 

[BlueDragon]

Great. Perfect. Thank you.

 

[Neil4Real]

If anyone in SoCal wants to get in on this, I have a Mongoose and an annual FDRS subscription (just renewed it) I can part ways with.

 

[rugedraw]

Not sure what would be the best place to post this, but something happened yesterday that contradicted something I have been saying here and on other forums for some time now. An F150 that already had the BC 1.4 software and config installed on it with FDRS/FORScan received the OTA for BC 1.4. I was always under the impression that if you had the newer software on there already, when the OTA trigger was sent to the vehicle, that OTA would fail (for a lack of a better word) because the software was already installed on it.

I guess Ford scripted the OTA to run anyway and at least enable the config in case the IPMA was already updated for whatever reason. This is obviously a good thing, but I wanted to share it here because I was under the impression that this would not be the case if the latest IPMA software was installed.

 

[benk016]

Not sure what would be the best place to post this, but something happened yesterday that contradicted something I have been saying here and on other forums for some time now. An F150 that already had the BC 1.4 software and config installed on it with FDRS/FORScan received the OTA for BC 1.4. I was always under the impression that if you had the newer software on there already, when the OTA trigger was sent to the vehicle, that OTA would fail (for a lack of a better word) because the software was already installed on it.

I guess Ford scripted the OTA to run anyway and at least enable the config in case the IPMA was already updated for whatever reason. This is obviously a good thing, but I wanted to share it here because I was under the impression that this would not be the case if the latest IPMA software was installed.

I believe the FDRS version didn't include all the config so when the OTA comes there's at least that part that doesn't match and applies it.

 

[rugedraw]

I believe the FDRS version didn't include all the config so when the OTA comes there's at least that part that doesn't match and applies it.

Yea, the FDRS version without a doubt does not include the config. I assumed that when the OTA trigger caused the interrogator to poll the module and it saw the firmware it wanted to install was already there, the OTA trigger would just cancel itself out right then and there, but thankfully I was wrong and that is not the case.

 

[Mike G]

Yea, the FDRS version without a doubt does not include the config. I assumed that when the OTA trigger caused the interrogator to poll the module and it saw the firmware it wanted to install was already there, the OTA trigger would just cancel itself out right then and there, but thankfully I was wrong and that is not the case.

So just running the IPMA Config by itself isn't enough to put the correct asbuilt values in?

 

[Mike G]

Is this the same thing that was going on with the trucks? Where doing the IPMA/PSCM would update the software but not do the config correctly? So you had to go back and do the config separately to get the whole enchilada?

 

[rugedraw]

So just running the IPMA Config by itself isn't enough to put the correct asbuilt values in?

Is this the same thing that was going on with the trucks? Where doing the IPMA/PSCM would update the software but not do the config correctly? So you had to go back and do the config separately to get the whole enchilada?

Yea, FDRS does not enable the config. Same thing as with the trucks. Ford would have to add a guided routine to the IPMA to enable the config like the "enable bluecruise kit" from the 21G01 campaign that was put in there to enable BC on the job 1 F150s/Mach E's that never go the OTA.

 

[wildcatjw97]

Hi FDRS Experts.

I purchased a used 2021 (Job 1) Mach E First Edition for my son a couple of months ago and started my first foray down updating it with FDRS yesterday. I successfully updated a dozen modules shown. It then said I had a GWM update which was my first USB one and it updated successfully.

Then that opened up an APIM update. I started that USB update on the running car at ~5:30pm yesterday. After still showing it updating at 1am, I gave up and turned the car off and went to bed. I turned the car back on this morning hoping to see a successful update, but it still says "Software Updating. Do not remove the USB drive". I know it was 5-6GB of data, but It still can't be updating, can it?

Should I pull the USB and try again, or just keep letting it run this update? Not sure what I should do next?

Thanks for the help.

 

[Mike G]

Hi FDRS Experts.

I purchased a used 2021 (Job 1) Mach E First Edition for my son a couple of months ago and started my first foray down updating it with FDRS yesterday. I successfully updated a dozen modules shown. It then said I had a GWM update which was my first USB one and it updated successfully.

Then that opened up an APIM update. I started that USB update on the running car at ~5:30pm yesterday. After still showing it updating at 1am, I gave up and turned the car off and went to bed. I turned the car back on this morning hoping to see a successful update, but it still says "Software Updating. Do not remove the USB drive". I know it was 5-6GB of data, but It still can't be updating, can it?

Should I pull the USB and try again, or just keep letting it run this update? Not sure what I should do next?

Thanks for the help.

Try disconnecting the 12V battery negative terminal (10mm wrench or socket) for 2 minutes and then reconnect and start the car with the USB drive in the console port.

 

[wildcatjw97]

Tried that but on restart it still shows as updating. The Stnc version still shows as the same as before (23352 revision 1122).

What should I do now?

 

[noway]

On USB updates it will just fail if drive is removed or car shut down during updating. It is not a problem, but it showing it still updating after restart is just that it has started again. It will keep doing so forever until it succeeds

Just select "yes" on the dialog when it asks if it successfully installed regardless, and it will check if anything is updated. When it detects missing software just re-run the whole process with a different USB drive in case USB drive was bad.

Sponsored