irmr2

CLIFF NOTES:

Timing belt snapped
Valves checked by brother in law, looked okay
Crankshaft fluctuation sensor did break
Timing belt replaced, sensor left disconnected, engine doesn't respond as fast
Tried to bypass CKF by splicing to CKP
Engine worked great for about 2 mins, then started to missfire bad
Drove home, disconnected splices
Engine runs good, but doesn't respond as fast again.
Want engine to run better
Where to turn now?

END/ CLIFF NOTES.

I've been searching around the web for a decent looking Acura forum for a couple of days now, and I've joined a couple forums to see which crowd I like.

I've mostly joined because of my wife (who happens to own a clean 96 GSR), but I'd like to learn a few things too.
We purchsed the car with an AEM cold intake, DC header and a GReddy catback exhaust.

I'm attempting to fix this problem myself because the closest Acura dealership is and hour and a half away, and the Honda stealership are dicks!

Now onto the problem: The car was driving fine until the timing belt snapped one day. I towed the car to my brother-in-law's house (the Honda nut in the family), and he checked the valve clearences, luckily, he said nothing was damaged except the crankshaft fluctuation sensor. He said something along the lines of "it cracked". He replaced the timing belt with a GReddy piece (the sensor is just kinda hanging there) and handed it over. This is where the problems start.

The car runs ABSOUTELY fine, except it doesn't feel as fast as it used to be. It feels as if something is holding it back. My guess is it's in a safe-mode due to the sensor being cracked, IDK. I took it to Autozone to have the codes checked and it read:

P107 or P108, one of the MAP sensor codes

P0420, Catalyst System Efficiency Below Threshold (Maybe the gutted cat. is the reason )

P1336 Crankshaft Speed Fluctuation Sensor Intermittent Interruption

P1337 Crankshaft Speed Fluctuation Sensor No Signal

I figured the MAP sensor code was triggered because of the crankshaft codes.
I don't exactly have $300 laying around for a new sensor, so I searched the web and found that you can trick the computer by using the same signal as the Crankshaft Position sensor. Found it here: http://rywire.com/store/faqdes...0a1b9.
I spliced together the correct wires, and I think it worked.
The engine didn't exactly cooperate at first, it would turn over, but hessitate for about 5 seconds, almost dying, then run fine at about 1k rpm's.
I took it around town for about 10mins and hammered the throttle when I reached a dead road. The accelleration was back full blast and vtec engaged smoothly....... hicup, hicup wtf!!!
Then the engine started to miss. I babied it to another Autozone (engine was missing above 2.5k rpms) and had the codes pulled again. This time I only got one code.

P1300 Random Misfire.

I got home quickly, disconnected the splices and tried to turn over the car again. Luckily, it started right up as if nothing happened. It runs the same as it did before I spilced the wires, and no indication that it was ever misfiring. I'm guessing timing could be a culpret, but i'm out of idea's.
I'm not sure where to turn. Honda's arn't exactly my area of knowledge.
I would appreciate any advice or thoughts you guys have. TIA.

Mike

P.S. Sorry to make you guys read through my life story, I tried to shorten it as much as I could.


Modified by irmr2 at 2:38 PM 10/24/2006

irmr2

Bump with cliff notes.

JasonST

Are u still getting the random misfire code? Check ur wiring make sure each wire to the injectors are correct.

irmr2

when I disconnected the ckf from ckp, the code went away. Runs great without any missfire. Still not up to par though.

the check engine light hasn't come on since yesterday morning, and no codes are stored right now.

all I can say is OBD1 > OBD2