ECU module programming guide using FDRS

[rugedraw]

I've seen "PMI" mentioned in the ECU Module Programming Guide but I have no clue what that is. Can you elaborate or provide a link to an explanation?

Thanks

The only time you need to PMI a module is if something goes wrong during the updating process. When you start updating, if you come across an issue, post it here with a screenshot and we'll guide you through it.

Sponsored

 

[Erikp]

So with FDRS are the non-dealer versions able to perform PMIs? I was just told they were not and I have no experience to say otherwise. Can anyone confirm?

If performing a PMI on an out of date system, and the module is dead and cannot pull config from original module is it true its required to start from as-built data and requiring it to be updated to latest software?

in other words, will a 100% bricked BCM force the entire system to need to be updated to current software?

im not new to diagnostic software, but never used FDRS and I’m not sure if I’m gunna be over my head with all the other modules by trying to replace JUST me BCM on a truck running software from 2021

 

[rugedraw]

So with FDRS are the non-dealer versions able to perform PMIs? I was just told they were not and I have no experience to say otherwise. Can anyone confirm?

If performing a PMI on an out of date system, and the module is dead and cannot pull config from original module is it true its required to load latest software version for the VIN requiring you to update all other modules?

debating tackling this issue myself

Non-dealer FDRS can do PMI. The right thing to do when doing the PMI, is selecting "no" when FDRS asks if it is the original module. That way, instead of loading original AB data, it will load the latest available data based on the software state of the module network.

 

[Erikp]

Non-dealer FDRS can do PMI. The right thing to do when doing the PMI, is selecting "no" when FDRS asks if it is the original module. That way, instead of loading original AB data, it will load the latest available data based on the software state of the module network.

that’s what I thought, dealer seems to figure as built was the only way to replace the dead BCM. I don’t know enough to say other wise.

im waiting to hear back from ford engineers before I make my decision to tow my truck out of there and fix it myself.

 

[rugedraw]

that’s what I thought, dealer seems to figure as built was the only way to replace the dead BCM. I don’t know enough to say other wise.

im waiting to hear back from ford engineers before I make my decision to tow my truck out of there and fix it myself.

Due to your situation, I can move you to the top of the list to borrow one of my mongoose cables if that's what you decide to do.

 

[JEB]

If performing a PMI on an out of date system, and the module is dead and cannot pull config from original module is it true its required to start from as-built data and requiring it to be updated to latest software?

in other words, will a 100% bricked BCM force the entire system to need to be updated to current software?

I’m not sure I completely understand your question, but PMI’s are not configurable—they are automated. By default, they automatically grab and load the latest software available for a module along with the as-built configuration data previously saved to the cloud. You can’t direct the PMI otherwise. If that new software grabbed during the PMI conflicts with the software in other modules, it could conceivably trigger an FDRS prompt to update other modules once the PMI is completed.

 

[Erikp]

I’m not sure I completely understand your question, but PMI’s are not configurable—they are automated. By default, they automatically grab and load the latest software available for a module along with the as-built configuration data previously saved to the cloud. You can’t direct the PMI otherwise. If that new software grabbed during the PMI conflicts with the software in other modules, it could conceivably trigger an FDRS prompt to update other modules once the PMI is completed.

that answered the question. PMI will grab latest software, and not what was already in the dead BCM correct? Would explain all my issues then.

 

[JEB]

that answered the question. PMI will grab latest software, and not what was already in the dead BCM correct? Would explain all my issues then.

Yes.

 

[Erikp]

Yes.

Thanks for the help. Some really knowledgeable people on these pages.

 

[Braeden]

Anyone noticing FDRS login issues today?

 

[fordtruckman2003]

Huh? Isn't "10th 11th 12th" 3 calendar days? I'm going to buy a 2-day license soon. This information could be very useful.

10th + 2 = 12th

If you buy early on first day you can squeeze 3 full days out of it. It starts working immediately that day, then you get two full days after.

 

[Kanuck]

that answered the question. PMI will grab latest software, and not what was already in the dead BCM correct? Would explain all my issues then.

Where in Canada are you?

 

[Erikp]

Where in Canada are you?

Vancouver island, BC.

 

[Kanuck]

Vancouver island, BC.

What exactly are you trying to do to your truck? Fix or update or hoth?

 

[Erikp]

What exactly are you trying to do to your truck? Fix or update or hoth?

Repair it. I’ve been all over forums and such and I’ve probably explained it in this post too, but in case not the short story is BCM replacement required updates of all modules, and in doing so they bricked the IPC and they can’t get it to update or do a PMI now.

im getting frustrated with ford dragging their feet and am tempted to tow it away and deal with it myself as I have multiple trips in jeopardy now that I won’t a have a truck for the foreseeable future. I’m told up to 2 weeks to hear back from ford (it’s been 5 day), any module or likely part is a week away, and they’re booking a week out. 4-5 weeks is the timeline I’m given.

while it’s possible the IPC is bricked for good, I feel with FDRS and enough time and effort (and the great knowledge on this thread) I can get it sorted.

Sponsored