ECU module programming guide using FDRS

[Snakebitten]

Alexa already has the Fordpass skill, you can use the Alexa app to do just that. One of the best use case for me is to auto lock my truck at night before bed at 10:30PM everyday. Alexa announces she's locking my truck from the Echo Show in my living room. You can even unlock, start, stop truck too.

I wish Ford would have an option to auto lock the truck when walking away using the key fob proximity. I had that with other cars. For the first few months my truck was left unlocked all day/night until Alexa.

It'll be nice to have Alexa in the truck so I can tell her to open my garage as I'm pulling in or set my AC in the house as I drive home from work.

I was under the impression that the Alexa skill for FordPass was for Sync3?

Sponsored

 

[tcp]

I was under the impression that the Alexa skill for FordPass was for Sync3?

Probably also for Sync3 too, the skill description just says works with Sync. But can confirm it works for SYNC4. Been using it for almost a year now.

 

[Jesse-Infotainment]

Jesse,

I tried changing my job 2 2021 F150 to a 4 and it didn't work. I just wanted to let you know.

Ok, thanks. I wasnt 100% it may only be the 22 software then

 

[tcp]

1FTFW1ED0MFB66211

Before my license expires today... here ya go!

 

[MitchCox]

Before my license expires today... here ya go!

I think that one keeps showing up even after it is applied. At least it did for me. I installed it successfully and it refreshed and said it still needed it.

 

[RetroMan]

Sorry for the double ask but my other ask is now a few pages back. If somebody has the time for a FDRS vin check. 1FTFW1ED4MFB60461 Trying to see what I am up against in the coming days when my gear arrives.

 

[tcp]

Sorry for the double ask but my other ask is now a few pages back. If somebody has the time for a FDRS vin check. 1FTFW1ED4MFB60461 Trying to see what I am up against in the coming days when my gear arrives.

 

[tcp]

I think that one keeps showing up even after it is applied. At least it did for me. I installed it successfully and it refreshed and said it still needed it.

Yeah same here. I think I saw multiple reports of it doing the same to others as well so I'm not to worry.

 

[RetroMan]

Thank you very much

 

[mflynndelta]

Sorry. What state are you in? If you are in Kentucky near me, we can get it going.

no worries I am in North Carolina

 

[ENG430]

Can any one check my vin if I have a new update please.
My license expired last week.

1FTFW1E51MFC37912

 

[jordandev]

Ok. Here's how it went today after being stuck at 21281 for a few weeks (302A, with 360, without adaptive cruise)

Had TCU/APIM/IPC updates appear a couple days ago like the couple others with 302As.

1. started TCU -> 169 MB USB update
2. APIM update kicked off automatically next -> 866 MB USB update
3. truck now at 22087 revision 415
4. GWM update shows up -> 248 MB USB update
5. around 2.5 hours has passed (likely gave extra power off time etc…)
6. IPC update start -> non-USB -> 99198 steps… (oops wasn't quite ready for a long one, should have known from the IPC a few weeks ago ), been running for 3+ hours now and only half way

So likely ends up being 8-9 hours for these updates (close to what it was to get from 1.6 to 2.3.0 in the first place )

And yes… I've done these all with the Nano still (I know… but I don't have a CCM to brick and avoid network scans so haven't had issues)

 

[Paul Neubauer]

Ok. Here's how it went today after being stuck at 21281 for a few weeks (302A, with 360, without adaptive cruise)

Had TCU/APIM/IPC updates appear a couple days ago like the couple others with 302As.

1. started TCU -> 169 MB USB update
2. APIM update kicked off automatically next -> 866 MB USB update
3. truck now at 22087 revision 415
4. GWM update shows up -> 248 MB USB update
5. around 2.5 hours has passed (likely gave extra power off time etc…)
6. IPC update start -> non-USB -> 99198 steps… (oops wasn't quite ready for a long one, should have known from the IPC a few weeks ago ), been running for 3+ hours now and only half way

So likely ends up being 8-9 hours for these updates (close to what it was to get from 1.6 to 2.3.0 in the first place )

And yes… I've done these all with the Nano still (I know… but I don't have a CCM to brick and avoid network scans so haven't had issues)

It makes zero sense why these updates take so long to install! An iPhone can update over a gigabyte file in less than 10 minutes but Ford still can't figure this thing out.

 

[Snakebitten]

I'm assuming that there's a legitimate explanation for why updating your iPhone VS your IPMA or APIM are not the same thing. But I do believe that Ford could improve read/write speeds at a co$t.

 

[morrisosu]

Ok. Here's how it went today after being stuck at 21281 for a few weeks (302A, with 360, without adaptive cruise)

Had TCU/APIM/IPC updates appear a couple days ago like the couple others with 302As.

1. started TCU -> 169 MB USB update
2. APIM update kicked off automatically next -> 866 MB USB update
3. truck now at 22087 revision 415
4. GWM update shows up -> 248 MB USB update
5. around 2.5 hours has passed (likely gave extra power off time etc…)
6. IPC update start -> non-USB -> 99198 steps… (oops wasn't quite ready for a long one, should have known from the IPC a few weeks ago ), been running for 3+ hours now and only half way

So likely ends up being 8-9 hours for these updates (close to what it was to get from 1.6 to 2.3.0 in the first place )

And yes… I've done these all with the Nano still (I know… but I don't have a CCM to brick and avoid network scans so haven't had issues)

That IPC upgrade was brutal...be sure ya got a power supply and connect the neg to the chassis. Don't make the mistake I did and missed the note about not connecting directly to the battery...sounds like the BMS gets wonky if you do.

Sponsored