LogoLogo
  • Welcome!
  • Mission Statement
  • Contributing Guidelines
    • Embed CADs in Wiki Articles
  • VEX Worlds Livestream Archive
    • VEX U
    • V5RC High School
    • V5RC Middle School
    • VIQRC Middle School
    • VIQRC Elementary School
    • JROTC
  • ⚙️Hardware
    • Design Fundamentals
      • Gear Ratios
      • Internal Forces (Stress)
      • Torque
      • RPM
      • Center of Mass
    • Introduction to VEX Parts
      • Structure
        • C-Channels and Angles
        • Fasteners
        • Retainers
        • Gussets and Brackets
        • Bearings
        • Plate Metal and Flat Bars
      • Motion
        • High Strength Components
        • Gears and Sprockets
        • Traction Wheels
        • Mecanum Wheels
        • Omnidirectional Wheels
        • Flex Wheels
    • Robot Decorations
      • Part Dyeing
      • Metal Coloring
      • License Plate Holders
    • Lifts
      • Double Reverse Four Bar (DR4B or RD4B)
      • Four Bar
      • Scissor Lift
      • Six Bar
      • Other Lifts
      • Best Practices
    • Shooting Mechanisms
      • Catapult
      • Flywheel
      • Linear Puncher
    • Drivetrains
      • Tank Drive
      • Mecanum Drive
      • Holonomic Drive
      • Designing a Drivetrain
      • Best Practices
    • Pivots & Joints
    • Pneumatics
      • Best Practices - Pneumatics
    • Intakes
    • Flip Out Mechanisms
    • Defensive Mechanisms
    • Misc. Building Techniques
    • VexU
      • Common Manufacturing Techniques
        • 3D Printing
        • Laser Cutting
      • Custom Manufactured Parts Library
      • Commercial Off The Shelf Parts Library
  • 👑Team Administration
    • New Team Resources
      • Creating The Team
      • Gaining Interest for Robotics Teams
      • Attending Competitions
        • Elimination Bracket
    • Team Dynamics
      • Organization Structure and Longevity
      • Member Allocation and Management
      • How *Not* To Run a Team
    • Team Finances
      • One-Year Team Financial Breakdown
      • Funding Your Teams
    • Hosting Competitions
      • Live Streaming
      • Tournament Manager
        • Competition Electronics
        • Creating a Tournament
        • Tools
          • Field Set Control
          • Connecting Mobile Devices
          • Connecting Raspberry Pis
        • Match Control
          • Inputting Match Scores
          • Inputting Skills Scores
          • Inputting Scores on TM Mobile
        • Displays
        • Alliance Selection
      • Additional Event Partner Resources
    • VexU Organization Management
      • Getting Started in VexU
      • Team / Personnel Management
      • Volunteering At Local Events
  • 📚The Judging Process
    • The Engineering Design Process
      • Test and Refine
    • The Engineering Notebook
      • Segments of the Notebook
      • BLRS2 '23-'24 Engineering Notebook
      • Integrating Inventor Models into Documentation
      • Engineering Notebook Rubric Breakdown
    • The Interview
      • Interview Rubric Breakdown
    • Using Notion for an Engineering Notebook
      • How to Setup a Notebook
      • How to Create Entries
      • How to Export a Notebook
      • Purdue SIGBots Notion Template
        • Game Analysis
        • Identify The Problem
        • Brainstorm Solution
        • Select Best Approach & Plan
        • Build Log
        • Programming Log
        • Testing Solution
        • Tournament Recap
        • Innovative Feature
  • 🖥️VEX CAD
    • CAD Programs
      • Inventor
      • Fusion 360
      • Solidworks
      • OnShape
      • Protobot
    • Making a Chassis
      • Inventor Chassis: The Basics
        • Installation
        • User Interface Overview
        • Dark Mode
        • Assemblies
        • Placing Parts
        • Navigating CAD
        • Changing Visual Style
        • Grounding
        • Connecting Two C-Channels
        • Modifying Existing Constraints
        • Toggling Visibility on Existing Parts
        • Completing Half of the Chassis
          • Inner Drive Channel
          • Bearing Flats
          • Motors
          • Wheels
          • Sprockets
          • Spacers, Washers and Standoffs
          • Spacers Cont.
        • Creating Mid-Plane
        • Mirroring
      • Inventor Chassis: Best Practices
        • File Structure
        • Subassemblies
        • Wheel Subassembly
        • Origin Planes
        • Cross Brace
        • Drive Channels
        • Simple Motor iMates
        • Replacing Simple Electronics
        • Completing Half of the Drive
          • Bearing Flats (Best Practice)
          • Wheels
          • Powered Gear
          • Spacer Boxing
          • Spacers, Washers and Standoffs (Best Practice)
        • Model Browser Folders
        • Mirroring (Best Practice)
        • Model Browser Folder (Right)
        • Main Assembly
      • Fusion 360 Chassis
      • Solidworks Chassis, Chain, and Custom Plastic
    • Remembering The Best
      • 62A Skyrise
      • 400X Nothing But Net
      • 2587Z Nothing But Net
      • 365X Starstruck
      • 62A In The Zone
      • 202Z In The Zone
      • 5225A In The Zone
      • 169A Turning Point
      • 929U Turning Point
      • 7K Tower Takeover
      • 5225A Tower Takeover
      • 62A Change Up
    • Scuff Controller
  • 💻Software
    • Odometry
    • Path Planning
    • Robotics Basics
      • Arcade Drive
      • Tank Drive
      • Joystick Deadzones
      • Curvature (Cheesy) Drive
      • Subsystem Toggling
    • Organizing Code
      • Code Style
      • Code Styling Guide
      • Writing Good Comments
      • Version Control
    • Control Algorithms
      • Bang Bang
      • PID Controller
      • Basic Pure Pursuit
      • Flywheel Velocity Control
      • Kalman Filter
      • Take Back Half (TBH) Controller
      • RAMSETE Controller
    • Competition Specific
      • Operator Control
      • Autonomous Control
    • C++ Basics for VEX Robotics
      • Basic Control Flow
      • Enumerations
      • Namespaces (::)
      • Multiple Files (C/C++)
    • VEX Programming Software
      • PROS
        • OkapiLib
      • vexide
      • Robot Mesh Studio (RMS)
      • EasyC
      • RobotC
      • VEXcode
      • Midnight C
    • General
      • Stall Detection
      • Register Programming
      • Sensors and Odometry in Autonomous
      • Embedded Programming Tips
      • Debugging
      • Bit Shift
      • Bit Mask
      • Autoformatting
      • Finite State Machine
      • Data Logging
    • Object Recognition
      • Red Green Buoy
      • AMS
      • OpenCV
      • OpenNI
    • 🤖AI in VRC: Pac-Man Pete
  • ⚡VEX Electronics
    • V5 ESD Protection Board
    • VEX Electronics
      • VEX V5 Brain
        • V5 Electronics Observations and Issues
      • VEX Controller
      • VEXnet and V5 Robot Radio
      • VEX Battery
      • VEX Motors
    • VEX Sensors
      • 3-Pin / ADI Sensors
        • Encoder
        • Potentiometer
        • Limit Switch
        • Bumper Switch
        • Accelerometer
        • Gyroscope
        • Ultrasonic
        • Line Tracker
        • LED Indicator
      • Smart Port Sensors
        • GPS Sensor
        • Rotation Sensor
        • Vision Sensor
        • Optical Sensor
        • Distance Sensor
        • Inertial Sensor (IMU)
        • 3-Wire Expander
    • V5 Brain Wiring Guide
    • Legacy
      • VEX Cortex
      • Power Expander
      • VEX Motor Controller
      • VEX Cortex Wiring Guide
  • General Electronics
    • General Topics
      • External Boards
        • ASUS Tinker Board S
        • Arduino
        • Beagleboard
        • Leaflabs Maple
        • LattePanda
        • Meadow F7 Micro
        • Netduino
        • ODROID-XU4
        • Pandaboard
        • Raspberry Pi
      • Analog-Digital Converter (ADC)
      • Bit-Bang
      • GPIO
      • I2C
      • Jitter
      • Line Noise
      • List of Tools
      • Output Drive
      • Power Consumption
      • Radius Array
      • Resettable Fuse (PTC)
      • SPI
      • Slew Rate
      • Stalling
      • USART
      • UART
      • 5 Volt Tolerant
      • DC Motor Basics
