Error in AS BUILT file?

[RadioDoc]

After looking through the Livnitup spreadsheet at the various configuration options, decided on a whim to take my truck's AS BUILT file and toss it into Notepad++ to see what was there. Was not expecting to see the data structured like XML, which was surprisingly nice as it made sorting through the data easy, and I'll have a fun project to work on over the next couple of weeks as I pick it apart to see exactly how everything was configured from the factory. What struck me as odd though is at the end of the file I came across an ERROR tag. Has anyone else seen anything like this? Is this normal, or did something go sideways when the file was generated? I also tried pulling the file again just in case it was an error when I pulled it the first time, however the ERROR tag is still there in the new file.

Here's what I'm seeing in the .ab file. I tried to capture the overall file structure while paring down the length a lot - original worked out to 776 lines, I've reduced that significantly for the sake of the discussion. I've also sanitized it quite a bit.

<AS_BUILT_DATA>
    <VEHICLE>
        <VIN>myvin</VIN>
        <VEHICLE_DATA>
            <DATA LABEL=""><CODE>xxxx</CODE><CODE>xxxx</CODE><CODE>xxxx</CODE></DATA>
        </VEHICLE_DATA>
        <PCM_MODULE>
            <DATA LABEL="PCM #">9x PCM data labels each with 3x code blocks formated same as data above,
            matches text from https://www.motorcraftservice.com/AsBuilt/Details</DATA>
        </PCM_MODULE>
        <BCE_MODULE>
            <DATA LABEL="xxx-xx-xx">all modules AS BUILT data, 6F0-01-01 thru 7E6-01-07, 1-3 code blocks per label</DATA>
        </BCE_MODULE>
        <NODEID>6F0
            ... tags in this section contain what looks like part numbers for installed equipment associated with each node, 
            will be deciphering/cross referencing all of these later.  One NODEID for each address group (first 3 chars of the data
            addresses above in the BCE_MODULE section)
        </NODEID>
        ... more NODEID tags (706, 716, 720, 723, 724, 726, 727, 730, 732, 733, 737, 746, 750, 754, 760, 765, 791, 7C7, 7E0, 7E4)
        <NODEID>7E6
            ...
        </NODEID>
        <ERROR>
            <ERRORCODE>614</ERRORCODE>
            <ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
        </ERROR>
    </VEHICLE>
</AS_BUILT_DATA>

Sponsored

 

[TarpDogg]

After looking through the Livnitup spreadsheet at the various configuration options, decided on a whim to take my truck's AS BUILT file and toss it into Notepad++ to see what was there. Was not expecting to see the data structured like XML, which was surprisingly nice as it made sorting through the data easy, and I'll have a fun project to work on over the next couple of weeks as I pick it apart to see exactly how everything was configured from the factory. What struck me as odd though is at the end of the file I came across an ERROR tag. Has anyone else seen anything like this? Is this normal, or did something go sideways when the file was generated? I also tried pulling the file again just in case it was an error when I pulled it the first time, however the ERROR tag is still there in the new file.

Here's what I'm seeing in the .ab file. I tried to capture the overall file structure while paring down the length a lot - original worked out to 776 lines, I've reduced that significantly for the sake of the discussion. I've also sanitized it quite a bit.

<AS_BUILT_DATA>
    <VEHICLE>
        <VIN>myvin</VIN>
        <VEHICLE_DATA>
            <DATA LABEL=""><CODE>xxxx</CODE><CODE>xxxx</CODE><CODE>xxxx</CODE></DATA>
        </VEHICLE_DATA>
        <PCM_MODULE>
            <DATA LABEL="PCM #">9x PCM data labels each with 3x code blocks formated same as data above,
            matches text from https://www.motorcraftservice.com/AsBuilt/Details</DATA>
        </PCM_MODULE>
        <BCE_MODULE>
            <DATA LABEL="xxx-xx-xx">all modules AS BUILT data, 6F0-01-01 thru 7E6-01-07, 1-3 code blocks per label</DATA>
        </BCE_MODULE>
        <NODEID>6F0
            ... tags in this section contain what looks like part numbers for installed equipment associated with each node,
            will be deciphering/cross referencing all of these later.  One NODEID for each address group (first 3 chars of the data
            addresses above in the BCE_MODULE section)
        </NODEID>
        ... more NODEID tags (706, 716, 720, 723, 724, 726, 727, 730, 732, 733, 737, 746, 750, 754, 760, 765, 791, 7C7, 7E0, 7E4)
        <NODEID>7E6
            ...
        </NODEID>
        <ERROR>
            <ERRORCODE>614</ERRORCODE>
            <ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
        </ERROR>
    </VEHICLE>
