| 1 | |
| 2 | == Command Based Robots == |
| 3 | |
| 4 | Structure Documentation: |
| 5 | |
| 6 | Subsystem |
| 7 | + Default Commands |
| 8 | - Continuously executing until Interrupt |
| 9 | + Relation To Robot |
| 10 | - Subsystems can be compared to mechanisms that use the same overall resources |
| 11 | - realize that two actions cannot occur at the same time, that require the same subsystem |
| 12 | + Dependencies |
| 13 | - Dependencies are created by the requires(Subsystem subsystem) |
| 14 | - These prevent two different commands from utilizing the same resources on the robot |
| 15 | |
| 16 | Commands |
| 17 | + Interrupts |
| 18 | - Called to stop a command from running |
| 19 | - Specifically when robot is disabled or a dependency overlaps |
| 20 | + Connection With Buttons |
| 21 | - Commands can be easily mapped to buttons through the OI class |
| 22 | |
| 23 | Input Class |
| 24 | + Input Devices |
| 25 | - Input devices are mapped through joystick and button objects |
| 26 | + Button Actions |
| 27 | - Commands can be mapped to buttons or triggers in the OI class |
| 28 | |
| 29 | Robot Map |
| 30 | + Ports |
| 31 | - This class centralizes port numbers and connection numbers for robot-wide use |
| 32 | |
| 33 | Command Groups |
| 34 | + About |
| 35 | - Command Groups are used for command sequencing and parallelizazation |
| 36 | - Basically running things in a specific order or at the same time |
| 37 | - think about automated actions |
| 38 | + Sequential |
| 39 | - TODO(testing) |
| 40 | + Parallel |
| 41 | - TODO(testing) |