Powered by GitBook
LogoLogo

This work is licensed under a Attribution-ShareAlike 2.0 Generic License

On this page
  • Example Schedule and What to Expect
  • What to Bring

Was this helpful?

Edit on GitHub
Export as PDF
  1. Team Administration
  2. New Team Resources

Attending Competitions

PreviousGaining Interest for Robotics TeamsNextElimination Bracket

Last updated 1 year ago

Was this helpful?

There are 2 main parts to a competition. There are qualification matches, and elimination matches. During the qualification matches, teams are competing in random matches to rank higher going into elimination matches. In elimination, teams follow a bracket in single-elimination matches until the competition winner is decided in the finals matches.

Example Schedule and What to Expect

In the above schedule, you can see that there is a very early start and a lot of movement throughout the whole day. Below, the schedule will be broken down a little bit.

  • Doors Open

    • This is the first chance to get into the competition venue and set up the team's pit. Most likely the team's pit is a table with some chairs, some outlets (very limited), and a sign with your team number. Get in early to find your pit, get familiar with the venue (look for competition fields, skills fields, judging areas, and restrooms).

  • Registration and Check-In

    • Here, teams need to go to the registration table and check-in with the Event Partner or volunteers. There will be a list of all teams and the team will be asked for any remaining paperwork that is needed (team registration, photography release, covid screening, etc.). Be prepared with everything required by the EP to make this go smoothly. Additional information for the event may also be given at this time (lunch orders, venue map, etc.).

  • Drivers Meeting

    • Here, the head referee will introduce themselves and the referee team. They will likely go over some rules that are commonly broken by teams and introduce the general layout of the competition. Here is a great time to ask about any recent Q&A posts as well as rules that might be unclear.

  • Tournament

    • Here are the qualification matches for the day. They will be discussed later but most likely, each team will play 6-8 matches allianced with and against randomly generated teams. These matches will determine the ranking for elimination matches.

  • Lunch

    • Teams are normally given about an hour here to eat, and often run skills runs. Events will often give the option to order food (most likely pizza) or teams can bring their own food or run out for something. Qualification matches resume promptly after this and this break can be shortened to make up for delays so be sure to listen for announcements and stay in earshot.

  • Alliance Selection

    • After all qualification matches are played, a ranking is given to each team. The top teams (normally 8-12) get to choose another team to alliance with through the elimination rounds. Starting from the number 1 seeded team, teams take turns selecting a team. The chosen team can decline, however, once they decline, they cannot be chosen by another team. After all, alliances are formed, elimination matches are played.

  • Awards

    • Event Partners, Volunteers, and Judges give awards here based on the outcome of the day. The quantity varies by each event but generally, there is excellence, design, and 2 tournament champions along with others at the EP's discretion. All of this is laid out on robot events for each competition as well as what each award qualifies a team for.

