Programming Master Task List: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
No edit summary
No edit summary
Line 7: Line 7:
| Test Ball_Manipulator Class<br>  
| Test Ball_Manipulator Class<br>  
| Calvin<br>  
| Calvin<br>  
| Test on the robot using mock inputs and outputs and/or dashboard.<br>
| Test on the real robot once controls and robot are built.<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&nbsp; Also power the outputs (LEDs)<br>
|-
| Dashboard output<br>
| Eric &amp; 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  
| Debug outputs, sensors  
| -
| Cristian
| Need to add debugging output based on DS inputs.&nbsp; One button debugs one (or one small set of) sensors by printing useful information (decoder ticks, revolutions per min, etc).&nbsp; Use unused drive joystick buttons ('''on the base only''') or spare toggle switches.&nbsp; If we run out, use a spare toggle switch to enact "debug" mode and change the meaning of other inputs.<br>
| Need to add debugging output based on DS inputs.&nbsp; One button debugs one (or one small set of) sensors by printing useful information (decoder ticks, revolutions per min, etc).&nbsp; Use unused drive joystick buttons ('''on the base only''') or spare toggle switches.&nbsp; If we run out, use a spare toggle switch to enact "debug" mode and change the meaning of other inputs.<br>
|-
|-
Line 24: Line 16:
| Peter<br>  
| Peter<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>
| 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>
| Peter<br>
|
Assess the DS Input usage by code that gets used in both auto and teleop.&nbsp; For these, the code needs to not use the DS inputs directly; rather they need to use variables/function calls that return values that...
*In Autonomous: Set as described in "Read DS&nbsp;Inputs before Autonomous
*In teleop: Set at the top of each processing iteration by reading the DS normally.
|-
| Document driver controls<br>
| Done - Bear 1/31<br>
| Driver (joystick drive) needs to be documented in the wiki. Use the [[DriverStationControls]] page as a guideline.
|-
| Read autonomous mode from DS<br>
| -<br>
| Look at the controls documentation ([[DriverStationControls]]) and write code that will read the autonomous mode. This has to be done in disabled mode (see Read DS Inputs before Autonomous, above).
|}
|}


<br>
<br>

Revision as of 15:35, 31 January 2009

Task
 Assigned To
 Description
Test Ball_Manipulator Class
 Calvin
 Test on the real robot once controls and robot are built.
Debug outputs, sensors Cristian 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.
Read DS Inputs before Autonomous
 Peter
 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.


Retrieved from "https://wiki.penfieldrobotics.com/wiki/index.php?title=Programming_Master_Task_List&oldid=1066"