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
  • Season Overview (US Centric)
  • Starting a Team
  • Team Branding

Was this helpful?

Edit on GitHub
Export as PDF
  1. Team Administration
  2. VexU Organization Management

Getting Started in VexU

PreviousVexU Organization ManagementNextTeam / Personnel Management

Last updated 12 months ago

Was this helpful?

This article is a Work In Progress. Please let us know how we can improve it.

sig.robotics.purdue@gmail.com

Season Overview (US Centric)

  • May - Game Reveal

    • At the end of the Vex Robotics World Championship each year, the game for the following season is announced. At this time, teams can order Game/Field Elements, read over the rules, and begin planning for the following season.

      • Since this is also the time of year that High School seniors are finalizing their college decisions, it is likely that some incoming Freshmen will contact teams. It is often a safe practice to delay robot design decisions until the next semester begins so that ALL recruits/incoming members have the ability to actively participate in the team.

      • This is a great time to work out logistics of the VexU team for the following year. Discuss topics like officers, budget, goals, etc. while there is still time to plan and not get distracted by robot designing.

  • August - Fall Semester Begins

    • This is the most common start time for US universities, but it may fluctuate. This is when the majority of recruiting & onboarding for new members should take place. It is best practice to take the first few weeks of the semester to advertise the team on campus, host a call out meeting, and wait on designing the robots until you have members onboard and on-campus.

  • December - Early Season VexU Tournaments Begin

    • Since the majority of VexU teams don't touch their robots until September/October, the earliest competitions are normally in the middle of December each season. If there are no competitions nearby, running skills at a VRC event or hosting a scrimmage is a great way to set a deadline for the team without having to travel far.

  • January/February - Majority of VexU Tournaments

    • The vast majority of VexU competitions take place between January & March. Check the for more information about how teams can qualify to the World Championship each year. VexU often times has a limited number of events as well, so expect to need to travel some distance to competitions and scrimmages.

  • April - Vex Worlds

    • Historically, the VexU world championship has been alongside the VRC Middle School, and VRC JROTC world championships. This is typically the last week in April, or the first in May. RECF will announce dates & venues for each coming world championship in June/July during the Event Partner Summit.

      • Since the final invitations for the world championship do not get sent until late March, it is oftentimes helpful to begin planning transportation/lodging before a team becomes qualified for the event. Ensure that refunds are possible with any reservations if this approach is taken.

Starting a Team

The first thing that has to happen when starting a VexU team is to find a group of students to participate. Most often, for new VexU teams, this comes from a group of students who competed in VRC joining together at a university. If there are enough students to start the club, hanging flyers around campus and hosting a call-out meeting to explain the program are a great way to generate more interest in the team.

If there is known interest on a university campus, the process of having the university recognize the club can begin. Different schools will have different requirements but the core is most commonly a group of student officers, and a faculty advisor. A faculty advisor should be able to help with the majority of the process.

Becoming a recognized student organization should help with the majority of aspects needed when starting a VexU team. This will vary by university, but Registered Student Organizations (RSO) often receive access to a bank account, university email services (for joined accounts), and assistance with finding a workspace.

This will be one of the most difficult aspects to creating a VexU team as space is limited & expensive at most universities. The space does not need to be fancy by any means, but there should be room for the 12'x12' field (ideally with walking space around it), 2-3 tables for working (one specifically for cutting), and storage for parts. As a team is formed and begins working, the specifics of a space will change & best practices will be developed, but there needs to be a foundation before work can begin.

Look for space in research focused buildings on a univeristy campus, or often times discarded rooms under the control of a specific school. Often times, universities will have rooms that were allocated for a specific use years ago that is no longer being utilized in that way.

Learn more in our Robot Events articles.

Team Branding

Depending on the size of the associated university, there may be guidelines for the branding of a team. If a team is associated with a university, there will likely be branding guidelines and limitations as to how one should present the university. Regardless, it is best practice to develop a branding guide for the team that has primary colors, fonts, and formats of the team's logo.

The best way to begin branding is through social media like Instagram to share what the team is working on & show off sponsors alongside upcoming events.

Reach out to university alumni, local companies, and STEM education programs for funding. Learn more about budgeting and funding options in our articles.

Register on

👑
RECF Qualifying Criteria
Team Finances
RobotEvents.com