Bad Ostrich?

[Syclone#892]

Re: Bad Ostrich?

Well I played with the checksum disable and any time I had the box checked it would not verify but if unchecked the box it would verify everytime.

So I also and still wondering what exactly the checksum is for maybe someone will chime in eventually

Hmm funny you mention that because I did order that since you save a couple bucks with purchase of the ostrich. I am going to double check my box tomorrow but I don't think I ever got it. Maybe that will help out!

Hey Tooky I hear a couple of my goofy co-workers ran into you the other night on hwy. At least I think it was you the one couldnt remember your name or much of anything and the other didnt show up to work on sun.

Sounds like your sy is running good congrat!:tup:

 

[Tooky]

Re: Bad Ostrich?

LOL!! Oh man now it all makes sense. I was cruising the strip after the car show and these 2 guys on Harleys (or some similar bike) pull up and are just freaking out over my truck, and they kept raving about their friend "Davey" and his "TWIN TURBO" Syclone and how fast it is, man I was laughing because the guy said "TWIN TURBO" like 6 times in a row, I shit you not. I was wondering who could this possibly be in the area that I haven't heard of?

I just never put "David" and "Davey" together. Can you PM me a bit about your truck?

 

[JSM]

Re: Bad Ostrich?

Checksum is a double check of sort for the ecm to verify it read ALL of the data. Think of it in simple terms of adding up all the bits for EVERYTHING in the chip, and putting a # equal to that sum. (not exactly how it works but close). The sum gets put into the checksum.

Now the ecm can do the math itself, compare to the checksum and say GREAT I have read all the data. Works great when data isn't changing.

If any piece of data changes (your tuning) then the sum of the data will change, so then the checksum will also need to change. Tunerpro/promgrammer have tools to recalculate the checksum but you would have to do that after every change, and the ecm would throw a code between when you made a tuning change and recalculated the checksum.

Easiest to just cancel the checksum check which is done by putting AA in for a checksum.

 

[Tooky]

Re: Bad Ostrich?

Why hasn't the ECM ever thrown a code for me when I'm real time tuning, given that I haven't disabled the checksum? The data is changin' but the ECM ain't complainin'...

Maybe something in the Ostrich/TunerPro that handles this regardless of the 0xAA setting?

 

[turbodig]

Re: Bad Ostrich?

Why hasn't the ECM ever thrown a code for me when I'm real time tuning, given that I haven't disabled the checksum? The data is changin' but the ECM ain't complainin'...

Maybe something in the Ostrich/TunerPro that handles this regardless of the 0xAA setting?

Actually, I think the later tunerpro code calc's your checksum for you, and puts it in.
Change something in your bin, then check the checksum to see if it changes after a save/upload.

If your checksum wasnt $AA, or wasn't calculated right, you'd know.

 

[Syclone#892]

Re: Bad Ostrich?

Thanks the checksum info makes a little more sense now
I did just download tunerpro so maybe mine already does it?

Hey Tooky I sent you a pm, pretty funny about the TT comments considered that kid has seen the truck once:lol:
Good thing I only work there once a week and don't have to see them much!:rotf: