Ford As Built Data Deciphering

Car configuration discussions and experience sharing
Lukeyson
Posts: 18
Joined: Fri Mar 22, 2019 1:15 pm
Vehicle: Fiesta ST150/XR4, 2.0 Duratec, 2007

Re: Ford As Built Data Deciphering

Post by Lukeyson » Mon Apr 08, 2019 6:20 am

I found a better source of VINS and was able to get way more of them. Ford's Germany plant looks like they produced some 350,000 Fiestas in the early 2000's, and then by 2007 were making around 600,000 per year - so yes, that is an idea of how many vins I've been able to extract. The Spanish Plant started making Fiestas some time in the mid 2000's I think.

So i have had success. By focusing only on German built 2007 ST150 Fiestas in RHD, I have been able to get 2 x Perfect Bits in the GEM for auto-lights and auto-wipers, and another bit for the Folding Mirrors - although the Folding Mirrors looks like it can be done by updating a PID too.

HOWEVER, I have not yet been able to identify if there are any perfect bits for the Auto Climate Control, since the comparator app only seems to use the secondary feature list for comparison, and not the primary features. I think what I might need to do is find a way to manually add 'auto climate' as a secondary feature for those affected cars into the downloaded HTML text for those small number of cars with that feature and see if the comparator can pick it up and give me perfect bits that way.....

So, I am now hugely positive that I may be able to install the modules, sensors, switches and looms and be able to enable those features for an early Fiesta.


Luke

er65nsunny
Posts: 7
Joined: Sat Jul 06, 2019 11:35 am
Vehicle: 2008 ford Edge Limited 3.5 L

Re: Ford As Built Data Deciphering

Post by er65nsunny » Sun Jul 14, 2019 10:36 am

I was wondering if anyone would know which As Built code block is for the color palette option for a 2009-2010 Lincoln navigation ACM. I would like to program that into a 2009-2010 Ford Edge ACM

er65nsunny
Posts: 7
Joined: Sat Jul 06, 2019 11:35 am
Vehicle: 2008 ford Edge Limited 3.5 L

Re: Ford As Built Data Deciphering

Post by er65nsunny » Wed Jul 24, 2019 5:02 pm

I finally figured out the AS built code to change and it worked. FORScan is amazing.

Skythunder83
Posts: 2
Joined: Tue Aug 13, 2019 11:55 am
Vehicle: Mustang SC 4.6 2008 / Explorer RWD 4.0 2006

Re: Ford As Built Data Deciphering

Post by Skythunder83 » Fri Aug 16, 2019 10:23 pm

FORScan is amazing and great thx to @ClockWorK for the asbukitexplorer that is great work. I just started with FORScan few days ago and how much it helped me through many things many years I looked for, I'm sad I didn't know about it before, but now I do so :mrgreen:

bluewater
Posts: 2
Joined: Thu May 31, 2018 8:11 pm
Vehicle: F-150, 3.5L Echoboost/382, 2016

Re: Ford As Built Data Deciphering

Post by bluewater » Tue Oct 22, 2019 10:03 pm

ClockWorK wrote:
Wed Mar 30, 2016 4:21 pm
Last month, I purchased a modified As-Built file (.AB) for my car to enable the AWD gauge on my 2013 Taurus SHO.
I first used FORScan to read and save the .ABT files from every module of my car.
Then I compared the FORScan files to the purchased .AB file, and identified the difference. At 720-01-02, one byte (and the checksum) were different.
Lastly, I used a beta of FORScan to program the changed bytes in the vehicle As-Built data.

Originally, all my comparing was being done by hand, and that was tedious.
Since I'm about to try enabling some more features, I needed an easier way to compare As-Built data.

It looks like this:
Image

The difference shown is two bits. I'm not clear on whether these are single-bit flags (changed two values from binary 0 to 1) or if this is a 2-bit field (change one value from binary 00 to 11).

Then I started thinking, I can look up VINs of different vehicles and possibly narrow down which bits of As-Built data correspond to which optional features. Possibly. But I've only messed with the IPC module so far.

Definitely could use a map or spreadsheet of known As-Built fields / values / descriptions.
Good job ClockWork! I just found out this useful tool to compare As-Built files. At the beginning, the "Show Module Names" button works. However, after running the tool a few times, the Module Names are not shown anymore. Please let me know what needs to be done to show the Module Names.

Thanks in advance!

User avatar
fordsmax471
Posts: 134
Joined: Mon Aug 07, 2017 5:29 pm
Vehicle: Ford S-Max 2,0 TDCi 2017 PowerShift

Re: Ford As Built Data Deciphering

Post by fordsmax471 » Wed Oct 23, 2019 3:15 am

Last edited by fordsmax471 on Wed Oct 30, 2019 3:28 am, edited 2 times in total.
ELS27 v4.0 USB

bart56
Posts: 1
Joined: Fri Oct 25, 2019 1:52 pm
Vehicle: 2011 Ford, 2006 Mercury, 2008 Fusion

Re: Ford As Built Data Deciphering

Post by bart56 » Mon Oct 28, 2019 8:42 pm

FiveLeeter918 wrote:
Wed Jan 31, 2018 3:56 pm
Correct. I did also notice that the navigation turn by turn in my cluster switched from ft to yards, but that doesn't bother me, and I don't pay for Sirius so no loss there.

So I found a comprehensive list of Forscan mods to the Edge, some cool change possibilities but none of them worked for my car. Definitely gave me hope of some other options that I'd like to figure out for the SHO.
So where did you find the Edge list? I've found F150 and Explorer and some of the others posted here but none for the Edge specifically. I have a 2011 Limited.
Thanks

Post Reply