ECU module programming guide using FDRS

[RellIk&5]

The OTAs are hard to say what level. OTA coincides with a update that you have done manually.

The updates for ota have been targeted up until 2.3.0 and it did the APIM and TCU

1.4.0 was TCU - Securalert
1.6 was gateway
1.7.1 was APIM 21146
2.0 was gateway
2.1.1 was gateway
2.3.0 was APIM/TCU they had to be done at the same time
2.4.1 was Gateway a fix for the Zone light Drain
2.4.3 was Step One IPC update
2.4.4 was step two IPC update
2.4.5 was an APIM update to 20282
2.5.1 was 4 Modules IPMA, CCM, CMR, PSCM


So to ask what version OTA you are at is not relevant when you have been manually updating.

Every update up until 2.5.1 has been released on FDRS. The other thing is if you have updated modules they have no association with an ota and otherwise would have not been updated.

I used to have Securalert in my Ford app, but whenever I tried to enable alerts for only specific schedules I would get a server error. Then all of a sudden the Securalert option disappeared from my ford app. I've manually updated to 2.4.1, so not sure if one of my updates didn't fully take and that's why Securalert is now gone or what???

Sponsored

 

[Jesse-Infotainment]

Has to do with the network scna.. Iceman has a solution

 

[BHunted1]

Seriously? This was you, right? https://www.f150gen14.com/forum/threads/power-up-2-3-0-ota-rolling-out.7724/post-155699

After all this time, you’re holding that against me? Comeon man, we’re all frustrated. Its not personal. Sheesh.
And you were needling me dude.

 

[BHunted1]

The OTAs are hard to say what level. OTA coincides with a update that you have done manually.

The updates for ota have been targeted up until 2.3.0 and it did the APIM and TCU

1.4.0 was TCU - Securalert
1.6 was gateway
1.7.1 was APIM 21146
2.0 was gateway
2.1.1 was gateway
2.3.0 was APIM/TCU they had to be done at the same time
2.4.1 was Gateway a fix for the Zone light Drain
2.4.3 was Step One IPC update
2.4.4 was step two IPC update
2.4.5 was an APIM update to 20282
2.5.1 was 4 Modules IPMA, CCM, CMR, PSCM


So to ask what version OTA you are at is not relevant when you have been manually updating.

Every update up until 2.5.1 has been released on FDRS. The other thing is if you have updated modules they have no association with an ota and otherwise would have not been updated.

Is there any info I can send ya from my recent updates?

 

[Static]

The OTAs are hard to say what level. OTA coincides with a update that you have done manually.

The updates for ota have been targeted up until 2.3.0 and it did the APIM and TCU

1.4.0 was TCU - Securalert
1.6 was gateway
1.7.1 was APIM 21146
2.0 was gateway
2.1.1 was gateway
2.3.0 was APIM/TCU they had to be done at the same time
2.4.1 was Gateway a fix for the Zone light Drain
2.4.3 was Step One IPC update
2.4.4 was step two IPC update
2.4.5 was an APIM update to 20282
2.5.1 was 4 Modules IPMA, CCM, CMR, PSCM


So to ask what version OTA you are at is not relevant when you have been manually updating.

Every update up until 2.5.1 has been released on FDRS. The other thing is if you have updated modules they have no association with an ota and otherwise would have not been updated.

This is interesting, my truck stalled on 1.4.0 but I'm pretty sure I got 1.6. Haven't been able to get any OTA updates after that. Never had the issues with not being able to turn on Auto updates or see the sync version, just always failed the OTA's after they rolled through their install windows, and now it has stopped trying anything, the last window I had was from Feb.

 

[Shoebox72069]

This is interesting, my truck stalled on 1.4.0 but I'm pretty sure I got 1.6. Haven't been able to get any OTA updates after that. Never had the issues with not being able to turn on Auto updates or see the sync version, just always failed the OTA's after they rolled through their install windows, and now it has stopped trying anything, the last window I had was from Feb.

