SpeedStacks WCA Timer

Tyson

Veteran
Joined
Apr 18, 2008
Messages
640
Location
Burlingame, CA, USA
WCA ID
2004MAOT02
I just got off a conversation with SpeedStacks and they want to work with the WCA to design a timer specifically for cubing.

There are certainly a lot of issues we can address here, and many ways to improve the StackMat timer to suit WCA competitions. So I'd like to open this up for discussion, but it would be best if posts are concise and too the point, and you're not responding unless you really have something truly to add. Otherwise, it will be difficult to sort through everything and figure out what changes we want to make to design a better timer.

SpeedStacks has a patent on this one idea... so simple really: two hands to start the timer, two hands to stop the timer! That's it! And that's basically one of the defining features that makes these timers usable for the WCA.

Anyway, we should probably start by identifying problems that we encounter in WCA competitions before we discuss solutions and improvements. I can think of the following off the top of my head:

1. +2 for starting and stopping the timer while in contact with the puzzle. Eliminating this possibility would be nice, if we could eliminate the ability to stop or start the timer while touching the puzzle.

Other features, like scramble generation, and statistics are more frills. We can talk about those later.
 
And perhaps a way to remove DNS's??

Can you clarify what DNS situations?

I think being able to measure pre-inspection time might be good.

A guard on the reset button.

One thing we should do is to get some quote on how much the features would cost to implement.
 
Cube competition timer must have a mode for timing preinspection.

1- Competitor puts his hands on pads. Cube is hidden.
2- Competitor triggers the 15s countdown by removing his hands from pads, uncovers the cube and inspects. Countdown displayed on screen.
3- Competitor has 15s to start the solve (= trigger the timer again, while countdown goes on). Timer emits a "beep" at 10, 11, 12, 13, 14.
4- Solve not started at 15s -> Timer emits says "BEEEEEP".

-> Not more judges interfering, no more stopwatches, and competitors perfectly informed of time left.
-> Same timer as today, with a loud speaker, and a new software.
 
Last edited:
Cube competition timer must have a mode for timing preinspection.

1- Competitor puts his hands on pads. Cube is hidden.
2- Competitor triggers the 15s countdown by removing his hands from pads, uncovers the cube and inspects. Countdown displayed on screen.
3- Competitor has 15s to start the solve (= trigger the timer again, while countdown goes on). Timer emits a "beep" at 10, 11, 12, 13, 14.
4- Solve not started at 15s -> Timer emits says "BEEEEEP".

-> Not more judges interfering, no more stopwatches, and competitors perfectly informed of time left.

Don't you think the implementation of Step 1 might drive up the cost a lot?

Oh lol... no no, right. Like a BLD start. The timer doesn't cover it for you :-P
 
External power supply for the displays would be nice. Timers could also draw power from the displays when connected.

What about a bluetooth interface? That would make connecting the timer really easy and perhaps enable connecting to programs running on mobile phones or pda's.
 
Last edited:
This may seem a little odd, but it solves real problems, so give it a chance.

I'd want to replace the flat rubber surface with some kind of soft basket. Imagine a small basketball hoop with the net tied together. The problems that would solve are...

1. You can't hit the sensors while still holding the cube. The solve is not valid unless the cube is in the basket.

2. You don't have to drop the cube on the table, thereby avoiding cube damage and unintended extra turns

Also...

3. It looks cool.

4. It would make the much more TV friendly duel version of the sport possible. First solved cube in the basket wins! No boring waiting and math to find the winner.
 
I'd want to replace the flat rubber surface with some kind of soft basket. Imagine a small basketball hoop with the net tied together

That's a very good idea, but perhaps you could just make a small barrier that stands up a few inches between the hand sensors and where the cube should end up. Also, the barrier should be right up against the hand sensors, so that the only possible way to press the sensors is with the very fingertips (like the WCA says); this way cheating would be much more obvious. I think that people stopping/starting the stackmat with their palms/wrists is definitely one of the StackMat's greatest flaws for cubing.

Also some extra padding would obviously help, so that the cube doesn't get beat up.
 
Along with having the stackmat timer countdown, if possible, at least make it so you don't have to wait for the green light to show up, because that makes the 15 seconds, like 13 seconds. Importing scrambles would also be nice, and doing at least an average of 5 would be awesome. People who use up all the time to inspect (like me) need he feature of not having to wait for the green light.

