Jump to content
SAU Community

Recommended Posts

Hello everyone. I am wrapping up the last bit of my suspension build. I am looking for recommendations for alignment specs to start with. I have an appointment in the middle of march to get an alignment and corner balance done by a shop at the Nurburgring. I've been reading through some of the past threads and have a general idea of what I should do, but want to confirm that I am going the right direction with my setup. My current setup is:

MCA Red series coilovers (11kg front, 7kg rear)

Factory sway bars

SPL castor rods, outer tie rods, front sway bar end links, rear upper control arms, traction rods, subframe bushings, and spherical knuckle bearings

GK tech front upper control arms

Superpro rear lower control arm bushings, rear sway bar end links bushings, front and rear sway bar mount bushings. 

Full Race ETS Pro 

Dunlop Dirreza ZIII (265/35R18) 200TW

From what I can tell I should start with

355mm front 345mm rear ride height

6 degrees castor front 

-3.25 degrees camber front

2mm total toe out front

-1.5 degrees camber rear

1mm total toe in rear

Any input would be appreciated. Thank you in advance 

 

20180929_155839.jpg

Link to comment
https://www.sau.com.au/forums/topic/476033-r32-gtr-fast-roadtrack-alignment/
Share on other sites

I would use zero toe at the rear, especially if you have solid ends on the arms.  I would also use slightly less toe in on the front.  -1 total, or even zero, especially if you have solid ends on the castor arms.  Your front camber target will be ace for fast corners, but will eat tyres on normal street driving.  Good for the 'ring but.

Tyre pressures are the big unknown here.  I would start with 38psi and consider going higher for a fast track.

The other big unknown is the suspension settings.  You will need to work out where to set the dampers to work with those springs and whatever tyre pressures you might end up with (assuming that you have an IR pyrometer and work out from tyre temps that you need different front to rear).

Thanks for the reply. From my reading, I'm under the impression that toe is more of a factor than camber, when it comes to tire wear. Also from reviewing Sydneykid's posts, seems like toe out is desired on the front for better turn in. If your want stability under braking a little toe in is needed, but some toe out will help the back end come around better. Not looking for a track spacific setup, but a reasonable compromise for carving up mountain roads and doing some non competition track time. Still need to figure out tire temps once I hit the track.

Everything Sydneykid has to say is essentially correct and well considered.  But it is mostly aimed at Skylines without suspension arms that remove all the bush compliance.

Toe in = stable, toe out = active (and therefore, effectively, unstable).  So, yes, toe out is recommended for enhancing turn in.  But at very high speeds that lack of stability can make the car very difficult to drive.  Better to start a little more conservative and adjust the alignment after discovering how it drives with something less likely to kill you.

Now, the other thing about toe-in & out is that stock suspensions have plenty of movement in them from all the squidgy bushes.  What that means is that when the car is moving forward, there is a load pushing the wheels backward, relative to the body.  If there is compliance in the bushes then the general response is for the toe-in to decrease.  So let's start at the rear.  If you set -1mm of toe-in at the rear and that decreases, you will actually end up with zero toe, or possibly even toe-out when the suspension gives.  If you have really stiff bushes or steel rod ends, then there is less deflection and you don't get the same effect.  Better to reduce the static toe-in to zero, to get the wheels pointing where you would want them to be from the start.  The aim of stock alignments on stock bushes is to get close to zero toe while under way.

Toe out at the back can make the car incredibly kill-deathy.  Depending on spring rates, ARB stiffness, damper settings and road bumpiness, it can make it super willing to rotate, sending you off into the furniture at high speed.  Again, better to start slightly conservative.

At the front, it's the same story.  Stock alignments are toe-in, compliance pushes that out to zero-ish.  With less compliance, set zero to get zero, or slightly positive when moving.

Neg camber = inside edge wear.

Toe out = inside edge wear.

Therefore Neg camber + toe out = much faster inside edge wear.  Usually, to even out tyre wear, alignment shops will use toe-in with neg camber to push the wear across the whole face of the tyre.  But if you want aggressive cornering turn-in and grip, you don't want the toe-in, so you have to accept the wear.

 

  • Like 1

