Jump to content
SAU Community

Dolphin Ride Height

bentwagon

By bentwagon,
in Four Door Family & Wagoneers

 Share

Recommended Posts

bentwagon Experienced

bentwagon

Posted
Posted

Looking at getting a Stagea which has a Dolphin Aeroform kit and would like to compare ride heights with others as this one seems quite low. Ride heights are - Front and Rear 355mm from wheel centre to top of wheel arch. Would be interested in hearing what other people have and if they have found any problems with their heights. My main concern is I hit the gravel often as a spectator for local Rally events.

Cheers

Link to comment
https://www.sau.com.au/forums/topic/337764-dolphin-ride-height/
Share on other sites
SMOKEYV35 Mentor

SMOKEYV35

Posted
Posted (edited)

yer, they really are a low kit, i considered one and in the end decided against it. i have persisted with driving super low cars for the past 6-7 years - my last two cars having around 60mm at the cat - and it just makes the car so impractical. it was fine when i was younger, at uni, and drove a lot less frequently and often had a lot more spare time to get places, but driving daily and often in a hurry, it was just a PITA in the end.

and with the dolphin kit, they're so blunt, that if you do manage to catch a corner coming out a drive way i'd say you'd do some damage. and i see you're in adelaide - aren't they infamous for kit wrecking spoon drains??

i also reckon its hard to get the dolphin kit looking its best without a low ride height, which is a bit of a catch 22 if you want to maintain practicality - which for your dirt road stuff is obviously an issue. maybe look for a stock one, or one with a dayz kit which are a fair bit less aggressive.

which car are you looking at? is it iron chef's car?

Edited by SMOKEYC34
KiwiRS4T Grand Master

KiwiRS4T

Posted
Posted

Those ride heights are not low. Mine is at 340/350 and doesn't look particularly low -but i have no body kit at all. From a legal point of view body kits don't count but from a practical point of view if you are going damage it all the time on driveways or parking buildings etc then its probably not the right one.

SMOKEYV35 Mentor

SMOKEYV35

Posted
Posted

ah yep, cool.

i considered that car myself. there are a few references to it in this thread.

http://www.skylinesaustralia.com/forums/Vi...ea-t334058.html

i have the auction grade sheet for it if you want, pm me your email and i'll send it to you. the auction sheet shows it as being in very good condition with only minor cosmetic scratches - however, someone who inspected the car in adelaide posted in my thread said that in real life this is not the case. in the end i decided that it wasn't worth paying the premium price for the colour alone as the car is fairly stock standard otherwise, and i wasn't convinced on the kit due to how much i'd have to lower the car to get it looking right - maybe its just the rims but it looks a bit strange to me at that height with such a deep kit. also, fact i was in melbourne and would have had to buy the car sight unseen was a risk i wasn't willing to take. then there was all this time pressure being put on me about someone else having made an offer to pay in installments so i'd need to make a quick decision etc etc, and in the end i just decided to leave it alone.

but dont let any of that stop you! if you're in adelaide go check it out and you can decide for yourself. just connecting some dots for you ;-)

SMOKEYV35 Mentor

SMOKEYV35

Posted
Posted

