Colony: Issueshttps://roboticsclub.org/redmine/https://roboticsclub.org/redmine/redmine/favicon.ico2009-12-18T11:55:07ZRobotics Club
Redmine Task #964 (Feedback): investigate new AVR simulator?https://roboticsclub.org/redmine/issues/9642009-12-18T11:55:07ZRyan Cahoonrcahoon@andrew.cmu.edu
<p>Just posted on LadyADA:</p>
<p><a class="external" href="http://www.adafruit.com/blog/2009/12/17/simavr-avr-simulator/">http://www.adafruit.com/blog/2009/12/17/simavr-avr-simulator/</a></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 #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> Enhancement #798 (Assigned): get all the library inti's and functions to behavehttps://roboticsclub.org/redmine/issues/7982009-10-21T23:08:08ZBrad Neuman
<p>multiple init calls should not cause undefined behavior</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 #693 (Assigned): Better sanity check for invalid BOM typehttps://roboticsclub.org/redmine/issues/6932009-10-02T21:56:45ZKevin Woo
<p>assert would be nice</p> Enhancement #577 (Assigned): Improve library error codeshttps://roboticsclub.org/redmine/issues/5772009-09-11T01:22:12ZBrad Neuman
<p>Each library function should check a global value to see if the library is properly init'd, if not it should return an error code</p> Bug #575 (Assigned): Battery Level Indicatorhttps://roboticsclub.org/redmine/issues/5752009-09-11T00:20:55ZAustin Buchanabuchan@andrew.cmu.edu
<p>Make an battery level indicator behavior using the orbs</p> Task #390 (Feedback): Investigate how to use the JTAG ICEhttps://roboticsclub.org/redmine/issues/3902009-03-27T21:02:49ZKevin Woo
<p>We want to do profiling of functions</p> Task #368 (Assigned): Make sure all robots program the correct xbee id from eepromhttps://roboticsclub.org/redmine/issues/3682009-03-20T21:07:48ZKevin Woo
<p>EEPROMs are all programmed and code to read it is fine. We just need to make sure the wireless code does it.</p> Enhancement #320 (New): Automatically update robot status page with testing stationhttps://roboticsclub.org/redmine/issues/3202009-01-23T22:55:06ZKevin Woo
<p>Update all the status so we don't have to. The robot status on the Trac.</p> Enhancement #237 (Feedback): Design Dragonfly Replacement Boardhttps://roboticsclub.org/redmine/issues/2372008-02-08T17:51:15ZKevin Woo
Things to fix:
<ul>
<li>No critical IO or communications lines over the motors</li>
<li>ARCHs integrated into board
<ul>
<li>Built in I2C to ARCHs</li>
</ul>
</li>
<li>Integrated SPI hookups to encoder connectors
<ul>
<li>Separate chip select lines</li>
<li>CLK and MISO/MOSI from SPI module</li>
</ul>
</li>
<li>16MHz External clock</li>
<li>Fix FTDI chip to use 3.3v VCCIO instead of 5V</li>
<li>External pull ups for buttons</li>
<li>Cheaper range finders? Perhaps Digital ones.</li>
</ul>