The Judge's Award, Rookie All-Star Award, and Rookie Inspiration Award were changed from Championship to Championship Division. 

Teams must use SES to ship their robot and crate(s) home from the Championship event.  Exceptions to this rule will be made on a case-by-case basis.  

Subject line:  "Robot Removal, for Team (your team #)";

Reason you are requesting an exception – detailed explanation;

Upon reception of this information, FIRST will, in good faith, consider your request.  The Director of FRC will review each case and will provide a written response.  This decision will be final.

The FFIA will be judged by a panel of leading experts in the fields of engineering and patent law, including Dean Kamen, and representatives from Abbott and others, to determine the winning idea.

The winner will be announced at the FIRST Championship. The winning student(s) will be granted an award sponsored by the Abbott Fund and also will have the opportunity to meet with a venture capitalist firm for a real-world experience in discussing their invention and possible business application.

The FFIA competition is open to all FRC and FTC teams officially registered for the current 2012/2013 FIRST competition season. Teams may apply at the FFI PORTAL.  The FFIA portal for student submissions will open at Noon Eastern Time on Thursday, November 8, 2012 and close for submissions at Noon Eastern Time on Thursday, February 21 March 14, 2013.

The Chairman’s Award, the Woodie Flowers Award, and the Entrepreneurship Award, and the Media and Technology Innovation Award must be submitted through the FIRST Student Team Information Members System (STIMS) https://my.usfirst.org/stims/site.lasso.   The Main or Alternate contact for your team must assign at least one (1) and up to four (4) student award submitters in FRC TIMS.  Those students will be notified of their status via email and may then log into the STIMS and be able to view the awards submission section on their main page.

The FIRST Dean’s List Award must be submitted by the team’s main or alternate contact through TIMS, https://my.usfirst.org/frc/tims/site.lasso.

The FIRST^® Future Innovator Award (FFIA) must be submitted via the FFIA portal. http://www.allthingspatent.com/FRC/

Submission for awards, with the exception of the Media and Technology Innovation Award, will open at Noon Eastern Time on Thursday, November 8, 2012 and close for submissions at Noon Eastern Time on Thursday, February 21, 2013.

Submission for the Media and Technology Innovation Award will open at Noon Eastern Time on Friday, March 1, 2013 and closed for submissions at Noon Eastern Time on Friday, March 22, 2013.

This award recognizes the team that develops and implements an outstanding marketing strategy, complete with rationale for digital channels/devices to disseminate content.

Submissions will be reviewed and evaluated by a Comcast designated judge panel. This is independent of current FIRST Program competition season judged awards.

At the 2013 Championship, the winner of the Media and Technology Innovation Digital Media Award will be announced at the awards ceremony.

 Submission will be judged on the following criteria:

• Strategy
  • Target right audience with right message
  • Develop a clear strategy for choice of distribution channels and content creation
  • Must use at least two channels.  More channels are not necessarily better
• Overall Experience – Ensure content and channels fit together in look and feel
  • Are you promoting a positive impression of FIRST and its mission?
• Visual Design
  • Appealing
  • Easy to read
  • Visual fit with FIRST – Even though the team has its own identity, is it clear that this team is a part of FIRST?
• Navigation – Content organization and prioritization
  • Simple
  • Intuitive
• Content – Is information compelling and optimized for consumption.  More than just text.  (Think about using sound, video.)  Good content should be engaging, relevant, appropriate
  • Was original content created?
  • Content is kept up-to-date and refreshed
  • Action-oriented
  • Use of live links
  • Appropriately cited and not infringing on others’ trademarks or copyrights
• Functionality – Content loads quickly.  Works with multiple major browsers
  • Ease of use
  • Efficiency – Able to complete required tasks easily
  • Utility
• Engagement
  • Did your digital media engage an audience to find out more about your team or about FIRST?
  • How did you track the results?