</AS_BUILT_DATA>

Here's an F-150 forum post discussing exactly the same Error 614 on their ab files. Looks like a common error and nothing to be concerned about: https://www.f150gen14.com/forum/threads/ecu-module-programming-guide-using-fdrs.8249/post-174155

 

[Toinky]

After looking through the Livnitup spreadsheet at the various configuration options, decided on a whim to take my truck's AS BUILT file and toss it into Notepad++ to see what was there. Was not expecting to see the data structured like XML, which was surprisingly nice as it made sorting through the data easy, and I'll have a fun project to work on over the next couple of weeks as I pick it apart to see exactly how everything was configured from the factory. What struck me as odd though is at the end of the file I came across an ERROR tag. Has anyone else seen anything like this? Is this normal, or did something go sideways when the file was generated? I also tried pulling the file again just in case it was an error when I pulled it the first time, however the ERROR tag is still there in the new file.

Here's what I'm seeing in the .ab file. I tried to capture the overall file structure while paring down the length a lot - original worked out to 776 lines, I've reduced that significantly for the sake of the discussion. I've also sanitized it quite a bit.

<AS_BUILT_DATA>
    <VEHICLE>
        <VIN>myvin</VIN>
        <VEHICLE_DATA>
            <DATA LABEL=""><CODE>xxxx</CODE><CODE>xxxx</CODE><CODE>xxxx</CODE></DATA>
        </VEHICLE_DATA>
        <PCM_MODULE>
            <DATA LABEL="PCM #">9x PCM data labels each with 3x code blocks formated same as data above,
            matches text from https://www.motorcraftservice.com/AsBuilt/Details</DATA>
        </PCM_MODULE>
        <BCE_MODULE>
            <DATA LABEL="xxx-xx-xx">all modules AS BUILT data, 6F0-01-01 thru 7E6-01-07, 1-3 code blocks per label</DATA>
        </BCE_MODULE>
        <NODEID>6F0
            ... tags in this section contain what looks like part numbers for installed equipment associated with each node,
            will be deciphering/cross referencing all of these later.  One NODEID for each address group (first 3 chars of the data
            addresses above in the BCE_MODULE section)
        </NODEID>
        ... more NODEID tags (706, 716, 720, 723, 724, 726, 727, 730, 732, 733, 737, 746, 750, 754, 760, 765, 791, 7C7, 7E0, 7E4)
        <NODEID>7E6
            ...
        </NODEID>
        <ERROR>
            <ERRORCODE>614</ERRORCODE>
            <ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
        </ERROR>
    </VEHICLE>
</AS_BUILT_DATA>

Just downloaded mine again and ended up with two errors:
<ERROR><ERRORCODE>612</ERRORCODE><ERRORMSG>PCM DATA NOT FOUND</ERRORMSG></ERROR>
<ERROR><ERRORCODE>614</ERRORCODE><ERRORMSG>CCC DATA NOT FOUND</ERRORMSG></ERROR>

I'm not where I can check the .ab file from the first time I downloaded it. It's on a different computer, but I'm curious.

 

[RadioDoc]

Ok glad to know at least I'm not the only one. I have to wonder if that's due to a mismatch between the vehicle data and installed components or what.

 

[fauxhican]

Thanks for sharing on the XML formatting. I've been starting to play with the as-built data with python, you just gave me something else to explore.

My efforts have been around the VIN based encoding with the motorola SREC format, trying to decode and see what I can learn about which character positions contain the actual settings values for each, then mapping between models and packages.

 

