<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="http://forum.robosavvy.com/feed.php?f=24&amp;t=13956" />

<title>RoboSavvy Forum</title>
<subtitle>Robosavvy Forum: The largest online community of Humanoid Robot Builders</subtitle>
<link href="http://forum.robosavvy.com/index.php" />
<updated>2014-01-09T01:50:51+01:00</updated>

<author><name><![CDATA[RoboSavvy Forum]]></name></author>
<id>http://forum.robosavvy.com/feed.php?f=24&amp;t=13956</id>
<entry>
<author><name><![CDATA[dfreelan]]></name></author>
<updated>2014-01-09T01:50:51+01:00</updated>
<published>2014-01-09T01:50:51+01:00</published>
<id>http://forum.robosavvy.com/viewtopic.php?t=13956&amp;p=43022#p43022</id>
<link href="http://forum.robosavvy.com/viewtopic.php?t=13956&amp;p=43022#p43022"/>
<title type="html"><![CDATA[Darwin Camera: EMI?]]></title>

<content type="html" xml:base="http://forum.robosavvy.com/viewtopic.php?t=13956&amp;p=43022#p43022"><![CDATA[
Our team is experiencing an issue where the camera likes to cut off  after 1-5 minutes of walking around.<br />We have reason to believe this could be an EMI issue, both because of the error message below:<br /><br /><dl class="codebox"><dt>Code: </dt><dd><code>Jan  7 22:38:27 darwin51 kernel: &#91; 3983.828178&#93; hub 3-0:1.0: port 2 disabled by hub (EMI?), re-enabling...<br />Jan  7 22:38:27 darwin51 kernel: &#91; 3984.036153&#93; usb 3-2: USB disconnect, device number 2<br /></code></dd></dl><br /><br />and also because the cable in the camera is completely un-shielded.<br /><br />I've only been able to fix the camera by rebooting the robot, or plugging the camera out and back in.<br />When turning the camera off with rmmod and turning back on with modprobe, and that doesnt work. After modprobe, dmesg simply tells me it cannot connect to the device.<br /><br /><br />In total, here is my evidence I have to make a conclusion with:<br />1. That silly kernel message<br />2. Cannot replicate this bug with all the software running on the robot and the servos manually turned off (right button)<br />3. Cannot replicate bug with only cognition going (this is the program which queries the camera)<br />4. I have never been able to recreate the bug while holding the robot (putting less strain on the servos)<br />5. (this needs more testing, could just be happenstance) appears to happen faster when the battery is low. seems to last on average longer when a newly charged battery is in. So this might be a voltage problem?<br />6. The only time I replicated this when the robot has been plugged into the wall has been when I also had the battery plugged in.<br />7. never been able to replicate this with only the AC in<br /><br />Has anybody encountered something similar? find out it was something else? Any hardware fixes?<p>Statistics: Posted by <a href="http://forum.robosavvy.com/memberlist.php?mode=viewprofile&amp;u=7688">dfreelan</a> — Thu Jan 09, 2014 1:50 am</p><hr />
]]></content>
</entry>
</feed>