Jump to content
SAU Community

Recommended Posts

My 32 has developed a weird missfire latley and i'm buggered if i know what is causing it. The car drives normally for about 20 minutes, then a slight miss appears under boost and it get worse and worse until the car is almost undrivable, even idle is awful.

The strange thing is if you leave it for a while, then drive it again, it drives normally for 20 minutes and then the miss comes back just as it did before.

Now if it was a coil pack or a plug you would think the miss would be there all the time but it only shows up after driving for a while, starts small and get worse and worse.

I'm going to pull the plugs out and check em and the coil packs aswell this weekend but if anyone had any other ideas i'd appreciate it.

Cheers

Link to comment
https://www.sau.com.au/forums/topic/107868-strange-missfire-issue/
Share on other sites

i doubt whether its your coils. You mite wanna get a compression test and a leak down test to make your its not your cylinders. I had a similar problem with missing and what not and i am in the process of a full engine rebuild at the moment. Not saying im right....might be worth a check tho to save yourself chasing your tail.

Regards

Hey hey,

Had a similar prob, but was only misfiring and losing power at high rev's and high boost.

But yes, it was the coil packs that were causing the problem. I ended getting a set of Splitfires that fixed the problem. Also tried perrmatex hi-temp gasket silicone to seal the coils, that worked except when running max boost(you just feel the misfire)

Any anywho have a read here.

Hope it helps,

Brad

Sounds like mine... :huh: will be watching this thread. Should keep each other up to date if either fixes the problem :P

Mine after 10-15 mins is shuddering a bit and sounds like the timing is waaaay out... Sound familier?

Oh and I've just serviced my coil packs and the're all in ecell nic.. Have'nt tested them though.

http://www.skylinesaustralia.com/forums/in...howtopic=107286

Edited by Drift_Limo

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

    • That looks good, but I think you're going to need much beefier side skirts now.
    • They are daft and there's a reason it never caught on. Steering feel? We don't need no stinking steering feel!
    • I gotta pull you up on this. It's driving me crazy. A shutter is something that closes, like over a window or in a cmera. The word you want is shudder. That LSD is clearly f**ked. Take it to a diff shop and get it disassembled and examined by an expert. YOu might have plates welded together or something equally crazy.
    • Define "starting to fail". Wy not just rebuild them?
    • Check the Nistune doco. There are a few assumptions being made here that might not be valid. I will list the things that occur to me: Base map. Base map for what? Base map for Z32? Then the cranking pulse width is probably wrong for an RB25. The extra 500cc of capacity might well be enough to prevent it from catching. Base map for RB25? I don't think you can load one of those into a Z32. You have to just make the settings correct for an RB25 in the Z32 base map. That is either K or the TIM to get the pulsewidth right. Loom. You bought a loom for an RB. And you plugged it into a Z32 ECU. Did you make sure that any iwre differences were swapped. From memory, there's at least a couple. And as per the others, I would suggest making sure that the fuel pressure is correct while cranking and that the injectors are actually flowing as expected. They really must come out and go on the bench, unless you do find that you have messed up as per above points. I would also suggest watching in Nistune to make sure that everything is reading correctly. That the correct binary flags are raised at the right time (like the crank signal), that there's no stupid values in K or TIM. That you have not got mismatched firmware for the ECU and/or a wrong image loaded.
×
×
  • Create New...