Uploading AS-BUILT file error

[Shiko]

got an issue with my truck lights, they stay on for about 10 minutes on farwell (DLR, headlights and parking lights), tried to fix with the sync setting, battery reboot, signal handle pulled back after turn off or even turning the light knob to off an back to auto or off altogether, none worked.

Also the lights remain on throughout while charging the car and car switched off.

i downloaded the as built file based on my VIN from motorcraft but when trying to load it getting warning message saying "number of blocks in file and module doesnt match, continue anyway?" i'm afraid to proceed and cause a programming issue.

anyone is familiar with this process to help ?

2024 F150 LIGHTNING FLASH TRIM

Sponsored

 

[Shiko]

Anyone know if i can get the AS-BUILT file for the Body Control Module ONLY (BCM)
rather than the all AS built Files from motorcraft ?

i would like to reset only the BCM module.

 

[GDN]

Is your error above while you are trying to write your changes to the module? Just say no and cancel out.

Then load it again so you can edit the file. Download your full As Built from Ford and look through it for the same lines of the module you want 726-XX etc. Then update them.

I may not be following the problem, but Forscan is pretty simple. You may have fat fingered something, so don't write bad changes. Just get out of those changes without saving, then start over.

 

[rugedraw]

When you load FORScan and it asks you if you want to load the existing profile, select no so it does a fresh scan. Then check to see if you get the same warning about the number of blocks not matching.

 

[ZSC100]

Go ahead, there are some block mismatches on some modules no matter what. This happens because there are some customization things in the config memory space that aren't present in the As-Built file. When you see "number of blocks in file and module doesn't match, continue anyway?" It just means some info won't be used, no biggie.

Things like user profile settings set as preferences or settings from the infotainment saved into the module won't be updated. So, those will never be in the factory AB. It's not a problem. Just be aware that when you revert to an AB for that module that you saved from FORScan it WILL overwrite/revert those settings.

And,, lastly, Ford's BCM software in regards to lighting (and other things) sucks. My truck randomly will leave lights on too. It also still remains that you can't turn off the interior lights without starting the truck which is the dumbest bug to have missed, EVER. There's no excuse for that to have ever operated that way, it should've been caught in testing.

 

[Shiko]

Is your error above while you are trying to write your changes to the module? Just say no and cancel out.

Then load it again so you can edit the file. Download your full As Built from Ford and look through it for the same lines of the module you want 726-XX etc. Then update them.

I may not be following the problem, but Forscan is pretty simple. You may have fat fingered something, so don't write bad changes. Just get out of those changes without saving, then start over.

Thanks, great idea !
will definitely try this.
might go little further and export pdf file of the forscan module and the one from motorcraft and run comparison to see where are the differences.

 

[Shiko]

When you load FORScan and it asks you if you want to load the existing profile, select no so it does a fresh scan. Then check to see if you get the same warning about the number of blocks not matching.

good idea, i'll try that ! thank you.

 

[Shiko]

Go ahead, there are some block mismatches on some modules no matter what. This happens because there are some customization things in the config memory space that aren't present in the As-Built file. When you see "number of blocks in file and module doesn't match, continue anyway?" It just means some info won't be used, no biggie.

Things like user profile settings set as preferences or settings from the infotainment saved into the module won't be updated. So, those will never be in the factory AB. It's not a problem. Just be aware that when you revert to an AB for that module that you saved from FORScan it WILL overwrite/revert those settings.

And,, lastly, Ford's BCM software in regards to lighting (and other things) sucks. My truck randomly will leave lights on too. It also still remains that you can't turn off the interior lights without starting the truck which is the dumbest bug to have missed, EVER. There's no excuse for that to have ever operated that way, it should've been caught in testing.

i'm worried it will mess up stuff on the programming and then i'll be in bigger trouble....

also- if it reset to factory setting- does it include all the recent updates since manufacturer to date or will i need to start updating ?
scary move doing a rewrite with errors.. i saw some youtube videos with people doing it and no error popped so make it even more scary 🫣

 

[ZSC100]

i'm worried it will mess up stuff on the programming and then i'll be in bigger trouble....

