Jump to content
SAU Community

Recommended Posts

  • Replies 109
  • Created
  • Last Reply

Top Posters In This Topic

Hey Ryan,

Apologies in advance for the following. I'm just offering up an idea which I think could save you a bit of time and effort (so don’t shoot me!!!!!)

I'm assuming that "data entry" is the reason why the results have taken so long to process. EG: the results are written on paper and need to be typed into spread sheets.

Why not enter the time(s) at the end of each run straight into a spread sheet?

It doesn’t strike me as much more effort than writing it down.

I understand that this means up to 3 laptops are required to work on 3 separate spread sheets, but merging the documents has got to be easier than re-entering the data. (Paper times could still act as a backup).

SAU VIC could then announce the results that night during the after DECA drinks, instead of people pestering you for results a month on.

This might not be the most elegant solution.. But its an idea..

- THIS DEC DECA WAS THE BEST YET BTW!

Cheers

I've fixed the macro but there's a few updates I need to do the results spreadsheet. It now needs to cater for more than 50 drivers (when I wrote the spreadsheet a few years ago we never had more than 50 drivers) and there's a number of rule changes which I need to write into the scoring macro as Ryan/Leon are having to do some manual changes now. My macro skills are pretty average so it takes me a while to figure it out, I'm an engineer not an IT person so I've just figured out how to write basic code myself.

Regarding data entry, I think it's still important to have the pen and paper for the records but you could also have 3 laptops with decent battery and MS Excel (about 3 hours for the morning session, charge during the break). I'd gladly bring my laptop up for DECA's but it's old and only lasts about 30minutes when I unplug it. Then it's just a case of copy/pasting to one master file, run the score macro and then do some quick sanity checks to make sure it's all correct.

I've fixed the macro but there's a few updates I need to do the results spreadsheet. It now needs to cater for more than 50 drivers (when I wrote the spreadsheet a few years ago we never had more than 50 drivers) and there's a number of rule changes which I need to write into the scoring macro as Ryan/Leon are having to do some manual changes now. My macro skills are pretty average so it takes me a while to figure it out, I'm an engineer not an IT person so I've just figured out how to write basic code myself.

Regarding data entry, I think it's still important to have the pen and paper for the records but you could also have 3 laptops with decent battery and MS Excel (about 3 hours for the morning session, charge during the break). I'd gladly bring my laptop up for DECA's but it's old and only lasts about 30minutes when I unplug it. Then it's just a case of copy/pasting to one master file, run the score macro and then do some quick sanity checks to make sure it's all correct.

Or cheapo Andriod tablets...

Works fine, thanks Ryan :D Wooooootttt

16 / 52 Best position so far :)

For those that can't see...

https://dl.dropbox.c...20Round%204.png

Cheers Simon.

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

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • 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.
×
×
  • Create New...