Jump to content
SAU Community

Recommended Posts

Looks like a nice pick up. Glad to see even though you went to the darkside, you picked the right car :P

Yeah, it's always annoyed me that Toyota don't make an affordable small-midsized RWD car.

The last small car was the AE86 and we all know the stigma attached to those cars, plus for a basic mid 80's car they are sickeningly over priced. After that the next step is an IS200 which isn't cheap and the aussie ones have junk engines. Toyota also don't do any RWD 4cyl turbo engines either so you have to convert stuff to get what you want. Bloody bean counters....

It's a shame really, as I think Toyota would have done a good job at it, but they let that segment of the market go.

Oh well, I'm glad that Nissan didn't! I think I'll always have a hankering for an AE86 though...

Yes, it has a mildly worked Clevo in it, the whole drive train (except diff) come out of our old XD Ute we used to race.

It hasn't been out of 'the box' for too long, so there is still some fine tuing to do, but it is doing 1:45's at Winton.

Still pretty much a basic Falcon underneath, just beefed up suspension - thanks to my good friends at Pedders in Bendigo, brakes are slotted rotors (standard size and standard callipers), with Bendix Ultimate pads.

One of my favourite pictures. The guys at RPM Photography were in the right spot with the finger on the button for this one lol. Kudos to them for this, as it's by far the shot of the year at QR for me.

post-41931-1202361721_thumb.jpg

great shot! but coming second whats going on! ?? haha

:P Smarty... I had wastegate problems so I missed race 1 and had to start from the back in race 2.

I could ask why it is that you only just managed to get under 60sec on the Clubman yesterday at QR too :O

i have a plethora of excuses !! which one would you like to hear! lol

i thought youd like that!:no:

Well, I think maybe it's age catching up?

Semi-slick 285 hoosiers leave nice lines hey lol

is that r33racer in front?

It's his father driving it actually. Michael didn't drive it much last year.

Thats an interesting shot, where was it taken?

It was at the old Morwell Hillclimb circuit here in Vic. It's closed down now, but was a lot of fun. It's just a pity you couldn't get any heat into the tyres before a run.

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