The FRC Website Award was started in 2003 to recognize excellence in student designed, built and managed websites.  Given the new digital possibilities to spread the FIRST message, FRC has expanded the website award to include other digital media.  With the Media and Technology Innovation Award, students are encouraged to look beyond building a team website, taking into account the numerous ways people search for and consume content.  Students should think broadly, considering channels (traditional sites, mobile, apps), devices (smart phones, tablets), and content (social, rich, and viral* media).   Be Imaginative!

The FIRST^® Future Innovator Award (FFIA) must be submitted via the FFIA portal. http://www.allthingspatent.com/FRC/ LINK COMING SOON. Submission for awards will open at Noon Eastern Time on Thursday, November 8, 2012 and close for submissions at Noon Eastern Time on Thursday, February 21, 2013.

3. The team may bag their bumpers separately from their robot. However, the separately-bagged bumpers must be sealed with their own tag, and that tag number must be entered on the Robot Lock-Up Form.

A formal business plan must be completed and entered through the FIRST Student Team Information Members System (STIMS) https://my.usfirst.org/stims/site.lasso.

The Awards Submission section of STIMS will open for submissions at Noon Eastern Time on Thursday, November 8, 2012 and close for submissions at Noon Eastern Time on Friday, February 22, 2013 Thursday, February 21, 2013.

There will be no change to the value of CLIMBING at the FIRST Championship, as mentioned in Section 3.1.5.2.

Good luck to all Teams competing at the FIRST Championship!

The Q&A will be closing for questions at noon on Wednesday, April 24, 2013. If you have specific, game-related questions, please ask them at the Drivers’ Meeting at Championships.

The procedure for the full-size Practice Fields at Championships has been posted on the FIRST Championship homepage.

Congratulations to all Teams on a successful FRC Regional Season! Good luck to those Teams competing at the FIRST Championship!

There is an issue with the VEX BAG Motors supplied in the Kit of Parts (lot numbers 2491BL, 2462BL, and 2493BL) that causes the motor to stop working. VEX has published instructions, now legal per R33, regarding the fix. 

The integral mechanical and electrical system of any motor may not be modified. Motors, servos, and electric solenoids used on the ROBOT shall not be modified in any way, except as follows:

1. The mounting brackets and/or output shaft/interface may be modified to facilitate the physical connection of the motor to the ROBOT and actuated part.
2. The electrical input leads may be trimmed to length as necessary.
3. The locking pins on the window motors (P/N: 262100-3030 and 262100-3040) may be removed.
4. The connector housings on the window motors (P/N: 262100-3030 and 262100-3040) may be modified to facilitate lead connections.
5. The Integrated Encoder Module (P/N: 276-1321) may be installed on the VEX 2-wire Motor 393 (P/N 276-2177).
6. The VEX 2-wire Motor 393 (P/N: 276-2177) gears may be changed or replaced per the Supplier instructions.
7. The VEX BAG Motor (P/N: 217-3351) may be repaired per the Supplier instructions found at http://www.vexrobotics.com/217-3351.html.

Good Luck to all Teams competing in Week 7 Events!

The FIELD for ULTIMATE ASCENT is a 27 by 54 ft. carpeted area, bounded by ALLIANCE WALLS, FEEDER STATIONS, LOW GOALS, and GUARDRAILS.  The FIELD floor is covered with carpet (Shaw Floors, Philadelphia Commercial, Neyland II, 20, 30550 30753, “Ground Pepper”).  Three (3) GOALS are located at each end of the FIELD above each ALLIANCE WALL.  A fourth GOAL and three (3) FEEDER STATIONS are located in the corners next to each ALLIANCE WALL. A PYRAMID is adjacent to each ALLIANCE’S AUTO LINE.  At the top of each PYRAMID sits a PYRAMID GOAL.  Each LOADING ZONE is a trapezoidal area bounded by two (2) FEEDER STATIONS, an ALLIANCE WALL, a GUARDRAIL, and Red or Blue tape.

