Programming Master Task List: Difference between revisions

From 1511Wookiee
Jump to navigationJump to search
No edit summary
(fixed task list for 2013)
 
(29 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{| cellspacing="1" cellpadding="15" border="1" width="100%"
'''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'''
|-
|-
| Debug outputs, sensors
| Decide on programming task subdivisions and goals
| Cristian
| Everyone
| 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>
|  
|-
We need to plan the robot code for this year, and divide it into subtasks that we should tackle.
| Explore use of the camera<br>
 
| -<br>
| TODO
| End goal: get camera to track either our own trailer colors or the opposition trailer colors (we want both to work eventually). Start by looking at the examples. Once you are familiar with the examples, try integrating the relevant classes into our code.<br>
|-
| Field control system<br>
| Calvin<br>
| Develop a graphical application for controlling the field for Rally (does not use robot code, obviously! we'll be doing this probably in Java).<br>
|-
| Mouse Interaction<br>
| -<br>
| After the mouse electronics are explored, if we need any sort of driver class, write one. Either way, a class should be written to track movement, providing meaningful X-Y movement in normal distance measurements (inches, feet, etc -- NOT ticks).<br>
|-
| Autonomous: bump our empty trailer<br>
| Becca,Shauna<br>
| If one of our alliance partners doesn't show, we want to be able to move their trailer out of the way of the nearby enemy payload specialist.<br>
|-
| Trap door up/down LEDs<br>
| Cristian<br>
| Light these LEDs to respond to sensor input.<br>
|-
| Double-check Drive code for issues with encoder/counter change<br>
| Andy/Mike/Peter<br>
| Encoders were changed to counters due to I/O limitations. Need to check that this does not impact the drive control code.<br>
|-
| Update Driver's Station Firmware<br>
| Eric<br>
| Newer firmware for the DS is out. We need to update ours. [b]You must have a mentor help you with this task[/b]<br>
|-
| Test new firmware with our FMS<br>
| Eric<br>
| Set up Rally FMS system and test with the DS firmware to make sure it didn't break us!<br>
|}
|}
<br>

Latest revision as of 14:46, 10 January 2013

Note: These are not in any order currently!!

Task
Assigned To
Description
Status
Decide on programming task subdivisions and goals Everyone

We need to plan the robot code for this year, and divide it into subtasks that we should tackle.

TODO