| Steven Donow |
14-01-2014 17:43 |
Team Update 1-14-2014
Most changes should be bolded, I may have missed a few, it's hard to format
Link
Quote:
General Updates
Windows 7 Activation Update:
If you've received an error while trying to activate Windows on your Classmate, please refer to the procedure for activating the Windows 7 OS, 2014 Windows 7 Activation Procedure_Rev0, which has been posted at http://www.usfirst.org/roboticsprogr...ical-resources.
In order to activate the copy of Windows 7, teams must download this tool and run the application.
LRI Training
On Saturday, January 11, we hosted more than 50 Lead Robot Inspectors at FIRST HQ as part of LRI Training. Many of the changes in this Team Update are a result of their feedback and are an attempt to clarify the true intent behind each rule. We thank them for their time spent as volunteers and for their feedback as we strive for continuous improvement of the Manual.
Section 3: The Game
Section 3.1: Game Details
Section 3.1.4: Scoring
The change made by Team Update 2014-01-07 to Section 3.1.4: Scoring, part A created unintended consequences for exactly when a BALL would be considered SCORED in a GOAL. The intent was to make sure that a BALL that “bounced out” of a GOAL did not count as SCORED. We believe the following change better captures that intent.
A BALL is considered SCORED in an ALLIANCE’S GOAL if
A. a ROBOT causes one (1) of their ALLIANCE’S BALLS to cross completely and remain completely through the opening(s) of one (1) of their ALLIANCE’S GOALS
B. the ALLIANCE ROBOT last in contact with the BALL was entirely between the TRUSS and their ALLIANCE’S HIGH GOALS, and
C. the BALL is not in contact with any ROBOT from that ALLIANCE.
…
A CATCH occurs when a BALL SCORED over the TRUSS by a ROBOT’S ALLIANCE partner is POSSESSED by that ROBOT before contacting the carpet, the ROBOT which SCORED the TRUSS, or HUMAN PLAYER.
Section 3.2: Game Rules
Section 3.2.3: General Rules
G10
The following actions are prohibited with regards to interaction with FIELD elements (items A-D exclude BALLS):
grabbing,
grasping
grappling
attaching to,
damaging,
becoming entangled
Violation: FOUL. If the Head Referee determines that further damage is likely to occur, DISABLED. Corrective action (such as eliminating sharp edges, removing the damaging mechanism, and/or re-Inspection) may be required before the ROBOT will be allowed to compete in subsequent MATCHES.
Section 4: The Robot
Section 4.2: Safety & Damage Prevention
R9
Protrusions from the ROBOT and exposed surfaces on the ROBOT shall not pose hazards to the ARENA elements (including the BALLS) or people.
Section 4.4: Fabrication Schedule
R13
ROBOT elements created before Kickoff are not permitted. ROBOT elements, including software, that are designed before Kickoff are not permitted. unless they or their source files are publicly available prior to Kickoff.
Exceptions include the following:
BUMPERS,
OPERATOR CONSOLE,
battery assemblies per R5-A, and
software and designs with source files publicly available prior to Kickoff.
R14
The ROBOT (including items intended for use during the competition in alternative configurations of the ROBOT, excluding items permitted per R17 R18) must be bagged or crated (as appropriate for your event), and out of Team hands by Stop Build Day, February 18, 2014 (refer to the FRC Administrative Manual, Section 5 for more details).
Section: 4.6: BUMPER Rules
R26
BUMPERS must be supported by the structure/frame of the ROBOT (see Figure 4-10). To be considered supported, a minimum of ½ in. at each end of the BUMPER must be backed by the FRAME PERIMETER. Additionally, any gap between the backing material and the frame
- must not be greater than ¼ in. deep, and or
- 8 in wide.
R27
Each ROBOT must be able to display red or blue BUMPERS to match their ALLIANCE color, as assigned in the MATCH schedule distributed at the event (reference Section 5.1.1: MATCH Schedules). Markings visible when installed on the ROBOT, other than those explicitly required per R28, are prohibited.
Section 4.8: Power Distribution
R35
The one ROBOT battery, Anderson Power Products (or APP) Connectors (p/n SB50), the one main 120-amp (120A) circuit breaker (Cooper Bussman P/N: CB185-120), and the one Power Distribution (PD) Board shall be connected as shown in Figure 4-11.
R51
Each power regulating device may control electrical loads per Table 4-4. Unless otherwise noted, each power regulating device may control one and only one electrical load.
Table 4-4: Legal Power Regulating Device Use
Electrical Load
Jaguar, Victor, or Talon motor controller
Spike H-Bridge Relay
VEX Motor Controller 29
Solenoid Breakout
M3-RS390-12
M3-RS395-12
M5-RS545-12
M5-RS555-12
M7-RS775-12
262100-3030
262100-3040
ARA motors
AE235100-0610
am-2235
am-2161
am-2194
R86
If the regulator is kept off-board the ROBOT with the compressor, then only low-pressure (60 psi or less) “working” air can be stored on the ROBOT. The “working” pressure gauge must be installed on-board the ROBOT at all times (Figure 4-17).
Figure 4-17: (Updated to match rule) Off-Board Compressor, Regulator, and Gauge with Additional On-Board Gauge
Section 5: The Tournament
Section 5.5: Tournament Rules
Section 5.5.2: Eligibility and Inspection Rules
At each event, the Lead ROBOT Inspector (LRI) has final authority on the legality of any COMPONENT, MECHANISM, or ROBOT. Inspectors may re-Inspect ROBOTS to ensure compliance with the rules.
ROBOTS are permitted to participate in scheduled Practice MATCHES prior to passing Inspection. However, the FTA, LRI or Head Referee may determine at any time that the ROBOT is unsafe, per Section 3.2.1: Safety, and may prohibit further participation in Practice MATCHES until the condition is corrected and the ROBOT passes Inspection.
ROBOTS without BUMPERS will be considered unsafe.
ADDED BLUE BOX
If a ROBOT cannot report for a MATCH, the Lead Queuer should be informed and at least one (1) member of the TEAM should report to the ARENA for the MATCH to avoid receiving a RED CARD, with the exception of a Team that has not passed Inspection, per Rule T6.
T12
Power and air pressure should only be enabled on the ROBOT during those portions of the Inspection process where it is absolutely required to validate certain system functionality and compliance with specific rules (firmware check, confirmation of safe release of stored energy up to and including actuation of the mechanism, etc.).
Section 6: The Glossary
CATCH: the event when a BALL SCORED over the TRUSS by a ROBOT’S ALLIANCE partner is POSSESSED by that ROBOT before contacting the carpet, the ROBOT which SCORED the TRUSS, or a HUMAN PLAYER.
SCORE: to accrue points for an ALLIANCE as described in Section 3.1.4: Scoring.
|
|
