But I've only messed with the IPC module so far.ĭefinitely could use a map or spreadsheet of known As-Built fields / values / descriptions.ĬlockWorK wrote:Last month, I purchased a modified As-Built file (.AB) for my car to enable the AWD gauge on my 2013 Taurus SHO. 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. 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). Since I'm about to try enabling some more features, I needed an easier way to compare As-Built data. Originally, all my comparing was being done by hand, and that was tedious. Lastly, I used a beta of FORScan to program the changed bytes in the vehicle As-Built data. At 720-01-02, one byte (and the checksum) were different. Then I compared the FORScan files to the purchased.

I first used FORScan to read and save the.

Last month, I purchased a modified As-Built file (.AB) for my car to enable the AWD gauge on my 2013 Taurus SHO.