While the two versions of the Talon have similar functionality, there are some differences teams should be aware of. Please see http://www.crosstheroadelectronics.com for more information.

The only power regulating devices for actuators permitted on the ROBOT include:

1. Jaguar motor controller (P/N: MDL-BDC, MDL-BDC24, and 217-3367),
2. Victor 884 motor controller (P/N: VICTOR-884-12/12),
3. Victor 888 motor controller (P/N: 217-2769),
4. Talon motor controller (P/N: CTRE_Talon, CTRE_Talon_SR, am-2505 and am-2195),
5. VEX motor controller (P/N: 276-2193) for controlling VEX 2-wire Motor 393 (P/N: 276-2177) only, and
6. Spike H-Bridge Relay (P/N: 217-0220 and SPIKE-RELAY-H).

Good luck at Week 4 Events!

Mandatory C++ Update:

If your team programs using C++, please make sure you’ve installed the update posted last week before taking the field at an event. CSAs will be circulating in the pits to ensure and assist with this update for those particular teams affected.

From last week’s Team Update: A required update has been released for C++. This update fixes an error in the implementation of Network Tables feeding information to the SmartDashboard. It also fixes an issue with LiveWindow code causing crashes for teams using threads. Full release notes can be found on the 2013 Software Notes page. Our thanks to the teams and volunteers that helped us identify and troubleshoot the issues and solutions during Week 1 Events.

Bandwidth

We want to remind teams of the bandwidth limit incorporated in to this year’s communication protocol (described on pg 7 of the FMS Whitepaper and legislated per [R59]-B). Generally speaking, this limit restricts the amount of information that can pass through the field network on a team’s VLAN. This setting can be mimicked at home using the Bridge Configuration Utility.

Pay special attention to the camera setting and related data rates on page 7 of the FMS Whitepaper.  If you notice sluggish or erratic control using these settings at home, you can expect the same behavior at an event. If you disable these limits at home, you’ll be able to transmit more data, however once you’re on a competition field, the limits will be back in place, and you may again experience sluggish or erratic controls.

Thank you, and good luck at Week 3 events! 

TEAMS and/or ROBOTS may not employ strategies that use DISCS to either aid or inhibit a ROBOT CLIMB.

Violation: TECHNICAL FOUL. If the DISC(S) inhibits an opponent’s CLIMB attempt, the opponent ROBOT’S ALLIANCE is awarded points for a successful Level 3 CLIMB will be granted credit for a Level 3 CLIMB at the end of the MATCH.

ROBOTS may not contact or otherwise interfere with their opponents’ PYRAMID. Inconsequential contact will not be penalized.

Violation: TECHNICAL FOUL. If an opponent’s CLIMB is affected,

1. RED CARD, and
2. Each affected opponent ROBOT will be awarded points for a successful Level 3 CLIMB granted credit for a Level 3 CLIMB at the end of the MATCH.

Regardless of who initiates the contact, a ROBOT may not contact an opponent ROBOT

1. contacting its PYRAMID or
2. touching the carpet in its LOADING ZONE.

Violation: FOUL. If purposeful or consequential, TECHNICAL FOUL. If an opponent's CLIMB is affected, each affected opponent ROBOT will be awarded points for a successful Level 3 CLIMB granted credit for a Level 3 CLIMB at the end of the MATCH.

General Announcements

A required update has been released for C++. This update fixes an error in the implementation of Network Tables feeding information to the SmartDashboard. It also fixes an issue with LiveWindow code causing crashes for teams using threads. Full release notes can be found on the 2013 Software Notes page. Our thanks to the teams and volunteers that helped us identify and troubleshoot the issues and solutions during Week 1 Events.

General note: TEAM Members may not lift other TEAM Members in the ALLIANCE STATION (either up on shoulders or otherwise) as this is a safety issue and will yield a Yellow Card per Section 5.5.4.

