ECU module programming guide using FDRS

[Ajzride]

A new concern that just struck me... One of the primary reasons for going through the FDRS updates was to get the "latest" IPMA update. Having this is required for two FORScan changes I've been wanting to make. However, since I have a DTC associated with the IPMA (caused by switching from regular Sideview mirrors to Tow Mirrors and not realigning the 360 cameras), I wonder if those FORScan changes will even take ?...

Perhaps I should consider realigning the cameras using FDRS since I now have the license? I just don't want to risk mucking up the images (as has happened with some people) because the images are currently fine.

DTCs wont affect ForScan. Onward Ho!!

Sponsored

 

[FirstFord]

DTCs wont affect ForScan. Onward Ho!!

Thank you - good to know! I will Ho onward now, and see how the new FORScan mods work out.

 

[Demps]

As I gather resources and some knowledge for using FDRS to update my truck for the first time I have some questions, probably not the last.

While doing USB FDRS updates to my 2021 PowerBoost is it necessary to have the engine on? Can I do the updates using a 12V power supply with ignition on engine off?

Any advantage to using an USB C vs. an USB A flash drive?

Can I safely make FORScan mods using a cable other than a Mongoose? I’m thinking of an OBDLink EX.

While an USB update is running is it necessary for the computer to be tethered to the truck?

When the update requires my attention will it time-out if I’m not prompt enough?

Thanks for bearing with me.

 

[rugedraw]

As I gather resources and some knowledge for using FDRS to update my truck for the first time I have some questions, probably not the last.

While doing USB FDRS updates to my 2021 PowerBoost is it necessary to have the engine on? Can I do the updates using a 12V power supply with ignition on engine off?

Any advantage to using an USB C vs. an USB A flash drive?

Can I safely make FORScan mods using a cable other than a Mongoose? I’m thinking of an OBDLink EX.

While an USB update is running is it necessary for the computer to be tethered to the truck?

When the update requires my attention will it time-out if I’m not prompt enough?

Thanks for bearing with me.

The USB ones can be done with ignition on and the power supply instead of engine running if you prefer,

No advantage of which USB slot you use afaik.

Yes, the Mongoose will work for FORScan, too, but always good to have your own FORScan cable if you don't have your own Mongoose and will be borrowing one of mine.

It is not necessary to be plugged in to the truck while the USB update is running, but it will make things easier if you do leave it plugged in so it verifies the update after it installs on its own.

I don't think it will time out......not 100% sure.

 

[onodelta]

Anyone have any idea why it would still say this? I have put the as built data in the module using forscan and it went through and it reads it correctly when I check it but the code still remains, any idea why? U2100:00-0A Configuration not complete

 

[rugedraw]

Anyone have any idea why it would still say this? I have put the as built data in the module using forscan and it went through and it reads it correctly when I check it but the code still remains, any idea why? U2100:00-0A Configuration not complete

What module? What are you trying to do?

 

[onodelta]

What module? What are you trying to do?

SECM, I took steering wheel from King ranch and want to install the SECM from it on Limited. Any errors I had with the old one have gone away and now this one works with functions my original steering didn't work, like the heated steering wheel. The wiring is the same from a king ranch to a limited, same modules except the king ranch SECM has ML34-3G600-FLJ3ET7 and original is ML34-3G600-FSJ31D7. I was gonna swap the module over into my original one but that "not configuration" code won't go away, I was so close. Wiring diagrams are the same, steering wheel buttons are all the same and have same features on both of these steering wheels. Original one getting U3000 code and needs replacing. The errors went away in the cluster also. And as I said, it did accept the As built data for the truck with data from motorcraftservice. May just not like the module

 

[rugedraw]

SECM, I took steering wheel from King ranch and want to install the SECM from it on Limited. Any errors I had with the old one have gone away and now this one works with functions my original steering didn't work, like the heated steering wheel. The wiring is the same from a king ranch to a limited, same modules except the king ranch SECM has ML34-3G600-FLJ3ET7 and original is ML34-3G600-FSJ31D7. I was gonna swap the module over into my original one but that "not configuration" code won't go away, I was so close. Wiring diagrams are the same, steering wheel buttons are all the same and have same features on both of these steering wheels. Original one getting U3000 code and needs replacing. The errors went away in the cluster also. And as I said, it did accept the As built data for the truck with data from motorcraftservice. May just not like the module

