Programming Master Task List: Difference between revisions

Revision as of 09:39, 15 February 2009

Task	Assigned To	Description
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. "done but need testing"
Explore use of the camera	-	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.
Field control system	Calvin	Develop a graphical application for controlling the field for Rally (does not use robot code, obviously! we'll be doing this probably in Java).
Mouse Interaction	Cristian	A class has been writen, and measurement has been made. Sign problems need to be resolved.
Trap door up/down LEDs	Cristian	Light these LEDs to respond to sensor input. "done but need testing"
Update Driver's Station Firmware	Eric	Newer firmware for the DS is out. We need to update ours. [b]You must have a mentor help you with this task[/b]
Test new firmware with our FMS	Eric	Set up Rally FMS system and test with the DS firmware to make sure it didn't break us!

@@ Line 19: / Line 19: @@
 | Mouse Interaction<br>
 | Cristian<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>
+| A class has been writen, and measurement has been made. Sign problems need to be resolved.<br>
 |-
 | Trap door up/down LEDs<br>