ECU module programming guide using FDRS

[JScaro]

Got a question that somebody here may be able to answer. A member on the Mach-E forum who's APIM was 'stuck' due to an OTA used the USB method to get himself unstuck, rather than doing the whole TSB 22-2150 procedure with the various cables. He now has a concern that since he used the USB method to get unstuck and updated (don't know what version he's on currently) that he won't be able to get OTAs (says 2.6.0 has failed repeatedly) because corrupted data is still in the APIM even though he did get unstuck using the USB method.

I have not heard anything about this potential issue from anyone on this forum who has reported getting unstuck using the USB stick and leaving it in until it finally 'takes'.

Can anybody comment on the potential of this actually happening?

Mike

I'm one of the ones that got "unstuck" using the traditional USB method and it kick started right away.
Since then I never received an OTA and do believe my APIM / GWM / TCU is corrupt.
I have a Mongoose and year license and like doing the updates so I didn't worry about it.
Hoping in the long run things will sort themselves out.

Sponsored

 

[Mike G]

I'm one of the ones that got "unstuck" using the traditional USB method and it kick started right away.
Since then I never received an OTA and do believe my APIM / GWM / TCU is corrupt.
I have a Mongoose and year license and like doing the updates so I didn't worry about it.
Hoping in the long run things will sort themselves out.

Would doing a PMI on the GWM and APIM help out do you think?

Maybe @Jesse-Infotainment can chime in here on this topic cause I'd really like to know if getting the APIM unstuck using just the USB stick is just 'kicking the can down the road' as far as keeping future OTAs from downloading.

Myself personally, I couldn't care less about OTAs due to where I live. But if this is a problem and these folks should really be doing the 22-2150 procedure to get their APIMs unstuck instead of the USB stick method then we need to know that.

Mike

 

[BHunted1]

Spoke to ota dept this morn. They said the alleged fix they released still has not fixed ota. They are working on it again.
Believe it when I see it. I also do everything manually now but explained my frustration and would hope ota would work so we dont have to deal with these issues.

 

[JScaro]

Would doing a PMI on the GWM and APIM help out do you think?

Maybe @Jesse-Infotainment can chime in here on this topic cause I'd really like to know if getting the APIM unstuck using just the USB stick is just 'kicking the can down the road' as far as keeping future OTAs from downloading.

Myself personally, I couldn't care less about OTAs due to where I live. But if this is a problem and these folks should really be doing the 22-2150 procedure to get their APIMs unstuck instead of the USB stick method then we need to know that.

Mike

I didn't want to do a PMI on them since things "seem" to be working to my knowledge so don't fix what's not broken theory.
As long as I can update through FDRS - I could care less about OTA. I think Ford is still a few years behind on OTA to working properly.

 

[Snakebitten]

I don't think it's our trucks that are the failure point for OTA. At least not after you get past the infamous APIM snag Ford pushed that eventually triggered the TSB.

Afterall, regardless of whether the truck escaped that purgatory the TSB method or the USB stick, from then on countless trucks have what appears to be clean records in the cloud.

Not to mention that trucks have reported OTA success after the TSB or USB procedure got the APIM past that point.

Ford has the ball now. OTA is in their court again. In my opinion anyways. But I'm just one Ole man on the interweb. Lol

 

[BHunted1]

In lieu of what I mentioned, they admitted there is still a prob. I also told them, I believe they intentionally black listed early victims.

 

["Steve"]

miracles do happen.

 

[pmontalbano]

Anyone ever have an issue with an update disappearing from FDRS? I was going through all available updates and attempted to do the APIM and TCU modules. (They update together). When I inserted the USB drive into my truck, I got a message that this drive was not compatible. Since I needed some time to get another USB stick, I told FDRS that this update was not successful. It went on to the TCU update which I said to cancel. Both updates have now disappeared as available updates in FDRS. I have since gotten another USB stick that does work and I updated the GSM and ICP with this stick. Now I want to update the APIM and TCU modules, but I am unable to select them as available updates.

 

[Jesse-Infotainment]

Anyone ever have an issue with an update disappearing from FDRS? I was going through all available updates and attempted to do the APIM and TCU modules. (They update together). When I inserted the USB drive into my truck, I got a message that this drive was not compatible. Since I needed some time to get another USB stick, I told FDRS that this update was not successful. It went on to the TCU update which I said to cancel. Both updates have now disappeared as available updates in FDRS. I have since gotten another USB stick that does work and I updated the GSM and ICP with this stick. Now I want to update the APIM and TCU modules, but I am unable to select them as available updates.

Send me your vin. I’ll see if I can get them

 

[Snakebitten]

Well that answers that question.
OTA is definitely something Ford CAN push if you are past the TSB version

 

[pmontalbano]

Send me your vin. I’ll see if I can get them

Thanks Jesse, the VIN is 1ftfw1e84mfb62858

 

[Kanuck]

Please refresh my old warped memory please.... TSB version?

 

[mastacon]

Anyone in the Sacramento area have a mongoose cable?!?!?!

 

[BHunted1]

Well that answers that question.
OTA is definitely something Ford CAN push if you are past the TSB version

But not at a push of a button unfortunately.

 

[Mike G]

Please refresh my old warped memory please.... TSB version?

Previously on "ECU module programming guide using FDRS"...

Two members of both this forum and the Mach-E forum stated in separate posts that it was their belief that they overcame their 'stuck' version of the APIM software using the USB stick programming method (instead of following the TSB 22-2150 procedure with all the cables etc.) and as a result they suspect that although their APIMs did update to get past the 1.7.1 version, that they still may have some corrupted data bits that weren't cleared out using the USB stick process, and so it was felt that this is the reason they were not getting new OTA updates (I think in both cases they were seeing OTA 2.6.0 failing repeatedly).

So the vehicles are 'unstuck' but there is a suspicion that using FDRS to load the updated APIM module software to a USB drive and just leaving the drive in the vehicle's USB port until it finally does 'take' may not completely clear out the corrupted data bits that caused the OTA failures in the first place. I have not experienced this issue on my F-150, and on my Mach-E the APIM was replaced back in early Feb, and I don't get OTAs out here in the country where I live. And there is zero evidence to suggest that OTAs are delivered using wifi connections, despite Ford telling us to connect our vehicles up to our home wifi.

So, now you're caught up.

Mike

Sponsored