Ted B LPM trouble

[ShoThang]

OK, so I got the glovebox out, took the screw out, took sticker off, and cleaned the board (I forgot to clean the bottom part so i spent over an hour cleaning the chip cuz it had grease on it). Now, when I put the chip in and plug in the computer connection under the hood, then turn the key in the "On" position, the fan turns on.

Does anybody have any idea why this would be happening? Or would I be better of just emailing Ted about this?

Thanks for any help you can provide.

 

[AutoSHO]

Flip the chip over. It is upside down.

 

[luigisho]

Contact Ted. IIRC the fan on problem requires a reburn.

 

[Bizzy]

could also be a weak computer. I had the same problem with my LPM, I swapped my 94's X2J with an X2J from a 92 that has an Intel processor in it. then the LPM worked like a charm.

you may want to pull your ECU out and take the cover off it and see if the chip is a moto or Intel. Seems that the Intel ones were more condusive to working with the LPM's

Might sve you some time and frustration mailing the chip back and forth.

 

[Axianator]

Assuming SHOthang is using one of Ted's "new-style" Autologic chips (and I'd say he is), then it would be next to impossible for it to be installed upside-down with the PCM in the car. Just an FYI.

The 'fan-on' situation that SHOthang described is actually referred to as "Limp home" mode and is a safety mode employed by the PCM for a variety of reasons. For the reason in this case, I'd have to side with Bruce's theory and say that your PCM's chipset is probably to blame, SHOthang. Do as Bruce has recommended and pop the case top off of your PCM and have a look inside at the chipset. If it's a Motorola chipset (denoted by an 'M' on the upper-left of the main IC on the board), then you may have found the problem. A majority of the time when limp mode is triggered at startup and a chip is connected to the computer via the J3 service port, then a compatibility problem between the chip and PCM chipset is usually to blame. Reprogramming will (unfortunately) not help in this case and the problem can only be solved by using another PCM with a different chipset.