ECU module programming guide using FDRS

[Snakebitten]

I think it's the value we see as DID F188 in FDRS?

So is Forscan rendering the F188 value as
Part Number?
Calibration level?
Strategy?
Calibration?

I am just spitballing. The gurus around here will know.

Sponsored

 

[Paul Neubauer]

Quick question and sorry if it's been asked before: when we refer to "BBC" as the software version, is that one of the things I can see in FORScan for the IPMA? Mine below (lane centering no issues):

I think it is the strategy line which on your screenshot is showing ACJ.

 

[Kanuck]

If I remember correctly...last time I compared my As Builts to Forscan...it was the Strategy in Forscan that matched F 188 on the As Builts

 

[Big Dog Daddy]

@SilverPigeon the IPMA f188 on my truck is ACJ I believe the latest update would bring you to BBC.

 

[SilverPigeon]

Thanks guys ?

 

[Kanuck]

If it would help...I can dig out my laptop and see what my XLT is.

 

[Kanuck]

I did any way....
Previous version was ACJ
FDRS as of Nov 9, 24 PTS as of Nov 13, 24 Forscan Nov 9,24 all show RJ6T-14H102-BBC

 

[SilverPigeon]

I did any way....
Previous version was ACJ
FDRS as of Nov 9, 24 PTS as of Nov 13, 24 Forscan Nov 9,24 all show RJ6T-14H102-BBC

Thanks again Don ?

 

[superfordman]

@SilverPigeon the IPMA f188 on my truck is ACJ I believe the latest update would bring you to BBC.

Correct, just save yourself and stay on ACJ, BBC is the new broken one

 

[JEB]

Thanks guys ?

If you want a more expansive view of your module programming, you can also download your as-built data directly from motorcraftservice.com and open it with an XML reader. The IPMA will look something like this:

<NODEID>706
<F10A>ML3T-14H106-EFE</F10A>
<F110>DSPJ6T-14G647-AG</F110>
<F111>ML3T-14H107-FF</F111>
<F113>ML3T-14G647-NA</F113>
<F120>PJ6T-14H102-MDG</F120>
<F121>RJ8T-14H102-TBA</F121>
<F122>RJ8T-14H102-GAB</F122>
<F124>RJ6T-14H103-BBA</F124>
<F125>PL3T-14H103-BBN</F125>
<F127>RJ6T-14H103-GAA</F127>
<F129>ML3T-19G490-BC</F129>
<F12A>ML3T-19G490-BB</F12A>
<F12B>ML3T-19J220-AB</F12B>
<F12C>ML3T-19J220-AB</F12C>
<F16B>ML3T-14H310-EDD</F16B>
<F17F>1AA156IO</F17F>
<F188>RJ6T-14H102-BBC</F188>
<F18C>ECUR2107902169</F18C>
<F1DC>SL3T-14H103-GDC</F1DC>
<F1E0>PXML3T-14G647-AA</F1E0>
<F1F3>28741964</F1F3>
</NODEID>

 

[rugedraw]

Probably isn’t. I only ask because I’m still personally a little scared of FORScan Beta, which is what I expect you used to revert and roll back the first round of installs. I keep Beta around for ”in case of emergency, break glass” situations, but I remain a little concerned about relying on one software package to revert and remove absolutely everything installed by another software package, leaving nothing of the original install behind. Probably unwarranted skepticism, but for me it’s there.

FORScan Beta is a life saver.

Yep, I'm cooked, whenever it can or could engage LC, get this new warning showing up now...

I know you know more about this kind of stuff than the average person. If you feel up to the task, I can get you the files for ACJ so you call roll yourself back. Or reach out to Jesse and he can help you out. It takes three hours to flash just like updating it does, but all he would have to do is remote in to get it going.

 

[JEB]

FORScan Beta is a life saver.

Indeed it is. I‘ve used it for life-saving, notwithstanding its limitations. I remain concerned about it, but I think everyone who works on Ford electronics should have a copy of it and at least a working knowledge of their own about how to use it, what it can do and what it can’t. The first two stickies here are a good place to start. https://forscan.org/forum/viewforum.php?f=13&sid=549dece07c8af7f378e371e5471fe3db

 

[rugedraw]

Indeed it is. I‘ve used it for life-saving, notwithstanding its limitations. I remain concerned about it, but I think everyone who works on Ford electronics should have a copy of it and at least a working knowledge of their own about how to use it, what it can do and what it can’t. The first two stickies here are a good place to start. https://forscan.org/forum/viewforum.php?f=13&sid=549dece07c8af7f378e371e5471fe3db

Admittedly, I used to be terrified of the beta version, but after seeing the amount of issues that have been resolved with it in the hands of a capable user, I'm a huge fan.

 

[JEB]

Admittedly, I used to be terrified of the beta version, but after seeing the amount of issues that have been resolved with it in the hands of a capable user, I'm a huge fan.

I am a fan, too. Sometimes it’s your only hope. But it’s a powerful and dangerous program and, unfortunately, it can’t fix everything. Case in point: the recent IPMA problem. It can get you out of a bad install and get you back to where you were, but for now that seems to be about as far as you can go.

 

[Dave79]

Admittedly, I used to be terrified of the beta version, but after seeing the amount of issues that have been resolved with it in the hands of a capable user, I'm a huge fan.

I've wondered for a while now about the beta ability to program modules. It seems pretty clear that no one here uses it for "normal" module updates, but is that because it's not possible or just because it's really not a good idea? In other words, can it theoretically be used to get our trucks all updated without going to FDRS? And if the answer to that question is "yes", can it also do that using the regular Forscan adapters like the vLinker?

I'm not about to try updating my modules with it anytime soon, just wondering why no one around here ever seems to say much about that possibility.

Sponsored