When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I've got a 3 month old Quarterhorse I bought new and am using the latest tuner pro build. In tuner pro I am using an A9L bin and uploading that to my A9P.
I can't seem to get rid of my code 15 and, after researching, it seems TP takes control of this so I am not sure how to fix it. Doesn't seem to matter of I use a 56 or 64k bin, I even put decipha's A9L2 tune on and it does the same thing.
I'd usually ignore it but I notice when the check engine light flashes for the code 15, I then have connection problems with the Quarterhorse and it really interrupts logging.
I wonder if this would mean I actually do have a bad PCM. I am not noticing any problems though.
I do have another A9P PCM I could use to test with but I was hoping to get this checksum issue resolved before I switch to that PCM.
Man, I don't know, I know one of the flashes I did on mine gave me a checksum error. The version of BE I am using (BE2012) actually calculates a new checksum and loads it into the ECM when I flash it. I was trying to see what it is calculated from, I think it is a composite of the values, because mine is currently 16877 and original was 19650. I know the ECM uses that to determine that the BIN file is not corrupt.
Ok, I found it! Here is what BE says:
The checksum is Fords way of detecting if a calibration is corrupt. The Checksum is
a mathematical addition of all parameters within a tune. When the EEC is powered
up it goes through a self-test and calculates a checksum. It then compares this
checksum to a stored value in memory. If both values match then the tune is good.
If the checksum does not match, then the tune is assumed to be bad and a check
engine light may illuminate. The starting and ending addresses are the range in
which the EEC adds all parameter values to come up with the checksum. The result
is then compared to the value displayed is the ROM PID.
Last edited by 85lebaront2; Jul 13, 2013 at 01:19 PM.
Reason: Added explanation.
Ya, the program calculates this and I can't control it.
I am not really sure of the problem but I am going to remove the Quarterhorse from inside the PCM and mount it remotely with a flexible cable. I know my PCM moves from vibrations and I wonder if the QH is touching something
All I have is the option to calculate it or not. I know that since I don't use a piggyback device all mine is done through the Mongoose cable. The advantage is it actually loads the calibration directly to the ECM, the disadvantage is I can't have multiple tunes I can change with a switch.
I used the tweecer and I never felt having multiple tunes is necessary. I used the switch but just stuck with one tune. Ended up not needing/using it. I know you can have multiple tunes if you are using QB with BE and a rotary switch but I don't feel the need.
If I have a tune I want to test with, I load it into tunerpro and click the emulate button. Effectively this gives me 2 tunes to work with but when I drive all I want is the tune with the most power.
I am more interested right now in just getting everything worked out, shift points, lockup, fuel economy etc. before I build my new engine, then maybe more power, but I intend to get most of that through compression and the F3 heads.
To add, the tweecer caused me so many issues I got rid of it, the only advantage it has over the others is the switch. Still don't miss the switch, or the tweecer.
a bad checksum won't throw a check engine light, you probably have something out of range when the engine is running do a KOER - key on engine running test and pull codes, you should find out what its complaining about
2 year later update, sry for the revival but its needed
a few months back I went through the code and verified BE and TunerPro were both calculating checksums incorrectly
I worked with mark the creator of tunerpro and we now have tunerpro correctly calculating the checksum on all ford ecus, I have the updated gufb, cbaza, and 99-04 ford def files on my website as free downloads that will correctly caculate out the checksum
2 year later update, sry for the revival but its needed
a few months back I went through the code and verified BE and TunerPro were both calculating checksums incorrectly
I worked with mark the creator of tunerpro and we now have tunerpro correctly calculating the checksum on all ford ecus, I have the updated gufb, cbaza, and 99-04 ford def files on my website as free downloads that will correctly caculate out the checksum