Haunted Jeep

bmg9b · **Posted:** Fri Nov 10, 2006 11:24 pm

So, I'm driving home tonight and the check engine light blinks for like 20 seconds, and then I never see it again. Anyone got an idea what this means? I'm in the middle of reading the Owners Manual from front to back as we speak (type) so, if it's in the manual go ahead and respond anyway... that way it will just confirm what I find. I hope this is "normal" and not something going wacky... I've never seen a check engine light blink before.

Oh yeah, it's a 2006 Renegade 6-speed 4x4 if that helps any. Thanks!

bmg9b · **Posted:** Fri Nov 10, 2006 11:50 pm

"If the 'Malfunction Indicator Light' is flashing while the engine is running, severe catalytic converter damage and power loss will soon occur. Immediate service is required."

Uh oh. It's brand freakin' new... what's up with that? Any help?

It ran for a good 20 minutes after the issue with no problems. I think it's haunted.

CaKJFreedom · **Posted:** Fri Nov 10, 2006 11:50 pm

You could try to see if any codes were thrown out. Here's how and a list of what the codes are is included in a link in the thread.
reading codes

bmg9b · **Posted:** Sat Nov 11, 2006 12:14 am

OK, did that. It went through the diagnostic, but I didn't get any codes out of it.

You know, they make it sound like the Jeep is going to blow up in a matter of seconds, but the light really isn't that noticeable. I think if I were a soccer mom beating my 3 blonde-haired kids in the back seat I might have missed it. They should re-think the design.

saxdogg · **Joined:** Fri Jun 02, 2006 7:26 pm **Posts:** 199

BLinking means there is a misfire condition...raw fue may get to the CC which is why they say it may be damaged if you keep driving. Weird it would come and go...perhaps a faulty coil...I'd take it to the dealer, chances are there's a code stored they will pull which will tell what happened.

JP

chrisroth1 · **Joined:** Wed Aug 02, 2006 11:16 pm **Posts:** 69

with an 06 you can't do the turn off turn on thing to pull up a code, you will need a scanner to see if there is a code stored, the dealer or even autozone (free) will read the code for you; good luck

bmg9b · **Posted:** Sat Nov 11, 2006 10:13 am

Alright, so I called the local dealership today and the service writer didn't seem that concerned. I've got an appointment for Monday at 7am.

I'll let you guys know what turns up in case it happens to any of you.

bmg9b · **Posted:** Mon Nov 13, 2006 8:08 pm

Took the Jeep in this morning... no codes. Sigh. Maybe I'm just loosing it.

detroit_doc · **Posted:** Mon Nov 13, 2006 10:05 pm

My WRX did that to indicate a knock detection. Knock (aka detonation or pre-ignition) occurs when the fuel/air charge detonates before the spark plug fires. This usually happens under high-load, low rpm conditions and is bad for your engine. Some engines use a knock sensor to detect preignition so that it can modify fueling/ and or ignition timing to prevent it.

Were you towing or carrying a heavy load?

My WRX ran on premium fuel and the computer was always trying to get more ignition advance and lean out the closed loop fuel map. My WRX computer would keep advancing the ignition timing and leaning out the closed loop fuel air mix until knock occurred and then would retard ingnition timing and add fuel. So if I got a tank or two of really good gas it would ramp the ignition timing up and lean out the a/f mixture. If I then got some not so good gas, I would have several knock events (check engine light would flash) and the computer would start pulling timing and richening the closed loop a/f mixture until it went away.

No codes were recorded for knock events, just the momentary check engine light flash.

At least in my WRX misfire events were recorded and would leave the check engine light lit continously until I read the code with a OBD-II scanner.

bmg9b · **Posted:** Mon Nov 13, 2006 11:01 pm

Hmmm.. I wasn't towing.. but I usually keep the Jeep in the 1,000 to 2,000 RPM range (6-speed). Is that too low? I feel bad reving it up past the 2,500 RPM mark. My rule has been see what RPM the car does at 55mph in the highest gear (since 55mph is SUPPOSED to be the most fuel-efficient speed) and that's about where I tend to shift at. I don't do it for fuel mileage, so I can change my habbits... it's just a little system of mine... maybe I'm just quirky.

Thanks for the info, Doc.

Jeepjeepster · **Posted:** Mon Nov 13, 2006 11:15 pm

You can rev the 3.7 over 2500rpms without any problems. People with the auto must get to 3k to get up to speed if people are pushing you; I do at least? If im driving around town ill stay around 2k rpms but people kinda get mad. I just do not see the use in flooring it only to stop at the next red light? Thats all this place is, is red lights? :evil:

The only time I get over 4k is when Im passing someone on the highway. Not much I can do about it then unless I want to stay behind pokey.

detroit_doc · **Posted:** Tue Nov 14, 2006 1:14 pm

bmg9b wrote:

Hmmm.. I wasn't towing.. but I usually keep the Jeep in the 1,000 to 2,000 RPM range (6-speed). Is that too low? I feel bad reving it up past the 2,500 RPM mark.

Just like anything I think moderation is the key. Too low of an RPM puts stress on the main bearings. Very low RPM under high load is also tough because your oil pressue is lower at low RPM. Too high of an engine speed puts stress on the valve train.

I have an automatic libby, but I have owned a lot of manuals (and still do). My guess is that I would shoot for a cruise RPM of 1,800 - 2,200 regardless of my speed. I definately would not "lug" the motor cruising in lower 1,000 RPM range. It's probably much better for your engine to cruise at 2,500 RPM than it is to cruise at 1,100 RPM.

In my S2000 I cruise down the freeway at 4,000 RPM at 70 MPH in 6th gear. I'm sure that motor would be happy doing that for 200,000 miles. But that motor hates to be lugged down low. Cruising anywhere under 2,000 RPM and it starts complaining.

Haunted Jeep

Who is online