ECU module programming guide using FDRS

[jordandev]

So my Nano finally got here and now I see there have been some more serious problems than the network scan corruption… tried reading back in the thread some but it’s been moving fast.

Will I not be needing CCM updates if I don’t have adaptive cruise, BC, etc?

Or is it better to just not use the Nano anymore? Really didn’t want to shell out for a mongoose

Sponsored

 

[Platinum Peasant]

I can't remember which module it was, but I posted here about it. There was an update for it but it did NOT show up under the SW-Updates tab. Instead it was under the ALL tab for the module itself.

Nobody else has ever mentioned such a thing though.
If you want to check, just select one of the modules on the left side of the FDRS screen and the right side automatically shifts to the ALL tab for that module. Scan down the list and look for an update being listed.

I could be making an assumption, but after finding that oddity and applying the update no differently than any other update, it seemed like I started getting updates available again. Could have been a coincidence.

My memory is that of an old man, but I think it was an IPC update? This thread is so long it's not easy to go back and find a single post.

I just checked mine. Nothing else to update except the GSM. Just waiting like the others for the mothership to throw me some more crumbs.

 

[JEB]

So my Nano finally got here and now I see there have been some more serious problems than the network scan corruption… tried reading back in the thread some but it’s been moving fast.

Will I not be needing CCM updates if I don’t have adaptive cruise, BC, etc?

Or is it better to just not use the Nano anymore? Really didn’t want to shell out for a mongoose

I don’t have BC either. Doesn’t matter. The CCM update is chained to the updates for other modules in this round such that you really can’t avoid having to update it whether you have BC or not. Sorry for your predicament, but it appears that the Nano’s better days are behind it, now that Ford has moved it’s update efforts on to modules and CANs that the Nano can’t handle and that you can’t get around by selective programming.

 

[Bob_Mac]

So my Nano finally got here and now I see there have been some more serious problems than the network scan corruption… tried reading back in the thread some but it’s been moving fast.

Will I not be needing CCM updates if I don’t have adaptive cruise, BC, etc?

Or is it better to just not use the Nano anymore? Really didn’t want to shell out for a mongoose

My suggestion, return the Nano and check this thread or this one for someone who would either loan you their Mongoose or work with you on getting your updates completed.

 

[Ajzride]

Has anyone actually gotten their BlueCruise to start working in the last 48 hours? There are so many posts it's hard to tell, but it seems like it's just troubleshooting lately. I'm wondering if Ford has stopped sending the last set of APIM/GTWY out that we need.

 

[sailorz]

After 22028 I had "ghost" GWM and GSM updates that wouldnt do anything when I downloaded and ran them. There is a little refresh icon next to the Download button on each of those updates. The GSM module is still a ghost update but the GWM module actually refreshed and let me get up to 22034.

 

[JEB]

After 22028 I had "ghost" GWM and GSM updates that wouldnt do anything when I downloaded and ran them. There is a little refresh icon next to the Download button on each of those updates. The GSM module is still a ghost update but the GWM module actually refreshed and let me get up to 22034.

I keep seeing the update for the GSM module being referred to as a “ghost” software update. I don’t think it’s a software update at all. I think It’s a service procedure to be used when replacing the GSM that’s been mislabeled as a software update. Hover over the update with your cursor and you’ll see a pop up which says:

“This procedure restores the configuration data in the Parking Assist Module (PAM). This application enables the user to install a replacement module.”

I have no idea why they are calling it software and because of the mislabeling I expect it will never clear until it’s properly labeled and transferred to the section of FDRS where other service procedures can be found.

 

[antho]

I've notice in some modules the data is in HEX rather than ASCII. Something to worry about? Originally this VIN was in ASCII but now shows in HEX. See my GWM below. The Vin is correct at F190 but its in HEX.

