ECU module programming guide using FDRS

[TJSparky]

For all with XLT 302a 8” cluster 5.0L a new IPC update showed up in FDRS for me this morning, might be available for others.

Sponsored

 

[abd79]

The TCU update I applied yesterday required a USB. Ford seems to have rejiggered the updates over the weekend. The GWM appeared immediately in the list of available updates and none of the updates I did (GWM, APIM, TCU, PCM) were chained to any other update.

For me it was TCU chained to APIM first. Then stand alone GWM appeared. Then another stand alone GWM and finally another stand alone APIM.

I honestly though can’t remember if the TCU was USB or not.

 

[abd79]

For all with XLT 302a 8” cluster 5.0L a new IPC update showed up in FDRS for me this morning, might be available for others.

My license just ran out, would be interested if something new came out today though.

Job 1 Lariat PB. 1FTFW1ED0MFB66211

 

[JEB]

For me it was TCU chained to APIM first. Then stand alone GWM appeared. Then another stand alone GWM and finally another stand alone APIM.

I honestly though can’t remember if the TCU was USB or not.

That’s what I was expecting to see. But I didn’t. I applied the GWM, TCU, APIM and PCM, in that order, without any stating that it required another update to be applied. No new updates appeared after applying these four.

For anyone interested, the latest Sync version for me was 4.0.22095. But the sync install was weird. According to FDRS, the update was over 800MB but it installed very quickly in two files, neither the strategy nor calibration versions changed and the only difference I noticed was that the Sync version changed on the head unit.

 

[abd79]

That’s what I was expecting to see. But I didn’t. I applied the GWM, TCU, APIM and PCM, in that order, without any stating that it required another update to be applied. No new updates appeared after applying these four.

For anyone interested, the latest Sync version for me was 4.0.22095. But the sync install was weird. According to FDRS, the update was over 800MB but it installed very quickly in two files, neither the strategy nor calibration versions changed and the only difference I noticed was that the Sync version changed on the head unit.

My APIM update went in 2 pieces ultimately ending up at the same version you noted with only F188 changing. Weird for sure but they must be gearing up for something…..

 

[Jesse-Infotainment]

My license just ran out, would be interested if something new came out today though.

Job 1 Lariat PB. 1FTFW1ED0MFB66211

Nothing

 

[abd79]

Nothing

Thanks! Was kinda hoping for that answer!

 

[JEB]

My APIM update went in 2 pieces ultimately ending up at the same version you noted with only F188 changing. Weird for sure but they must be gearing up for something…..

I agree. There is something going on.

I just double checked my before and after software versions at Node F188. No change. MU5T-14G676-EJ. Very odd.

 

["Steve"]

For all with XLT 302a 8” cluster 5.0L a new IPC update showed up in FDRS for me this morning, might be available for others.

sheit. i think i'll wait a few weeks before i do this again. maybe until june and i'll have 18 updates like jesse said. hah. can't be buyin a license every other week.

 

[abd79]

I agree. There is something going on.

I just double checked my before and after software versions at Node F188. No change. MU5T-14G676-EJ. Very odd.

Did you check in FDRS? I’ve noticed that even doing network scans not all Asbuilt data is being uploaded.

 

[RetroMan]

I have been pouring over this topic here for a few days now reading and hopefully absorbing the needed info to update my job 1 2021 PB Lariat. I currently have OTA 2.3.0 I have ordered the suggested mongoose and battery charger. As I wait for my Amazon delivery I was hoping to get a heads up on what updates are pending for my vin and if there are any particular ones on said list i should perform first. Thank you to all that have made this topic and guide so informative and helpful to others. This is a great group and very much apricated. I am happy to have found it.

1FTFW1ED4MFB60461

Please and thank you.
Lee

 

[JEB]

Did you check in FDRS? I’ve noticed that even doing network scans not all Asbuilt data is being uploaded.

Yes. As usual, the software version for the APIM on FDRS was incomplete. Only the prefix loaded. So, I checked the As-Built on Motorcraftservice the day after I completed the updates. I’ll check FDRS again before my license expires.

 

[abd79]

Yes. As usual, the software version for the APIM on FDRS was incomplete. Only the prefix loaded. So, I checked the As-Built on Motorcraftservice the day after I completed the updates. I’ll check FDRS again before my license expires.

Clicking on the APIM module in the vehicle inventory then scrolling down you should be able to see what F188 actually is as reported by your truck after an initial connection.

 

[speedracercjr]

I agree. There is something going on.

I just double checked my before and after software versions at Node F188. No change. MU5T-14G676-EJ. Very odd.

Maybe building up to Alexa in the truck?

 

[JEB]

Clicking on the APIM module in the vehicle inventory then scrolling down you should be able to see what F188 actually is as reported by your truck after an initial connection.

That’s exactly what I was going to do after logging back in.

EDIT: Just doubled-checked in FDRS. The as-built was updated correctly and matches FDRS. No change in Node F188 after yesterday’s update.

Sponsored