Jump to content
SAU Community

Recommended Posts

A R33 25 should beat the R32 GTS off the mark thats assuming both are stock.

There is a bit of difference in performance, manual tends to be a bit quicker, although the auto tends to have more top end speed.

I have raced my R33 GTS25 both auto and manual, I managed a 16.4 pass over the 1/4 when auto, and after the conversion I ran a 16.0 ET. I have found the manual to be quicker off the mark, and trough the rev range, but have to watch for alot more wheel spin.

Also the manual tends to have a few more kw at the rear wheels, than it's auto counterpart. We gained 16rwkw when we did the conversion.

Link to comment
https://www.sau.com.au/forums/topic/28142-32-or-33/page/2/#findComment-587443
Share on other sites

I prefer the R33 because it looks cooler, to me anyway. I find the 32's quite old now and even earlier S1 33's too. I have a S2 96 model GTS-t and I chose it because I loved the 33's rear end, and the front end was much more aggresive than the more rounded Series 1 front end. I never liked the look of the 34's when I first saw them, but now they have grown on me. But, my favourite is the R33 S2. I am not talking anything about performance etc, modded, just 100% stock factory models.

R32 Gts-t

R33 Gts-t

R34 Gtt

Thanks. Anyone else prefer Series 2 over Series 1.

Link to comment
https://www.sau.com.au/forums/topic/28142-32-or-33/page/2/#findComment-588340
Share on other sites

OK, auto goes ok, but i will look at a conversion in the future.

Overdrive is a option on the stick there is a button which gives you the top gear, with out it for example on a high way your 100km cruising speed will be at about 1000more rpm 3000 rather than 2000.

Two modes, snow and power. Snow limits your changes to a max of 4000rpm and most often less, and you start of in second gear (ie very slugish when tackling round aobuts)

Power mode allows the car to rev out to red line, and if you have it in normal and realy put the foot down quick it automaticly pops into power mode for you.

I picked my car up for $9400, in perfect condition, with 12months redgo. It was absolutely stock, factory radio etc etc, bar some 17" wheels. It had 69800kms when i got it, it was a total bargain, and beleive the fella who sold it to me realy underpriced the car, its only downside was the auto box. But it had the 2.5ltr engine so i thought that was a good compromise.

Hope that helps.

Ps i manual change the auto box quite alot and it seems to of been built for this coz it allows you to do it freely, with a simple push/pull it jumps into place with no worries, i use it for slowing down mostly then when stopped put it back into drive, coz the box changes for optimum performance on its own.

Link to comment
https://www.sau.com.au/forums/topic/28142-32-or-33/page/2/#findComment-589061
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


  • Latest Posts

    • 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. 
    • Holy hell! That is absolutely stunning! Great work!!!
    • It does when you start adding everything else in. But it's not just compute. It's the logic. Getting your timing right (I'm not meaning ignition timing for the engine). Making sure of your memory mappings, seeing your interrupts. Microcontroller devices only have so much capacity. For the most part, you want all those timers and interrupts in use on your engine control, which means you're left with less than ideal methods for timing and management of other control functions.   Let's put it this way, my job is all about building custom hardware, that goes into cars, and integrates with them. We're also waiting on a media confirmation from SpaceX too fora world first we've just completed with them in NZ too. It's not just the little toys I play with. But you know, you can think and believe what you want.
    • I don't think it's a good buy, the trend looks bad     lol.
×
×
  • Create New...