Jump to content
SAU Community

Recommended Posts

hi guys

my dads old car who is owned by his race car driver now just pulled a 2.22 around bathurst whish is preety quick for an rb20

it has 230rwkw and could get more with cams

just thaught i would tell yas about it and how good the rb20 is

cya guys

greg

Forgive me for being very skeptical of this time.

When was it done?

In the 1991 Tooheys 1000 on the last run for the top 10 shoot-out Mark Skaife put in a sizzling lap of 2min 12.630secs in his GTR — the fastest ever lap by a touring car at Bathurst.

I have grave doubts that something putting out 230rwkw can get anywhere close to 10secs slower over that distance.

Consider that time was top ten shootout as well. Actual fastest race lap by Skafe that year was 2min 14.50secs in the GTR.

well there was definately no full track laps on the weekend. there must have been some misunderstanding about the times.

Ray did drive well though, and came away second in class which is a great result considering its an essentially stock car with a cage....he was even running on road tyres not semi slicks or slicks.

And the car is a beautifully turned out example too :( some pics to come but I havent got around to posting them yet

well there was definately no full track laps on the weekend.  

Not unless some people snuck up there at 3am :)

And the car is a beautifully turned out example too :(  some pics to come but I havent got around to posting them yet

If its the one Im thinking of the yes it is a very nice one. :)

Thats the one:)  Clutch woes...i know the pain...a night of this has all but killed my 2,000km old clutch:

Not CLUTCH problems Roy, clutch PEDAL problems. It broke the 3 spot welds where the pedal pivot is welded to the plate that bolts to the firewall. Nothing that 10 or so cable ties couldn't fix. Finding the problem in the first place took some time though, it looked like a hydraulic leak at first glance. The clutch pedal went up and down, but the pivot fork didn't go in and out.

So I only got 2 runs on Saturday SoSK only got 3 runs, would have been much faster with 6 runs like the rest of the field. Plus I had no time to tune the set up, what it came off the trailer with was it.

Great weekend though, needed those Jacks on Saturday night to releave the back pain from lying upside down under the dash fixing the clutch pedal. That's motor racing:cheers:

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

    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...