Jump to content
SAU Community

Recommended Posts

  • 2 weeks later...

Phillip Island 16-06-2013 After a wet start in the morning the day got better. Still very cold, had a lot of trouble getting heat into the tyres.

Couple of issues spun the rear yoke in the tail shaft in the 1st session. (Carbon Fibre Shaft) For some reason also pumped lots of oil out of the catch can in the same session??? Sorted itself out in the next one???

Lots of time to be had in my driving, but over all great day.

  • Like 1
  • 3 weeks later...
  • 2 months later...
  • 5 months later...

My first time at Nurburgring Nordschleife in a Suzuki Swift (www.rentracecar.com). Awesome experience.

9.30 Bridge to Gantry, more in it with more practice and a clean lap (no oil/yellow flags).

Also went for a taxi lap in the 911 Turbo S (991 shape) Ring taxi with a drive who'd done over 10,000laps. Amazing.

the track was quiet because the lap before it started raining lightly. i figured i'd go out for another lap so went straight back onto the track. aside from the oil spill and having to give way to the renault in the Foxhole it was a clean lap.

I was surprised by the little swift too! only 100kw but it has lots of grip, decent suspension and not much weight. you barely have to brake and it was really fun to drive. lacks the power on the long uphill section in keselchen but you can still carry good corner speed for most of the track. in one of my other laps i was chasing a C63 AMG, he blew away from me on the straights but i could eat him up into corners - i think he was more worried about writing it off than I was though.

LOL...awesome! Cant believe how little traffic you have. I shat myself as I left the pits in the Swift. I thought it was going to roll over on him at speed if I clipped a kerb but was actually an amazing little car!

  • 1 month later...
  • 2 months later...

quiet in here...

Took the Soarer to Mt Cotton last weekend. 48.30. 0.43sec off the Production Road Reg record - mods are exhaust, coilovers and tyres. And my final sector of that run was 0.35sec off my best time for that sector - got too sideways coming back over the crest into the RH turn just before the finish...

footage from my car - the fastest run of the weekend first then a few with little stuff ups:

footage from the side of the track including a nice slide over lover's leap:

  • 7 months later...

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