Colony Scout: Issueshttps://roboticsclub.org/redmine/https://roboticsclub.org/redmine/redmine/favicon.ico2013-10-22T21:00:58ZRobotics Club
Redmine Task #2211 (Fixed): List of Electric Parts for Back of Scouthttps://roboticsclub.org/redmine/issues/22112013-10-22T21:00:58ZRachael Ortega
<p>Mechanical team needs a list of all the electrical parts to be put on the back of the Scout. We would like a list, dimensions, and number of wires.</p> Bug #2169 (Fixed): FL Encoder Ticks Backwardhttps://roboticsclub.org/redmine/issues/21692013-03-31T18:31:16ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Colony software has determined that the front left encoder is backward.</p>
<p>This has been fixed in software, but should be fixed in hardware next time the scout is taken apart.</p>
<p>Lots of wires in there. Don't know how you guys keep them all straight.</p> Bug #2138 (Fixed): Look into timestamps in sonarhttps://roboticsclub.org/redmine/issues/21382013-02-17T19:45:09ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Turns out headers aren't automatically filled in. This may be creating a bug in the sonar code, which relies on timestamps that are probably zeroed out.</p>
<p>We should manually generate timestamps for sonar, and make sure the code around this is consistent.</p> Task #2137 (Wontfix): Add roslaunch scriptshttps://roboticsclub.org/redmine/issues/21372013-02-17T19:26:54ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Once done with other things:</p>
<p>Make a bunch of launch scripts. One of them should start up all the sensor nodes; others should make it easier to run behaviors.</p> Task #2136 (Fixed): Change teleop_on behavior.https://roboticsclub.org/redmine/issues/21362013-02-17T19:14:00ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Change teleop so that the simulator ignores teleop commands if a behavior is running.</p> Task #2135 (Fixed): Remove headers from messageshttps://roboticsclub.org/redmine/issues/21352013-02-17T19:13:19ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Most .msg files have headers, which make it hard to spoof them on command line.</p>
<p>We should get rid of that.</p> Bug #2134 (Fixed): Concurrency Issue with Behavior Overwritehttps://roboticsclub.org/redmine/issues/21342013-02-10T19:38:02ZAlex Zirbelazirbel@andrew.cmu.edu
<p>In BehaviorGUI.py, if you run a new behavior, the rosnode kill used to stop the old behavior will often kill the newly running behavior, causing the new behavior to send a couple /set_motors commands but then die.</p>
<p>Known workaround: pausing and resuming the behavior does get the behavior running again.</p> Bug #2133 (Fixed): Adding scout with an empty name is bad.https://roboticsclub.org/redmine/issues/21332013-01-29T23:05:12ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Because it can't be killed. Don't let it be added.</p> Bug #2132 (Fixed): Delay before motor commands starthttps://roboticsclub.org/redmine/issues/21322013-01-28T23:21:57ZAlex Zirbelazirbel@andrew.cmu.edu
<p>The first motor command rarely works.</p>
<p>Putting a delay before sending any commands is a quickfix, and this could be a decent patch. It would be better to find out why this is happening, though. Maybe we need to add a wait for service call to make sure ROS is set up before we let behaviors run any commands.</p> Bug #2131 (Fixed): Resume button doesn't workhttps://roboticsclub.org/redmine/issues/21312013-01-28T23:20:57ZAlex Zirbelazirbel@andrew.cmu.edu
<p>In the python GUI, the resume button does nothing.</p> Bug #2130 (Fixed): Running a scout then starting teleophttps://roboticsclub.org/redmine/issues/21302013-01-28T23:20:21ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Interaction of teleop and behaviors is bad.</p>
<p>For example, if teleop is on, then the behavior will seem to be bugged, because teleop sends zero motor commands while everything else is still running.</p>
<p>Teleop and behaviors cannot be allowed to run at the same time.</p> Bug #2129 (Fixed): Killing and respawning makes a scout uncontrollablehttps://roboticsclub.org/redmine/issues/21292013-01-28T23:12:27ZAlex Zirbelazirbel@andrew.cmu.edu
<p>1. Create a new scout (ie "testbot")<br />2. Run a behavior on testbot<br />3. Kill testbot via GUI<br />4. Spawn another scout called testbot.</p>
<p>Testbot is now uncontrollable and resumes the behavior of the previous testbot.</p> Bug #2122 (Fixed): Standardize encodershttps://roboticsclub.org/redmine/issues/21222012-11-17T08:35:52ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Encoders currently give 336 ticks/m. They should be giving 363.78. The difference is probably due to rounding errors.</p> Bug #2120 (Wontfix): Remove old teleop and clean up scoutsim folderhttps://roboticsclub.org/redmine/issues/21202012-11-16T22:44:34ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Now that we have baked-in teleop, the old one should go.</p>
<p>Etc.</p> Enhancement #2114 (Wontfix): Make it easier to make new behaviorshttps://roboticsclub.org/redmine/issues/21142012-11-13T00:15:02ZAlex Zirbelazirbel@andrew.cmu.edu
<p>Make the makefile check the behaviors/ folder and compile anything it finds there into a behavior. Auto-generate any lists which need to exist to refer to these behaviors.</p>