Module Build Data WRONG!

[Jpalmer1]

Like many of you, I followed my 2025 Maverick Hybrid AWD build closely until I received it. During that time, I downloaded the "Module Build Data (As Built)" as soon as it was available online. Now, having received my Maverick and connecting FORscan, I find that the As Build Module Build Data I downloaded for my VIN during the build is NOT correct! Just one example: It showed: 720-13-01 F100 0001 80AD . . however, in reality, FORscan shows: 720-13-01 E100 0001 809D

The above happens to be for the Seatbelt minder & chime.

Anyone else noticed this or have an explanation?

Ford, you watching? . . would love to understand why this is.

Thanks.

Sponsored

 

[oysterville]

Why does this matter? Does it make your truck play the Benny Hill theme song on loop from the external speaker or something?

 

[The Real Maverick]

Ya.

My thought "different" ≠ "wrong".

Most trucks, probably yours too have three different build dates too. Which if not "normal" is typical.

 

[Blue_Max]

I don't think you want Ford watching you use FORscan.

 

[colinl]

Can't say that I have ever felt the slightest bit of curiosity to compare the motorcraft service as-built for my truck to what is actually set on the truck... but I'm guessing this is normal.

Probably, some of it relates to user configurable parameters like the back seat occupant reminder, but some of it might be due to a reflash update.

 

[JetFixxxer]

Does it make your truck play the Benny Hill theme song on loop from the external speaker or something?

Sign me up!

 

[OleFordGuy]

Oh my, the sky is falling

 

[pestojest]

I'm not understanding this question at all. These aren't things you can customize in your build, anyway. So why is it an issue in the first place? Not trying to be dismissive, I just really don't understand what you'd expect instead.

 

[Fcnrwy]

Post-N-Go


Jerry

 

[deanobc]

Like many of you, I followed my 2025 Maverick Hybrid AWD build closely until I received it. During that time, I downloaded the "Module Build Data (As Built)" as soon as it was available online. Now, having received my Maverick and connecting FORscan, I find that the As Build Module Build Data I downloaded for my VIN during the build is NOT correct! Just one example: It showed: 720-13-01 F100 0001 80AD . . however, in reality, FORscan shows: 720-13-01 E100 0001 809D

The above happens to be for the Seatbelt minder & chime.

Anyone else noticed this or have an explanation?

Ford, you watching? . . would love to understand why this is.

Thanks.

A week after I took delivery of my 25, I thought there might be an issue, which turned out to be nothing. However, they did discover a bunch of codes, mainly sensing electrical issues all concentrated on the right side of my Mav. We found out that this was also nothing to worry about as it was part of the test run they do post assembly line at the plant and someone had forgotten to clear the codes. I have had absolutely zero issues with my Lariat Hybrid after 3 months and approaching 4000 miles.

 

[Jpalmer1]

A week after I took delivery of my 25, I thought there might be an issue, which turned out to be nothing. However, they did discover a bunch of codes, mainly sensing electrical issues all concentrated on the right side of my Mav. We found out that this was also nothing to worry about as it was part of the test run they do post assembly line at the plant and someone had forgotten to clear the codes. I have had absolutely zero issues with my Lariat Hybrid after 3 months and approaching 4000 miles.

Dean, I have noticed a bunch of codes in there as well, and was wondering. That explanation makes sense. Thank You.

Sponsored