Ford As Built Data Deciphering

[ClockWorK]

I appreciate the feedback. The whole reason I write programs and share them is to help people, so it's great to hear when I'm accomplishing that. And it's good to occasionally bump this thread to let people know there's a simple comparison tool.


I think some other programmers are working on a more detailed AsBuilt viewing program, but I don't know if it does the same things that mine does.

[qfmrc]

If you just want to cough up some cash, this guy will sell you modified as-built for the Fusion:
http://www.fordpimods.com/2013-2016-for ... auges.html
Looks like 16 Fusion can add Tire Pressure and Digital Speedometer.
If you buy from that guy, you can compare before/after and identify which bits were modified. Then share the info. That's what I did with my Taurus and the AWD gauge, and now it's an option in FORScan.

However, I know that some users here and on XDA already know which bits you need to modify. Come join the discussion.
http://forum.xda-developers.com/windows ... s-t3321397

Another option is to use the Deducer part of the AsBuiltCompare program to compare a bunch of Fusions (and maybe Explorers) and narrow down the bits that correspond to the gauges. This is what I used to figure out the Engine Hours gauges that are now available in FORScan for the Taurus.

Or you can just change bits. I don't *think* you can brick the IPC to the point that you can't simply change bits back. But I would recommend first exporting the AsBuilt data for your IPC before you change anything.

Thanks Clockwork.

[trife86]

Hey clockwork,Any help getting AWD Gauge working on a 2013 PI Taurus, I Dont see it in the regular options and not sure where else to look,

I played with dark car mode and enabled keyless entry but cant figure out the AWD Guage, I Have the asbuilt data from the ford website if you need anything to compare to?

Thanks in advance

[cavemanb]

Hey clockwork,Any help getting AWD Gauge working on a 2013 PI Taurus, I Dont see it in the regular options and not sure where else to look,

I played with dark car mode and enabled keyless entry but cant figure out the AWD Guage, I Have the asbuilt data from the ford website if you need anything to compare to?

Thanks in advance

This worked on my 2015, you can try it----

[trife86]

Here is my line of code for it
720-01-02 8A14 0003 3D08

I Did try changing the 8 to a B (but it comes up with a checksum error, and I did not proceed) Only change i tried that actually gave me a error so far

[ClockWorK]

You have to also change the checksum (the last 2 chars) whenever you change any AsBuilt bits.

If I'm not mistaken, change
8A14 0003 3D08
to
BA14 0003 3D38
and you should no longer receive the checksum error.


Or, FORScan should have an IPC section (not As Built) where this option can be toggled on/off directly.

[trife86]

You have to also change the checksum (the last 2 chars) whenever you change any AsBuilt bits.

If I'm not mistaken, change
8A14 0003 3D08
to
BA14 0003 3D38
and you should no longer receive the checksum error.


Or, FORScan should have an IPC section (not As Built) where this option can be toggled on/off directly.

That change did it, No toggle on off for that option but the line BA14 0003 3D38 worked great, thanks buddy

[posts]

I don't really know what I'm doing and could use some help. 6 months into the 2014 Fiesta ST build Ford added a double honk if the key is outside of the car while running. I have two as built files, both 2014, both with the same options, one honks, one does not. Can anyone help me figure out what I need to do to turn this off on my car?

Honk : https://www.dropbox.com/s/nm64g9evlk37c ... 95.ab?dl=0

No Honk : https://www.dropbox.com/s/tcia2soj32lkd ... 48.ab?dl=0

I have compared the files using the AB comparison tool and only a few things are changed mostly related to air bag and ABS. Any help will greatly be appreciated.

[ClockWorK]

The two AsBuilt files appear to have very different BCMs (726-XX-XX). Which is why that particular section does not show pairs of values when comparing. One file simply lacks 726-18-01 thru 726-49-04.

[posts]

The two AsBuilt files appear to have very different BCMs (726-XX-XX). Which is why that particular section does not show pairs of values when comparing. One file simply lacks 726-18-01 thru 726-49-04.

Both files were created using the same website, is there a different way to create the AsBuilt files? We just plugged the vins into the website and downloaded the files. Sorry I'm very new to this but trying to learn how it all works.