<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Willow Garage Robotics</title>
	<atom:link href="http://www.foresight.org/nanodot/?feed=rss2&#038;p=3121" rel="self" type="application/rss+xml" />
	<link>http://www.foresight.org/nanodot/?p=3121</link>
	<description>examining transformative technology</description>
	<lastBuildDate>Wed, 03 Apr 2013 18:23:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Dan Donahoe</title>
		<link>http://www.foresight.org/nanodot/?p=3121#comment-859485</link>
		<dc:creator>Dan Donahoe</dc:creator>
		<pubDate>Fri, 03 Jul 2009 15:09:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=3121#comment-859485</guid>
		<description>Nice video.</description>
		<content:encoded><![CDATA[<p>Nice video.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Monson</title>
		<link>http://www.foresight.org/nanodot/?p=3121#comment-859463</link>
		<dc:creator>Nathan Monson</dc:creator>
		<pubDate>Fri, 26 Jun 2009 20:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=3121#comment-859463</guid>
		<description>CAD and PCB designs are available on their public SVN.  But I don&#039;t think their hardware strategy includes a 10,000 step Instructables site for building your own PR2 robot.  ;)  PR2 costs more than a house, and requires multidisciplinary expertise to build your own.

Instead, I think their strategy is to loan actual PR2s to researchers for free, in return for their software enhancements.

As for the software, it runs on much cheaper platforms.  You don&#039;t need a PR2 to play along at home.  You can glue a laptop to a Roomba, buy a &lt;$2K laser scanner, and have their OS up and running pretty quickly.</description>
		<content:encoded><![CDATA[<p>CAD and PCB designs are available on their public SVN.  But I don&#8217;t think their hardware strategy includes a 10,000 step Instructables site for building your own PR2 robot.  <img src='http://www.foresight.org/nanodot/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />   PR2 costs more than a house, and requires multidisciplinary expertise to build your own.</p>
<p>Instead, I think their strategy is to loan actual PR2s to researchers for free, in return for their software enhancements.</p>
<p>As for the software, it runs on much cheaper platforms.  You don&#8217;t need a PR2 to play along at home.  You can glue a laptop to a Roomba, buy a &lt;$2K laser scanner, and have their OS up and running pretty quickly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Conley</title>
		<link>http://www.foresight.org/nanodot/?p=3121#comment-859460</link>
		<dc:creator>Ken Conley</dc:creator>
		<pubDate>Fri, 26 Jun 2009 17:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=3121#comment-859460</guid>
		<description>Thanks for the writeup of Steve&#039;s talk. To answer the question about open hardware, It&#039;s designed to be very hackable: we intend for people to modify the sensor packages on the package to their own needs and we also have been working with other hand manufacturers to provide some compatibility there as well. Our software is also intended to be generalizable to other robot hardware/sensors and has already been ported several times. But the robot isn&#039;t open in the open source sense like our software, mainly because even if we went through the effort of releasing every spec, its hard to imagine that others would benefit: there are too many parts with too high of a price tag for others to easily manufacture. That&#039;s one of the reasons why we&#039;re loaning out ten of the PR2s for others to use, i.e. making it as open as possible by providing access.</description>
		<content:encoded><![CDATA[<p>Thanks for the writeup of Steve&#8217;s talk. To answer the question about open hardware, It&#8217;s designed to be very hackable: we intend for people to modify the sensor packages on the package to their own needs and we also have been working with other hand manufacturers to provide some compatibility there as well. Our software is also intended to be generalizable to other robot hardware/sensors and has already been ported several times. But the robot isn&#8217;t open in the open source sense like our software, mainly because even if we went through the effort of releasing every spec, its hard to imagine that others would benefit: there are too many parts with too high of a price tag for others to easily manufacture. That&#8217;s one of the reasons why we&#8217;re loaning out ten of the PR2s for others to use, i.e. making it as open as possible by providing access.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Peterson</title>
		<link>http://www.foresight.org/nanodot/?p=3121#comment-859454</link>
		<dc:creator>Chris Peterson</dc:creator>
		<pubDate>Wed, 24 Jun 2009 18:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=3121#comment-859454</guid>
		<description>The software is open source.  What about the hardware: is it open as well?</description>
		<content:encoded><![CDATA[<p>The software is open source.  What about the hardware: is it open as well?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Willow Garage Robotics &#124; Everything News Portal!</title>
		<link>http://www.foresight.org/nanodot/?p=3121#comment-859452</link>
		<dc:creator>Willow Garage Robotics &#124; Everything News Portal!</dc:creator>
		<pubDate>Wed, 24 Jun 2009 10:46:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.foresight.org/nanodot/?p=3121#comment-859452</guid>
		<description>[...] Read more &#8230;  [...]</description>
		<content:encoded><![CDATA[<p>[...] Read more &#8230;  [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>