Jump to content
SAU Community

Recommended Posts

well... what we know so far is that Sam is a nice looking gal who drives a 33 GTST with FMIC. Drives hard and well. Lives @ GC (dammnit!!.. why not Brisbane!!!) and has a good friend called Crystal.

and oh yeah... she loves to whore in the graveyard shift with us :D

  • Replies 62.7k
  • Created
  • Last Reply

Top Posters In This Topic

  • chaos

    7164

  • Ska

    5791

  • BelGarion

    3645

  • Nexus9

    3590

Top Posters In This Topic

like wat. Im female and own a skyline that would whipp glenns ass.

thats all that matters :D

ok... i was hoping that it would be somewhere along the lines like:

hi, i'm glenn. i'm from Singapore and been here for 3.5yrs now. finished my Bachelors of IT in UQ and currently doing my MBA. I drives a very rare R32 with RB25DE. I am handsome, charming and articulate but Matt still thinks i'm shameless.

Everyone thinks my NA is slow but they still have problems trying to lose me in their rearview mirrors during mountain runs ;) ... HAR

lol glenn I believed sam just owned you :D

well .. if car matches up turbo to turbo.. yes... she owned me... but if car matches up turbo to NA... there's nothing much to own...

yes... on the straight you're fast.... but in mountain runs, its a different story ;)

Guest
This topic is now closed to further replies.



  • Similar Content

  • Latest Posts

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