ECU module programming guide using FDRS

[christophers]

IDS had an As built editor (shown in the screen shot below). Is this function easily accessible within FRDS or does the software have to be fooled into trying to PMI an ECU while its offline or tricked somehow to get to this stage? Also, does the checksum have to be manually calculated when doing this?

Russian sanctions are limiting the usual options for many people, so I'm interested in learning the proper way to edit As Built data with FRDS.

I dont understand what context you're asking as part of, or how the sanctions relate, but ForScan can do this. I know that an extended license for forscan is required to do some work, but I don't remember what the payment method is, which may be a problem. ForScan would be easier than IDS, IMHO.

Sponsored

 

[My42waffles]

IDS had an As built editor (shown in the screen shot below). Is this function easily accessible within FRDS or does the software have to be fooled into trying to PMI an ECU while its offline or tricked somehow to get to this stage? Also, does the checksum have to be manually calculated when doing this?

Russian sanctions are limiting the usual options for many people, so I'm interested in learning the proper way to edit As Built data with FRDS.

While ids did have that capability, my understanding was that you had to fill the whole thing in bit by bit every time. You weren’t able to just change one but like with forscan.

 

[Airborne_Ape]

I dont understand what context you're asking or how the sanctions relate, but ForScan can do this.

ForScan is developed Russia and their payment provider platform was based in Germany. ForScan can only do this up to certain ECU's produced. Development is paused and there's moderate risk they might pull the plug on development altogether whereas it's no longer a viable business and they can't pay their staff.

At some point 2022 and newer F150s won't be able to write as built data to ECU's using ForScan even if they have a valid extended licence key.

Any new Ford owners which need a module calibration added to a special test build of the software to write as built changes is SOL. This is something some of us have already encountered with our 2021's.

While ids did have that capability, my understanding was that you had to fill the whole thing in bit by bit every time. You weren’t able to just change one but like with forscan.

That's what I thought, but I would like to know if it's an option.

If optioning an ECU bit by bit in FRDS is a tedious task, I'd be happy to know that it's at least a valid option. I would like to learn about the process in FRDS since ForScan might be dead.

It could finally be an excuse to bill people for my time optioning their F150's.

 

[christophers]

So, while payment is an issue, it's possible to offer the software for free until the issues are resolved. I know this is not ideal, but if the software is completely unavailable, another product can/will be developed and if the sanctions are ever resolved, ForScan will turn out to be no longer relevant.

 

[Bob_Mac]

That's what I thought, but at least it is an option. Due to sanctions against Russia the ForScan developers can't accept any payments. Users are unable to buy extended licences for programming and the development is paused. Any new Ford owners out there that need a module calibration added to a special test build of the software to write as built changes is SOL. I suspect this applies to every new Lightning owner at the very least.

If optioning an ECU bit by bit in FRDS is a tedious task, at least it is a valid option. I would like to learn about it since ForScan might be dead from this point.

Tedious yes, but worth it? You can already d/l your AsBuilt from Ford, you have the spreadsheet from @Livnitup and d/l the As-Built Compare tool from Jesse Yeager to create the checksums...

 

[Bob_Mac]

So, while payment is an issue, it's possible to offer the software for free until the issues are resolved. I know this is not ideal, but if the software is completely unavailable, another product can/will be developed and if the sanctions are ever resolved, ForScan will turn out to be no longer relevant.

They already have a free version...

 

[christophers]

They already have a free version...

It's free but can't do everything that the extended license enabled it to do.

 

[Snakebitten]

So, while payment is an issue, it's possible to offer the software for free until the issues are resolved. I know this is not ideal, but if the software is completely unavailable, another product can/will be developed and if the sanctions are ever resolved, ForScan will turn out to be no longer relevant.

The folks behind Forscan are very clever and dedicated. I doubt the unforseen current obstacles created by the few idio..........well, let's just say that they'll find a way around this.

 

[christophers]

They already have a free version...

https://forscan.org/faq.html#qlic1

"FORScan for Windows is distributed under Standard License that has no configuration and programming functions, as well as some service functions. These functions become available after installing Extended License."

 

[christophers]

The folks behind Forscan are very clever and dedicated. I doubt the unforseen current obstacles created by the few idio..........well, let's just say that they'll find a way around this.

100% agree. i know a few ways to get around it, but working to avoid sanctions knowing that money will end up in the hands of those sanctioned is a US federal crime :/

that being said, a cursory reading of OFAC rulings and sanctions shows that it's like swiss cheese and rather easy to navigate without violating any sanction rules. i hope that the forscan developers figure this out and continue operation.

 

[rpeterslll]

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.

YEs, give it time. I had mine running in the driveway for hours, and then I pulled out of the driveway and it started updating. No one knows what triggers it, but since it asks you to set the engine to run, I would keep the truck running and idle. Maybe drive it every couple hours and see if it start. After the first APIM update, the future USB installations start within a few minutes. So something is wrong with the as built APIM version. Also be sure to not unplug the USB at any time until it tells you to do so. Even thought it looks like nothing is happening, its still working. It will prompt to remove it, just be patient.

 

[christophers]

YEs, give it time. I had mine running in the driveway for hours, and then I pulled out of the driveway and it started updating. No one knows what triggers it, but since it asks you to set the engine to run, I would keep the truck running and idle. Maybe drive it every couple hours and see if it start. After the first APIM update, the future USB installations start within a few minutes. So something is wrong with the as built APIM version. Also be sure to not unplug the USB at any time until it tells you to do so. Even thought it looks like nothing is happening, its still working. It will prompt to remove it, just be patient.

mine took 30 days exactly then started. USB was in the truck the entire time. it will work.. eventually haha

 

[Platinum Peasant]

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?

@Livnitup has a google document in the forscan thread that details what each module does, what each line controls. There are tabs at the bottom, navigate to DSM. I was reading through DSM and got to that line in it and the thought just hit me to try changing the as built info to do a software "on/off". If you need any help with it, PM me. Would GLADLY help anyone avoid my hours of frustration.

 

[Platinum Peasant]

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.

My best guess is that the DSM software update has some bugs, one of which is making the truck "forget" it has certain features. When I unplugged my DSM, it said running board fault. So i knew it was still detecting something, and thats when the asbuilt data change idea hit me shortly after.

 

[jtake]

So my running boards have not been working since updating the DSM. I followed the suggestion from Platinum Peasant and looked at the running board entry in the DSM using Forscan, and saw that it was disabled -- 00. I redid the entry to 01, saved it, and voila, my running boards started working again!

Great sleuthing Platinum Peasant!

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!

Sponsored