ECU module programming guide using FDRS

[RickBullotta]

The results have been the 502 A and up active DSS headlamps are ok. THe XLT to 501 A headlights are not

Ths interaction the BCM has with the headlight module is via LinBus.

The active DSS do not have the linbus that is at teh BCM the LinBus is ran through the HCM.

The crazy part is the passenger side works on all examples that have the issue along with the Driver Fog and Driver Fog DRL.

If someone is in dallas.. And wants to allow me to do the BCM update on their truck I have all the parts to make the headlight work. Youll leave working. I just want to know what the deal is.

Do you still have a contact at Ford engineering who can help us sort through this?

Sponsored

 

[Jesse-Infotainment]

Do you still have a contact at Ford engineering who can help us sort through this?

No. I only spoke to him a couple of times. He may be an engineer but he was more in teh Mach E world.

 

[Jesse-Infotainment]

@JDPEagle got the exact saem update package I did for my truck. There has to be something we are missing.. I jsut cant figure it out.

I asked Sparky but if you could just to test do a write all in the BCM in forscan. Load factory AS build and then write all see what happens. Possibly the BCM didnt get reconfigured all the way or POSSIBLY the as build was changed but not actually written. I have seen that before in ACMs. Where it can be changed but not stick.

Its a long shot but who knows.

 

[JDPEagle]

@Jesse-Infotainment: I did try a write-all with both a backup file and a factory AS BUILT. Both returned an error on the execution. I’m glad to try both again shortly.

Also, I was able to get my hands on a new HCM this morning. What’s the “over/under” on the “updated” BCM frying the new module upon boot-up?

 

[Jesse-Infotainment]

@Jesse-Infotainment: I did try a write-all with both a backup file and a factory AS BUILT. Both returned an error on the execution. I’m glad to try both again shortly.

Also, I was able to get my hands on a new HCM this morning. What’s the “over/under” on the “updated” BCM frying the new module upon boot-up?

Ok I shouuld have been more specific. What to do is in the BCM there is a load factory As build button. Select it. And then write all.

Im really racking my brain on this.

 

[JDPEagle]

Ok I shouuld have been more specific.

Sorry, @Jesse-Infotainment. I should have been more specific, too. I did attempt to load the Factory AS-BUILT data last evening to no avail.

I did try it again a few minutes ago, and here are the results (which were the same as yesterday evening's results):

1. I was first presented with a Warning message of "Number of blocks in file and module doesn't match. Continue anyway?"
2. After continuing, I went to "Write All." It would almost complete and present the error message, "Writing blocks failed - incompatible configuration."
3. Further examination of the log shows that "Writing block 91 failed - incompatible configuration." All other blocks wrote successfully (up to and including block 92).

Block 91 is having an issue.

 

[Jesse-Infotainment]

Sorry, @Jesse-Infotainment. I should have been more specific, too. I did attempt to load the Factory AS-BUILT data last evening to no avail.

I did try it again a few minutes ago, and here are the results (which were the same as yesterday evening's results):

1. I was first presented with a Warning message of "Number of blocks in file and module doesn't match. Continue anyway?"
2. After continuing, I went to "Write All." It would almost complete and present the error message, "Writing blocks failed - incompatible configuration."
3. Further examination of the log shows that "Writing block 91 failed - incompatible configuration." All other blocks wrote successfully (up to and including block 92).

Block 91 is having an issue.

Yeah.. It changed. But the main blocks wrote andIm guessing no change in the situation?

 

[JDPEagle]

Yeah.. It changed. But the main blocks wrote andIm guessing no change in the situation?

No change. Should I proceed with the module replacement in the name of science? Any possibility that the “upgraded” BCM would destroy the new headlight module?

 

[Jesse-Infotainment]

No change. Should I proceed with the module replacement in the name of science? Any possibility that the “upgraded” BCM would destroy the new headlight module?

You can. I can tgive a promise. Im starting to hope the actual headlamp assembly isnt blown up.

I wish someone had a power probe or real good way to diag the headlamp.

Your BCM update package was IDENTICAL to mine. So I dont know what the issue is. I really dont

 

[antho]

You should be able to pull the update log in FDRS or PTS. May be able to dig through that. I think there are 2 versions of the log. If someone could load that log we could look through it.

 

[RickBullotta]

Typically a BCM update wouldn't be released without reason. Are there any TSBs or service bulletins related to this?

 

[Jesse-Infotainment]

Typically a BCM update wouldn't be released without reason. Are there any TSBs or service bulletins related to this?

unintended tailgate release. Same as the last one just been updated to 2023 strategy

 

[RickBullotta]

unintended tailgate release. Same as the last one just been updated to 2023 strategy

Then there's ZERO chance I'm installing it! I have an Undercover SE that'll hold my tailgate in place! ;-)

 

[DudeitsDenny]

For those who did the BCM update and everything works, what build date/headlight package do you have?

I have a job 1 Powerboost Lariat 501A (LED Reflector) - ready to do updates via FDRS but seeking clarity on BCM. Is it only LED projectors which get borken by latest BCM? Or both LED projectors and reflectors?

I have a Job 1 King Ranch Powerboost. Build start date was April 2021 and was parked till October. All of my lights are working. The only issue I’ve had is the IPC update that I need to use a USB. It won’t start the update so I’ll drive around with it for a while. Maybe someone can answer this question for me. On the IPC update it says it needs to be a 32GB usb but the software was only around 177,000kb not even 1GB why the over kill or did it not download all of the software?

 

[JDPEagle]

***SHORT UPDATE***
I installed a new HLC module, and the DRL and low beams are again operational. Will tackle the reason that high beams are not actuating on the subject (drivers side) headlight later this afternoon (perhaps need to reload the post-update FORSCAN values).

Sponsored