https://roboticsclub.org/redmine/https://roboticsclub.org/redmine/redmine/favicon.ico2011-10-26T21:50:37ZRobotics ClubColony Scout - Task #1877: Wireless on ARMhttps://roboticsclub.org/redmine/issues/1877?journal_id=45432011-10-26T21:50:37ZBen Wassermanbwasserm@andrew.cmu.edu
<ul><li><strong>Due date</strong> set to <i>11/16/2011</i></li><li><strong>Assignee</strong> set to <i>Ben Wasserman</i></li></ul> Colony Scout - Task #1877: Wireless on ARMhttps://roboticsclub.org/redmine/issues/1877?journal_id=46342011-11-07T23:05:44ZBen Wassermanbwasserm@andrew.cmu.edu
<ul><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul><p>All the wireless will be handled by the AVR, not the ARM. I'm planning on using the library David Schultz and I were writing 2 years ago during Formation Control. I think it should be this way because the Zigbee chip is built into the AVR, and also so we don't bog down the ARM interfacing with it.</p>
<p>We had written most of it, and were in the process of testing. It was fairly reliable, but had some issues that we were still hunting down when the semester ended.</p>
<p>The new library also incorporates TCP-like reliability functionality, but this had not been implemented yet, due to the unresolved bugs in the main functionality. David says that the current state is already more reliable than the current Colony 3 wireless library, but I'd like to try to work out the bugs before trying to implement them. Mostly, I'd like to ensure that the library won't crash or break itself. Once that is done, I'd say move on to reliability features.</p>
<p>Since the interaction of AVR and Zigbee is very similar between Scout and Colony 3, then we can probably do development on the Colony 3 bots before we port it over to Scout.</p>