ECU module programming guide using FDRS

[jmm3807]

What sync version/revision are you on?

What does the software update show when you hover over?

Sync 22034 revision 364
Same version after I updated it. Was a very short update with no USB required. Prior to starting the update I had an APIM error and it listed a TSB next to it. I think this update was to fix that TSB. No idea really.

Sponsored

 

[CUL8ER]

Awesome board tip! When you say “reset module” is there a specific procedure you follow to reset the module?

In Forscan the tab above where you change the modules allows you to do a module reset after you have made the changes. This essentially restarts the module.

 

[iceman77]

I did get a 30 day from them after spending so much on the helm licenses. They work, but you have to give them remote control of your computer for about 3 minutes for them to install it. If you are like me and your laptop only does FDRS and nothing else, probably not a concern. If you are running FDRS on your primary laptop, probably be pretty wary of doing it that way.

Whatever they do, looks illegal to me. You guys want to go this route, feel free to do it privately, but I would kindly ask to keep such stuff out of this public thread

 

[JaHoova]

Yes before the USB. Only connected to CAN Via nano.

I'd try a mongoose if you can get a hold of it. That's all I can thing

 

[Airborne_Ape]

Anyone see anything out of the ordinary with this? The FDRS logs from the run are super chewy... and this is Java

This part looks suspicious, as though there is some sort of Bosch VCM 3 or VCMM hardware validation check for your BECM software update. Your debug logs shows it downloads the file fine in 6.1 seconds, but then gets to this stage and starts closing connections and begins to debug itself (unless if I'm reading it wrong which is entirely possible since I don't write code). Maybe some others can shed some light on this.

These few lines make me worry a little about this entire thread and the direction Ford might take with all future updates. Theoretically, big blue could lock out all non-Bosch J2534-2 passthrough devices right? Hopefully I'm just being too pessimistic.

2022-04-02T07:24:13,288 INFO hmi.otxImpl.LaunchBundleFunctionImpl - Launching bundle "Battery Energy Control Module (BECM) Software Update"
2022-04-02T07:24:13,449 INFO otx.core.BaseApplication - Adding runtime logs appender to COMMS channel logger
2022-04-02T07:24:15,440 ERROR j2534.win32.InstalledDeviceImpl - Not supported on non-Bosch device.
2022-04-02T07:24:15,456 WARN dflt.sources.VciConnectionSource - Failed to clear last used device: Error 1 clear last used device = Not supported on non-Bosch device. [J2534_ERROR:ERR_NOT_SUPPORTED]

This may be a good thing for the BECM, it might prevent some of you from killing your truck. I certainly don't have the courage to update my BECM at home and would encourage others to leave that module alone since it's a critical component.

 

[ibgregr]

I completed all of my updates today without any issues. I see BC is there and even went for a quick test drive and it kicked in. But...on the Ford Connected Services site it still shows Activation Pending and the date on my Sync screen is the October date. Is there anything I can do to kick it into actually officially activating?

 

[Fordphanatic]

I completed all of my updates today without any issues. I see BC is there and even went for a quick test drive and it kicked in. But...on the Ford Connected Services site it still shows Activation Pending and the date on my Sync screen is the October date. Is there anything I can do to kick it into actually officially activating?

I called Ford customer support for the same problem. They told me to disconnect and reconnect to fordpass. That cycled the date to current date and no more activation pending showing in fordpass

 

[ibgregr]

I called Ford customer support for the same problem. They told me to disconnect and reconnect to fordpass. That cycled the date to current date and no more activation pending showing in fordpass

Yup...I just found another forum post in a different section that said to do the FordPass reset. Did that and BOOM...activated!

Thanks!

 

[Fordphanatic]

Glad to see this thread is back to life!

 

[JEB]

This part looks suspicious, as though there is some sort of Bosch VCM 3 or VCMM hardware validation check for your BECM software update. Your debug logs shows it downloads the file fine in 6.1 seconds, but then gets to this stage and starts closing connections and begins to debug itself (unless if I'm reading it wrong which is entirely possible since I don't write code). Maybe some others can shed some light on this.

These few lines make me worry a little about this entire thread and the direction Ford might take with all future updates. Theoretically, big blue could lock out all non-Bosch J2534-2 passthrough devices right? Hopefully I'm just being too pessimistic.

