Jump to content
SAU Community

R32 Gtst-4 Front Axle(?) Removal

s213b

By s213b,
in General Maintenance

 Share

Recommended Posts

s213b Rising Star

s213b

Posted
Posted

Hi,

I'm 3/4 of the way through the removal of my rb20 from my 89 r32 gtst4, have gearbox out (rb20 awd box's same as r32 gtr box's??) and have gotten up to removing the front hub/axle (front right wheel off, I need to get the big central hub but off) but have hit a few snags.

1) does anyone know what size that nut is? Is it 36mm? (my sockets go up to 19.... Great

2) gear box is out, brake booster disconnected etc, can't stop the wheel rotating when I try to undo the big nut with an adj spanner + huge flat blade between wheel studs.

The nut seems to be corroded on and f*cking tight, help?

I'm now driving an extremely troubled Daihatsu charade so this is pretty urgent. :D

Cheers

Link to comment
https://www.sau.com.au/forums/topic/391512-r32-gtst-4-front-axle-removal/
Share on other sites
s213b Rising Star

s213b

Posted
  • Author
Posted

I think it might be 27...

I was using a socket (imperial... Haha) and a penetrant and a 3 foot breaker bar and it was bending the jack pole in between the wheel studs (had it there to stop wheel spinning)

I'll have a go with a metric socket today ;)

bigjiz Collaborator

bigjiz

Posted
Posted

If ur trying to get the drive shaft out u dont need to take hub off u undo the tierod end, the two nuts under the hub (thinks its the lower control arm) and the carster r od just the two bolts u dont have to the front bolts and get a plie bar and pop the caster rod off and u should be able to lift the hub up and the drive shaft Will just come out with it

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