Free play
The simulator A real robot program, running in your browser. Change the code, press Build, and drive it. Nothing here is graded — break it on purpose and see what happens.
Arcade drive One stick forward, one stick to turn. The week 4 robot. Drive and intake Adds a roller and a beam break. Go pick something up. Command-based Subsystems, a default command and a bound button. The week 5 shape.
Drive Code
The robot has not moved yet.
Waiting for a robot. Press Build.
Robot State Which periodic method is running right now 0.00s
Disabled Motors off. Code still runs robotPeriodic. Autonomous Runs autonomousInit, then autonomousPeriodic. Teleoperated Runs teleopPeriodic. This is driving. Test Runs testPeriodic. Teams use it to poke one mechanism.
Disabled. Nothing you write in teleopPeriodic will move a motor.
Timing One loop is 20 milliseconds. Always. Speed 0.25x 0.5x 1x 2x
Loops run 0
Loops per second 0
Joysticks Controller 0, as the robot code sees it Keyboard
Right X 4
0.00 left / right Z X C V Q E
On-Ramp keys WPILib keys
WASD on the left stick, arrows on the right stick, Q and E for the bumpers.
A D W S left right up down Z X C V Q E
Plugged a controller in? Press a button on it and it will show up here.
PWM Outputs What the motor really gets, after inversion DIO Digital inputs. Tap one to force it. This robot has not allocated a digital input yet.
Command Scheduler Commands the scheduler is running this loop 0
Nothing scheduled. If you bound a command to a button, hold that button — and check that CommandScheduler.getInstance().run() is in robotPeriodic.
SmartDashboard Everything your code has published Nothing published yet. Add SmartDashboard.putNumber to your code and it will appear here.
Other Devices CAN motor controllers, and the game piece Nothing on the CAN bus. These motors are wired to PWM.
Console System.out.println, with the loop it happened on Wiring sheet KitBot — tank drive, nothing bolted on yet
Left drive PWM 0
Right drive PWM 1 (mirrored gearbox)