[Gmecm] More '730/$8D tuning questions...

[dozierhc at aol.com]

Claire...
 
Are you checksumming the EPROMs or at least disabling the checksum algorithm by placing an "AA" at the Program ID location ($8008?)  This could certainly cause this type of action.
 
I would burn an EPROM with the $8D set to "$AA" at location, or checksum what you have again and manually update the locations $8006-7 with the resultant checksum and try that.
 
Hank
------------------------------

Message: 8
Date: Thu, 19 Apr 2007 06:57:54 -0500
From: "Clair Davis" <clair.davis at charter.net>
Subject: Re: [Gmecm] More '730/$8D tuning questions...
To: <gmecm at diy-efi.org>
Message-ID: <003201c78279$f6eb06c0$03000004 at davis>
Content-Type: text/plain;   charset="iso-8859-1"

Yes, they are both $8D, and I was surprised, too.  With the emulator (Moates
APU-1) in place, it's not a problem of a chip not burning right, and the
bin's can be swapped around easily.  I think I need to do a bit more
research on other 5-speed calibrations and see which ones will load up and
idle without a hitch.  The only error code I could retrieve was "12", so
that's not very revealing, either.

Clair


----- Original Message ----- 
From: "Robin Handley" <Robin at FuryWorld.fsnet.co.uk>
To: <gmecm at diy-efi.org>
Sent: Thursday, April 19, 2007 1:45 AM
Subject: Re: [Gmecm] More '730/$8D tuning questions...


> > right up when I reloaded the bin I was driving with last weekend.  I
> > couldn't even get the ALDL to synch up until the last bin was loaded.
>
> I'm surprised by this. Aren't the two .BINs you're using both $8D? If so,
> AIUI, the only difference should be the lookup values, so why would the
ALDL
> be affected?
>
> Robin
>
________________________________________________________________________
AOL now offers free email to everyone.  Find out more about what's free from AOL at AOL.com.