Q141 Change

After additional review, we are changing our answer to Question 141 on the Q&A.  Once a robot has been awarded points for a Level 3 climb as the result of a penalty, it will no longer be eligible for additional climb points. The applicable rules are being changed to improve clarity.

Q: Per G16 and G27 a robot is awarded points for a Level 3 climb if their climb is interfered with. If the disrupted robot attempts another climb after the incident, is it eligible for additional climb points?

A: Yes. No.

Good Luck to all Teams competing in Week 1 Events!

The following field drawings have been updated to reflect current designs:

• Goal Bottoms
• Goal Chains
• Pyramid Cap Locking Mechanism

Updated drawings can be found on the Manual Homepage

The most recent FRC Blog describes the observations and lessons learned about ULTIMATE ASCENT game play during the two Week 0 scrimmages attended by FRC staff. One observation in particular is the basis for an edit, shown below, to Rule [G35].  

During the creation and refinement of ULTIMATE ASCENT, we anticipated DISCS to occasionally and accidently be shot off the FIELD by ROBOTS and FEEDERS. However, we underestimated the intensity and degree to which FEEDERS would launch DISCS at the opposite ends of the FIELD.  The aggressive throws plus the propensity for DISCS to leave the FIELD at high velocity caused a more distracting, and more notably hazardous, environment than anticipated for participants and equipment in and around the ARENA.

We strongly resist any significant rule changes after games are released, but this change is required to improve the safety for all FRC event participants. After discussing several options, we believe this particular change is the most effective and efficient way to mitigate risks. We apologize for our error and for having to make this game modification.   

DISCS may be fed onto the FIELD only under the following circumstances:

A.      during TELEOP through the FEEDER SLOTS for any DISCS and

B.      during the last thirty (30) seconds of TELEOP over the FEEDER STATIONS for Red and Blue DISCS.

 Violation: FOUL

As a reminder to Teams, a required Driver Station update was released on February 5. All Teams must update their Driver Station software to at least version 1.29.13.00.

Teams should not touch the GOALS at any point as this could impact the weight sensors used to score DISCS. Teams will be reminded of this during the Drivers’ Meeting, and the GOALS will be labeled with “Do not touch” stickers.

Driver Station Update

There is a new version of the Driver Station software, and we strongly recommend that teams install this update.

This is not a mandatory update because the 01.29.2013 version will function at a competition; however, it fails to log or plot actual packet communications loss and latency data. The Field Management System (FMS) does report this data to the field crew correctly, but the team will not see it on their Driver Station machine. The new version, 2.12.13.00, of the Driver Station software corrects this, and the charts tab shows the blue packet loss plot and the green packet latency. Additionally, the DS logged data will include those values so they can be viewed in the DS Log File Viewer.

Such data reported in the Driver Station is extremely useful to teams evaluating their wireless traffic at home and on the practice fields. It will also be very helpful to CSAs or others attempting to trouble-shoot control issues.

In addition to correcting the data issue, the Dashboard window position will be docked properly while in the Driver account.

FMS Twitter Feed

At the conclusion of each match, the Field Management System posts the results to Twitter. Specific details on the data included in each tweet and the format can be found in the 2013 FMS Twitter Feed document posted on theManual homepage.   

Pre-Field Checklist

In order to help teams have a smooth experience with their Control System on the competition Field, FRC has compiled a list of tips and tricks that teams should use to help prepare for the event. We recommend you use this as punch list before you head to the Field for a Match; either at home, in your Pit, and/or on the Practice Field.

If you run in to any issues, please ask about them using the FRC Technical Q&A if still at home or, if at an event, contact the Control System Advisor (CSA) using National Instruments’ Parkway System (via the Parkway kiosks or a mobile device). A short guide to using NI Parkway is available here if you wish to familiarize yourself with the system before your event.

Good luck to all teams participating in Week 0 events!

