robertf

its been a while since I've messed with any 1227730 ecm's but yesterday a friend needed some changes done to a .bin so I volunteered. Every time I try to run a burned chip or use an emulator I get no communication from the serial link and jumping A & B on the aldl doesn't display codes. Thats usually a sign that of hardware or checksum problems.

I've used 3 different ecm's, one of those being a bench unit not hooked to a vehicle and I get the same results everytime

Here is what I've done so far:
burned stock chip, socketed memcal.
used ostrich 2.0 with socketed memcal
used ostrich 1.0 with socketed memcal
used both emulators on stock memcal with moates adapter
tried various stock $8d bins from moates file site on the emulators with 8D and AA in the .bin.
swapped cables with the emulators
successfully read the contents of the emulator with eprom reader.


Next to my bench 1227730 I have a 1227747 and that is communicating just fine with the 1.0 and the same cable. Everything works as it should with an unmodified memcal. I'm hoping I'm overlooking something obvious. Switches and jumpers were set to 28 pin. Used a 27c256 eprom.

Any ideas or suggestions on things I may have overlooked? This was supposed to be a simple fan temp change, but it has consumed my entire saturday troubleshooting my own equipment.

And to top it off I've got some software I wrote to pull the .bin using mode 2 that I can't trouble shoot because of the uncooperative emulator. I've started another thread if someone would like to test that out for me.

robertf

well the planets aligned and it seems that all of the stupid little things that can go wrong with individual equipment did. combination of someone flicking the switch on the aldl cable, a stupid error in some homebrew software that allowed the checksum to compute correctly yet placed data in the wrong area, and an ostrich 2.0 that won't work with tpi computers were the problem.

I remember that the ostrich 2.0 didn't work with the older tbi computers when it came out unless you used that socket booster, but were '730s ever a problem with it? it works fine on other makes/equipment, and my crappy willem eprom burner reads it just fine.

enswrob

is the offset correct?

Six_Shooter

iTrader: (2)

Ostrich 2.0 works fine with the '7730/'7749 ECMs without a socket booster.

I would be looking at the socketed MEMCAL, that may be your problem. If a pin on the socket is not soldered to the MEMCAL solidly you will experiance problem like you are.

This is why I use Moates' adaptors.

Have you read the Ostrich or newly programmed EPROM through the MEMCAL? That would also be a way to test the MEMCAL itself. You can do this by using an HDR1 (moates.net), or similar.