EDIT: Also, because of the patent with starting and stopping with 2 hands, I don't know if your saying that we can't have that feature with the WCA one, but if we can't, then we might be able to incorporate something like a sensitive area, were if you drop the cube their, the timer will stop, which will get rid of the puzzle hitting the time issues. Also, you can start by having the cube on the sensitive mat, so if you don't take it off in 15 seconds and start solving, it's a DNF. This will resolve many issues concerning hitting the timer with the cube, and the patent.
 
Last edited:
1) Extending the auto shut-off to 1 hour would allow multi BLD to be timed on a Stackmet (not to mention big cubes BLD for most people).

2) In competitions in the Southeast we disqualify tons of solves for people who sit when doing their solves, and stop the timer at 0.22 or 0.19 or similar times because their wrists stop the timer as they pick up the cube. This doesn't necessarily have to be implemented into the timer, we could just say "sit at your own risk," or "your fault for stopping the timer incorrectly (before the solve end)". But, if there is an easy way to fix this on the timer that would be cool though. Maybe the timer could register the "false stop", but contniue timing. Regulation could penalize this with a +2. This idea almost sounds too complicated though, and the more I think about it the easier it would be to just give a DNF for "incorrect timer usage."

I'll try to think of more ideas, but those come to mind immediately.

Chris
 
Last edited:
Cube competition timer must have a mode for timing preinspection.

1- Competitor puts his hands on pads. Cube is hidden.
2- Competitor triggers the 15s countdown by removing his hands from pads, uncovers the cube and inspects. Countdown displayed on screen.
3- Competitor has 15s to start the solve (= trigger the timer again, while countdown goes on). Timer emits a "beep" at 10, 11, 12, 13, 14.
4- Solve not started at 15s -> Timer emits says "BEEEEEP".

-> Not more judges interfering, no more stopwatches, and competitors perfectly informed of time left.
-> Same timer as today, with a loud speaker, and a new software.

The problem with the beeps is that the volume is never going to be correct. In quiet scenarios, it's going to be too loud, in loud scenarios, too quiet. I would prefer to just have two extra LED's that indicate you've passed certain pre-inspection points (like 8 seconds and 12 seconds). The judge would have to call these. Now, it would be nice if these could be set, but that would be a lot of complexity we may not need. In the end, display the solve time and the inspection time (down where the clock currently is). And then penalties can be applied accordingly.
 
at least make it so you don't have to wait for the green light to show up, because that makes the 15 seconds, like 13 seconds
I was thinking about that too, and agree with that. I think the green light was needed because the pressure-sensitive pads were too sensitive; perhaps using buttons could fix this in addition to the .02 error.
 
This sounds cool, but here are 2 things worrying me a bit:

1 - How much will it cost? I mean, people all over the world have invested quite a bit of money on equipment. We'd need to buy a LOT of those new timers.

2 - What will happen to current times/records? Will they be erased? I don't think it's "fair" to compare times with different equipment.
 
1) Extending the auto shut-off to 1 hour would allow multi BLD to be timed on a Stackmet (not to mention big cubes BLD for most people).

2) In competitions in the Southeast we disqualify tons of solves for people who sit when doing their solves, and stop the timer at 0.22 or 0.19 or similar times because their wrists stop the timer as they pick up the cube. This doesn't necessarily have to be implemented into the timer, we could just say "sit at your own risk," or "your fault for stopping the timer incorrectly (before the solve end)". But, if there is an easy way to fix this on the timer that would be cool though. Maybe the timer could register the "false stop", but contniue timing. Regulation could penalize this with a +2. This idea almost sounds too complicated though, and the more I think about it the easier it would be to just give a DNF for "incorrect timer usage."

I'll try to think of more ideas, but those come to mind immediately.

Chris
I think it is unfair to hand out DNFs for stoping the timer accidentally, I think it should have two modes, one of them, for most events, that will not stop the timer until it is over one second, another, for things like magic master magic and maybe even pyraminx, Where sub 1's would be allowed.
 
I think it is unfair to hand out DNFs for stoping the timer accidentally...

In case anyone else is wondering about this, here is why we do that:

A6b) It is the competitor's responsibility that the timer is stopped correctly.

...I think it should have two modes, one of them, for most events, that will not stop the timer until it is over one second, another, for things like magic master magic and maybe even pyraminx, Where sub 1's would be allowed.

I think this is making the equipment costs too high.

I do see a problem though with people talking about a timer that tracks pre-inspection. If the timer is to do this, then this mode must be able to be toggled off for BLD events. This increases costs too. I think a pre-inspection mode should not be included for this reason. The only exception to this would be if the costs/budget for the timer allow for it (and it is worth it).

Chris
 
Back
Top