ECU module programming guide using FDRS

[Ebrou]

Jesse,
Since our trucks have been going through chip shortages, could we be missing running modules? My first blend date was 7/6 and then got pushed to 7/26 I believe, I was not ramped anywhere since it a few weeks difference in blends. Does my module count look correct on each bus based on what options I have? Shooting in the dark here...
---- EDIT---- I pulled another XLT VIN and the same modules appeared... so that is not it... back to the drawing board I guess....

XLT 302 high 4x4 sport pkg SCREW
5.0L
8" cluster with 12" center stack
360 cams with Co pilot assist
Tow tech package

Sponsored

 

[Jesse-Infotainment]

Jesse,
Since our trucks have been going through chip shortages, could we be missing running modules? My first blend date was 7/6 and then got pushed to 7/26 I believe, I was not ramped anywhere since it a few weeks difference in blends. Does my module count look correct on each bus based on what options I have? Shooting in the dark here...


XLT 302 high 4x4 sport pkg SCREW
5.0L
8" cluster with 12" center stack
360 cams with Co pilot assist
Tow tech package

Looks Good. We could be right. the non BC cars arent getting the full package. You say you did not get a CCM update.? You got an IPMA update. Could be the 22034 Update is tied to another module update. Hard to say honestly. I would need @iceman77 to look at the developer side of things. Like the update prerequisites. I believe they have some notes that he can see or make sense of.

Im not a developer.. SO I dont speak that language. If anyone is and maybe take a look at the update packages in the log and find anything that specifies anything that would be helpful. I saw @antho has done something similar before where he showed an update that it had some notes. Maybe he can did into the XLT vins and see if he sees anything.


Anyone that has the capability or knowledge is welcome to help. Its out of my league.

 

[Ebrou]

Looks Good. We could be right. the non BC cars arent getting the full package. You say you did not get a CCM update.? You got an IPMA update. Could be the 22034 Update is tied to another module update. Hard to say honestly. I would need @iceman77 to look at the developer side of things. Like the update prerequisites. I believe they have some notes that he can see or make sense of.

Im not a developer.. SO I dont speak that language. If anyone is and maybe take a look at the update packages in the log and find anything that specifies anything that would be helpful. I saw @antho has done something similar before where he showed an update that it had some notes. Maybe he can did into the XLT vins and see if he sees anything.


Anyone that has the capability or knowledge is welcome to help. Its out of my league.

I received the IPMA, CCM, PSCM updates in the beginning of March. The only issue I ran into was after the install of the IPMA it gave me a configuration error, I did the reinstall and it went through all the module configurations again one by one on its own (IT did not reinstall the update itself, good thing it.... was long enough) All my DTC's cleared at that point. I did not realize before I started, i had downloaded all three SW updates and went to install CCM first, it gave me an error. I logged out of FDRS and reconnected to truck and only downloaded the CCM module and it kicked off right away.

on 21281 v244

Since Feb I have completed the following updates: TRM, DDM, PDM, IPC, CCM, PSCM, IPMA, GSM, GWM. The only update out of them all that asked for a USB stick was the GWM.

 

[Platinum Peasant]

I made the Forscan change to fix the running boards after the DSM update.

I'm now noticing they don't deploy on approach. The setting is on for it. Anyone else experience this? Is there possibly another Forscan change to fix?

Check 744-23-01, what is your data in this line?

 

[travbz24]

Check 744-23-01, what is your data in this line?

Here's what it shows.

0000 0000 006F

 

[antho]

Looks Good. We could be right. the non BC cars arent getting the full package. You say you did not get a CCM update.? You got an IPMA update. Could be the 22034 Update is tied to another module update. Hard to say honestly. I would need @iceman77 to look at the developer side of things. Like the update prerequisites. I believe they have some notes that he can see or make sense of.

Im not a developer.. SO I dont speak that language. If anyone is and maybe take a look at the update packages in the log and find anything that specifies anything that would be helpful. I saw @antho has done something similar before where he showed an update that it had some notes. Maybe he can did into the XLT vins and see if he sees anything.


Anyone that has the capability or knowledge is welcome to help. Its out of my league.

Yeah, I can look for some job 1 XLT's when i get a chance. Would have to find some that have updated or tried to update rather.

Here's what it shows.

0000 0000 006F

This would enable approach PRB
0100 0000 006F

 

[Jesse-Infotainment]

Yeah, I can look for some job 1 XLT's when i get a chance. Would have to find some that have updated or tried to update rather.

