ECU module programming guide using FDRS

[Jesse-Infotainment]

They do work.. I just usually dont wait long enough to find out. These updates I do not believe were pushed out in a large scale. So this would have been a bad test case. After these updates I will be waiting for OTAs unless its an update I really need to do asap.

Sponsored

 

[Snakebitten]

Stupid question, for those of you that have updated your software through FDRS or other manual methods, do your OTA updates work now?

I'm a little intimidated and not thrilled about buying hardware and a license to update my truck, but may be willing to go that route if it is just a one-time thing to catch me up and get me receiving future OTA updates.

How would we know?
FRDS is like crack once you.... Well, you know what I mean. ??

Of all the people willing to WAIT to see if their truck is going to get the next OTA, you aren't likely to find them here.

Or put another way, around here the news that a new module update is available takes maybe 2 minutes to be shared. Then everyone with an expired 2-day license starts going out to their truck to check if their OTA settings are just right. Then start agonizing as they basically watch the clock..... Soon to fold and re-up their license.

I'm just saying.

 

[speedracercjr]

On that same vein - anyone know how long it takes to get caught back up on OTA? I think I'm over the 1.7.1 hump after kicking my APIM but its been a week of happy run time and I haven't seen an OTA yet.

I was hoping I would see at least one before I grab the software and start catching things back up, which I was going to do regardless.

@Jesse-Infotainment correct me if I'm wrong but Shoe will have to update via FDRS because 1.7.1 and 2.1 are "old" in the OTA server eyes and aren't being pushed, right?

 

[Shoebox72069]

@Jesse-Infotainment correct me if I'm wrong but Shoe will have to update via FDRS because 1.7.1 and 2.1 are "old" in the OTA server eyes and aren't being pushed, right?

It's like you read my mind! This is exactly why I was asking.

Not really a good thing for folks that arent aware nor do they want to start poking... if you have to pay for software and catch it up yourself. I however enjoy the adventure!

 

[BHunted1]

Yup. Just happened to me. Just updated a week ago, days later more came out.
Just my timeline.
- First ota was Nov 2021. Twice, it came and twice it failed.
- Myself and dealer got fed up because they were failing.
- Ford ok’ed Apim replacement. Tech updated only what it took to complete the install.
- Weeks went by, no ota.
- Got fed up and bought a Nano. Sub for 2 days of fdrs license. 3 Times!
- As of today, STILL no otas.
- Still no BC.
I’m more pist that ford has new 2022 vehicles that have everything functioning.
My truck was built Feb ‘21 so I’m considered a job 1 truck.
It’s been a long battle with Ford and you’d think they’d rush these fixes for early buyers and slow down reinventing the wheel with new vehicles. But you know that won’t happen.
I’ll never learn my lesson and wait till bugs are worked out of first time new vehicles. But I keep burning my hands on the stove. ?

 

[Jesse-Infotainment]

@Jesse-Infotainment correct me if I'm wrong but Shoe will have to update via FDRS because 1.7.1 and 2.1 are "old" in the OTA server eyes and aren't being pushed, right?

He could get lucky and get the 2.3.0 OTA still. It’s a crap shoot. He would be best in my opinion to get to the latest as of today and work from there . The early OTAs do not seem to be that reliable. These later ones seem better but people are still having issues.

In truck is always better if it’s an option. The other thing I tell people is there are several updates to modules not touched by OTAs. I would feel it’s best practice to get everything done you can now to be at least as far up to date as the job 2 and 22 trucks are

 

[TJSparky]

Selling my VCX nano if anyone is interested. I’m gonna get the Mongoose and try that.

https://www.f150gen14.com/forum/threads/vxdiag-vcx-nano-red-ford.9383/

 

[Snakebitten]

My VCX nano will join the drawer in my roll around toolbox that has accumulated a fair amount of distinguished ODB devices.
Enough of them that at times I can't recall or distinguish the original reasoning behind the acquisition.
Currently the Porsche, the Mazdarati, and the Powerboost all have unique ones. You'd think that the software on the other end of the cable would be the only thing different between the vehicles. Alas, it's just not that standardized.

 

[JEB]

My VCX nano will join the drawer in my roll around toolbox that has accumulated a fair amount of distinguished ODB devices.
Enough of them that at times I can't recall or distinguish the original reasoning behind the acquisition.
Currently the Porsche, the Mazdarati, and the Powerboost all have unique ones. You'd think that the software on the other end of the cable would be the only thing different between the vehicles. Alas, it's just not that standardized.