[Toinky]

Thanks for sharing on the XML formatting. I've been starting to play with the as-built data with python, you just gave me something else to explore.

My efforts have been around the VIN based encoding with the motorola SREC format, trying to decode and see what I can learn about which character positions contain the actual settings values for each, then mapping between models and packages.

@fauxhican, in case you are not aware, there is a spreadsheet by livnitup that would be potentially valuable for you to cross-reference. Also the one by EONR24 that you should check out. If you can't find them easily, I can point you to them.

 

[fauxhican]

@fauxhican, in case you are not aware, there is a spreadsheet by livnitup that would be potentially valuable for you to cross-reference. Also the one by EONR24 that you should check out. If you can't find them easily, I can point you to them.

I've been watching those developments. I'm doing this half as practice with python, and half for purposes of cross referencing some of these mappings. EONR24 has made some serious advancements, and pretty quickly, using the livnitup spreadsheet as a starting point from what I've gathered. I may be overly cautious on some of this, but my goal was to try to decode the hex data further, to avoid any blind spots in those spreadsheets or rely on forscan's abilities to perform corrections with the checksum processes. Just looking for some verification of the data on the front end instead of making my truck a guinea pig with someone else's settings. It may prove fruitless, or only confirm the work they've already done. Won't hurt to know more.

I currently have my own truck data, and some from 2 other users that were kind enough to share theirs for models and feature packages different from my own. Between those, and what others are posting in spreadsheets, I should be able to do some cross checking and hopefully generate some useful information that isn't out there yet for the Maverick. If anyone else wants to share data, I just need a VIN number in a PM for any configuration not represented here:

Year

Model

ECOBoost

Hybrid

FWD

AWD

AAWD

FX4

BAP

Tremor

Lux

4ktow

co-pilot360

2024

XLT

X

X

X

X

2024

XLT

X

X

X

X

2023

Lariat

X

X

X

 

[MaverickMom]

After looking through the Livnitup spreadsheet at the various configuration options, decided on a whim to take my truck's AS BUILT file and toss it into Notepad++ to see what was there. Was not expecting to see the data structured like XML, which was surprisingly nice as it made sorting through the data easy, and I'll have a fun project to work on over the next couple of weeks as I pick it apart to see exactly how everything was configured from the factory. What struck me as odd though is at the end of the file I came across an ERROR tag. Has anyone else seen anything like this? Is this normal, or did something go sideways when the file was generated? I also tried pulling the file again just in case it was an error when I pulled it the first time, however the ERROR tag is still there in the new file.

Here's what I'm seeing in the .ab file. I tried to capture the overall file structure while paring down the length a lot - original worked out to 776 lines, I've reduced that significantly for the sake of the discussion. I've also sanitized it quite a bit.

<AS_BUILT_DATA>
    <VEHICLE>
        <VIN>myvin</VIN>
        <VEHICLE_DATA>
            <DATA LABEL=""><CODE>xxxx</CODE><CODE>xxxx</CODE><CODE>xxxx</CODE></DATA>
        </VEHICLE_DATA>
        <PCM_MODULE>
            <DATA LABEL="PCM #">9x PCM data labels each with 3x code blocks formated same as data above,
            matches text from https://www.motorcraftservice.com/AsBuilt/Details</DATA>
        </PCM_MODULE>
        <BCE_MODULE>
            <DATA LABEL="xxx-xx-xx">all modules AS BUILT data, 6F0-01-01 thru 7E6-01-07, 1-3 code blocks per label</DATA>
        </BCE_MODULE>
        <NODEID>6F0
            ... tags in this section contain what looks like part numbers for installed equipment associated with each node,
            will be deciphering/cross referencing all of these later.  One NODEID for each address group (first 3 chars of the data
            addresses above in the BCE_MODULE section)
        </NODEID>
        ... more NODEID tags (706, 716, 720, 723, 724, 726, 727, 730, 732, 733, 737, 746, 750, 754, 760, 765, 791, 7C7, 7E0, 7E4)
        <NODEID>7E6
            ...
        </NODEID>
        <ERROR>
            <ERRORCODE>614</ERRORCODE>
            <ERRORMSG>CCC DATA NOT FOUND</ERRORMSG>
        </ERROR>
    </VEHICLE>
