|
|
|
![]() |
|
|||||||
|
||||||||
19-03-2010 22:16
Alex Dinsmoor
It turned out (from what I saw) that a ball was ripped, and so got caught in the ball return. Our human player tried pushing the balls as fast as he could down the chute, but nothing worked.
We ended out replaying the match.
And of course hanging again (as you can see
)
19-03-2010 22:16
Bill_BAre they stuck because the hanging 'bot has distorted the tower's geometry?
19-03-2010 22:22
Alex Dinsmoor
|
Are they stuck because the hanging 'bot has distorted the tower's geometry?
|
19-03-2010 22:44
Wildcat|
It turned out (from what I saw) that a ball was ripped, and so got caught in the ball return.
|
19-03-2010 22:50
Alex Dinsmoor
|
really? i heard on the webcast that it was cause some teams had some duct tape type of substance on their robot that rubbed off on the ball causing them to get stuck. oh btw good thing there was a replay, i was afk for the original XD
|
19-03-2010 23:07
The CyborgIt's amazing how just a little bit of tape or ripped ball can cause a jam like that, especially when a couple of more balls fail to unjam it. Is this the only case of something like this happening?
20-03-2010 07:17
GaryVoshol
There were two cases of this at Cass.
One was user-induced when a robot's hanger mechanism stopped a ball from coming off the return (and generated penalties).
The other was caused when a faster-moving ball caught up with a slower one on the return, and the friction between the two ball surfaces caused them to slow down even further. The first ball dropped into the gap between the end of the return and the tower crossbar. <G18> was applied.
20-03-2010 09:08
Travis Hoffman
|
There were two cases of this at Cass.
One was user-induced when a robot's hanger mechanism stopped a ball from coming off the return (and generated penalties). The other was caused when a faster-moving ball caught up with a slower one on the return, and the friction between the two ball surfaces caused them to slow down even further. The first ball dropped into the gap between the end of the return and the tower crossbar. <G18> was applied. |
20-03-2010 22:05
The CyborgWell, I found out today what the case was.
Apparently one of the teams had some sticky stuff on their gripper/kicker mechanism that managed to adhere to the ball, which caused the ball to slow down on the way down the ramp and get stuck in the space in between the ramp and the hanging pole on the tower (since the ball didn't have enough velocity to just simply bounce down). GooGone did the trick of getting rid of the sticky stuff on the ball
.
20-03-2010 22:24
nikeairmancurry|
Well, I found out today what the case was.
Apparently one of the teams had some sticky stuff on their gripper/kicker mechanism that managed to adhere to the ball, which caused the ball to slow down on the way down the ramp and get stuck in the space in between the ramp and the hanging pole on the tower (since the ball didn't have enough velocity to just simply bounce down). GooGone did the trick of getting rid of the sticky stuff on the ball . |
20-03-2010 23:14
The Cyborg|
This is correct.. I was working on the field and many teams were using duck tape on the front of there robots. We ended up rotating out 8 balls off the field, to help prevent this. Also, every team, that had something close to a sticky substance, was checked out to see if it was going to become an issue.
|
21-03-2010 17:12
DonRotolo
|
Someone should lash some 2006 pokey pokey sticks together and create the most entertaining volunteer position we've had since....the 2006 pokey pokey guy.
|