I ran 3deg neg camber on the track and it was great - definitely faster through the corners. Having easily adjustable arms the theory was to return to neg 1 for the road but since you effectively need a full alignment with each change it didn't happen. So it was cr*p on the road - skittish and chewing out tyres. If you can manage a lot of track time in a short period it might be worth doing but otherwise best to go with a street friendly set up.

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

    • First up, I wouldn't use PID straight up for boost control. There's also other control techniques that can be implemented. And as I said, and you keep missing the point. It's not the ONE thing, it's the wrapping it up together with everything else in the one system that starts to unravel the problem. It's why there are people who can work in a certain field as a generalist, IE a IT person, and then there are specialists. IE, an SQL database specialist. Sure the IT person can build and run a database, and it'll work, however theyll likely never be as good as a specialist.   So, as said, it's not as simple as you're thinking. And yes, there's a limit to the number of everything's in MCUs, and they run out far to freaking fast when you're designing a complex system, which means you have to make compromises. Add to that, you'll have a limited team working on it, so fixing / tweaking some features means some features are a higher priority than others. Add to that, someone might fix a problem around a certain unrelated feature, and that change due to other complexities in the system design, can now cause a new, unforseen bug in something else.   The whole thing is, as said, sometimes split systems can work as good, and if not better. Plus when there's no need to spend $4k on an all in one solution, to meet the needs of a $200 system, maybe don't just spout off things others have said / you've read. There's a lot of misinformation on the internet, including in translated service manuals, and data sheets. Going and doing, so that you know, is better than stating something you read. Stating something that has been read, is about as useful as an engineering graduate, as all they know is what they've read. And trust me, nearly every engineering graduate is useless in the real world. And add to that, if you don't know this stuff, and just have an opinion, maybe accept what people with experience are telling you as information, and don't keep reciting the exact same thing over and over in response.
    • How complicated is PID boost control? To me it really doesn't seem that difficult. I'm not disputing the core assertion (specialization can be better than general purpose solutions), I'm just saying we're 30+ years removed from the days when transistor budgets were in the thousands and we had to hem and haw about whether there's enough ECC DRAM or enough clock cycles or the interrupt handler can respond fast enough to handle another task. I really struggle to see how a Greddy Profec or an HKS EVC7 or whatever else is somehow a far superior solution to what you get in a Haltech Nexus/Elite ECU. I don't see OEMs spending time on dedicated boost control modules in any car I've ever touched. Is there value to separating out a motor controller or engine controller vs an infotainment module? Of course, those are two completely different tasks with highly divergent requirements. The reason why I cite data sheets, service manuals, etc is because as you have clearly suggested I don't know what I'm doing, can't learn how to do anything correctly, and have never actually done anything myself. So when I do offer advice to people I like to use sources that are not just based off of taking my word for it and can be independently verified by others so it's not just my misinterpretation of a primary source.
    • That's awesome, well done! Love all these older Datsun / Nissans so rare now
    • As I said, there's trade offs to jamming EVERYTHING in. Timing, resources etc, being the huge ones. Calling out the factory ECU has nothing to do with it, as it doesn't do any form of fancy boost control. It's all open loop boost control. You mention the Haltech Nexus, that's effectively two separate devices jammed into one box. What you quote about it, is proof for that. So now you've lost flexibility as a product too...   A product designed to do one thing really well, will always beat other products doing multiple things. Also, I wouldn't knock COTS stuff, you'd be surprised how many things are using it, that you're probably totally in love with As for the SpaceX comment that we're working directly with them, it's about the type of stuff we're doing. We're doing design work, and breaking world firsts. If you can't understand that I have real world hands on experience, including in very modern tech, and actually understand this stuff, then to avoid useless debates where you just won't accept fact and experience, from here on, it seems you'd be be happy I (and possibly anyone with knowledge really) not reply to your questions, or input, no matter how much help you could be given to help you, or let you learn. It seems you're happy reading your data sheets, factory service manuals, and only want people to reinforce your thoughts and points of view. 
    • I don't really understand because clearly it's possible. The factory ECU is running on like a 4 MHz 16-bit processor. Modern GDI ECUs have like 200 MHz superscalar cores with floating point units too. The Haltech Nexus has two 240 MHz CPU cores. The Elite 2500 is a single 80 MHz core. Surely 20x the compute means adding some PID boost control logic isn't that complicated. I'm not saying clock speed is everything, but the requirements to add boost control to a port injection 6 cylinder ECU are really not that difficult. More I/O, more interrupt handlers, more working memory, etc isn't that crazy to figure out. SpaceX if anything shows just how far you can get arguably doing things the "wrong" way, ie x86 COTS running C++ on Linux. That is about as far away from the "correct" architecture as it gets for a real time system, but it works anyways. 
×
×
  • Create New...