2022-04-02T07:24:13,288 INFO hmi.otxImpl.LaunchBundleFunctionImpl - Launching bundle "Battery Energy Control Module (BECM) Software Update"
2022-04-02T07:24:13,449 INFO otx.core.BaseApplication - Adding runtime logs appender to COMMS channel logger
2022-04-02T07:24:15,440 ERROR j2534.win32.InstalledDeviceImpl - Not supported on non-Bosch device.
2022-04-02T07:24:15,456 WARN dflt.sources.VciConnectionSource - Failed to clear last used device: Error 1 clear last used device = Not supported on non-Bosch device. [J2534_ERROR:ERR_NOT_SUPPORTED]

This may be a good thing for the BECM, it might prevent some of you from killing your truck. I certainly don't have the courage to update my BECM at home and would encourage others to leave that module alone since it's a critical component.

What programmer was being used here? I kamikaze’d my way through a few updates, including the BECM, last month with the Mongoose and didn’t have any issues. Was the Nano choking on the BECM?

At any rate, this is an interesting observation about Ford potentially locking down updates for non-Bosch programmers. But I doubt it would happen because they could get into a lot of hot water with manufacturers of J2534 products that Ford has certified to work with FJDS and FDRS, including some pretty big hitters like Opus (f/k/a Drew Technologies) and Snap-On, just to name a couple. https://www.motorcraftservice.com/diagnostic/FJDSSupport?categoryId=247 The outcry from independent repair and body shops would be tremendous.

 

[rpeterslll]

After all the APIM updates and IPC updates, my menu in my instrument panel Menu appears by default after I restart the truck and it doesn't retain its last selection. Is everyone's doing this?

 

[JEB]

Speaking of Opus, it appears that the Mongoose for Ford is now back in stock on Amazon.

 

[JEB]

After all the APIM updates and IPC updates, my menu in my instrument panel Menu appears by default after I restart the truck and it doesn't retain its last selection. Is everyone's doing this?

Mine is not.

 

[iceman77]

Got it figured out. There was a DSM SW update today so I did that and it fixed everything. So with the DSM update it put the boards back to factory original settings but instead of the annoying locking the truck from the door outside button the steps going up and not even 2 seconds later they come back down, it appears Ford fixed the bars and they stay up when pressing the outside door button, door outside keypad lock, or fob lock button is pushed and you around the vehicle walking away. This is nice that's finally fixed as that was annoying.

Now before I did the DSM update I was doing some testing in Forscan and found a great setting with the step bars only coming down when the door was opened but as you approach they stay up and your approach lighting still works (as long as you don't have Lincoln AutoFold Mirrors set instead of the original AutoFold Mirrors) as well as the step bar switches will work. This is great when you are walking around your vehicle but tired of the steps going up and down constantly. My settings on the sync screen are Power Running Boards Auto, Timer 5 min, Approach Setting and Lighting set to on. After you have this all set leave it and don't touch. Make the changes below in Forscan then do the module reset and away you go. So the settings I used were the following.

744-23-01 > 0001-0001-00XX
744-23-02 > 0101-0000-XX
or for those with older block setup for that line 744-23-02 > 0101-00XX

I think for Approach Detection Power Running Boards it is enough to set the ADPRBOC flag to 0 (or DISABLE). OEM value is 1 (or ENABLE).

744-23-01 -> 00xx-xxxx-xx--

Works just fine for my '22 F-150 Platinum PowerBoost. The lights lit up when approaching the truck but the power running boards stay in. They deploy ONLY when doors are opened!

 

[CUL8ER]

I think for Approach Detection Power Running Boards it is enough to set the ADPRBOC flag to 0 (or DISABLE). OEM value is 1 (or ENABLE).

744-23-01 -> 00xx-xxxx-xx--

Works just fine for my '22 F-150 Platinum PowerBoost. The lights lit up when approaching the truck but the power running boards stay in. They deploy ONLY when doors are opened!

Perfect. Not sure what the rest of your 22 OEM settings were for those 2 lines? Did it add an extra block to your 744-23-02 Line? Also did you check your switch on boards if you like them left on?

Sponsored