You likely got a broken 1.7.1 which exploded for a lot of people. I finally got mine fixed after creating an USB from FDRS and leaving it plugged in for a month. I haven't heard any official word from Ford yet either on a supposed fix they were supposed to have for it...

 

[Snakebitten]

The OTAs are hard to say what level. OTA coincides with a update that you have done manually.

The updates for ota have been targeted up until 2.3.0 and it did the APIM and TCU

1.4.0 was TCU - Securalert
1.6 was gateway
1.7.1 was APIM 21146
2.0 was gateway
2.1.1 was gateway
2.3.0 was APIM/TCU they had to be done at the same time
2.4.1 was Gateway a fix for the Zone light Drain
2.4.3 was Step One IPC update
2.4.4 was step two IPC update
2.4.5 was an APIM update to 20282
2.5.1 was 4 Modules IPMA, CCM, CMR, PSCM


So to ask what version OTA you are at is not relevant when you have been manually updating.

Every update up until 2.5.1 has been released on FDRS. The other thing is if you have updated modules they have no association with an ota and otherwise would have not been updated.

@JEB
This is what I meant.
I never have to ask him because with just a little patience.....
Technically, THAT post ^ wasn't trickle down.
It was a full on waterfall. Lol

Again, thank ALL you guys for your tenacity and generosity.

 

[JEB]

Has to do with the network scna.. Iceman has a solution

Here is @iceman77 ’s fix for the missing SecuriAlert function. https://www.f150gen14.com/forum/threads/ecu-module-programming-guide-using-fdrs.8249/post-167846

 

[Snakebitten]

After all this time, you’re holding that against me? Comeon man, we’re all frustrated. Its not personal. Sheesh.
And you were needling me dude.

That was you?
I do remember reading it. It was a pretty good rant! A classic. Lol

I don't speak for anyone but myself but I remember thinking, at the time, man can these new complicated and "unfinished" trucks be irritating. And you were the perfect example.

Currently my empathy is BIG TIME for Iceman. As helpful as he has been, he's getting the WORST luck imaginable with his truck. If he lived close by I would swap exhaust heat exchangers with him and I would wait for the new part to ship. I have other cars to drive, so I wouldn't even feel the pain of no rental/loaner from the dealership.

 

[tonesto7]

I'm looking for VINs guys. I'm trying to collect some data and test something I recently created so the more VINs you PM the better.

I'm trying to build out some module data info, plus this will also help with letting you guys know when you may have updates available.

 

[Bob_Mac]

I'm looking for VINs guys. I'm trying to collect some data and test something I recently created so the more VINs you PM the better.

I'm trying to build out some module data info, plus this will also help with letting you guys know when you may have updates available.

You should already have mine...

 

[abd79]

I'm looking for VINs guys. I'm trying to collect some data and test something I recently created so the more VINs you PM the better.

I'm trying to build out some module data info, plus this will also help with letting you guys know when you may have updates available.

PM’d you

 

[BHunted1]

Ever see this number for the Sync?

DID F0E9 - FFF1-14D358-FF

 

[JEB]

Ever see this number for the Sync?

DID F0E9 - FFF1-14D358-FF

Yes. I’ve seen it, at least the part beginning “FFF1.” So has @Snakebitten and @TJSparky . They posted screenshots around post 1018. It seems to be a bug in FDRS when displaying the APIM strategy. It will show a normal strategy after a network scan and then a couple of hours later it’ll change to this nonsense. And then it will change back.

 

[Snakebitten]

Yep
I can launch FDRS without any adapter, pull from the mothership, and get different values for the APIM than I get 2 minutes later if I repeat the whole process.

So it's definitely ONLY an FDRS related phenomenon since there's no influence from the truck itself or an adapter.

I haven't actually seen any impact that I've noticed. But who knows?

Sponsored