Jump to content
SAU Community

Recommended Posts

Smokey, Misfire (valve stem seals maybe)

I have a rebuilt rb30 bottom end with new rings and bearings. New standard head gasket and an rb25det head.

I have got a misfire from idle and it struggles as you accelerate gently (wideband reads lean as expected due to misfire).

My crankcase breather is just venting to air at the moment with very little smoke at idle, but if I kink this pipe I get excessive smoke from the exhaust on deceleration. It still smokes a bit a idle from the exhaust.

The smoke is more white than anything, but has a slight smell of oil.

I have done the usual search and come to the conclusion its the valve stem seals.

Am I right?

Can bad valve stem seals cause a misfire?

P.s. I have wasted spark running perfectly, fuel pressure and injectors are ok, afm is ok.

Link to comment
https://www.sau.com.au/forums/topic/299729-smoke-on-overrun/
Share on other sites

connect your crankcase breather asap to see if it stops it THEN see if you still have a problem THEN we can start ruling things out. common sense would tell you to connect anything thats supposed to be connected to see if its causing the problem, and i dont mean blocking it off... connect it as standard.

its happened before - dysfunctional PCV has caused an oil problem on other cars including my own. start from there.

Edited by SECURITY

SECURITY saved my life with the same situation!

Stock RB25, catch can setup with blocked PCV, would smoke just after start up when i took off from lights, and came to a stop.

Reconnected PCV, never seen another whiff :D

Defiantly never blocking the PCV again.

Im running msd coils in wasted spark mode. Cas has been replaced. Plugs at 0.8.

Misfire happens from startup most of the way up the rev range have not taken the revs over 4000rpm as mototr has only been built and not mapped yet.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Similar Content

  • Latest Posts

    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...