EuroFanatic
10+ Year Contributor
- 31
- 0
- Oct 3, 2011
-
Springfield,
Illinois
First of all, having to post in the noob section is very annoying when I have my car torn apart in the garage and need it running asap and have to wait for answers for days before someone sees the question...
1996 Eclipse GST 2.0T
Starts after about 4-5 cranks, then will idle VERY rough. Burns very rich. After it warms up, the idle spikes to about 3k and holds. Only way to drop it is to shut the car off.
No vac leaks, replaced EVERY vac hose and pressure tested the boost pressure system. New plugs and wires. New air filter. No modifications besides an air filter put before the MAF sensor.
No check engine light, key on off ect method pulls no codes. Also with a Matco scan tool it says no ECM present, but the ECM is there, I can see it. Would run without it. If I unplug the connector to the computer on the MAF the car drops idle to a manageable level and evens idle. Plug it back in and the car idles waay high again. Seems like its in its own limp mode and runs VERY rich (black smoke) and I cannot get to the CEL to diagnose why.
Is there anyway to force the data link connector to give up its information? Are there any ideas on what could cause this?
1996 Eclipse GST 2.0T
Starts after about 4-5 cranks, then will idle VERY rough. Burns very rich. After it warms up, the idle spikes to about 3k and holds. Only way to drop it is to shut the car off.
No vac leaks, replaced EVERY vac hose and pressure tested the boost pressure system. New plugs and wires. New air filter. No modifications besides an air filter put before the MAF sensor.
No check engine light, key on off ect method pulls no codes. Also with a Matco scan tool it says no ECM present, but the ECM is there, I can see it. Would run without it. If I unplug the connector to the computer on the MAF the car drops idle to a manageable level and evens idle. Plug it back in and the car idles waay high again. Seems like its in its own limp mode and runs VERY rich (black smoke) and I cannot get to the CEL to diagnose why.
Is there anyway to force the data link connector to give up its information? Are there any ideas on what could cause this?