Request VIN Lookup Thread

[S14suspense]

The update failed the same day it was sent to you on 12/15 due to a manifest mismatch. The server did not send the correct files to your truck and your truck rejected the OTA. What you are seeing is a phantom message that you can ignore. There is nothing you can do but wait for the update to be sent to you again.

Interesting, thanks again.

Sponsored

 

[jwwadkins]

I doubt they will replace the APIM because they were able to successfully update it; there would be no need to replace it if that's the case. After they APIM, they tried to update the TCU. First time, it failed and the second time it failed, they were given the option to update it via CAN instead of USB. When FDRS said it would take an hour to do, they exited the program and did not update it.

Thanks,

I will do the updates with FDRS. They ordered a APIM back in September or October. My APIM was locked, for too many tries to fix OTA. I hope I didn't wait all that time for nothing.

 

[rugedraw]

Thanks,

I will do the updates with FDRS. They ordered a APIM back in September or October. My APIM was locked, for too many tries to fix OTA. I hope I didn't wait all that time for nothing.

If I remember correctly, a locked out APIM will eventually get unlocked and can be updated, but I'm not 100% sure about that. I believe I remember reading that somewhere. Maybe someone else can chime in and verify if that is the case or not.

 

[jwwadkins]

As long as it's updateable I am good with whatever they did. I will try to start all the other updates this coming weekend.

Thanks again
rugedraw

 

[Roger1108]

Thank you, RugeDrew, the dealership responded back and said that the APIM program works, they said it has the latest software? What is your advice to do now? What would my next steps with Ford.
Thanks for the info about Secure Alert, didn't know lol. One thing that I do know that I didn't get any OTA updates, never seen anything on screen but "you're up to date" lol
Thanks again! Roger

 

[rugedraw]

Whoever you spoke to is either incompetent or a liar. Your truck is on Sync 20301. Attached is general service bulletin 23-7146 sent to all Ford dealers in October. In the GSB there a link to the attached pdf that advises dealers of the latest Sync version for all Ford connected vehicles.

The screenshot below is from Ford dealer website indicating what Sync version your truck is on. The install date is 6/28/2021 which is the same day your truck was built. This is a very clear indicator that your truck has never gotten an update and is on very old software.

 

[Roger1108]

Whoever you spoke to is either incompetent or a liar. Your truck is on Sync 20301. Attached is general service bulletin 23-7146 sent to all Ford dealers in October. In the GSB there a link to the attached pdf that advises dealers of the latest Sync version for all Ford connected vehicles.

The screenshot below is from Ford dealer website indicating what Sync version your truck is on. The install date is 6/28/2021 which is the same day your truck was built. This is a very clear indicator that your truck has never gotten an update and is on very old software.

OMG Rugedrew, you have so much wealth of information!! I don't know what to do without the you and the forum family. I will wait till I hear back from Ford, I might have to go to another dealership if they are not willing to go through the steps to get my truck to update.
Thank you again!! Roger

 

[00Dan]

1FTFW1ED2MFB61365

I updated everything via FDRS in October. In December, I received 6.3.0 via OTA. Now the weird part - this month I got a notification for an update scheduled to install overnight, and it’s 6.3.0 again. Selecting update details says 6.3.0 has not been installed. Further, it never goes past the scheduled notification; I’ve never received a failure message.

 

[rugedraw]

1FTFW1ED2MFB61365

I updated everything via FDRS in October. In December, I received 6.3.0 via OTA. Now the weird part - this month I got a notification for an update scheduled to install overnight, and it’s 6.3.0 again. Selecting update details says 6.3.0 has not been installed. Further, it never goes past the scheduled notification; I’ve never received a failure message.

You can ignore that message. OTA 6.4.0 was sent to you on 12/20 and the OTA timed out and failed on 1/3. It does not seem like your truck was started or driven at all during that time, so the OTA trigger was never activated. It will eventually be resent to you.

 

[mau47]

It seems like they did replace the SCCM on 12/27 and updated some modules. On 12/29, it seems they were messing with the SCCM again. On 1/4, they did some reading in PTS about some TSB's maybe looking for some help to fix it. The truck seems to have been untouched since then. It is possible they are waiting on engineering to get back to them as they are stuck.

Great, thanks for checking again, not sure why they backtracked saying they didn't replace the SCCM when they did. Is it typical of Ford to take 2-3+ weeks to respond to requests from a dealer?

 

[rugedraw]

Great, thanks for checking again, not sure why they backtracked saying they didn't replace the SCCM when they did. Is it typical of Ford to take 2-3+ weeks to respond to requests from a dealer?

I've seen cases where it has taken that long. Right now, the engineers have their hands full with a bunch of stuff. I would not be surprised if things are delayed more than usual.

 

[JEB]

This is what my truck shows from the August 12th OTA. This is a PCM update, and I have not gotten a OTA or PCM update since. This make me think that this is stopping my truck from getting OTA's. I have some updates in FDRS and was thinking about doing them this coming week.

What is the thoughts of doing a PMI on the PCM module and see what pops up in FDRS?

EDIT:
This is what my as-builts is showing... could the highlighted error be causing my lack of OTA's?
<NODEID>
7E0
<F110>DSML3A-12A650-RVD</F110>
<F111>ML3A-12B684-KKA</F111>
<F113>ML3A-12A650-GMC</F113>
<F17F>1BE05CN7</F17F>
<F188>ML3A-14C204-VXC</F188>
<F18C>7834099211013</F18C>
<F190>1FTFX1E81MKE01710</F190>
<F1E0>PXML3A-12A650-RVD</F1E0>
</NODEID>
<ERROR>
<ERRORCODE>612</ERRORCODE>
<ERRORMSG>PCM DATA NOT FOUND</ERRORMSG>
</ERROR>
<ERROR>
<ERRORCODE>614</ERRORCODE>
<ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
</ERROR>

The error codes you are seeing in your as-built are common. I have them, other F-150s I’ve looked at have them. I even saw the same errors in a Bronco Sport. I don’t think they have anything to do with you not receiving OTAs.

 

[Big Dog Daddy]

@rugedraw can you check and respond to @DansFord here. He needs a fdrs check I'm sure! stuck on 1 7.1 vin in picture below.

 

[Kanuck]

The error codes you are seeing in your as-built are common. I have them, other F-150s I’ve looked at have them. I even saw the same errors in a Bronco Sport. I don’t think they have anything to do with you not receiving OTAs.

Thanks Jeb... was just a thought. The FORD OTA GODS just don't like me for some reason. FDRS is my friend..lol

 

[rugedraw]

@rugedraw can you check and respond to @DansFord here. He needs a fdrs check I'm sure! stuck on 1 7.1 vin in picture below.

@DansFord Your truck is on Sync 20301 which is old software from 2020 known to break the OTA process. Your dealer needs to manually update your APIM or diagnose it as faulty and replace it with a new one. Otherwise, your truck will never get any updates.

Sponsored