ECU module programming guide using FDRS

[Snakebitten]

I thought the CCM update was a part of a 4 module package of updates?
I know you could intentionally skip it, but maybe until it is accomplished, Ford's cloud wouldn't consider the combined update done, thus stalling the release of others.

Wasn't the very last main Bluecruise enabling update the 4-module package and it included the CCM?

I'm old and that was a loooong time ago.
I was the first (or second) to brick the CCM with the nano and then confirm that the Mongoose could recover a purple CCM.
(It was my previous 21 Platinum Powerboost)

Sponsored

 

[Big Dog Daddy]

I guess that’s another aspect that maybe I haven’t read enough of the forum to have all the info yet. But, I thought the nano corruption was limited to the data that gets sent to Ford via FDRS (hence avoiding the network scan workaround?), it does not impact the as built data in the truck. Is that valid? Or has it been determined that corrupt data could be written to the truck as a result of using the nano? In which case, yeah, the nano gets a big NO from me.

Everyone here on the forum is helping each other thru collective experience from the 1000's of posts we've all made. We all want to see you successfully update your truck! These guys don't want to set you up for failure, because when it happens it's very difficult to correct.

On completion of the USB update, created in fdrs, fdrs will continue on thru the odb cable and query the apim checking for a successful install, it will then do some programming changes to your as built to enable new software features. Finally it will report a successful install to the Ford cloud. At this point is where the nano creates the problem.

Sure ford approved the nano with there software, but there are known problems with it, who's fault is that Ford and fdrs or the manufacturer of the nano? Do you think Ford is going to rewrite there software to ensure compatability with it? Probably not. They don't care. They only care to make sure that there 2k VCM works for there dealership network. The bottom line is using the nano could leave you in an unrecoverable position, and your truck will be at the dealer for months to get repaired, if it's even possible as you've already screwed up the as built data they will rely on to repair your truck!

 

[Rineland]

Everyone here on the forum is helping each other thru collective experience from the 1000's of posts we've all made. We all want to see you successfully update your truck! These guys don't want to set you up for failure, because when it happens it's very difficult to correct.

On completion of the USB update, created in fdrs, fdrs will continue on thru the odb cable and query the apim checking for a successful install, it will then do some programming changes to your as built to enable new software features. Finally it will report a successful install to the Ford cloud. At this point is where the nano creates the problem.

Sure ford approved the nano with there software, but there are known problems with it, who's fault is that Ford and fdrs or the manufacturer of the nano? Do you think Ford is going to rewrite there software to ensure compatability with it? Probably not. They don't care. They only care to make sure that there 2k VCM works for there dealership network. The bottom line is using the nano could leave you in an unrecoverable position, and your truck will be at the dealer for months to get repaired, if it's even possible as you've already screwed up the as built data they will rely on to repair your truck!

Thanks @Big Dog Daddy ! That’s a thorough explanation of the issue with the nano and makes the workaround I was reading about still seem pretty risky. I appreciate the collective knowledge in this thread, it’s a lot to read through. I appreciate the warnings against using the nano, but I’m stubborn and need to understand all the data myself before I rule it out.
Mongoose it is. Can’t say I’m going to buy it just for an APIM update, but if there are other modules in need of updating, maybe it makes sense. Seems like there could be a business in this, traveling around updating Ford trucks for a fraction of the price of a mongoose and FDRS license. Hmmm…

 

[Jmendoza]

Thanks @Big Dog Daddy ! That’s a thorough explanation of the issue with the nano and makes the workaround I was reading about still seem pretty risky. I appreciate the collective knowledge in this thread, it’s a lot to read through. I appreciate the warnings against using the nano, but I’m stubborn and need to understand all the data myself before I rule it out.
Mongoose it is. Can’t say I’m going to buy it just for an APIM update, but if there are other modules in need of updating, maybe it makes sense. Seems like there could be a business in this, traveling around updating Ford trucks for a fraction of the price of a mongoose and FDRS license. Hmmm…

Shoot i think @rugedraw was loaning a mongoose (don't quote me if it was him ?). U pay him amount and he ships to you and when u return a refunds you amount .. could be a way to to this without purchasing

 

[JScaro]

Everyone here on the forum is helping each other thru collective experience from the 1000's of posts we've all made. We all want to see you successfully update your truck! These guys don't want to set you up for failure, because when it happens it's very difficult to correct.

On completion of the USB update, created in fdrs, fdrs will continue on thru the odb cable and query the apim checking for a successful install, it will then do some programming changes to your as built to enable new software features. Finally it will report a successful install to the Ford cloud. At this point is where the nano creates the problem.

Sure ford approved the nano with there software, but there are known problems with it, who's fault is that Ford and fdrs or the manufacturer of the nano? Do you think Ford is going to rewrite there software to ensure compatability with it? Probably not. They don't care. They only care to make sure that there 2k VCM works for there dealership network. The bottom line is using the nano could leave you in an unrecoverable position, and your truck will be at the dealer for months to get repaired, if it's even possible as you've already screwed up the as built data they will rely on to repair your truck!

@Big Dog Daddy
I don't think the Nano is approved anymore and really should be removed from the main page @iceman77

Just my 2 cents worth

Here's the list
https://www.motorcraftservice.com/diagnostic/FJDSSupport?categoryId=247

 

[Jesse-Infotainment]

There is a BCM update available. 21-22

It is two parts. SO it will install one file and then another BCM update will show right after.

It is safe to install. I am only letting people know so they arent wondering why there is another BCM update right after the one they did.

So it is two seperate BCM updates. Tehy both need to be done. Do ot stop after only the first one.

 

[Snakebitten]

Thanks Jesse for being both our notification alert, and our canary in the mine.

 

[Snakebitten]

By the way, I'm happy for BCM updates.
I think these trucks could use some polishing up in the 12V usage aspect. Maybe there's some good consequences related?

 

[Jesse-Infotainment]

By the way, I'm happy to BCM updates.
I think these trucks could use some polishing up in the 12V usage aspect. Maybe there's some good consequences related?

Not sure. Ford doesn’t give much in the way of info on these so it is hard to say

 

[dolsen]

@Big Dog Daddy
I don't think the Nano is approved anymore and really should be removed from the main page @iceman77

Just my 2 cents worth

Here's the list
https://www.motorcraftservice.com/diagnostic/FJDSSupport?categoryId=247

Glad to see that, I checked about a month ago and the Nano was still on there.

 

[TJSparky]

Not sure. Ford doesn’t give much in the way of info on these so it is hard to say

Updating now! Thanks Jesse!

 

[TJSparky]

So after the BCM update(s) I got this error. B14E5 :08-0A. Didn’t have this DTC before. Tried to do a clear and retest and it still came back. Everything seems to be working fine. Going to drive the truck a few days and will report back.

 

[RickBullotta]

So after the BCM update(s) I got this error. Didn’t have this DTC before. Tried to do a clear and retest and it still came back. Everything seems to be working fine. Going to drive the truck a few days and will report back.

That's why I get the chills every time a BCM update shows up. I hope it clears itself soon!

 

[TJSparky]

Ah the entire headlight and DRL for the left side is out now. Amber side marker is working though.

 

[speedracercjr]

Ah the entire headlight and DRL for the left side is out now. Amber side marker is working though.

Shit that's a pretty big problem

Sponsored