Jump to content
SAU Community

Recommended Posts

I'm after a pair of good tyres in the next week to start getting the R32 on the road. Probably going to get Falken RT215's, but any other suggestions welcome.. Only need R16's so shouldn't be easier on the wallet. Budget is about $400

I've heard Brannigans are pretty good down here, are they good on prices as well?

Any other suggestions? or should I just pickup the yellowpages :D

cheers peepz..

Link to comment
https://www.sau.com.au/forums/topic/58797-need-some-decent-tyres-goldcoast/
Share on other sites

Branigans are the option you take when you have 50 bux to your name and wire poking out of your tyres... Cheap and nasty... Good service though...

Avoid F1 at all costs...

I found BBS to be good in the past, but they forgot to mention to me that they had moved last time I booked the car in, so my business went elsewhere...

Federals are underrated IMO...

Have you tried using the club sponsor Bob janes

Be interesting what prices you get compared to other tyre shops

Put them to the test!!

Let us all know the results.

Do not bother with the Federals unless you want cheap

I have tried both 235/40/18 and 245/40/18

Do not have very good grip

I Have some very worn out doggy 255/45/17 Nankang on the rear now, and they have ALOT better grip then the Federal ever had

Both are cheap tyres

I am going to try the Falken st112 next or something pretty soft

I am sick lighting up the back every time I go to the local shop!

thanks so much guys..

jax or action tyres sound great and they're close as anything, would prefer somebody who knows turbo cars.. and doesn't try and just sell me whatever they'd stick on the nearest commodore. I will probably go down to them today.

I'll probably check out bob jane too.. although I'm not a member :Oops:

Had dodgy tyres on the R33 and I hated it near the end, I want some pretty good ones this time - especially seeing as this car is not going to be daily driven..

May as well do something useful..

Here are the contact details of all these places:

Austyre N' Wheel

447 Nerang-Southport Rd Ashmore QLD 4214

ph: (07) 5597 0099 Wheel Alignment & Balancing

Action Tyre Service

12 Price St Southport QLD 4215

ph: (07) 5532 4599 Tyres--Retail

Southport - Bob Jane T-Marts

168 Gold Coast Hwy

Southport QLD 4215

Australia

ph: (07) 55912655

JAX Tyres Brakes & Suspension

Take Advantage Of Our "No Hassle Guarantee"

Unit 3/ 45 Nind St Southport QLD 4215

ph: (07) 5503 1233 Tyres--Retail

Coomera Tyre World

172 Siganto Drv Oxenford QLD 4210

ph: (07) 5502 9100 Tyres--Retail

Branigans Budget Tyres

Shed 5/ 41 Egerton St Southport QLD 4215

ph: (07) 5571 1366 Tyres--Retail

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

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