In competitive robotics, every second of a 60-second driver-controlled match counts. If a driver has to press one button to launch, hold down another button to reset the mechanism, and manually watch for the arm to return to position, they lose valuable seconds and mental bandwidth that should be spent navigating the field and lining up the next score.

The solution is simple: automate the cycle into a single button press.

By chaining the launch, delay, reload, and stop commands together, your driver can tap one button once, keep driving immediately, and let the code handle the mechanical timing in the background.

Before writing custom automation code in VEXcode IQ, you must disconnect the motor from direct controller stick or bumper assignments.

Decide which controller button makes the most ergonomic sense for launching. The right bumper (R Up) is typically ideal because it leaves your thumbs free on the joysticks while your index finger fires.

Start your stack with an event block:

Once triggered, the motor needs to turn just long enough to slip the gear, release the cam, or trip the release latch.

For most geared catapult and slingshot mechanisms, half a second provides ample rotation to trigger the release mechanism cleanly without over-straining the motor.

Immediately after the shot releases, the catapult arm must be drawn back down into firing position so it is ready for the next game piece.

The 3-second wait gives the motor enough time to wind back against the rubber bands or tension cables until it reaches the primed holding position. Stopping the motor at the end prevents motor burnout and preserves battery life.

Every robot build features slightly different gear ratios, friction points, and rubber band tensions. Once you download the program to your brain, run a few bench tests: