|
|
| (39 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| {| width="100%" cellspacing="1" cellpadding="15" border="1" | | '''Note: '''These are not in any order currently!! |
| | |
| | {| width="100%" cellpadding="15" cellspacing="1" border="1" |
| |- | | |- |
| | '''Task'''<br> | | | '''Task'''<br/> |
| | '''Assigned To'''<br> | | | '''Assigned To'''<br/> |
| | '''Description'''<br> | | | '''Description'''<br/> |
| | | '''Status''' |
| |- | | |- |
| | Test Ball_Manipulator Class<br> | | | Decide on programming task subdivisions and goals |
| | Calvin<br>
| | | Everyone |
| | Test on the robot using mock inputs and outputs and/or dashboard.<br>
| |
| |-
| |
| | Ball manipulator OI-based contol<br>
| |
| | Christian<br>
| |
| | Create code to read OI inputs and correctly call the member functions of Ball_Manipulator based on those inputs. Use the Logitech gamepad for the test input device. You will need to guess which inputs will be used for now. Put guesses at inputs in to dsmap.h Also power the outputs (LEDs)<br>
| |
| |-
| |
| | Dashboard output<br>
| |
| | Eric & Jeff<br>
| |
| | Dashboard output needs to be more robust and actually output all values as appropriate. A solution is known, but has issues. Work to integrate.<br>
| |
| |-
| |
| | Debug outputs, sensors
| |
| | -
| |
| | Need to add debugging output based on DS inputs. One button debugs one (or one small set of) sensors by printing useful information (decoder ticks, revolutions per min, etc). Use unused drive joystick buttons ('''on the base only''') or spare toggle switches. If we run out, use a spare toggle switch to enact "debug" mode and change the meaning of other inputs.<br>
| |
| |-
| |
| | Read DS Inputs before Autonomous<br>
| |
| | -<br>
| |
| | Any inputs needed in autonomous must be read-in prior to autonomous while disabled, the values saved, and the code which needs DS input needs to read the saved values.<br>
| |
| |-
| |
| | Check shared teleop/autonomous code for DS Input use<br>
| |
| | -<br> | |
| | | | | |
| Assess the DS Input usage by code that gets used in both auto and teleop. For these, the code needs to not use the DS inputs directly; rather they need to use variables/function calls that return values that...
| | We need to plan the robot code for this year, and divide it into subtasks that we should tackle. |
| | |
| *In Autonomous: Set as described in "Read DS Inputs before Autonomous
| |
| *In teleop: Set at the top of each processing iteration by reading the DS normally.
| |
|
| |
|
| |- | | | TODO |
| | Document driver controls<br>
| |
| | -<br>
| |
| | Driver (joystick drive) needs to be documented in the wiki. Use the [[DriverStationControls]] page as a guideline.
| |
| |} | | |} |
|
| |
| <br>
| |
