Jump to content
SAU Community

Starter Motor Problem Rb30/rb26

leeroy_25
 Share

Recommended Posts

leeroy_25 Community Regular

leeroy_25

Posted
Posted

Hoping someone can give me some help here that is not bad news! I tried to turn over my RB26/RB30 today to find there seems to be a problem with the starter motor. I bought the car with a seized RB26 and replaced it with and RB30/RB26 motor. The motor all turns over fine so that's not a problem. I fitted a Nismo twin plate clutch to it. Which I got second hand.

Basically the starter throws out and then starts chattering as if you have a flat battery. So I pulled the starter out and gave it a clean put some WD40 in it and spun it over on a battery and it seems fine?

Put it back in and same thing. Throws out and starts to chatter. Just to make sure the flywheel was not in a funny position I put the car in gear and rocked it. Doing so I noticed the sound of the starter motor disengaging from the ring gear. Every time you fire it out it appears to stick. Rock the car and it drops out again.

Can someone shed any light on this. Is there any way I have been sold a flywheel that has a different ring gear or spacing? Did I need to space the flywheel out or something that I missed? Damaged teeth on the starter? Or just a dudd starter motor under load?

Just for reference I have no battery in the boot and I am jumping off a battery to the front terminals.

Thank you

Lee

Link to comment
https://www.sau.com.au/forums/topic/323004-starter-motor-problem-rb30rb26/
Share on other sites

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