Jump to content
SAU Community

Recommended Posts

Silver C34 on Talavera Rd in Macquarie Park, about 30 seconds ago. Looking out the window at work.

Careful, the police have hitting this area really hard lately because it's a 50km/h zone.:whistling:

spotted a Black M35 on Bronze wheels (possible TE37's) crossing grand junction rd from bridge rd onto hampstead rd around 1.30pm, then a white S1 on main north rd turn right with u onto there, nd then u held me up because the falcon slowed down as u did to change lanes about 5-10 min later. nd wat looked to have been the same M35 or a similar one driving on hampstead rd heading towards grand junction rd again around 2.20pm.

Black M35 at Davoren Park On The Run this morning. Black Volk copies on the rear, silver WedSports on the front.

Anyone on here?

That would be my partners car

There hanbai m2 dt 05rs on the rear ( the wheels drift techs copied)

And yup a full kenstyle kit,

Now sitting on 18x9+20 o1g wheels

With some new bc coilovers

lol yea i was taking the kids home. nd thanks. yea ill hopefully get it resprayed soon. get the door rust fixed at the same time. still unsure of wat colour to go. nd then fix up my fog light. only cleaned headlights a few days ago as well. they were yellow.

just spotted at around 1.45pm: yellow s2 with large rims at Mudgeeraba Village, turned up Somerset Drive. I was a few cars behind, and not in my stag, so didn't get the opportunity to acknowledge...

4 days in Canberra, Thu arvo to Mon morning, and not one sighting. :nyaanyaa:

Not impressed with the average speed cameras planned for Hindmarsh Drive, either side of Red Hill. Plans to bring them online in late Feb after lightning damaged them. Purely for revenue raising I say. Yeh, sure there are hoons racing up and over Red Hill but having to use your brake constantly down hill is ridiculous. Reading the local paper suggests a 2% tolerance at most due to some legislation change in 2006 for speed measurement. I guess if it's successful, then NSW won't be far behind. Already got on one on GWH east of Bathurst for trucks. :mad:

Spotted my car driving away for the last time......

Congrats Marty, I know you'll look after her!

I spotted it getting the last once over. Must have gone soon after. I should have dropped in and said goodbye to her!

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