Colony: Issueshttps://roboticsclub.org/redmine/https://roboticsclub.org/redmine/redmine/favicon.ico2010-09-03T20:48:27ZRobotics Club
Redmine Bug #1390 (Fixed): Come to decision on wirelesshttps://roboticsclub.org/redmine/issues/13902010-09-03T20:48:27ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Clean up decision on wireless/talk to David if that hasn't happened yet.</p> Bug #960 (Assigned): xbee idhttps://roboticsclub.org/redmine/issues/9602009-12-05T07:05:22ZDavid Schultzdsschult@andrew.cmu.edu
<p>The xbee id should be set to the robot id (which is in the eeprom) on init.</p>
<p>The xbee currently just uses the last stored address in xbee memory, which works most of the time but is not failsafe.</p> Task #950 (Assigned): Wireless - xbee.chttps://roboticsclub.org/redmine/issues/9502009-11-27T17:54:25ZDavid Schultzdsschult@andrew.cmu.edu
<p>integrate serial.c xbee functions into xbee.c, clean up file</p> Task #949 (Fixed): Wireless - common functionshttps://roboticsclub.org/redmine/issues/9492009-11-27T17:53:41ZDavid Schultzdsschult@andrew.cmu.edu
<p>init, terminate, packet group handler registration</p> Task #948 (Fixed): Wireless - receive functionshttps://roboticsclub.org/redmine/issues/9482009-11-27T17:52:38ZDavid Schultzdsschult@andrew.cmu.eduTask #947 (Fixed): Wireless - send wrappers, high level secure ack behaviorhttps://roboticsclub.org/redmine/issues/9472009-11-27T17:47:58ZDavid Schultzdsschult@andrew.cmu.eduTask #946 (Assigned): Wireless - core send, ack functionshttps://roboticsclub.org/redmine/issues/9462009-11-27T17:46:40ZDavid Schultzdsschult@andrew.cmu.eduEnhancement #925 (Assigned): xbee baud rateshttps://roboticsclub.org/redmine/issues/9252009-11-13T19:55:07ZDavid Schultzdsschult@andrew.cmu.edu
<p>Currently, only default of 9600 baud works. Get other rates, specifically 115200, to work.</p> Bug #852 (Assigned): Xbee Documentationhttps://roboticsclub.org/redmine/issues/8522009-10-30T19:41:35ZDan Shopedshope@andrew.cmu.edu
<p>Make a page on wiki w/ Xbee setup/config commands</p>
<p>Link to PDF</p> Bug #790 (Assigned): XBee/Wireless Initializationhttps://roboticsclub.org/redmine/issues/7902009-10-20T01:38:01ZJohn Sextonjsexton@alumni.cmu.edu
<p>XBee and Wireless Init functions seem to conflict. dragonfly_init() appears to call xbee_init() [found in serial.c in libdragonfly], while wl_init() appears to call xbee_lib_init() [found in xbee.c in libwireless]. The two functions appear to be arguing over what to assign a few registers.</p>
<p>We found that to get the XBees to work, xbee_init() needs to be called again after drangonfly_init(), but before wl_basic_init_default() [which basically just calls wl_init()].</p>
<p>We also are not confident that calls to wl_set_channel() are working correctly, or if the channel is getting re-initialized by calls to xbee_init()/xbee_lib_init().</p> Bug #715 (Duplicate): Investigate XBee's on Bots 4 and 6https://roboticsclub.org/redmine/issues/7152009-10-08T01:58:19ZChris Mar
<p>Programs hang on call to wl_basic_do_default()</p> Bug #480 (Worksforme): XBee dongle: undefined output after 0https://roboticsclub.org/redmine/issues/4802009-04-28T15:11:44ZMartin Herrmannmartin@famherrmann.de
<p>When a packet containing a zero byte is received, random data may be output by the dongle. The problem does not seem to occur with an XBee on a Dragonfly board.</p>
<p>For example (hex data):<br />Packet data: 01 02 00 03 04<br />Output by the dongle: 01 02 00 xx yy (where xx and yy are random values)</p>
<p>To look at the data, I used and XBee dongle connected to a Linux machine running GtkTerm in Hex mode.</p>