All active circuits shall be wired with appropriately sized insulated wire:

Table 4-3: Legal Wire Size

The only power regulating devices for actuators permitted on the ROBOT include:

1. Jaguar motor controller (P/N: MDL-BDC, MDL-BDC24, and 217-3367),
2. Victor 884 motor controller (P/N: VICTOR-884-12/12),
3. Victor 888 motor controller (P/N: 217-2769),
4. Talon motor controller (P/N: CTRE_Talon and am-2195),
5. VEX motor controller (P/N: 276-2193) for controlling VEX 2-wire Motor 393 (P/N: 276-2177) only, and
6. Spike H-Bridge Relay (P/N: 217-0220 and SPIKE-RELAY-H).

The intent of the Robot Access Period is to provide Teams attending 2-Day Events comparable ROBOT access to that which Teams attending 3-Day Events receive during practice day. R21 has been updated to improve parity in the use of FABRICATED ITEMS between Teams attending 2-Day Events and Teams attending 3-Day Events.

Teams may bring a maximum of 30 lbs of FABRICATED ITEMS to each event to be used to repair and/or upgrade their ROBOT.

For Teams attending 2-Day Events, these FABRICATED ITEMS may be used during the Robot Access Period and/or brought to the Event, but the total weight may not exceed 30 lbs. FABRICATED ITEMS constructed during the Robot Access Period and bagged with the ROBOT are exempt from this limit.

The OPERATOR CONSOLE, BUMPERS, and any ROBOT battery assemblies (as described in R05-A) are exempt from this limit.

An optional update has been released for C++ and Java that corrects a few bugs in the SmartDashboard and RobotBuilder and fixes an issue with the PIDController class in C++. Full release can be found at the bottom of the 2013 Software Notes page.

Not all BaneBots motors ship with the BaneBots part numbers on them. Table 4-1 has been edited to include alternate part numbers that are printed on the motors received by Teams. 

The only motors and actuators permitted on 2013 FRC ROBOTS include the following:

Table 4-1: Legal Motors

The Driver Station software provided on the Kit of Parts website is the only application permitted to specify and communicate the operating mode (i.e. Autonomous/Teleop) and operating state (Enable/Disable) to the ROBOT. The Driver Station software must be revision 12.19.12.00 1.29.13.00 or newer. 

The only equipment, provided it does not jam or interfere with the remote sensing capabilities of another Team, including vision systems, acoustic range finders, sonars, infrared proximity detectors, etc. (e.g. including imagery that, to a reasonably astute observer, mimics the VISION TARGET), that may be brought in to the ALLIANCE STATION are as follows:

1. the OPERATOR CONSOLE,
2. non-powered signaling devices,
3. reasonable decorative items,
4. special clothing and/or equipment required due to a disability
5. devices used solely for the purpose of planning or tracking strategy provided they meet all of the following conditions:
   1. do not connect or attach to the OPERATOR CONSOLE
   2. do not connect or attach to the FIELD or ARENA
   3. do not connect or attach to another ALLIANCE member
   4. do not communicate with anything or anyone outside of the ARENA.
   5. do not include any form of enabled wireless electronic communication (e.g. radios, walkie-talkies, cell phones, Bluetooth communications, Wi-Fi, etc.)
   6. do not in any way affect the outcome of a MATCH, other than by allowing PLAYERS to plan or track strategy for the purposes of communication of that strategy to other ALLIANCE members.

DISQUALIFIED: the status of a TEAM, as determined by the Head Referee, in which they receive zero (0) Qualification Points in a Qualification MATCH or receive zero (0) points in, and lose, an Elimination MATCH.

A required update has been released for the FRC Driver Station. This update must be installed by all teams. This update fixes issues with DS-FMS diagnostics and includes the new Log File Viewer.

The 2013 Inspection Checklist is posted on the Manual Homepage. Teams can use this to practice going through Inspection with their ROBOT prior to Stop Build Day to help them better prepare for their events.

