Timing Equipment - New Ideas

Well I think the number of digits depends on what time we want the upper limit to be. Obviously if it has 6 digits, it could be up to 10 minutes with 3dp, or up to 1 hour. 5 digits Would be what we have at the moment. I think maybe we should sort out for certain what we want on the timer before we start making prototypes?
 
I prefer the 6-digit design. How high would it go? 99 minutes? That's perfect for something like MBLD (even though we only need up to 60)

We could go above one hour, we could theoretically do 1:00:00. But not many solves go above one hour now (the only candidate would be 5x5 BLD), so we may not need to.
 
I might have mentioned this before, but what about running CCT or similar on any tablet (and plugging your Stackmat in)? Jeremy tackled the problem for a bit, but he's got other WCA issues calling him right now, but someone can attempt to make this work.

The timing issue is separate.
 
I might have mentioned this before, but what about running CCT or similar on any tablet (and plugging your Stackmat in)? Jeremy tackled the problem for a bit, but he's got other WCA issues calling him right now, but someone can attempt to make this work.

The timing issue is separate.

That could be an idea, but what for competitions that can't afford the tablets/not have enough? We could do both...
 
It might be cheaper to go with 5 digits but with an adjustable decimal point. So you could go to 100 seconds with an accuracy of 0.001 seconds, to 1000 seconds with an accuracy of 0.01 seconds and to 10000 seconds (roughly three hours) with an accuracy of 0.1 seconds.
 
It might be cheaper to go with 5 digits but with an adjustable decimal point. So you could go to 100 seconds with an accuracy of 0.001 seconds, to 1000 seconds with an accuracy of 0.01 seconds and to 10000 seconds (roughly three hours) with an accuracy of 0.1 seconds.

That is an interesting idea. It would satisfy all that the timer needs.
 
you could go to 100 seconds with an accuracy of 0.001 seconds, to 1000 seconds with an accuracy of 0.01 seconds and to 10000 seconds (roughly three hours) with an accuracy of 0.1 seconds.

You people keep confusing five and six... 1:39.999, 16:39.99 and 2:46:39.9 all have six digits, not five.
 
It might be cheaper to go with 5 digits but with an adjustable decimal point. So you could go to 100 seconds with an accuracy of 0.001 seconds, to 1000 seconds with an accuracy of 0.01 seconds and to 10000 seconds (roughly three hours) with an accuracy of 0.1 seconds.

Or we could have just 2 modes with 6 digits. 1 mode goes up to 9:59.999, and the other goes up to 99:59.99. So 1 is for shorter events, and the other for longer events. Maybe even a software switch to change between them after 10 minutes? This would also mean that it doesn't have to be changed manually.
 
1:00:00 is the highest it would need to go for MBLD. So why do you want 6 digits? A ten minute solve doesn't need 3 decimal points (600.000)
 
There have only been three successful solves over 1hr (both 5x5 BLD). Of course, there are unsuccessful solves that aren't in the list, but the 6 digit timer could still go over 1 hour. So, we could go from 59:59.99 to 1:00:00 and theoretically could go to 99:59:99.

Another idea: The only solve above 100 minutes was Stefan's 2:34:36 fron 2004. So, we could do up to 100 minutes to 99:59.99, and then switch to 1:40:00. Could be a little confusing at first though.

What about a light for low battery on the timer? Also, I'll probably only update the 6-digit design.

Also, has anyone downloaded the Sketchup file? If so, could you please give some feedback on how the timer looks.
 
Last edited:
How about we use a 5-digit display (x:xx.xx) and after 10 minutes we display it in minutes and seconds instead (x:xx:xx), using hours for the leftmost digit if we really have to?

And if you want 1/1000-second precision, change "5" to "6".
 
Back
Top