Suggestions for resolving stuck balls

[Daniel_LaFleur]

I'm not so sure the rules need to be changed.

As far as a ball stuck in a robot: I believe that this is a robot design issue, and that robots can be designed to release a ball if disabled, loses power, loses comms, etc... and that those that are not designed to do so should be less desirable as a partner.

As for the Truss: This is a chance you take for the ability to get an extra 10 (or 20) points. Design you robot to ensure you clear the truss easily and practice, practice, practice (so as to not shoot when you are not in a good position).

JMHO

[Jon Stratis]

For a ball stuck in a robot...

If the robot is still functional and driving around, then I think it's really just too bad for the alliance. Yes, it sucks and you might lose the match because of it, but it was the alliance's decision to use that robot as part of the cycle. There's no way for the refs to be able to tell if a ball is permanently stuck, or if the robot will manage to eject it later in the game. Personally, I really don't want to force the refs to make a judgement call in this situation. If it does come down to a judgement call, there will be plenty of times where the team's judgement is different from the refs and people won't be happy. Can't you see the complaining now? "Why didn't you declare the ball dead 30 seconds earlier? We would have won the match!" "Why did you declare the ball dead? We just weren't quite lined up perfectly to shoot yet!"

If a robot is e-stopped with a ball, then it's easy for the ref's to call the ball dead. We don't want to encourage teams to perform full-speed ramming actions on a dead robot in order to try to eject the ball! A dead robot is probably dead for a reason, and that type of abuse won't help. I think the e-stop solution is the best one. It gives the alliance the option (in the case of a momentary loss of connection, like a cRIO reboot or a radio reset) to keep the ball in play or lose the robot for the rest of the match to get a new ball.

[Hallry]

Originally Posted by yash101

If that happens, just ram into a side of the truss and hopefully you will energize it enough to fall down and get back into the game. These are big robots, not those tiny VEX robots (Sorry VEXers. Even I am a VEXer). We have the momentum to get a ball unstuck from the truss.

And you plan on 'ramming' the truss...where and how exactly?

[Whippet]

Originally Posted by Hallry

And you plan on 'ramming' the truss...where and how exactly?

With the opposing ALLIANCE's BALL as their ALLIANCE partners watch in shock as TECHNICAL FOULs rack up...

[Bob Steele]

Originally Posted by yash101

I think that that is one of our least worries. Of all cases, the ball would rarely get stuck on the truss. If that happens, just ram into a side of the truss and hopefully you will energize it enough to fall down and get back into the game. These are big robots, not those tiny VEX robots (Sorry VEXers. Even I am a VEXer). We have the momentum to get a ball unstuck from the truss.


Other than that, how about we shut our mouths and stop giving suggestions? You all saw how they check CD and what their reaction to asking for game hints was! I think this time, let's just calm down and see how they react, because they want everything to be (at least seem like) a surprise!

Good luck and hopefully y'all get a functional robot up-and-running!

I might be wrong but when I read the update I thought they were asking for feedback from Chief volunteers. I could be wrong but I think they are looking for input.

After reading the comment below I guess I would retract this statement.
However, I do think that many of these volunteers read and honor the comments made on CD and welcome the input
I do believe that products and ideas developed by many minds working together are usually better than the work of a small number

I will respectfully continue to voice ideas through the medium of CD

[Hallry]

Originally Posted by Bob Steele

I might be wrong but when I read the update I thought they were asking for feedback from Chief volunteers. I could be wrong but I think they are looking for input.

I thought the same thing at first, but by 'Chief volunteers,' I believe they were referring to the actual position titles.

[Racer26]

My feelings on the matter?

1) BALLs on the TRUSS.

I think a BALL stuck on the TRUSS will be an exceedingly rare occurrence. It might happen one or two times through the entire season. I am OK with declaring it a FIELD FAULT purely because of this rarity. I agree it isn't technically a failure of the field, but this seems like the simplest remedy. The alternative in my mind, is if FMS can allow pausing a MATCH in progress so that a Field Volunteer (Ref, Field Resetter, Whomever) can remove the BALL from the TRUSS, and return it to play in the center field area, allow them to safely get off the FIELD, and resume play.

2) BALLs stuck in responsive-but-not-functioning ROBOTs.

If your ROBOT is still responding, and not dead (perhaps with low battery, or your manipulators are just not working as designed), then I'm inclined to say tough. You should have designed your ROBOT better, or been better prepared for your MATCH.

3) BALLs stuck in non-responsive ROBOTs.

If a ROBOT is completely dead, and FMS/Driver Station no longer has communications to it (ie. the Stack Lights at their ALLIANCE STATION are flashing), then I'm inclined to allow the TEAM to hit their E-Stop Button, ensuring their ROBOT cannot return to the MATCH later. At that point, any BALLs in that ROBOT's POSSESSION become field debris, and a new BALL to replace could be set at the ALLIANCE's PEDESTAL. If at some later point during the MATCH, the BALL which is field debris ceases to be in the POSSESSION of the E-Stopped ROBOT, then FIELD FAULT.