</AS_BUILT_DATA>

As a Computer/networking tech, I remember having to troubleshoot and repair hardware using a software with the acronym CCC. Service and repair shop software that updates daily regarding parts/prices/ and insurance repair estimating. The error looks as if the device used to pull the info was not part of the CCC network and the Car was expecting to communicate with the CCC database. just a thought, probable wrong.

 

[RadioDoc]

Just downloaded mine again and ended up with two errors:
<ERROR><ERRORCODE>612</ERRORCODE><ERRORMSG>PCM DATA NOT FOUND</ERRORMSG></ERROR>
<ERROR><ERRORCODE>614</ERRORCODE><ERRORMSG>CCC DATA NOT FOUND</ERRORMSG></ERROR>

I'm not where I can check the .ab file from the first time I downloaded it. It's on a different computer, but I'm curious.

The PCM data not found seems a bit weird. When you looked up your data, did you at least see a plain text set of PCM data? And does your .ab file have the <PCM_MODULE> section populated?

 

[RadioDoc]

I've been watching those developments. I'm doing this half as practice with python, and half for purposes of cross referencing some of these mappings. EONR24 has made some serious advancements, and pretty quickly, using the livnitup spreadsheet as a starting point from what I've gathered. I may be overly cautious on some of this, but my goal was to try to decode the hex data further, to avoid any blind spots in those spreadsheets or rely on forscan's abilities to perform corrections with the checksum processes. Just looking for some verification of the data on the front end instead of making my truck a guinea pig with someone else's settings. It may prove fruitless, or only confirm the work they've already done. Won't hurt to know more.

I currently have my own truck data, and some from 2 other users that were kind enough to share theirs for models and feature packages different from my own. Between those, and what others are posting in spreadsheets, I should be able to do some cross checking and hopefully generate some useful information that isn't out there yet for the Maverick. If anyone else wants to share data, I just need a VIN number in a PM for any configuration not represented here:

Year

Model

ECOBoost

Hybrid

FWD

AWD

AAWD

FX4

BAP

Tremor

Lux

4ktow

co-pilot360

2024

XLT

X

X

X

X

2024

XLT

X

X

X

X

2023

Lariat

X

X

X

Check out https://www.fordpro.com/en-us/fleet-vehicles/vin-decoder-and-guides/ if you haven't already. There's a set of PDFs towards the bottom of the page showing the VIN breakdown for each vehicle, although I would reckon that you're able to get more information out of the VEHICLE_DATA block in the .ab file, as the VIN only reveals the series/cab (VIN chars 5-7) and engine type (VIN char 8). According to the sheet for 2023, all of the Mavericks are [3FT][T][W8E/F/G][3/9][check digit][P][R][5x sequence ID]:
1-3: 3FT = Ford Motor Company, Mexico
4: T = Restraint Category (Manual Belts/Driver Frontal/Pass Frontal/Side Inflatable 1st & 2nd Row/Driver Knee)
5-7: W8E = 4x2
5-7: W8F = 4x4
5-7: W8G = AWD
8: 3 = Hybrid
8: 9 = Ecoboost
9: check digit
10: P = MY 2023
11: R = Hermosillo Veh. Assy Plant
12-17: Sequential Vehicle Identifier A00001 - F99999

The 3x hex blocks in the vehicle data I would believe are what you need to discern the exact package and installed options (my guess is that it's formatted the same as the rest of the fields as xxxx xxxx xx--).

 

[Toinky]

The PCM data not found seems a bit weird. When you looked up your data, did you at least see a plain text set of PCM data? And does your .ab file have the <PCM_MODULE> section populated?

I just went to the motorcraft website and ran it again. Here is a screenshot with NO PCM Modules listed! That would explain the error in the XML file. For what it's worth, there are no modules listed other than BCE modules (i.e., nothing after the BCE table).

Sponsored