How dope-eyesz/roboticsfall2026 works
This is a VEX V5 competition robot program. Its main workflow registers autonomous and driver-control callbacks, runs pre-autonomous setup, then responds to competition dispatch: autonomous performs inertial-guided turns, while driver control reads the controller and commands the drivetrain and lift. A separate odometry routine uses a rotation sensor for timed linear movement and reports readings to the controller screen, though the sampled code does not show it being called. Hardware instances are defined in src/setup.cpp; src/pre-auto.cpp is present but its implementation was not sampled.
Main entry points: auto.cpp Autonomous routine · control.cpp Driver control · main.cpp Program entry · odometry.cpp Odometry movement
Components 11
Competition entry
- Program entry
src/main.cpp - Pre-autonomous
src/pre-auto.cpp
Robot motion
- Autonomous routine
src/auto.cpp - Driver control
src/control.cpp - Inertial turns
src/inertial.cpp - Odometry movement
src/odometry.cpp
Hardware setup
- Hardware configuration
src/setup.cpp
Other components
- Competition system
- Robot driver
- VEX robot hardware
- VEX controller
Connections 14
- Program entry → Competition system: registers callbacks
- Competition system → Autonomous routine: dispatches autonomous
- Competition system → Driver control: dispatches driver control
- Program entry → Pre-autonomous: calls
- Robot driver → VEX controller: operates
- Hardware configuration → VEX robot hardware: configures devices
- Hardware configuration → VEX controller: configures
- Autonomous routine → Inertial turns: calls turns
- Autonomous routine → VEX robot hardware: resets sensor; sets velocity
- Inertial turns → VEX robot hardware: reads inertial; drives wheels
- Driver control → VEX controller: reads buttons and axes
- Driver control → VEX robot hardware: drives wheels and lift
- Odometry movement → VEX robot hardware: reads rotation; drives motors
- Odometry movement → VEX controller: prints readings