Coding in a sequence.

[DarthMaulCIS]

I plan for the solenoid to re-extend after the winch brings the catapult back down.

Initially, the solenoid is holding back a catapult. When it retracts(the button is pressed), the catapult will launch. Then, the winch will start after the catapult launches, to pull the catapult back to starting position. Once it is back to the starting position, the solenoid will re-extend to hold back the catapult again until the driver hits the fire button again.

Why wouldn't it work in TeleOp?

[Alan Anderson]

Originally Posted by DarthMaulCIS

Why wouldn't it work in TeleOp?

Teleop is called by Robot Main each time the Driver Station sends a packet of data, 50 times per second. It's supposed to quickly do its job and be done. If it doesn't run to completion before the next DS packet arrives, it'll start tripping the system communication watchdog and your ability to control the robot will suffer.

Using a long-running loop, or waiting for an event to occur, should not be done in Teleop.

[Mark McLeod]

Teleop MUST execute and complete/exit in less than 20ms, otherwise you will lose driver control.
It has to do this to keep up with the driver commands flooding in from your drivers.

If you call a sub vi that delays or add a delay of any kind into Teleop that is more than that 20 ms limit, then your driver's will begin to lose control as their command packets start to get dropped while the robot continues to do what Teleop was last told what to do.
For small time skips the drivers will start to notice slow or jerky robot reaction.
If you use the default Safety Config on the drive motors, then your robot will jerk to a halt after only a tenth of a second. Manipulators that are in motion will continue in motion and not be able to be stopped until your delay in Teleop finishes and Teleop is allowed to process the driver control commands again.
If you delay for really significant amount of time (seconds) and the Safety Config is not used, then the robot will continue driving on it's own according to what it last heard before you hit the button that started the sequence.
With no driver control that probably means crashing into a wall or your alliance partners.