Jump to content
SAU Community

Recommended Posts

Guys,

If you feel the need. The need for...... :D

PAIRC is hosting an event on the weekend of Sept 24/25.

Sup Req's here:

http://www.piarc.com.au/files//PIARCSeptem...Supp%20Regs.pdf

Saturday is non-timed practise. I expect you to get HEAPS of track time since its Grand Final Day.

Sunday is full noise sprints.

Link to comment
https://www.sau.com.au/forums/topic/86258-piarc-sept-2425/
Share on other sites

  • 2 weeks later...

G'day Andrew....

I'm moving back to Adelaide shortly, and would love to take the drive in the GT-R to Vic and PI sometime later in the year, or early new year....

is there anything coming up (SAU) that would be worth putting in the diary?

cheers!

Ben

Link to comment
https://www.sau.com.au/forums/topic/86258-piarc-sept-2425/#findComment-1582426
Share on other sites

Hey Ben - pretty much after Oct 23 (Maserati Dat @ Sandown) the racing calander comes to an end for the year and nothing much is on until the new season starts Feb 2006.

Be great to see your car down here though one day!

Link to comment
https://www.sau.com.au/forums/topic/86258-piarc-sept-2425/#findComment-1582506
Share on other sites

Ben,

Vic seems to run a little different to NSW. Winton has a practise day most Fridays and Calder most Wed but none of us really attended them because Calders practise days have dumb requirements (full race suit etc) and Winton is miles away.

Sandown doesnt have any practise days available and Phillip Island only has them Available on the Saturday of these PIARC weekends of which this is the last one for the year.

As a rule track days for us revolved around WRX Club sprints - which do offer "driver training - which is a non timed session with an instructor" or we tend to also attend PIARC as its the best track in Oz and Merserati Club events (which there is only 2 a year @ Sandown).

So really as I mentioned the Vic GTR's will be out:

Sept 24/25 for PIARC @ Phillip Island

Oct 8th for WRX Club @ Calder

Oct 23rd for Maserati @ Sandown

And that will be it until Feb next year I expect.

Oh - except for DECA Shepparton on Sat Novemeber 19th - but thats a motokhana event.

Cheers

Link to comment
https://www.sau.com.au/forums/topic/86258-piarc-sept-2425/#findComment-1582699
Share on other sites

No accom from Mav so this is just a drivers / bike riders weekend.

So far just me, Scotsman, Frank and Nige are entered for the Sunday I think.

Yeh im a no show. Will be doing the ride thing then getting back Saturday so i can catch up with my brother for his birthday on Sunday. :D

Link to comment
https://www.sau.com.au/forums/topic/86258-piarc-sept-2425/#findComment-1599830
Share on other sites

Guest
This topic is now closed to further replies.


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