tuning q for 730 ecm

timsiford at hushmail.com timsiford at hushmail.com
Tue Oct 17 14:58:33 GMT 2000


Dave,

I should probably make myself more clear when I say something.  Let me try 
this again...

I found the necessary parameter in the ANHT_HAC.PDF which I believed to 
control the mandatory lockup of the TC.  I submitted this info the GMECM 
mailing list and everyone who did respond to my posts was only in agreement 
that the address that I was referring to looked to be the address that I 
would need to change.  I added this parameter to my TC definition file (because,
 as you said, you can modify the TC definition files).  TunerCat was in 
the process of releasing a new TDF for the 8D so I asked him if he could 
do 4 things....
1) Add EPROM ID
2) Add Knock attack rate
3) Add knock decay rate
4) add mandatory TC lockup

I had added all 4 of these to my TDF.  The EPROM ID was not working due 
to a bug in TC where he wiped the EPROM ID on every save of the bin.  The 
knock attack and decay rates looked to be working aok.  The TC lockup appearend 
not to be working but more testing was still needed.  

I asked TC to add the above parameters ... I didn't tell him exactly how 
to do it.  My reference to the address was -my- reference that I used for 
creating my TDF for testing purposes.

Tim


At Sat, 14 Oct 2000 23:44:59 -0700, "Dave Zug" <dzug at delanet.com> wrote:

>
>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
>


More information about the Gmecm mailing list