eallanboggs

iTrader: (1)

My SES went out on its' own the other day. This was the RANDOM MISFIRE DTC that got set after I install a new cam with a 112 LSA. I thought my luck was running so good I even considered playing the POWERBALL, but today after the engine burped the SES came back on. I'm sure it's P0300 again even though I havn't checked it with AUTOTAP as yet. I'm willing to bet if it doesn't have a REAL misfire anytime soon the MIL will go out again on its' own. If it doesn't go out I guess it's time to contact Carputing?

1320_PERFORMANCE

Just like mines, it goes on/off when it wants too. I hooked it up to gm's tech 2 scanner and check out my misfire tables and it only misfires @ idle, when i rev the z up past 2k misfire table clears and reads zero. It doesnt bother me as long as i noe it doesnt have a real missfire.

gillbot

iTrader: (27)

Mine used to do the same thing with the P0300 code until lately. Now I've been getting a MAP sensor code instead.

EFILive

iTrader: (2)

Any chance you disturbed the crank position sensor?
More info here: http://www.seattleautomotive.com/ckpdoc.htm
You may just need a CKP relearn.
Takes about 30 seconds to do.
Paul

67SS509

iTrader: (25)

Can this relearn procedure be accomplished with AutoTap?

EFILive

iTrader: (2)

No, but a Tech2 or EFILive Pro (with bidirectional controls) can do it.
Paul

gillbot

iTrader: (27)

The P0300 is a common code that happens frequently on cammed cars. I believe it has more to do with the choppy idle of the lower LSA of aftermarket cams but anything is possible.

DaveSchott

iTrader: (5)

On some cars this could be the case. Mine did it after a sloppy mechanic cross-thread installed my #8 plug. misfires cleared up with some throttle. When changing the plugs a year later, found the problem, re-threaded the plug hole, and as a bonus no more misfires!

lesson learned: little things in the ignition, like partially seated wires or screwed up plugs can cause the condition. maybe not the only causes, but possible causes.