You are almost at the point where you should consider getting a multi-brand programmer, like Opus’ CarDAQ-Plus 3. They’re expensive, but you’ll have room to grow. You might need it. https://www.opusivs.com/products/j2534-pass-thru/cardaq-0?hsLang=en

 

[Jaug]

Pretty sure it would be an immediate post if it was there but gonna ask anyways. Anyone have the GWM show up yet to complete the BC updates. I didn’t have time before work to check. If Ford is watching this thread how about hooking us up since we are basically your free (paying out of our own pockets) Guinea pigs for what your techs will be doing.

 

[abd79]

For anyone interested below is the procedure I used to verify my setup for proper cameras in motion and BC.

1 - I found a donor 2021 Job2 truck on a dealers lot exactly the same as mine with BC on the window sticker (Minus mine is a powerboost and the donor one was a 5.0) and compared IPC, APIM and IPMA settings.

2 - I downloaded my AB and the donor trucks AB information

3 - Renamed the AB files from .ab to .xml

4 - Used WinMerge to "Prettfy the XML" and compared the values. I use @livinitup's spreadsheet to verify non important/truck specific info and only changed what was necessary.


These are all the changes I made to match the job2 truck with BC from factory.

IPMA
706-02-02 xxxF CExx xx--
706-04-01 xxxx 1xxx xx--

APIM
7D0-01-01 xxxx xxxx Bx--
7D0-01-02 Axxx xxxx xx--
7D0-01-03 xxxx xxxx xF--
7D0-01-04 xxxx FCxx 6x--
7D0-02-01 8xxx xxxx xx--
7D0-09-04 xxxx xxxx Fx--

IPC
720-01-02 xxxx Bx--

** Please note that some of these may be different for you and your truck. Mine is a Canadian Job1 Lariat Sport PowerBoost, attached is a snippet of my widow sticker for reference.

 

[abd79]

Pretty sure it would be an immediate post if it was there but gonna ask anyways. Anyone have the GWM show up yet to complete the BC updates. I didn’t have time before work to check. If Ford is watching this thread how about hooking us up since we are basically your free (paying out of our own pockets) Guinea pigs for what your techs will be doing.

No GWM update as of yet. Just checked.

 

[heffer86]

For anyone interested below is the procedure I used to verify my setup for proper cameras in motion and BC.

1 - I found a donor 2021 Job2 truck on a dealers lot exactly the same as mine with BC on the window sticker (Minus mine is a powerboost and the donor one was a 5.0) and compared IPC, APIM and IPMA settings.

2 - I downloaded my AB and the donor trucks AB information

3 - Renamed the AB files from .ab to .xml

4 - Used WinMerge to "Prettfy the XML" and compared the values. I use @livinitup's spreadsheet to verify non important/truck specific info and only changed what was necessary.


These are all the changes I made to match the job2 truck with BC from factory.

IPMA
706-02-02 xxxF CExx xx--
706-04-01 xxxx 1xxx xx--

APIM
7D0-01-01 xxxx xxxx Bx--
7D0-01-02 Axxx xxxx xx--
7D0-01-03 xxxx xxxx xF--
7D0-01-04 xxxx FCxx 6x--
7D0-02-01 8xxx xxxx xx--
7D0-09-04 xxxx xxxx Fx--

IPC
720-01-02 xxxx Bx--

** Please note that some of these may be different for you and your truck. Mine is a Canadian Job1 Lariat Sport PowerBoost, attached is a snippet of my widow sticker for reference.

Have you checked out the AsBuilt/ForScan backup comparer? I compare downlaoded AsBuilt data and my saves from Forscan very easily.

http://www.compulsivecode.com/Project_AsBuiltCompare.aspx

 

[abd79]

Have you checked out the AsBuilt/ForScan backup comparer? I compare downlaoded AsBuilt data and my saves from Forscan very easily.

http://www.compulsivecode.com/Project_AsBuiltCompare.aspx

Nice! Nope haven’t used that one before. Adding it to my tool bag. Thanks!

 

[abd79]

Interesting document from the Opus (Mongoose) website. I'm not sure if this is %100 accurate or not but this document recommends not having IDS and FDRS installed on the same machine. I currently have both installed on a single laptop and don't have any problems that I notice, can anyone confirm if this is true and we should not have IDS on the same laptop as FDRS? I don't use IDS often so don't mind getting rid of it if that's the case.

Sponsored