ECU module programming guide using FDRS

[Fordphanatic]

Congrats! I have not used Forscan. Do I need the OBDLink from the tutorial or will the Mongoose work?

The mongoose adapter works great with forscan too

Sponsored

 

[JEB]

The mongoose adapter works great with forscan too

So does the Nano.

 

[Fordphanatic]

So does the Nano.

Very true!

 

[RapidRedRick]

My power running boards are not moving anymore either. I did the PMI as both original and new, unplugged the battery for a few hours and tried again, even tried unplugging the running boards and completely unplugging the DSM for some time and trying it all again. Nothing seems to work. When I unplugged the DSM tho, i did get a POWER RUNNING BOARD FAULT message on the IPC. Goes away once you plug it back in. I think side loading firmware is the only solution at this point as @Jesse-Infotainment mentioned. That or go play dumb at your local dealer, something I don't really wanna do.

EDIT: I got them back alive! I went into Forscan, DSM module, went to line 744-23-02 and changed **xx-xxxx to 00 (configured them to NOT present). Saved the changes. Then went and changed it back to 01 (as built) and saved it. They came back alive instantly!

 

[RapidRedRick]

My power running boards are not moving anymore either. I did the PMI as both original and new, unplugged the battery for a few hours and tried again, even tried unplugging the running boards and completely unplugging the DSM for some time and trying it all again. Nothing seems to work. When I unplugged the DSM tho, i did get a POWER RUNNING BOARD FAULT message on the IPC. Goes away once you plug it back in. I think side loading firmware is the only solution at this point as @Jesse-Infotainment mentioned. That or go play dumb at your local dealer, something I don't really wanna do.

EDIT: I got them back alive! I went into Forscan, DSM module, went to line 744-23-02 and changed **xx-xxxx to 00 (configured them to NOT present). Saved the changes. Then went and changed it back to 01 (as built) and saved it. They came back alive instantly!

That is some awesome problem solving. I have a similar issue, I lost my heated steering/ heated & cooled seat functions. I believe the controlling lines are in the DSM. I would like to try that on/off trick too. Is there a guide that sows the functions of each of the lines in the module? How did you find where the line was to make the changes?

 

[Slappy McGee]

I haven’t dug through all the “tools” in FDRS but I find it odd there’s not a Ford-sanctioned fix for this stuff, which doesn’t seem unusual. My running boards are out of commission and I haven’t tried the seats yet so who knows how that will turn out!

That is some awesome problem solving. I have a similar issue, I lost my heated steering/ heated & cooled seat functions. I believe the controlling lines are in the DSM. I would like to try that on/off trick too. Is there a guide that sows the functions of each of the lines in the module? How did you find where the line was to make the changes?

 

[imnuts]

Congrats! I have not used Forscan. Do I need the OBDLink from the tutorial or will the Mongoose work?

You need a different cable and forscan (and a license for it i believe, though its significant cheaper). There is an excellent tutorial on how to do it by @Livnitup under the Forscan thread on this forum.

As mentioned, the Mongoose (and Nano) will both work with FORScan. Worst case you'll just have to go into settings and change the adapter FORScan is using.

 

[Snakebitten]

I haven’t dug through all the “tools” in FDRS but I find it odd there’s not a Ford-sanctioned fix for this stuff, which doesn’t seem unusual. My running boards are out of commission and I haven’t tried the seats yet so who knows how that will turn out!

I'm not sure why Ford would "sanction" what this thread represents. And certainly not the editing of ASbuilt parameters with Forscan.

Having said that, I wouldn't be surprised if Ford has some folks monitoring what is being shared here and have discussed it in the conference room in various contexts.

 

[antho]

Just wanted to shoutout @speedracercjr. He let me borrow his Mongoose and it fixed all of the corrupt Nano data i had. Its nice to be able to do a network scan with the truck connected! Sometimes jumping the gun isnt a good thing and i wish i knew about the Mongoose before i bought the paperweight Nano.

Also, The mongoose does not see my SODCMC and SODCMD in forscan just like the Nano. So i would assume its a Forscan and J2534 issue.

 

[speedracercjr]

Just wanted to shoutout @speedracercjr. He let me borrow his Mongoose and it fixed all of the corrupt Nano data i had. Its nice to be able to do a network scan with the truck connected! Sometimes jumping the gun isnt a good thing and i wish i knew about the Mongoose before i bought the paperweight Nano.

Also, The mongoose does not see my SODCMC and SODCMD in forscan just like the Nano. So i would assume its a Forscan and J2534 issue.

glad to help a fellow member out! To be fair we all thought the Nano was a budget deal, and it still kind of is as long as you know the pitfalls of the network scan and that it will only get updates so far.

 

[Slappy McGee]

I'm not sure why Ford would "sanction" what this thread represents. And certainly not the editing of ASbuilt parameters with Forscan.

Having said that, I wouldn't be surprised if Ford has some folks monitoring what is being shared here and have discussed it in the conference room in various contexts.

I guess what I was trying to say was that if the Ford "official" software update tool (FDRS) "disables" the power running boards in some capacity, they would presumably it would also provide some sort of tool to "fix" them since it seems to be a not-uncommon problem.

Perhaps I assume too much from the good people that brought you the 1.7.1 "borked" OTA update.

 

[ksimon123451]

I purchased a new to me 21 F150 Lariat 3 weeks ago with a stuck update 1.7, I just got my Mongoose and recommended battery charger, all the updates went off with out a hitch. Then came the Apim I created the USB and nothing. So my plan is to leave it plugged in the truck until it starts. I have it currently sitting in the driveway with the battery charger, key on engine off. I am getting the IPMA u2400 error and I no longer have lane centering and street sign adjusted cruise control.

I am excited to be apart of this forum and a new ford owner.

 

[Ajzride]

So my plan is to leave it plugged in the truck until it starts. I have it currently sitting in the driveway with the battery charger, key on engine off.

I believe that the engine has to be on for the USB update to kickoff. I know FDRS instructs you to engine on, and the popup tells you to drive the car as normal while updating.

 

[ksimon123451]

I believe that the engine has to be on for the USB update to kickoff. I know FDRS instructs you to engine on, and the popup tells you to drive the car as normal while updating.

Ok great thank you.

 

[Snakebitten]

I guess what I was trying to say was that if the Ford "official" software update tool (FDRS) "disables" the power running boards in some capacity, they would presumably it would also provide some sort of tool to "fix" them since it seems to be a not-uncommon problem.

Perhaps I assume too much from the good people that brought you the 1.7.1 "borked" OTA update.

Agree. Ford should have a remedy for the disabled power running boards.
And they just might, as soon as they know about it and then come up with an appropriate update routine that "toggles" the AB value similar to what was brilliantly discovered by one of our own.

I personally believe this grassroots OTA/FDRS group is fluid and FAST moving compared to what Ford's huge machine is.

Sponsored