This would enable approach PRB
0100 0000 006F

Im sure any of these guys will provide a vin.

 

[Whoskyle]

Yeah, I can look for some job 1 XLT's when i get a chance. Would have to find some that have updated or tried to update rather.

This would enable approach PRB
0100 0000 006F

I have a Job 1, May 6 2021, but can’t get APIM to update and since I tried the TSB that update disappeared.

XLT 302A
8” Cluster
No 360 Cams

 

[TJSparky]

Antho-
I sent you a PM. It’s about APIM ver for us in XLT 8” cluster trucks.

 

[Slappy McGee]

I'm currently in the same boat after getting up to Sync 244. Hoping a long nap and perhaps something in an overnight batch on Ford's servers will get me back in business tomorrow.

Long nap was successful and I'm up to SYNC 358. Letting the truck take a short nap (e.g. let the blue USB lights turn off) after loading the final GWM update as that seems to help make everything come back to life.

All my Orange modules are now green, save for PSCM which is gray. Not sure if that's something to worry about or can be safely ignored.

 

[jordandev]

You've got a couple now, but adding one more:

• stuck on 21281 v244
• XLT 302A with 360 cams
• no copilot assist (so no CCM vs Ebrou who does have this)
• VIN -> 1FTFW1E84MKE02174

Just found the "App Log" stuff in FDRS so have been taking a look as all those java stack traces are interesting (software dev here). Haven't seen anything super interesting in there yet tho...

 

[JEB]

Long nap was successful and I'm up to SYNC 358. Letting the truck take a short nap (e.g. let the blue USB lights turn off) after loading the final GWM update as that seems to help make everything come back to life.

All my Orange modules are now green, save for PSCM which is gray. Not sure if that's something to worry about or can be safely ignored.

Gray is not a concern. Just means the module didn’t report its status. Try doing a fresh network scan and see if it goes green.

 

[Slappy McGee]

Gray is not a concern. Just means the module didn’t report its status. Try doing a fresh network scan and see if it goes green.

Edit/Update:

This is what my "about" menu shows and maybe explains why I got BC without any notifications. I'm going to go ahead an assume that the blank date means I get BC "until the end of time" after going through this song and dance!

It turned green on my final scan and I'm now 100% up to date! Oddly enough, my Blue Cruise says "Activation Pending" on the Ford connected services page, and I've received no emails or anything and didn't see anything unusual in the menus so I took it out for a test drive and figured I'd see if the lane keeping assist had improved.

I hit the button and suddenly the dash lit up and I was officially Blue Cruising!

I need to try the ForScan updates for cameras at speed since that's not working, and as someone above mentioned, my PRB up/down works fine but the approach detection either isn't as sensitive or isn't working.

Before they were frankly too sensitive and whenever I'd lock the truck they'd stow and then immediately re-deploy since I was still near the truck.

Overall super happy this all worked, and really appreciate all the gurus sharing their wisdom!

 

[BHunted1]

It turned green on my final scan and I'm now 100% up to date! Oddly enough, my Blue Cruise says "Activation Pending" on the Ford connected services page, and I've received no emails or anything and didn't see anything unusual in the menus so I took it out for a test drive and figured I'd see if the lane keeping assist had improved.

I hit the button and suddenly the dash lit up and I was officially Blue Cruising!

I need to try the ForScan updates for cameras at speed since that's not working, and as someone above mentioned, my PRB up/down works fine but the approach detection either isn't as sensitive or isn't working.

Before they were frankly too sensitive and whenever I'd lock the truck they'd stow and then immediately re-deploy since I was still near the truck.

Overall super happy this all worked, and really appreciate all the gurus sharing their wisdom!

Check on your web dashboard and make sure its not pending for 600 bux and really shows one year free. Check your about screen in your truck, make sure the last line also matches a one year free date...

 

[JIMFOUNTAIN]

This is interesting. The changes appear to be trim specific. I originally had a “2” and my cameras were not working until Jesse had me change it to an “A”. I have a Job 1 Lariat. It’s also possible that with all the changes made to the IPMA to get BlueCruise working, non-BC trucks like mine have different camera settings.

What do you have in the second block of 7D0-01-04? Mine originally was 7xxx, changed to Fxxx.

Cameras in motion (Bed, Hitch, Rear) does appear to be very trim specific. Mine 7D0-01-04 is 0xxx. For completeness Platinum. Totally update SW.

Sponsored