Jump to content
SAU Community

R32 Gtst Missfire / Running Rough

1990R32

By 1990R32,
in General Maintenance

 Share

Recommended Posts

1990R32 Apprentice

1990R32

Posted
Posted

hey all,

Just a quick one, not sure if I'm in the right area here.

Basically i had my R32 washed and they washed the engine bay. now its running rough and missing under hard load and surging when coming on boost in 3rd.

I got home and checked the ECU codes and got code 55. so i disconnected the battery and waited a few min and re connected and all was good until i gave it a hit and it started missing at 4000 rpm then running rough and missing all the time under boost or any real driving load.

At the moment all I've done is check the injectors too see if water got into the plugs, checked fuse box, pod, afm, for water. I've also noticed that it does come and go with the missing and running rough as sometime i can drive normal for a few seconds and it plays up again.so basically I have just left it with the battery disconnected for now but is there anything else i could check?

Cheers

George

Link to comment
https://www.sau.com.au/forums/topic/460261-r32-gtst-missfire-running-rough/
Share on other sites
GTRPSI Mentor

GTRPSI

Posted
Posted

My money is on water got under the coil valley cover......

Remove coils, dry them, the whole valley, then put a smear of dielectric grease on the coil pack ends before fitting them back in to reduce any arcing from the rubber boots.

  • Like 1
Sinista32 Grand Master

Sinista32

Posted
Posted (edited)

Do as per above

Also dry the Pod,

Remove and clean the AFM with electrical contact cleaner and let it dry

Check the coil pack loom for disintegration allowing water to get into the wires

Oh and in future make sure all those areas are covered over when cleaning in the engine bay

Edited by Sinista32

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
 Share
Go to topic listing


  • Similar Content

  • Latest Posts

    • GTSBoy
      Looking for someone with a R34 front bar

      By GTSBoy · Posted

      That looks good, but I think you're going to need much beefier side skirts now.
    • GTSBoy
      Most women will agree that parking is the most taxing part of driving

      By GTSBoy · Posted

      They are daft and there's a reason it never caught on. Steering feel? We don't need no stinking steering feel!
    • GTSBoy
      new 1.5 LSD issues/concerns

      By GTSBoy · Posted

      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.
    • GTSBoy
      M35 Brake caliper replacement

      By GTSBoy · Posted

      Define "starting to fail". Wy not just rebuild them?
    • GTSBoy
      S1 rb25/s14 starting problem

      By GTSBoy · Posted

      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...