Jump to content
SAU Community

Recommended Posts

the kimi and Williams rumours are back.

you think he would have made his mind up by now if he was comeing back next year.

(pf1)

p2 times

0 1. Sebastian Vettel Red Bull-Renault 1m46.374s 33 laps

2. Fernando Alonso Ferrari 1m46.575s + 0.201 28 laps

3. Lewis Hamilton McLaren-Mercedes 1m47.115s + 0.741 22 laps

4. Felipe Massa Ferrari 1m47.120s + 0.746 23 laps

5. Mark Webber Red Bull-Renault 1m47.265s + 0.891 28 laps

6. Michael Schumacher Mercedes 1m48.418s + 2.044 27 laps

7. Adrian Sutil Force India-Mercedes 1m48.866s + 2.492 32 laps

8. Sergio Perez Sauber-Ferrari 1m49.578s + 3.204 27 laps

9. Kamui Kobayashi Sauber-Ferrari 1m49.730s + 3.356 29 laps

10. Jenson Button McLaren-Mercedes 1m49.751s + 3.377 10 laps

11. Jaime Alguersuari Toro Rosso-Ferrari 1m49.792s + 3.418 14 laps

12. Bruno Senna Renault 1m50.241s + 3.867 31 laps

13. Paul di Resta Force India-Mercedes 1m50.345s + 3.971 8 laps

14. Vitaly Petrov Renault 1m50.399s + 4.025 29 laps

15. Nico Rosberg Mercedes 1m50.790s + 4.416 28 laps

16. Rubens Barrichello Williams-Cosworth 1m50.897s + 4.523 24 laps

17. Pastor Maldonado Williams-Cosworth 1m50.937s + 4.563 30 laps

18. Heikki Kovalainen Lotus-Renault 1m51.950s + 5.576 26 laps

19. Sebastien Buemi Toro Rosso-Ferrari 1m52.257s + 5.883 15 laps

20. Jarno Trulli Lotus-Renault 1m52.489s + 6.115 25 laps

21. Timo Glock Virgin-Cosworth 1m53.579s + 7.205 25 laps

22. Jerome D'Ambrosio Virgin-Cosworth 1m54.649s + 8.275 25 laps

23. Daniel Ricciardo HRT-Cosworth 1m54.754s + 8.380 29 laps

24. Tonio Liuzzi HRT-Cosworth 1m55.198s + 8.824 26 laps

Edited by tweety bird

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