also- if it reset to factory setting- does it include all the recent updates since manufacturer to date or will i need to start updating ?
scary move doing a rewrite with errors.. i saw some youtube videos with people doing it and no error popped so make it even more scary 🫣

No, you are not modifying ANY of the software here, this is just configuration. In most all cases (I've seen) you can actually mess up the configuration and the module will still perform its core function if it relates to driving safely. So, here are the important things that no one really understands:

Always grab your factory AB file from Ford's Cloud, save it, keep it. (do this before you modify anything). Did you know that as you modify the truck's config that Ford's AB will update and reflect those changes. This is bizarre, but true. Basically that AB is generated as the truck is built, but from then on, it is modified by your truck.

So, next, before you change anything, always save your module by module configs. These will always work in the future to revert a module to a "point in time" and these will never have mismatch errors because they were saved from the very module you are working on. So keep in mind they may be saving user profile things, like seat positions, mirror positions, perferences, etc. So, armed with those two things, no fear in playing around.

Once you understand this save often methodology, you can play around with things with no worries. Also, in case you still don't know, the AB file contains ALL module configs (FORScan just uses the info for the particular module you are working with at the time). This is different than saving a module config in FORScan, that will just be for that module only.

As a way to help you gain confidence, go save your BCM config, the re-load it and see that there are no mismatch errors. Once you get that confidence that you can revert it, then dump your AB in there and ignore the mismatch error.

Again, you are not modifying ANY code (firmware) of the module with config changes.

 

[Shiko]

No, you are not modifying ANY of the software here, this is just configuration. In most all cases (I've seen) you can actually mess up the configuration and the module will still perform its core function if it relates to driving safely. So, here are the important things that no one really understands:

Always grab your factory AB file from Ford's Cloud, save it, keep it. (do this before you modify anything). Did you know that as you modify the truck's config that Ford's AB will update and reflect those changes. This is bizarre, but true. Basically that AB is generated as the truck is built, but from then on, it is modified by your truck.

So, next, before you change anything, always save your module by module configs. These will always work in the future to revert a module to a "point in time" and these will never have mismatch errors because they were saved from the very module you are working on. So keep in mind they may be saving user profile things, like seat positions, mirror positions, perferences, etc. So, armed with those two things, no fear in playing around.

Once you understand this save often methodology, you can play around with things with no worries. Also, in case you still don't know, the AB file contains ALL module configs (FORScan just uses the info for the particular module you are working with at the time). This is different than saving a module config in FORScan, that will just be for that module only.

As a way to help you gain confidence, go save your BCM config, the re-load it and see that there are no mismatch errors. Once you get that confidence that you can revert it, then dump your AB in there and ignore the mismatch error.

Again, you are not modifying ANY code (firmware) of the module with config changes.

sounds convincing, gonna try it this evening,
but i warn you, if this doesn't work, i'm going to find you...(Liam Neilsen voice). lol kidding.

thanks, appreciate the time you took to post your feedback, very kind of you!

 

[Shiko]

sounds convincing, gonna try it this evening,
but i warn you, if this doesn't work, i'm going to find you...(Liam Neilsen voice). lol kidding.

thanks, appreciate the time you took to post your feedback, very kind of you!

Successfuly uploaded the as built file from motorcraft, no apparent issues, but the lights staying on for 10 minutes is still happening…

 

[ZSC100]

Successfuly uploaded the as built file from motorcraft, no apparent issues, but the lights staying on for 10 minutes is still happening…

Sounds like a physical issue, like a light switch, door switch, or something

 

[rugedraw]

Successfuly uploaded the as built file from motorcraft, no apparent issues, but the lights staying on for 10 minutes is still happening…

When you plugged in to FORScan, was it showing any codes?

If your Fordpass is connected, message me the VIN and I can check.

 

[Shiko]

When you plugged in to FORScan, was it showing any codes?

If your Fordpass is connected, message me the VIN and I can check.

Hello Javier,
sent you a direct message.
Thank you.

 

[rugedraw]

Hello Javier,
sent you a direct message.
Thank you.

The truck is only reporting a few stored codes, but no active faults and the old stored codes don't seem relevant to your issue. No idea what could be causing it.....sorry.

Sponsored