Above is an example match schedule that a team might see in a day (In the Vex Via app). The above team will be playing 8 matches which is slightly above average (expect 6-8). Each of the above matches is randomly assigned as per the game manual. The time between matches is ranges drastically though so it is important to keep track of current matches and arrive roughly 5 minutes before matches. Before each match, make sure to also talk to alliance partners before the match. Discuss robot functionality, strategies, opponent research, and anything that might be relevant to the year's game.

What to Bring

  • Safety Glasses, Safety Glasses, Safety Glasses

    • Every person who will come to the field needs to have a pair of safety glasses or they will not be allowed to stand there. Some events will allow students with glasses (for vision) to not wear a pair of safety glasses but still bring another pair just to be safe.

  • Back-up Batteries

    • Matches will come up close to each other in the schedule and chargers will not be fast enough to keep one or even two batteries to be fully charged at the start of each match being played. At least 3 batteries is recommended for a standard competition to be safe and not add extra stress.

  • Back-up Motors

    • If possible, bring extra motors and cartridges. It is possible for motors to break during competitions whether it be from over-use or by being hit during a match. Also bring extra wires and zip ties (anything needed to replace a motor). Cartridges will also sometimes break or often wear out / need grease and make a robot perform poorly.

  • Tools!

    • Bring whatever tools you can. It would be best to have several sets of Allen keys, screwdrivers, and nut drivers. Power tools are not recommended but there are often areas for cutting (so bring a hand saw and file) as well as sometimes Dremel cutting tools or drills. It would also be a good idea to bring a set of screwdrivers, a nut driver, and a wrench to the field.

  • A Field Go Bag

    • Teams will have to run back and forth to the fields for matches and will not have time to run back to their pit for something right before a match so a small bag is a good idea. In here, have some extra screws and nuts, zip ties, rubber bands, and a set of small tools. Also, try to keep an extra battery here.

  • Limited Parts

    • It is common for teams to want to bring everything they own to each competition in case something breaks. Keep in mind that the pits will be crowded with limited space and no rebuilding should be taking place at a competition. Bring some metal, some gears (to replace current ones. not every size), some backup Lexan, and hardware.

  • Game Elements

    • There will not be easy access to game elements for practice or testing during competitions most likely. Do not bring large pieces (Turning Point Platforms for example) but smaller elements are very helpful.

👑
Example Competition Schedule
Example Match Schedule for Team 91A