Ostrich Verify

Rebuildman · Post by **Rebuildman** » Fri Apr 03, 2009 4:09 pm

I am using a 165 ecm I have a modified arap bin via TunerPro, burned to a chip which runs the engine fine. If I upload the bin to my Ostrich 2 I can't get it to verify. I have tried checking the disable checksum box on upload in TunerPro, also various configurations in the bin reguarding checksum disable (AA). If I upload a stock ARAP bin to the Ostrich it verifies fine. I am using the XDF 165 def. What the heck am I doing wrong? I tried the Ostrich with the modified bin loaded and a 'bad verify' and the ecm goes to limp mode. What else does the verify look at in TunerPro?
Thanks in advance!

Six_Shooter · Post by **Six_Shooter** » Fri Apr 03, 2009 4:37 pm

The verify is failing due to the checksum disable.

Since the bin in the Ostrich now has "AA" at the checksum byte, it is different that what is loaded into Tuner Pro RT, and therefore fails.

If you manually change the checksum byte to "AA", before uploading you will be able to verify correctly.

Another possibility, especially if the checksum disable is used for upload of the stock bin, is that you haven't saved the modified bin yet and the original bin is still loaded to Tuner Pro RT.

Try saving the modified bin first, then verifying.

Rebuildman · Post by **Rebuildman** » Sat Apr 04, 2009 7:15 pm

Using the stock arap bin with the checksum disable box unchecked in TunerPro I can upload and verify to the Ostrich the bin with either AA or 6E in the mask ID block.
I tried this with my modified ARAP bin and neither one works, still will not verify. So it has to be looking at something else. There must be something I did to my modified ARAP bin that causes this problem even though it runs the engine fine.