tuning q for 730 ecm

[Dave Zug]

If he takes it on faith, and he or you don't know that the byte is actually
a value that will hold TCC locked WHEN IT IS ALREADY LOCKED, but will not in
itself CAUSE A LOCK, the package can give false hope.  The descriptions are
short and sometimes cryptic (thanks be to allah for them though!). TunaCat
config files can be made by anyone can't they? You can put your own finds in
there I thought.

PS the ebove description for that parameter is NOT KNOWN TO ME TO BE
ACCURATE, I am illustrating a point about interpolating the comments. The
proof is in changing the byte and if it did not do what you thought it
should do, then either the package is pointing or converting wrong, or the
parameter doesnt do what you read the comment to mean.

Look thru the HAC for all the other TCC related params and look at the
assembly next to them and the other comments. Unfortunately this takes some
more patience and skill than I have lately.

----- Original Message -----
From: <timsiford at hushmail.com>
To: <gmecm at diy-efi.org>
Sent: Saturday, October 14, 2000 5:47 PM
Subject: Re: tuning q for 730 ecm


>
> >LOOK THRU THE DISSASEMBLIES, NOT JUST THE SOFTWARE PACKAGES!
>
> I should have mentioned that I pulled it directly from the hac
(anht_hac.pdf).
>  I am the one who referred TunerCat to this constant.
> L831D: FCB 76 ; UNLOCK PREVENTION THRESH, (76 MPH)
>
> Tim

----- End of forwarded message from owner-gmecm at diy-efi.org -----
----------------------------------------------------------------------------
To unsubscribe from gmecm, send "unsubscribe gmecm" (without the quotes)
in the body of a message (not the subject) to majordomo at lists.diy-efi.org