Jump to content
SAU Community

Recommended Posts

black 34gtt followed me up camron ave then right onto eastern valley way, then left up college street then left onto hayden drive. the driver then gave it a bit when he passed me.. sounded nice. this would have been between 530 and 540 this afternoon

Link to comment
https://www.sau.com.au/forums/topic/30059-spotted/page/574/#findComment-4764230
Share on other sites

Spotted bayside blue GTR in deakin and a white 34 GTT woden, lunch time today. Also spotted a white 33 with black bonnet at lanyon this evening around 9ish...

Oh and I almost forgot, spotted a silver r35 this morning near the canberra hospital (almost made me crash into the car infront of me, I WANT ONE!!!!!!!!!!!!!!!!!!!!)

Edited by dinero
Link to comment
https://www.sau.com.au/forums/topic/30059-spotted/page/574/#findComment-4764879
Share on other sites

spotted a black R32 with black or dark rims on erindale dr going through the sulwood roundabout around 8pm, a white R33 turning from drakeford onto erindale drabout 9.30, then some f*ckwit in another white R33 with nsw plates almost took me out doing easily 130-140kmh on drakeford a minute or two later, then another white R33 on isabella a couple of minutes later.

Link to comment
https://www.sau.com.au/forums/topic/30059-spotted/page/574/#findComment-4768617
Share on other sites

If anyone on here with a white 33 was driving through Calwell at about 6:30 tonight, you'd better check your tailights.

The one that cruised by my place had all hotplates off......

Had me worried then John. Would have been going past at that exact time myself only to realise that I was in the parents Hyundai instead :)

Actually spotted you going past work earlier this week, but again, I was in the Hyundai.

Link to comment
https://www.sau.com.au/forums/topic/30059-spotted/page/574/#findComment-4770386
Share on other sites

FRIDAY:

white 33 GTR at the meet.. sorry mate, no idea who you were

SATURDAY:

black 33 on college street belco at around 230-245

white 33 on nettlefold then right onto lathlain street belco at around 230-245

white 33 that may have been a GTR on point hut road (in a car park near the bridge) around 345-415

SUNDAY:

silver 32 cutting mad sick at the motorkhana

millenium jade R34 GTR V-SpecII Nur at the motorkhana.. there is almost nothing better looking

Edited by Ex!$t3nZ
Link to comment
https://www.sau.com.au/forums/topic/30059-spotted/page/574/#findComment-4771583
Share on other sites

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