ECU module programming guide using FDRS

[Snakebitten]

3.5.2 is 22 trucks early builds that’s the gateway x you guys have to stop with the revisions. They have a million different trucks out here at this point and they all are different.

Yea, I gave up a long time ago trying to make sense of the versioning numbers. Especially since having a 2021 for a year and now having a 2022? It would just give me a headache. I let YOU be the backoffice with the spreadsheets that make sense of those things. (I'd bet $million you have them)

Anyways, yes yesterday a GWM update popped up in FDRS for my Job2 2022. It was the FIRST meaningful update offered for such a recent build. I jumped on it rather than waiting for OTA. ?

Truck spent the night on the porch of the RV. I even gave it a good healthy trickle charge as desert for being such a good truck so far.

Sponsored

 

[speedracercjr]

Thanks to @antho for loaning me his license key my truck is back to 100% up to date. Hopefully fullscreen Carplay/AA rolls out soon!

 

[Kanuck]

I just updated my truck. Unsure what to do now...can someone please advise.

1. ACM will not or can not download the correct file for my module.
2. IPC says it has a DTC. How do I correct that?

I am still connected to the truck.
Thanks in advance.

Note Sync is now 22192 Rev 498...I must have done something right...lol

 

[Snakebitten]

Sometimes all you can do is shut it all down. Even go for a drive and allow the truck an opportunity to operate normally.

Then return to FDRS service bay mode and pick up where you left off.

I think of it similarly to a server that is receiving multiple upgrades to its core systems. I will apply one or two and reboot the server so it can fully apply the changes. Then return to updating status and do a few more.

 

[Kanuck]

Sometimes all you can do is shut it all down. Even go for a drive and allow the truck an opportunity to operate normally.

Then return to FDRS service bay mode and pick up where you left off.

I think of it similarly to a server that is receiving multiple upgrades to its core systems. I will apply one or two and reboot the server so it can fully apply the changes. Then return to updating status and do a few more.

Thanks

 

["Steve"]

3.5.2 is 22 trucks early builds that’s the gateway x you guys have to stop with the revisions. They have a million different trucks out here at this point and they all are different.

i don't care so much about the version/revision number....i was just curious if what came through bumped me passed the apim i had pending last week. if the wiki was updated, i could more or less guess that myself.

 

[Kanuck]

My screw ups.... ACM - I told it woofer install was NO - Should have been YES. It worked and the IPC cleared when I did a network scan.

With FDRS can I get the information I was seeing when connected to the truck without being connected to the truck? I assume the info is/was upload to the mother ship when I did the updates. Is FDRS used to see what updates that are outstanding on a truck with just the VIN number that members ask another member to see what updates are outstanding?

 

[Snakebitten]

Yes. If you log into FDRS without an ODB adapter, you simply hit cancel on the adapter select pop-up.

Then manually enter your VIN IF it isn't cached as a choice already.

FDRS will poll the mothership and download the current cloud records for that VIN. Including any Oasis history for the VIN if you request it.

Edit: What I wish I had access to is whatever "service" it is that Jesse and a couple of others have posted that clearly is showing OTA related history for a VIN. I don't know what that service is.

 

[Kanuck]

Yes. If you log into FDRS without an ODB adapter, you simply hit cancel on the adapter select pop-up.

Then manually enter your VIN IF it isn't cached as a choice already.

FDRS will poll the mothership and download the current cloud records for that VIN. Including any Oasis history for the VIN if you request it.

Edit: What I wish I had access to is whatever "service" it is that Jesse and a couple of others have posted that clearly is showing OTA related history for a VIN. I don't know what that service is.

Thanks....will give it a try

 

[Kanuck]

I just want to thank everyone on this forum for all the info and suggestions on how to update our trucks. Because of this forum, I have updated my truck and as far as I can tell, all is well.

 

[Snakebitten]

The collective can be a powerful force.

I remember the day this thread was started. I don't think Iceman or anyone else could have predicted...........

 

[BHunted1]

The collective can be a powerful force.

I remember the day this thread was started. I don't think Iceman or anyone else could have predicted...........

We are the Borg Collective. Resistance is Futile. We will Assimilate and conquer

 

[Demps]

I’m currently at 2.8.3 with functional BlueCruise through dealer FDRS. Got the last 2 minor updates. I’m expecting versions 3.1.1, 3.2.1, and 3.3.1. Modules to update are GWM, APIM, and TCU, presumably in this order.

These modules can be updated via USB flash drive. If the OTA updates fail, my thought is to create an USB flash drive for my truck by manually entering the VIN in FDRS and then inserting the flash drive in the truck to do the update. If the battery SOC is low would leaving the flash drive inserted and driving solve a low SOC condition that would block an OTA update?

I see the upside of this procedure as not needing to use a Mongoose VCI or worrying about the battery SOC. One downside is how to “report” the updates to Ford to be sure the next module is ready to be updated.

Any thoughts about this update procedure are appreciated.

 

[Ajzride]

I don’t think it will create the thumb drive without first talking to the truck to verify module numbers. You will need a cable.

 

[RickBullotta]

I’m currently at 2.8.3 with functional BlueCruise through dealer FDRS. Got the last 2 minor updates. I’m expecting versions 3.1.1, 3.2.1, and 3.3.1. Modules to update are GWM, APIM, and TCU, presumably in this order.

These modules can be updated via USB flash drive. If the OTA updates fail, my thought is to create an USB flash drive for my truck by manually entering the VIN in FDRS and then inserting the flash drive in the truck to do the update. If the battery SOC is low would leaving the flash drive inserted and driving solve a low SOC condition that would block an OTA update?

I see the upside of this procedure as not needing to use a Mongoose VCI or worrying about the battery SOC. One downside is how to “report” the updates to Ford to be sure the next module is ready to be updated.

Any thoughts about this update procedure are appreciated.

You can (and should) leave your truck running for most of the USB updates. It'll tell you when to restart the truck, and after restarting, when to remove the USB drive and reinsert it in your laptop to finalize the update. Follow the FDRS prompts and don't get impatient. Ask me how I know...

Sponsored