An optional update, Version 5.10, has been released for LabVIEW. This update addresses an issue with downloading new code with the Dashboard open and an issue with using the SPI bus.

The Kit of Parts Checklist for the Black Tote has been updated to correct the part number of the Analog Breakout Board.

The BaneBots M5-RS555-12 was omitted from Table 4-1, but included in Table 4-4. This omission was identified in this Q&A and is being corrected in this Team Update.

The only motors and actuators permitted on 2013 FRC ROBOTS include the following:

Table 4-1: Legal Motors

An issue has been reported with the FRC Bridge Configuration Utility where a team may end up with two IP addresses set on a network interface after using the utility, interfering with the operation of other FRC Tools. For information on how to check for and fix this issue, please see this page.

The Bill of Materials (BOM) Template for 2013 is now posted on the Manual Homepage.

Figure 2-7: The PYRAMIDS

An ALLIANCE specific PYRAMID is located in each half of the FIELD.  The PYRAMID is made out of 1 ¹/₂ in. diameter steel tubing and powder coated Red or Blue.  It is 94 in. wide at the base and each side slanted at a 68-degree slope.  The rungs are located 30 in., 60 in., and 90 in. off of the floor.  At the top of the PYRAMID is the PYRAMID GOAL, detailed in Section 2.2.4 The GOALS.

The PYRAMID has four (4), 24 in. square, 11 GA. (.120 in.) steel bases with hook and loop tape (“hook” side) on the bottom.  These bases secure the PYRAMIDS to the carpet.  To prevent damage to venue floors, these metal bases are surrounded by floor protectors.  These floor protectors are made from ¹/₈ in. thick hardboard. The floor protectors begin 12 in. outside of all the PYRAMID bases and continue to cover the floor underneath the PYRAMID (not including the bases themselves).  Additional carpet covers both bases and floor protectors and is held to the carpet using 2 in. wide, Black gaffers tape. The protectors and carpet create a ¹/₄ - ³/₈ in. lip around the PYRAMID.

Figure 2-8: PYRAMID Floor Protectors

Teams may have to remove their ROBOT from the PYRAMID after the MATCH is over with the aid of a FIRST supplied belay system, per G04.  The belaying device acts as a brake to prevent accidentally dropped ROBOTS from causing injuries to teams.  The device attaches to the ROBOTS with two carabiners or loops of rope. Teams must supply two attachment points for the belaying device to mount to their ROBOTS, per R10. The belaying rope is fed through a brake that is anchored to the lowest rung on the opposite side of the PYRAMID from the ROBOT. It is then fed through the PYRAMID top and down the other side to be attached to the ROBOT. There is a "bridle" that splits the rope into two sections, which are 90 in. long.

Only trained event staff are allowed to use the belaying device.

Figure 2-9: ROBOT Using Belay Device (UPDATED)

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

General Updates

In order to make the Classmate images available in time for Kickoff, the Wind River Workbench installations were installed using the 2012 licensing. Teams who wish to use an imaged Classmate for C++ development beyond Jan. 31^st will need to update to the 2013 license. Instructions for updating to the 2013 license have been posted here.

General Announcements

We wanted to make teams aware of two recent posts on the FRC Blog. A post from Wednesday clarifies the intent of [G23-1]. A post from Thursday announced changes to the answers to four questions on the Q&A.

Optional updates have been released for both C++ and Java. These updates make it easier to use the new Test mode and fix a few minor bugs discovered after the kickoff release. More detailed notes can be found on the 2013 Software Notes page.

While not in contact with the PYRAMID, a ROBOT’S horizontal dimensions may never exceed a 54 in. diameter vertical cylinder.

Violation: FOUL. If continuous or repeated violations, TECHNICAL FOUL.

Figure 3-5a: ROBOT inside 54 in. diameter cylinder

