Car's been acting a fool lately and i'm kind of confused with it, ive been reading around and think I have it pinpointed..but I have yet to get any real time to look at it.

The car revs just fine and the tach is wonderful in matching the engine's revs. When I go into vtec range (after the switchover) the tach will start bouncing erradically back and fourth and the exhaust will make a popping sound. While this is going on the car will die out for a split second occasionally.

Would this be an issue with the ignitor?

Also, while driving..if I floor the car it will pause for a slight second and then accellerate. Car feels really sluggish sometimes.

Done a basic tuneup but only running 1 o2 wire seeing as my 4-1 header doesnt have a bung for 2. (can anyone tell me the correct bung placement so I can fix this?)

The car's an 89 hb si w/ an obdo b16a swap. I/H/E w/ GSR cams.

Thanks!

 

Anyone? I searched but...every tach. issue that ive read on is slightly different. I think it might be the ignitor but i'm not sure. The tach is fine under vtec range.

 

Could be the O2 sensor issue. Are you throwing any other codes?

 

<TABLE WIDTH="90%" CELLSPACING=0 CELLPADDING=0 ALIGN=CENTER><TR><TD>Quote, originally posted by c0d0r &raquo;</TD></TR><TR><TD CLASS="quote">Anyone? I searched but...every tach. issue that ive read on is slightly different. I think it might be the ignitor but i'm not sure. The tach is fine under vtec range.</TD></TR></TABLE>

That would the first thing I'd check.

 

well...as far as the o2 sensor issue is, I currently am running both sensors..but they are in the before cat/after cat placement on my high flow cat. There are no codes showing on the dash, but I checked my ecu and am throwing 2 codes.

1. 23 which is the knock sensor..weird, I just replaced it.

2. 15-ignitor output. Is there any way I can service the dizzy for just the ignitor? Thanks!

 

Your hesitation is because of the O2 sensor. The tach and misfire means it's probably time for a new distributer.

 

As far as the knock sensor goes, you could always try replacing the wire that runs from the sensor to the ECU. It'll be a PITA, but an old, hard, broken wire will definitely throw a code. Did the car always throw the KS code, or did it just pop up?

Your dash CEL might be burnt out

 

If the ecu is throwing an ignitor code than its the ignitor. On a friends b16a it threw an ignition output code and we weren't getting any spark. Turned out to be a burnt/fried dizzy plug. Im pretty sure you can buy just an ignitor from autozone, but they might call it something else

 

the dash cel works, on startup it lights with all the other dummy lights to let you know it works. The ks sensor has always been lit. I replaced it and it went away a couple weeks ago..I'm guessing it's back for more. I swapped the o2's..car seems to be a bit stronger with daily d'n it (under 3 grand). What's weird is that i'm throwing the ignitor code but the car runs fine under vtec. I'm working on replacing the dizzy. 250 bucks is hard to come by lately though.

 

I think I realized the error of my ways. If you remember that a couple weeks ago my screw holding the button backed itself out causing the dizzy to crap out. (code 15 ignitor output) and I replaced a failed KS (code 23) I did both of these and the cel's on the dash went away, there's one n00b thing that i missed.

Resetting the ecu.

Just fixing the problems made the cel light on the dash go away yet the codes stayed stored in the pcm's internal memory. Procedure, procedure, procedure. I guess we all make mistakes.

I pulled the hazard fuse for 10 sec. today at work and re-started the car.

BOOM.

No codes, i'm going to keep my eye on it though.