716
<F10A>ML3T-14J009-EAJ</F10A>
<F110>DSMU5T-14G650-EC</F110>
<F111>MU5T-14H026-DA</F111>
<F113>MU5T-14G650-EAF</F113>
<F16C>ML3T-14J007-EAJ</F16C>
<F17F>1EG1CC0V</F17F>
<F188>ML3T-14H021-EAJ</F188>
<F18C>FUBCH21224031180</F18C>
<F190>3146544657315247314D4643323831383500000000000000</F190>

 

[kevinwright9]

Has anyone actually gotten their BlueCruise to start working in the last 48 hours? There are so many posts it's hard to tell, but it seems like it's just troubleshooting lately. I'm wondering if Ford has stopped sending the last set of APIM/GTWY out that we need.

I updated mine yesterday from Revision 244 up to current with Blue Cruise. Probably took 6 or 7 hours straight. I did the APIM update last, and after that was done, I did another scan, and that's when another APIM showed up. I used the Mongoose, and took my time when cycling from off to on, etc. I couldn't imagine it going any smoother, no DTCs showing up and everything seems to be working correctly. I will say I hadn't done much with Forscan so not sure if that made it easier or not.

 

[islandboy47]

I updated mine yesterday from Revision 244 up to current with Blue Cruise. Probably took 6 or 7 hours straight. I did the APIM update last, and after that was done, I did another scan, and that's when another APIM showed up. I used the Mongoose, and took my time when cycling from off to on, etc. I couldn't imagine it going any smoother, no DTCs showing up and everything seems to be working correctly. I will say I hadn't done much with Forscan so not sure if that made it easier or not.

Thanks for making my day with this great news! I'm going to kick off my updates tonight.

 

[Snakebitten]

That's good news.
Although it doesn't explain why some VINs will pull the final APIM update and others haven't yet, it does imply Ford hasn't yanked the updates.

 

[Ajzride]

I updated mine yesterday from Revision 244 up to current with Blue Cruise. Probably took 6 or 7 hours straight. I did the APIM update last, and after that was done, I did another scan, and that's when another APIM showed up. I used the Mongoose, and took my time when cycling from off to on, etc. I couldn't imagine it going any smoother, no DTCs showing up and everything seems to be working correctly. I will say I hadn't done much with Forscan so not sure if that made it easier or not.

well at least we know they are still releasing 244. I’ve been waiting 36 hours for it now. Won’t show up in FDRS.

 

[JEB]

I've notice in some modules the data is in HEX rather than ASCII. Something to worry about? Originally this VIN was in ASCII but now shows in HEX. See my GWM below. The Vin is correct at F190 but its in HEX.

716
<F10A>ML3T-14J009-EAJ</F10A>
<F110>DSMU5T-14G650-EC</F110>
<F111>MU5T-14H026-DA</F111>
<F113>MU5T-14G650-EAF</F113>
<F16C>ML3T-14J007-EAJ</F16C>
<F17F>1EG1CC0V</F17F>
<F188>ML3T-14H021-EAJ</F188>
<F18C>FUBCH21224031180</F18C>
<F190>3146544657315247314D4643323831383500000000000000</F190>

What programmer are you using to do these updates? I checked GWM Node F190 and it‘s reporting my VIN in normal ASCII.

 

[Platinum Peasant]

Everyone here waiting like…

 

[JEB]

I'm using the Mongoose. I updated it again and it cleared it up. My GWM has a hanging update that wont go away. Files all seem to be the same everytime. Who knows.


<F10A>ML3T-14J009-EAJ</F10A>
<F110>DSMU5T-14G650-EC</F110>
<F111>MU5T-14H026-DA</F111>
<F113>MU5T-14G650-EAF</F113>
<F16C>ML3T-14J007-EAJ</F16C>
<F17F>1EG1CC0V</F17F>
<F188>ML3T-14H021-EAJ</F188>
<F18C>FUBCH21224031180</F18C>
<F190>1FTFW1RG1MFC28185</F190>

Maybe your last network scan to clean up node F190 will kick up a fresh report to the Ford server and finally clear the update offer from the queue. Sometimes it takes a day.

Sponsored