While in contact with the PYRAMID, a ROBOT

1. may not have its horizontal dimensions exceed a 54 in. diameter vertical cylinder relative to the ROBOT and
2. may not extend any part of itself beyond a vertical plane defined by a perimeter offset from the base of the PYRAMID by 54 in., see Figure 3-5b and Figure 3-5c.
    

Violation: FOUL. If continuous or repeated violations, TECHNICAL FOUL.

Figure 3-5b: Offset Plane from PYRAMID Base

Figure 3-5c: ROBOT Contacting PYRAMID

The ROBOT must satisfy the following size constraints:

1. total length of the FRAME PERIMETER sides may not exceed 112 in. (see Figure 4-1 for examples),
2. PLAYING CONFIGURATION horizontal dimensions may never exceed a 54 in. diameter vertical cylinder (see G23 and G23-1), and
3. height may never exceed 84 in. tall.

Figure 4-1: FRAME PERIMETER Length Calculations

ROBOTS are required to use BUMPERS to protect all outside corners of the FRAME PERIMETER. For adequate protection, at least 8 in. of BUMPER must be placed on each side of each outside corner (see Figure 4-2).

Figure 4-2: BUMPER Corner Examples (UPDATED)

The only motors and actuators permitted on 2013 FRC ROBOTS include the following:

Table 4-1: Legal Motors

General Announcements

FIRST HQ hosted some of the Lead ROBOT Inspectors for training last weekend. It was an excellent opportunity for us to get feedback on the ROBOT Rules. One thing they wanted to be sure we remind teams of is that all ROBOTS must be compliant with R10.

The Inspectors also asked for clarification on the 8 in. BUMPER requirement of R22. As stated in the Blue Box on R22, the dimension is measured along the FRAME PERIMETER. In Figure 2013-01-15 below, the edge of the FRAME PERIMETER between Corner A and Corner B is only 6 in. To satisfy the 8 in. requirement for Corner A, there must be at least 8 in. of BUMPER in each direction. Thus, the measurement along the 6 in. side would continue past Corner B for 2 more inches.

Figure 2013-01-15

After the MATCH, ROBOTS may only be removed from a PYRAMID under the following conditions:

Strategies aimed solely at forcing the opposing ALLIANCE to violate a rule are not in the spirit of FRC and are not allowed. Rule violations forced in this manner will not result in assessment of a penalty on the target ALLIANCE .

Violation: TECHNICAL FOUL

The ROBOT weight may not exceed 120 lbs. When determining weight, the basic ROBOT structure and all elements of all additional MECHANISMS that might be used in different configurations of the ROBOT shall be weighed together.

For the purposes of determining compliance with the weight and volume limitations, the items listed below are not included in the weight assessment:

1. the ROBOT battery and its associated half of the Anderson cable quick connect/disconnect pair (including no more than 12 in. of cable per leg, the associated cable lugs, connecting bolts, and insulation) and
2. BUMPERS (including BUMPER covers, if appropriate).

The only pneumatic system items permitted on 2013 FRC ROBOTS include the items listed below.

1. Items available in the 2013 KOP,
2. Pneumatic pressure vent plug valves functionally equivalent to those provided in the KOP,

3. Solenoid valves with a maximum ? ¹/₈ in. NPT port diameter, and a maximum Cv of 0.32,
4. Solenoid valves that are rated for a maximum working pressure that is less than 125 psi rating mandated above are permitted, however if employed,  an additional pressure relief valve must be added to the low pressure side of the main regulator. The additional relief valve must be set to a lower pressure than the maximum pressure rating for the solenoid valve,
5. Additional pneumatic tubing, with a maximum 0.160 in. inside diameter, functionally equivalent to that provided in the KOP,
6. Pressure transducers, pressure gauges, and connecting fittings,
7. Pressure regulators with a maximum bypass pressure of no more than 60 psi,
8. Pneumatic cylinders,
9. Pneumatic storage tanks, and
10. Compressors compliant with R80.

