Here is the story... car ran fine so I parked it for the night and took out the diagnostic cable (Steve Ruse cable) because he accidently forgot to put in the 10K ohm resistor. I wanted to put in my own so I wont have to jump the resister myself all the time, no big deal just something I wanted to do. So I reconnected everything and left it for the night. Yesterday morning the car started (with the fan running) and ran really rough for about 5 seconds, then died.... it cranks and wants to run, but only for 5 seconds. So I try to check the codes and the SES light stays on all the time!!! even with the paper clip it... doesn't flash anything at all never mind a code.. just stays lit. I disconnected the computer and the light went out like it is supposed to. I figure it is a bad computer so I buy another remanufactured one and same thing!!!! The only code I got was about 2 weeks ago and it was a code 42... something about the distributor. But, that was only once... similar condiditons, ran really rough then stalled, gave me a code, then started and ran fine!!

What do I do now, I already bought a new computer for $100, and gave them my old one. I tried to check the sensors and relays to see if they fried the computer... but wouldn't you think the computer would be able to protect itself somehow instead of just dropping dead? I checked all of the fuses, I have fuel pressure, the starter works, and I check the connections from the ALDL to the computer... what gives!!
I just swapped the TPI from a carb and everything was working fine for about 2 or 3 weeks so I really doubt it would be a crossed wire, if it was wouldn't the computer last another 2 or 3 weeks before it died too! I had to reuse the original cal pack and chip, well the one that I modified. But the computer should still give a code even if I take out the chip and go into limp home right? It seems like the computer just died and cursed all that follow!

------------------
'86 TA, T-tops, T-5, 3.73, 4 wheel disks 350, compucam 2040, performer intake,SLP Headers, 3" race magnum muffler, 1.6 Comp rockers, Ripper shifter, perf. friction pads, Hypertech ignition, Earls brake hoses, Hotchkis springs, Tokico Illumina 5 adjustable shocks and struts, Lakewood panhard and trailing arms
14.50@ 97 with carb... now converted to TPI

 

Assuming that the wiring is fine, after killing an ecm, wasn't a best opinion. Some parts places have a *test ecm* that you can plug in that will test for shorted sensors.

The ecms are really stout, it takes 15-20 mins. at 3x the rated loading to pop a Quad Driver, and that is excellent engineering.

Fans on, engine off, your in at least fail soft mode.

First check for a shorted sensor, then for one just out of spec..

Just get junkyard ecms, no sense paying more then you need to.

 

Grumpy, thanks for the advise... also thanks for the info about the quad drivers, I was really worried that I fried the new one too. It was only in the car for about half an hour and the igntion was only on far about 2 min while I was trying to get it to give me a code and trying to start it just to see what would happen.

Just to let you know the junkyard only had one and they wanted $100 for it also, so I figured I would stand a better chance with the rebuilt. Unfortunately they are keeping my money until the remanufacturing people take a look at it!

But I still need a good plan of attack here, I'll start with the sensors, but what about the relays, could they be the problem too?

 

Since I'm full of questions right now, would it be possible for the mem-cal to cause all of this. I have been playing around with the chips quite a bit and although I put in a known working chip, that was after the incident. Any thoughts?

 

Do you have a ZIF socket in your memcal? If so that is probly your problem. I had a HELL of a time getting all of the connections to actually make connection.

Brendan

 

Yes I do have a ziff socket and it worked ever since I did the swap, about 3 weeks ago. Besides, even if the memcal was bad shouldn't I at least get a error?? Besides is was working at night then wouldn't start in the morning. I will check it because I am almost out of options!

And after checking the connections, they are all good!

[This message has been edited by slowTA (edited August 05, 2001).]

 

Somebody has to know whats going one here... or at least have a good idea.
In hopes of narrowing this down please do me a favor... take the memcal out of the computer and try to read the trouble codes and tell me what happens. If you get any codes then that means my computer is bad, PLEASE help!