Jump to content
SAU Community

Recommended Posts

  • Replies 103.8k
  • Created
  • Last Reply

Top Posters In This Topic

  • GTS-t VSPEC

    20904

  • Nizmo

    13582

  • SHUTO-BOY

    6636

  • skyzerr33

    5353

heres an idea

Open a .txt and just write all ure bs in there.

Its not the content its the attitude. Double posts are for noobs and tools (no offense) there is just no point to post 2-10 in a row especially when ure not saying anything but babbling crap. Sorry im gonna say it, get a life :(

Originally posted by Boostzor

heres an idea

Open a .txt and just write all ure bs in there.

Its not the content its the attitude. Double posts are for noobs and tools (no offense) there is just no point to post 2-10 in a row especially when ure not saying anything but babbling crap. Sorry im gonna say it, get a life :(

Thats ok, i am not offended. I would not have post-whored like this except, so many others have done it [this is where the idea came from! bad excuse but "i didnt start it".

Yeh trouble is i think i did start it. i think when i hit my 1000th post vspec got all excited and really turned it up. this is like "the island of doctor moreau" all over again adn u guys are the monkey men :lol:

Originally posted by nismoR34

so all of your 1081 posts are legitimate / bona fide posts then Boostzor? I doubt it :uh-huh:

You were a noob once too, correct me if im wrong!

Never said that, some of the pointless post are what makes SAU good fun but 10 posts in a row?? i dont think so, not fun for any1

Originally posted by GTS-t VSPEC

I thought the whole idea behind whoring was to get as many posts as possible down.

See'ya:burnout:

what he said.

boostzor, if you did start it, then you have opened up a can of worms...:jump:

Paul, how long have i been here? how long have u been here? i register like 6mnth or something b4 u and ure post count is wayy higher than mine. u have posted like 300 times in the last week or 2. Getting beyond the joke wouldnt u say?

Guest
This topic is now closed to further replies.



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