Difference between revisions of "RCwiproc"

From RoboJackets Wiki
Jump to navigation Jump to search
(Articles)
(Articles)
Line 27: Line 27:
 
*[http://spinroot.com/spin/Doc/Book91.html Enitre book on protocol design, a bit dated though like 1990 dated]
 
*[http://spinroot.com/spin/Doc/Book91.html Enitre book on protocol design, a bit dated though like 1990 dated]
 
*[http://bwrc.eecs.berkeley.edu/People/Faculty/jan/publications/p124.pdf Berkeley article on wireless protocol design. Gives a real world example of how to design a wireless protocol.]
 
*[http://bwrc.eecs.berkeley.edu/People/Faculty/jan/publications/p124.pdf Berkeley article on wireless protocol design. Gives a real world example of how to design a wireless protocol.]
 +
*[http://www.ohiolink.edu/etd/send-pdf.cgi?ohiou1121356426 Ohio University article. Details an intresting communications method]
  
 
==Links==
 
==Links==
 
[[RCcoms|Wireless Hompage]]
 
[[RCcoms|Wireless Hompage]]

Revision as of 11:40, 27 June 2006

Wireless Protocol

The host will be able to send each robot velocity, direction, and shoot directives, at with the time alloted between each sample of the playing field by the overhead camera. In such way the enitre system (host, camera, and robot) will behave as a real-time system. The robot will send its current error status, battery voltage, wheel velocity, unique ID, and whether or not it has the ball to the host but not in real-time.

Data Rate calculations

100 fps
At least two frames needed to track motion theta
Time per command 20ms
Each robot needs 3 bytes (will change)
6 robots = 18 Bytes
10 bits per Byte (Start bit , 8 data bits, 1 stop bit)
(18 Bytes/20ms)*(10 bits/1 Byte) = 9kbps
Double bit rate for Manchester encoding 18kbps
=19.2Bps baud rate

Articles

Links

Wireless Hompage