Well, it may the different part numbers causing the issue, but I can't say for certain. When you installed the new steering wheel, did you PMI the SECM, or did you just put the steering wheel in without programming it?

 

[FirstFord]

I drove my truck for the first time since making all of the FDRS updates, and very quickly noticed that apparently during the update process, some "nanny state" features that I had turned off were turned back on. This is understandable, and shouldn't be a big deal - just go back into the menu and turn them back off. Nope. Doesn't work that way. Now you can't turn Lane Assist OFF - you can only adjust to what intensity it "assists" you. Is there a way - perhaps through FORScan - to turn it back off? Secondly, the updates turned Collision Avoidance back on. You can turn it back off in the menu, but if you do, you get an illuminated warning icon in the instrument cluster that is illuminated the whole time the ignition is ON. Again, is there any way to turn off the warning icon?

 

[rugedraw]

I drove my truck for the first time since making all of the FDRS updates, and very quickly noticed that apparently during the update process, some "nanny state" features that I had turned off were turned back on. This is understandable, and shouldn't be a big deal - just go back into the menu and turn them back off. Nope. Doesn't work that way. Now you can't turn Lane Assist OFF - you can only adjust to what intensity it "assists" you. Is there a way - perhaps through FORScan - to turn it back off? Secondly, the updates turned Collision Avoidance back on. You can turn it back off in the menu, but if you do, you get an illuminated warning icon in the instrument cluster that is illuminated the whole time the ignition is ON. Again, is there any way to turn off the warning icon?

Yes, the newer IPMA software does have some different behaviors. Not sure what the difference is in terms of the eye nanny, but to turn off collision warning on the IPC seems to be here:

 

[FirstFord]

Yes, the newer IPMA software does have some different behaviors. Not sure what the difference is in terms of the eye nanny, but to turn off collision warning on the IPC seems to be here:

Terrific! Thank you yet again sir! I'll give that a try and see how things go.

 

[onodelta]

Well, it may the different part numbers causing the issue, but I can't say for certain. When you installed the new steering wheel, did you PMI the SECM, or did you just put the steering wheel in without programming it?

PMI basically does the same thing as putting the factory as built data into the module. And I did that manually with forscan. PMI copies data from (factory data from original module) original module into new one. So I just put the factory data into the new module and programming goes through. Steering angle sensor module also came with it and had same u2100 code and that went away when I did the same thing through forscan. But the part number on that vs old one matches 100%. Took the truck for a test drive with the King ranch wheel installed and all features work, lane assist and all of that, owner doesn't have blue cruise subscription active so I can't test that. But everything else does work.
Edit: here is a pic of everything working with the king ranch steering wheel installed in the limited truck.

 

[rugedraw]

I am not sure, but I am pretty sure U2100 is a configuration code if I remember correctly. Below is the ab data for the SECM on my truck. My truck has heated wheel and everything else you mentioned. Maybe you can compare it to what you are showing to make sure it matches and hopefully this helps.

 

[onodelta]

I am not sure, but I am pretty sure U2100 is a configuration code if I remember correctly. Below is the ab data for the SECM on my truck. My truck has heated wheel and everything else you mentioned. Maybe you can compare it to what you are showing to make sure it matches and hopefully this helps.

yes that's exactly the same coding I added with forscan into it and it accepted it. Everything functions as my original once did before someone hit the truck. Just this time the code doesn't go away since it is a king ranch wheel in a limited trim after all, not sure if it'll stay working or not with that code active thinking it's not programmed even thought it is and reads correct mileage from cluster and everything works and errors from dash are gone right away.

 

[rugedraw]

yes that's exactly the same coding I added with forscan into it and it accepted it. Everything functions as my original once did before someone hit the truck. Just this time the code doesn't go away since it is a king ranch wheel in a limited trim after all, not sure if it'll stay working or not with that code active thinking it's not programmed even thought it is and reads correct mileage from cluster and everything works and errors from dash are gone right away.

I'm not sure. I have the files for the SECM if you want to try to flash it with forscan, but if it ain't broke, don't try to fix it and just ignore the code.

Sponsored