Jump to content
SAU Community

Recommended Posts

  • 2 weeks later...

Wish you'd be there Andy.

SAU

NSW is very very grateful for MotorActive's offer of Meguiar's prizes on the day and thanks will be conveyed I'm sure by our Founder Christian or our President Ciaron.

We'll talk next week!

Kind Regards

Might come for a look in the new toy providing R33's are welcome lol. Would be rude for a skyline enthusiast not to come pay respect to the first of the rb26's. Is there something organised separately for cars other than 32's? Haven't noticed much.

I assume there will be 33 and 34 anniversary? But all cars are welcome and although the drive to gosford isn't planned or run through sau I think it will be quite a spectacular sight to see all those nice cars heading up the coast

The drive up to Gosford to Trackside isn't run or organised through Sau? Isnt that what this 'part B' of the day is about?

I'm in the Hunter Valley so was gonna maybe just head to Trackside rather than all the way to Sydney but may do both yet if I can get up early enough lol.

And yeah I assume there will be an R33 and R34 anniversary in the future but 25 years is somewhat special and a few years away yet for the 33's and 34's lol.

Correct Scott - Thanks

SAU.NSW Execs will be stretched at each end. We emphasise that regardless of whether drivers take the M1 route or Old Pacific Hwy route that road rules will be adhered to. There's no official cruise.

R32 GTRs at Trackside can have pride of place just outside the entrance and along the window outlook :)




  • Similar Content

  • Latest Posts

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • 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.
×
×
  • Create New...