CSC 499 | Grinnell College | Fall, 2013 | |
Bluetooth Communication with C |
|||
Week index: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, spring
Although the project will evolve over the semester, the following schedule outlines a possible time line for this project.
Color code:
Week | Dates | Activities | Status | Product(s) |
---|---|---|---|---|
Week 1: | 29 August–4 September | Reading concerning Bluetooth Communications | Not yet started | — |
Outline of steps required for Bluetooth communications | Not yet started | Outline of Bluetooth communication | ||
Week 2: | 5–11 September | Develop code to poll Bluetooth devices currently available | Not yet started | poll-bluetooth.c |
Develop code to match available Bluetooth devices with IPRE labels | Not yet started | display-bluetooth.c | ||
Week 3: | 12–25 September | Develop code for MathLAN workstation to send "beep" message to Scribbler 2 robot | Not yet started | send-beep.c |
Develop code for MathLAN workstation to send "blink light" message to Scribbler 2 robot | Not yet started | blink-light.c | ||
Week 4: | 12–25 September | Organize new MyroC header/implementation files | Not yet started | MyroC.h, MyroC.c |
Develop rConnect, rDisconnect, and sound procedures | Not yet started | Procedures to be added to header, implementation files | ||
Weeks 5-6: | 26 September–9 October | Develop robot commands for robot movement | Not yet started | Procedures to be added to header, implementation files |
Development of extensive test procedures for sound and motion | More precise specification needed | Programs test-sound.c, test-movement.c | ||
Weeks 7-8: | 10–18 October | Explore 2-way communication | More precise specification needed | Outline of 2-way protocol |
Explore mechanism for workstation to request and receive sensor information | More precise specification needed | Procedures to be added to header, implementation files | ||
Fall Break | ||||
Weeks 9-10: | 28 October–10 November | Investigate communications involving pictures | More precise specification needed | Outline plan for access and manipulation of pictures |
Identify procedure headers for pictures | More precise specification needed | Draft procedure signatures needed | ||
Weeks 11-12: | 11–24 November | Plan poster(s), Thursday Extra | Specification required | Draft poster, talk outline |
Develop code for picture processing | More precise specification needed | Procedures to be added to header, implementation files | ||
Weeks 13-14: | 25 November–8 December | Complete poster(s), Thursday Extra | Scheduling to be determined | Poster(s) to be placed on bulletin boards |
Complete header file, documentation of code | More precise specification needed | Possible posting on launchpad.com | ||
Spring 2013 | January / February | Possibly write/refine paper for publication | More precise specification needed | Possible publication venues to be identified |
Possible submission of paper, poster to regional, national conference | Not yet scheduled | Venue to be determined |
This time line will be updated regularly throughout the project.
created 24 April 2013 last revised 25 April 2013 |
|
For more information, please contact Henry M. Walker at walker@cs.grinnell.edu. |