says the man with the busted front bar :( hahah, just stirring.

yeh any car is driveable at any height if you're prepared to be ultra careful and make sacrifices bout where you drive and how fast.

my ls400 used to smash upper control arms on a daily basis and level speed humps with the exhaust - it looked tough as balls, but you get over it quickly....

Bronx Mentor

Bronx

Posted
Posted

i got same kit, and im on stock height, and its bad enough as is, driveways in this country were designed for the 4wd's.

ive got a heap of chips and cracks all throughout my bumper. cost me 400 bucks for a fix and paint. so if you do get one, be prepared to pay n fix it.

but its a damn sexy kit for sure.

  • 3 weeks later...
bentwagon Experienced

bentwagon

Posted
  • Author
Posted

OK, so I have bought the Stag, and yes I think the clearance at the front bar will be bearable for normal driving, but I would be confident with more clearance. Measured up the height of the bar and it is 420mm from base to fender, as shown in the pic. What I am wondering is what the height of a DAYZ bar would be?

Anyone keen to measure for me?

post-72216-1286764052_thumb.jpg

M I K E Mentor

M I K E

Posted
Posted

there is already a thread started on this if you search this section

can't remember the username but i know that it had measurements for exactly what you are after

be prepared to pay a bit of money for a dayz bar too :D

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
      Help Understand GTT Boost Setup

      By GTSBoy · Posted

      Nah. For something like boost control I wouldn't start my design with PID. I'd go with something that originates in the fuzzy logic world and use an emergency function or similar concept. PID can and does work, but at its fundamental level it is not suited to quick action. I'd be reasonably sure that the Profecs et al all transitioned to a fuzzy algorithm back in the 90s. Keep in mind also that where and when I have previously talked about using a Profec, I'm usually talking about only doing an open loop system anyway. All this talk of PID and other algorithms only comes into play when you're talking closed loop boost control, and in the context of what the OP needs and wants, we're probably actually in the realm of open loop anyway. Closed loop boost control has always bothered me, because if you sense the process value (ie the boost measurement that you want to control) in the plenum (after the throttle), then boost control to achieve a target is only desirable at WOT. When you are not WOT, you do not want the the boost to be as high as it can be (ie 100% of target). That's why you do not have the throttle at WO. You're attempting to not go as fast as you can. If the process variable is measured upstream of the throttle (ie in an RB26 plenum, or the cold side pipework in others) then yeah, sure, run the boost controller closed loop to hit a target boost there, and then the throttle does what it is supposed to do. Just for utter clarity.... an old Profec B Spec II (or whatever it is called, and I've got one, and I never look at it, so I can't remember!) and similar might have a MAP sensor, and it might show you the actual boost in the plenum (when the MAP sensor is connected to the plenum) but it does not use that value to decide what it is doing to control the boost, except to control the gating effect (where it stops holding the gate closed on the boost ramp). It's not closed loop at all. Once the gate is released, it's just the solenoid flailing away at whatever duty cycle was configured when it was set up. I'm sure that there are many people who do not understand the above points and wonder wtf is going on.  
    • joshuaho96
      Help Understand GTT Boost Setup

      By joshuaho96 · Posted

      This has clearly gone off on quite a tangent but the suggestion was "go standalone because you probably aren't going to stop at just exhaust + a mild tune and manual boost controller", not "buy a standalone purely for a boost controller". If the scope does in fact stop creeping at an EBC then sure, buy an EVC7 or Profec or whatever else people like to run and stop there. And I have yet to see any kind of aftermarket boost control that is more complicated than a PID controller with some accounting for edge cases. Control system theory is an incredibly vast field yet somehow we always end up back at some variant of a PID controller, maybe with some work done to linearize things. I have done quite a lot, but I don't care to indulge in those pissing matches, hence posting primary sources. I deal with people quite frequently that scream and shout about how their opinion matters more because they've shipped more x or y, it doesn't change the reality of the data they're trying to disagree with. Arguing that the source material is wrong is an entirely separate point and while my experience obviously doesn't matter here I've rarely seen factory service manuals be incorrect about something. It's not some random poorly documented internal software tool that is constantly being patched to barely work. It's also not that hard to just read the Japanese and double check translations either. Especially in automotive parts most of it is loanwords anyways.
    • Duncan
      R33 disk brake size

      By Duncan · Posted

      If you are keeping the current calipers you need to keep the current disc as the spacing of the caliper determines the disc diameter. Have you trial fitted the GTS brakes fit on a GTSt hub or is this forward planning? There could be differences in caliper mount spacing, backing plate and even hub shape that could cause an issue.
    • Godzillaskizza
      R33 disk brake size

      By Godzillaskizza · Posted

      Hi there I have a r33 gts with 4 stud small brakes, I'm going to convert to 5 stud but keep the small brakes, what size rotor would I need?
    • MBS206
      Help Understand GTT Boost Setup

      By MBS206 · Posted

      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.
×
×
  • Create New...