General Updates

Classmate Image Downloads

The Intel site hosting the Classmate Images is once again live. Teams can find it at: http://www.intel.com/content/www/us/en/intel-learning-series/first-frc-image-system-overview.html

Optional FRC Utilities Update

An optional FRC Utilities Update (v2) has been released which removes the menu bar and run controls from the cRIO Imaging Tool to allow it to fit on the Classmate screen. Teams may still need to hide the Taskbar to see the Imaging Tool buttons by: right-clicking on the Taskbar, selecting Properties, checking the box to “Auto-hide the taskbar”, then clicking OK to exit the dialog. No other changes have been made in this update. This update may be found via the 2013 Technical Resources page.

The DISCS are Wham-O part number 53214 (custom colored Red, White, or Blue) and have a nominal diameter of 10 ⁵/₈ 11 in., a nominal height of 1 ¹/₄ 1.4 in., and a weight of 180 ± 5 grams.

Points are awarded for the highest Level achieved for every ALLIANCE ROBOT that CLIMBS its PYRAMID. The Level to which a ROBOT has CLIMBED is determined by the lowest point of the ROBOT (in relation to the FIELD) at the point in which final scores are assessed per Section 3.2.4. CLIMB point values and Levels are defined in Figure 3-4.

Figure 3-4: PYRAMID Levels

A ROBOT has CLIMBED its PYRAMID if it contacts the PYRAMID and/or the floor (Level 0) in

1. sequential order (Level 0, 1, 2, 3) during ascent and
2. no more than two (2) Levels simultaneously.

ROBOTS may only be removed from a PYRAMID under the following conditions:

1. by the TEAM,
2. unpowered,
3. and under the supervision of a FIRST Technical Advisor (FTA), FTA Assistant, Referee, or Field Supervisor.

Additionally, if any part of the ROBOT is in Level 3, TEAMS are required to attach a FIRST supplied belay line, detailed in Section 2.2.6 Section 2.2.5, to their ROBOT to spot a ROBOT while the TEAM removes it from the PYRAMID.

Violation: YELLOW CARD

Regardless of who initiates the contact, a ROBOT may not contact an opponent ROBOT

1. contacting its PYRAMID or
2. touching the carpet in its LOADING ZONE.

Violation: FOUL. If purposeful or consequential, TECHNICAL FOUL. If an opponent's CLIMB is affected, each affected opponent ROBOT will be awarded points for a successful Level 3 CLIMB.

All active circuits shall be wired with appropriately sized insulated wire:

Table 4-3: Legal Wire Size

General Updates

Bridge Configuration Utility Update

A new version, 01.08.13.195, of the FRC Bridge Configuration Utility is now available for download on the Technical Resources page.  This updated version provides support for firmware version 2.02, which has been found on some of the D-Link DAP1522 Rev B units included in the 2013 Kickoff Kits.  Teams who have already downloaded the previous version of the utility can download and run the new installer to update the utility on their computer.

LabVIEW 2012 Update

National Instruments has released an update for LabVIEW 2012, the version included in the 2013 Kickoff Kits. The update is not required, however Teams using the Robot Simulator can expect improved performance when  sending the simulated camera image to the Dashboard.

Known Bug List

FRC has published, and will maintain, a list of any control system issues of which FIRST is currently aware and the corresponding fixes. The document, 2013 Software Notes, is found here.

Classmate Image Downloads

We are aware of the current error teams are seeing when trying to download the Classmate Images from the Intel site. We are working with Intel to resolve the issue and will Blog again when it is available. As a reminder, only Rookie Teams need to image their Classmates for 2013, and USB Keys were included in the Rookie Kit of Parts to allow them to do so without having to download the image.

In the meantime, please do not re-host the images as this would violate FIRST’s End User License Agreement with Microsoft.