| From | Message |
mac
GenI
 
6/21/2009
20:35:10
|
 Subject: Thoughts on my "Not Ready"
IP: Logged
Message:
I have done some things to fix scan codes on my 97 45.2 Dak.
After the repair (which i apparently botched, see below), the MIL did not return. (check engine light stayed out). But the two previous codes were stored. (P0107 and P0138---one being low voltage to MAP and the other being a faulty signal from/to an O2 sensor--I had replaced the O2 sensor (I replaced only the front one (#1 or Upstream...P1038, IIRC, refers to a downstream unit issue.) and checked map voltage, which was fine.
I interpreted these codes to be caused by a botched job on my part of installing a generic cut-in O2 sensor on an earlier round of trouble shooting (multiple splices in the leads).
So I replaced the botched #1 sensor with a complete stock type Bosch sensor and simply plugged it in.
After that the MIL went out right away but the stored codes would not release until I cleared them with a borrowed Actron 9125 scanner (slick tool, about $100 on Amazon) 200 miles later.
Then, another 120 miles later "not ready" was still displayed, Can't get it past smog with either stored codes or not ready. This is California.
So it was back to the Actron 9125 and the testing looked ok for everything but it had not completed the testing required for the O2 Sensor Heater Monitor what was listed as incomplete.
After 120 miles including several open loop (floored the sucker for 30-60 seconds) as well as two "cold" starts (ambient about 70 degrees) there should have been enough opportunity to either pass or fail (i.e. to fail 3x thus setting a code).
Could this be simply a poor connection...somewhere? Where the htd cicuit works not it doesn't. Or does it suggest I need to drop more $ on it and gofer a #2 sensor.
I'm going to pursue the connection issue in my next under the (&(*&%^ session.
But comments from those which more knowledge abotu this than I would really be appreciated.
|
WOW
Dodge Dakota
JOIN HERE
6/21/2009
23:01:59
|  RE: Thoughts on my "Not Ready"
IP: Logged
Message:
That is a HUGE motor!
|
original wow
Dodge Dakota
JOIN HERE
6/22/2009
06:03:13
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
Name thief Peterpan troll strikes again. Get a life somewhere else kid.
|
mac
GenI
6/22/2009
16:38:07
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
45,2 is indeed large. so is my typing finger that hit two keys at once<G>
|
grow up
Dodge Dakota
JOIN HERE
6/22/2009
17:51:32
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
Stop calling peole names, you peter pansy.
Anyone can post as wow.
If you want the name that bad, register it.
|
mac
GenI
6/22/2009
22:21:52
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
cut it out children!
Returning to the topic...
simply unplugging then replugging the connector seems to have resolved the problem. passed smog, even with the outsized engine <G>.
But the HCs are higher than I'd like...and may not pass next time. Slight misfire in there somewhere...
|
WOW
Dodge Dakota
JOIN HERE
6/22/2009
22:59:02
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
mac glad to see atleast you have a sense of humor
now what what the bore an stroke be on the 45.2 ?
|
mac
GenI
6/23/2009
22:35:58
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
I duuno. about like a 1904 FIAT I guess.
(soon to be a 2010 Fiat...<G>)
|
l1tech
Dodge Dakota
JOIN HERE
6/29/2009
22:21:06
| RE: Thoughts on my "Not Ready"
IP: Logged
Message:
In order for the o2 heater monitor to run the engine is going to have to be up to operating temp. Try driving at a constant speed of about 55 mph for about 10 minutes, stop and idle for about a minute and then drive at 55 again for another 10 minutes...that should do it. As always smooth steady driving is what is required to get monitors to run, flooring it and varying the speed alot will not allow the monitros to run, sometimes they will not run until a cool down cycle has been performed(vehicle sat overnight).
|
| | P 1 |
|
Post a reply to this message:
Username Registration: Optional
All visitors are allowed to post messages
|
