New Web Tool: FORScan Viewer & As-Built Diff Tool

[Firn]

Hi everyone,

Like many of you, I’ve relied heavily on Livinitup’s incredible master spreadsheets to map out modifications on my truck. While his research is the gold standard, hunting down specific hex values and comparing multiple modules can get tedious.

To help speed up the process, I built a web-based utility to provide a modern, searchable interface for our As-Built files.

You can use it here: asbuilt.altctrlwrench.com

What it does:

• Interactive Reference Viewer: You don't even need to have a file ready to use the tool. You can jump straight into viewing the reference sheets directly and search for features, addresses, or keywords by name to see how things are mapped.
• Exact Configuration Decoding: Upload your own .ab or .abt files to instantly view your truck's exact current configuration mapped against the reference data, showing you precisely what features are turned on or off.
• Side-by-Side Module Diffing: You can load multiple files simultaneously to compare changes across different backups or truck configurations. View these differences mapped directly to their human-readable feature names, or toggle off the database mapping completely to rapidly compare raw data changes across multiple files in a clean, side-by-side diff viewer.
• Smart Filtering: Search and filter by module (APIM, IPC, BCM, etc.) or specific feature keywords instantly—no more endless scrolling through rows of Excel.
• Custom Reference Sheets: While Livinitup's data is the default master index for the truck community, the tool supports uploading your own custom reference spreadsheets so non-F-150 users can map other vehicle profiles right now.

Always Up to Date
To ensure total accuracy, the tool pulls the latest data directly from the community reference mappings every single time I rebuild the cloud instance. You're always parsing against the most current discoveries.

Privacy & Data Handling
I want to be completely transparent: Your vehicle data is processed entirely in-memory. Your uploaded files are never saved to a database, stored on a server, or tracked.

Support & Feedback
Livinitup's research is the absolute backbone of the default logic, and I’ve included a permanent attribution and a link to his donation threads in the app sidebar to ensure his efforts are supported.

On my end, running this on a managed Google Cloud instance to keep performance snappy does carry an ongoing hosting cost. If you find the tool valuable, do me a favor and take a quick look at the "Support the Developer" section in the sidebar for hardware recommendations and my custom 3D-printed automotive parts.

If you run into an address that parses strangely or have a UI feature request, let me know here or via the public tracking repo linked in the app.

Hope this speeds up your programming sessions!

Best,
Firn (Alt Ctrl Wrench)

Sponsored

 

[PJnc284]

Finally live! Sure it will be getting a lot of use. btw the link in your post pulls up a google search instead of going to the site.

 

[Firn]

Finally live! Sure it will be getting a lot of use. btw the link in your post pulls up a google search instead of going to the site.

Fixed, thanks!

 

[bmwhitetx]

Hey, nice work (sorry I haven't replied to your DM). It might have been easy for you, but the spreadsheet is not the easiest to transform into a proper dataset from my POV.

Hopefully this spurs some more FORScan breakthroughs. I feel like we've slowed down quite a bit - the last significant update I made to the mods thread was last October.

 

[Mike G]

I haven't seen what you've done yet but will do so shortly. And thanks in advance for tackling something like this. I know it was a challenge.

One thing I have a question about though before even checking it out is; what did you do about the sections of the asbuilt that the spreadsheets had no reference data for? Cause I know there are some sections where there is actual configuration data in the vehicle's asbuilt file....but when you'd go looking for what those values meant in the spreadsheets...there were whole sections of configuration info 'missing' for those values. As if somebody intentionally didn't want us to know what the options were for those bits on that module.

 

[rugedraw]

@Firn This thing is absoltely awesome. I've used it a few times already and it makes comparing two ab files side-by-side as easy as easy can be.

One thing I have a question about though before even checking it out is; what did you do about the sections of the asbuilt that the spreadsheets had no reference data for? Cause I know there are some sections where there is actual configuration data in the vehicle's asbuilt file....but when you'd go looking for what those values meant in the spreadsheets...there were whole sections of configuration info 'missing' for those values. As if somebody intentionally didn't want us to know what the options were for those bits on that module.

Yes, there was info that was purposely omitted fromt he spreadsheet. Ford would have a titty-attack if everything was put out there.

 

[Firn]

I haven't seen what you've done yet but will do so shortly. And thanks in advance for tackling something like this. I know it was a challenge.

One thing I have a question about though before even checking it out is; what did you do about the sections of the asbuilt that the spreadsheets had no reference data for? Cause I know there are some sections where there is actual configuration data in the vehicle's asbuilt file....but when you'd go looking for what those values meant in the spreadsheets...there were whole sections of configuration info 'missing' for those values. As if somebody intentionally didn't want us to know what the options were for those bits on that module.

These should be displayed as "Unknown Module"

Hey, nice work (sorry I haven't replied to your DM). It might have been easy for you, but the spreadsheet is not the easiest to transform into a proper dataset from my POV.

Hopefully this spurs some more FORScan breakthroughs. I feel like we've slowed down quite a bit - the last significant update I made to the mods thread was last October.

I hope it helps. I'm working on something now that I hope improves the ability to dig through these sheets even more.

 

[Firn]

Advanced Diff Viewer Update (Phase 1)
I just pushed an update to the site adding Phase 1 of the Advanced Diff Viewer to help isolate hidden feature toggles.

Instead of a standard file-to-file compare, you can now load a group of 1 to 5 files for trucks without a feature (Have-Not Cohort) and stack them directly against 1 to 5 files for trucks with the feature (Have Cohort).

How it looks:
The tool aligns the cohorts vertically in a flat, horizontal row view. It strips the checksum noise and breaks every hex character into its 4 raw bits, prefixing the bits with the original hex value so you don't lose your place:

3-0011 0-0000 5-0101

The Logic:
The viewer checks every single bit position across all loaded files and filters out matching rows automatically.

• No Highlight: The bits match perfectly across both cohorts (background noise filtered out).
• Green: A global difference exists, but the files within that specific cohort are 100% unanimous. This indicates a stable feature state.
• Orange (*): A difference exists, but the files within that cohort disagree. The specific split bits drop to an asterisk to highlight localized variation.

Filtering & Drill-Down:

• The Lonely Row Rule: If an address block only has data on one side of the cohort mix, it filters it out entirely since there's no baseline to diff against.
• Expansion: Clicking any row expands it downward to show the raw, file-by-file breakdown so you can see exactly which truck broke consistency on an orange flag.

Check it out and let me know if you run into any bugs!

Sponsored