Game Play

[hotshot3]

Q: I am asking for clarification to the post involving a low-shooting robot. If I understand the rule correctly, no ball will be considered blocked until it has reached an elevation of 18". If a ball hits an opponents robot, even if it was released with the intent to be scored (such as from a low-shooter) but is at an elevation of less than 18", it is not considered a blocked shot.
Am I correct?

A: Yes, you are correct.

[hotshot4]

Q: In Revision 4 of the Game Manual, Specific Game Rule <SG7> has been revised so as to permit Robots to intentionally contact the Spin Bar during the "Teleop portion of the Match" rather than the previous restriction to the "Spin Time portion of the Match." There is no definition for "Teleop" in Section 2.3 -- Game Definitions of the Game Manual (Revision 4), although it seems reasonable to assume that "Teleop" is referring to the "Driver-Controlled Period" defined in Section 2.3. Assuming this to be correct, and as the Driver-Controlled Period includes both the Spin Time and the End Game portions of the Match, the revised <SG7> seems to have extended the time permitted for Robots to intentionally contact the Spin Bar to include the End Game portion of the Match. However, the last sentence of <SG7> states: "Touching the Spin Bar . . . during the End Game will result in a Penalty for the team." These statements seem to be at odds with one another. Can you please clarify the intent of the revised <SG7>?

A: Touching the Spin Bar during the Autonomous period will result in a penalty for each offense. Touching the Spin Bar during the End Game is allowed. The Game Manual will be updated to clarify <SG7>.

[hotshot4]

Q: I note that the field as pictured for the beginning of the match has the Near Blue Ball Chute on the same side of the Blue High Goal, while the Near Red Ball Chute is on the opposite side from the Red High Goal. During the autonomous period, doesn't this provide an advantage to the Red Alliance allowing one member to pursue close scoring at the Near Ball Chute while the other pursues close scoring at the High Goal essentially unimpeded by members of the Blue alliance. On the other hand, one member of the Blue Alliance is faced with either pursuing the close Near Ball Chute OR the close High Goal while the other would have to travel further to the High Goal or the Far Ball Chute and potential interaction with the Red Alliance robot. I think the probable reason for this configuration is that two robots pursuing scoring at the Far Ball Chute would likely provide an obstruction challenge during autonomous period, but it does seem to create a bias in favor of the Red Alliance. Is there any plan to balance the match assignments to compensate for this?

A: The FTC Qualification Match generation software uses an algorithm that balances several criteria, including red/blue alliance assignments. A description of this algorithm is found here: http://www.idleloop.com/matchmaker/

[hotshot4]

Q: Is contact allowed between the Robot and the High Goal?

A: No, a penalty will be assessed for each occurrence per rule <SG7>.

[hotshot4]

Q: Rule <S2> suggests that a robot cannot completely leave the field. Can part of the robot overhang the field perimeter towards the Off-Field Goals?

A: Yes, so long as no other rules are violated. See Rule <R4>b for robot extension rules.

[hotshot2]

Q: It appears that there is no rule provision or combination of rule provisions that would prohibit a robot satisfying the extension rule (<R4>) from reaching outside the 12' x 12' field and intentionally touching or moving one or both of the Off-field Goals.

Is this correct?

A: No. Intentionally moving the off-field goals would violate <G8>. (i.e. strategy/mechanism aimed solely at damage/tipping over of scoring areas)

[hotshot3]

Q: Rule 2.4.2.3 states "If a robot successfully opens a Ball Chute releasing all 15 balls onto the "PLAYING FIELD"....... If the robot catches the balls and are in the robot, is that considered on the "PLAYING FIELD" or do the balls have to be physically on the rubber mat?

A: The act of releasing all 15 balls will score the points. All 15 balls must be released. However, touching the trigger outside of the legal taped areas as defined in Rule <SG8> will incur a penalty. Also rule <S1> may come into play if the referee determines that there is field damage caused by a robot.

[hotshot4]

Q: I have a couple of related questions about the bonus balls. Must they be released and do they have to be released one per chute? In other words, if an opposing robot is in a position to pick up the bonus ball you are about to release, do you have to release it? Can you release both balls through one chute if one of your alliance robots is in position to collect both balls?

A1: Teams are NOT required to release their Bonus Ball into the Playing Field.

A2: Only one Bonus Ball may be introduced per Ball Chute. See rule <SG4> for complete details.

[hotshot4]

Q: We have a question concerning what is considered "intentional contact".
<SG7> states Robots may only make intentional contact with the spin bar and not any other portion of the High Goal...

We are considering a mechanism that will "deposit" the balls into the center hole of the High Goal that will not intentionally touch any of the sides of the hole. If another team, our own alliance or an opposing alliance, spins the high goal and our depositing mechanism comes in contact with the high due to this movement, is this considered a penalty?

A: Contact with the High Goal will be a judgment call by referees.

If the referee rules that the opposing alliance caused the contact with the high goal, a penalty will NOT be assessed per rule <G10>.

If the referee rules that contact with the high goal was caused by the team’s robot or by their alliance partner’s robot, a penalty WILL be assessed.

High Goal motion caused by balls entering or impacting the goal will be attributed to the alliance releasing the balls. For example, if the balls exiting your robot cause the High Goal to rotate and touch your robot, a penalty WILL be assessed.

[hotshot2]

Q: Can we click "abort program" during autonomous to prevent a motor from burning up.

A: Yes. Use of the "Abort Program" button during any portion of the match for either safety reasons or to prevent damage to a robot (either your own or another team's) is allowed and expected.

Keep in mind that using the "Abort Program" button disables your robot for the remainder of the match. I.e. if a team aborts during the autonomous period, they would need to remain disabled for the rest of the autonomous period and for the entire teleoperated period.

In the above example, the FCS would appear to allow the team to continue during the teleoperated period, the team MUST not re-enable their robot for the remainder of the game.