Originally posted by bnoon:
Not to much info for the right people... Even though there are different mask files out there, the programming patterns remain very much the same across the board. Take a look at a known mask file with a matching bin (Say, from a Mustang), and then stare at your pulled bin for a while... pretty soon, timing tables start to appear, MAF transfer functions pop out, coolant tables, etc, etc... Masks are easier to create than most people think.

2. I know enough about hex patterns in binary files and mask files to increase my MAF and O2 table resolution on my TA 2 fold. I just don't have the motivation to chase Ford codes... I just thought someone would have by now.


1. It's not that easy. I have Mustang binaries and the software to edit them. Even when I find the different locations certain things change it does not correlate to the code from a different platform. I wish it were that simple. For instance the tables and charts are not all listed together in their entirety. Various parts of them are also variables changable in previous scalars and even other single entries. Then just inserted into certain table data to form an X or Y axis.

I tried working on Tom's code for a while (SFG2 IIRC) and only found maybe a dozen primary location indexes. Those are the easy ones to find.

2. That's like comparing a VIC-20 to a super computer though. Not even in the same realm.

2000 SVT #674 13.47 @ 102 - All Motor! It was not broke; Yet I fixed it anyway.