<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Open Source Hardware and Industry</title>
	<link>http://squid-labs.com/blog/?p=17</link>
	<description>Squid Labs Blog</description>
	<pubDate>Tue, 07 Sep 2010 18:10:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: J.S.T. Katz</title>
		<link>http://squid-labs.com/blog/?p=17#comment-261</link>
		<pubDate>Wed, 03 May 2006 19:19:58 +0000</pubDate>
		<guid>http://squid-labs.com/blog/?p=17#comment-261</guid>
					<description>What are the tools needed to assist in hardware development for non-professionals? I for one would love to see good options for a logic analyzer(something like the digiview) or oscope using the computer as a front end, or an AVR studio interoperable ICE clone,  I dont see why these couldn't be realized with a huge reduction in cost over proprietary or even some kit options(especially with the dropping cost/rising performance of DSPs).  What else would people out there find useful? 

A lot of these costs are considered expected cost of entrance to work on these types of projects, you'll have a much larger base of people able to work on and understand future projects if you can create an affordable standardized toolset.</description>
		<content:encoded><![CDATA[<p>What are the tools needed to assist in hardware development for non-professionals? I for one would love to see good options for a logic analyzer(something like the digiview) or oscope using the computer as a front end, or an AVR studio interoperable ICE clone,  I dont see why these couldn&#8217;t be realized with a huge reduction in cost over proprietary or even some kit options(especially with the dropping cost/rising performance of DSPs).  What else would people out there find useful? </p>
<p>A lot of these costs are considered expected cost of entrance to work on these types of projects, you&#8217;ll have a much larger base of people able to work on and understand future projects if you can create an affordable standardized toolset.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Roy</title>
		<link>http://squid-labs.com/blog/?p=17#comment-13</link>
		<pubDate>Fri, 24 Mar 2006 21:30:46 +0000</pubDate>
		<guid>http://squid-labs.com/blog/?p=17#comment-13</guid>
					<description>What a great article, a coherent argument for open design.

There have been examples in the past, obviously and like you say Dan L, its really a reaction to open source software that means that we have to define the same for hardware/products.

For me the fundamental characteristic of any open source movement is the sharing of instructions to make a product, which in the hardware case is almost always restricted by patents. There are numerous examples of open source collaborative projects already existing on the web (I've been logging the ones I find on my blog, zero-waste.blogspot.com) although they do tend to be lo-tech for the very reason of ease of replication. But there are some with bigger ambitions. I guess that things are sure to become more hi-tech as the ability to synthesise products directly from computer becomes more ubiquitous. In the mean time, all that need be done is to share the existing source code: engineering drawings and schematics, sketches, anything that defines the creation of an object and you've got an open source project. There are plenty  of people who can interpret them, and I don't think it need necessarily be any harder than it is for software programmers.

Collaboration and the tools needed for it is indeed an area which needs to be developed, but I think instructables and the like are already close. Patents, as you say are an existing standard for communicating concept but a nightmare to navigate. The media needed is already there whether it be engineering drawings, CAD files, photographs, but it is a meaningful framework in which to exchange them that is needed. A kind of sourceForge equivalent perhaps? (he said, not knowing sourceforge that well at all)</description>
		<content:encoded><![CDATA[<p>What a great article, a coherent argument for open design.</p>
<p>There have been examples in the past, obviously and like you say Dan L, its really a reaction to open source software that means that we have to define the same for hardware/products.</p>
<p>For me the fundamental characteristic of any open source movement is the sharing of instructions to make a product, which in the hardware case is almost always restricted by patents. There are numerous examples of open source collaborative projects already existing on the web (I&#8217;ve been logging the ones I find on my blog, zero-waste.blogspot.com) although they do tend to be lo-tech for the very reason of ease of replication. But there are some with bigger ambitions. I guess that things are sure to become more hi-tech as the ability to synthesise products directly from computer becomes more ubiquitous. In the mean time, all that need be done is to share the existing source code: engineering drawings and schematics, sketches, anything that defines the creation of an object and you&#8217;ve got an open source project. There are plenty  of people who can interpret them, and I don&#8217;t think it need necessarily be any harder than it is for software programmers.</p>
<p>Collaboration and the tools needed for it is indeed an area which needs to be developed, but I think instructables and the like are already close. Patents, as you say are an existing standard for communicating concept but a nightmare to navigate. The media needed is already there whether it be engineering drawings, CAD files, photographs, but it is a meaningful framework in which to exchange them that is needed. A kind of sourceForge equivalent perhaps? (he said, not knowing sourceforge that well at all)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: dan</title>
		<link>http://squid-labs.com/blog/?p=17#comment-9</link>
		<pubDate>Thu, 23 Mar 2006 18:12:35 +0000</pubDate>
		<guid>http://squid-labs.com/blog/?p=17#comment-9</guid>
					<description>pt - you already are!  anything where you've explained how to do it is open source.  probably you are thinking &quot;something with significant intellectual property&quot;, and even then you've had lots of stuff where the CAD files, firmware, etc. are published by the project author.  the point where we're not seeing much yet on the open source hardware side is:
(1) collaborative projects
(2) projects that are at the forefront of technology</description>
		<content:encoded><![CDATA[<p>pt - you already are!  anything where you&#8217;ve explained how to do it is open source.  probably you are thinking &#8220;something with significant intellectual property&#8221;, and even then you&#8217;ve had lots of stuff where the CAD files, firmware, etc. are published by the project author.  the point where we&#8217;re not seeing much yet on the open source hardware side is:<br />
(1) collaborative projects<br />
(2) projects that are at the forefront of technology
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: pt</title>
		<link>http://squid-labs.com/blog/?p=17#comment-8</link>
		<pubDate>Thu, 23 Mar 2006 17:44:40 +0000</pubDate>
		<guid>http://squid-labs.com/blog/?p=17#comment-8</guid>
					<description>nicely done. i think i should start a listing/feature on make about open source hardware projects.</description>
		<content:encoded><![CDATA[<p>nicely done. i think i should start a listing/feature on make about open source hardware projects.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dan Lockton</title>
		<link>http://squid-labs.com/blog/?p=17#comment-7</link>
		<pubDate>Thu, 23 Mar 2006 15:45:27 +0000</pubDate>
		<guid>http://squid-labs.com/blog/?p=17#comment-7</guid>
					<description>Very interesting subject. Forgive me if this is really obvious, but it did occur to me a while ago that, in effect, patents (on hardware) go some way towards 'opening up' complex technology almost in an open-source way - except that you're prohibited from doing anything commercial with the information!

Nevertheless, there's nothing to stop prospective innovators learning from reading patents: understanding how devices work, and spotting improvements that could be made, and either waiting until the patents expire, or applying the knowledge gained in another field entirely.

As you say, &quot;Furthermore, hardware unlike software must be manufactured,&quot; and I guess this means that the barriers to entry for open source hardware are much higher than for software. Anyone can copy and tweak and deploy open source software with nothing more than a computer, but until everyone has multi-functional desktop RP machines and CNC mills it's a lot more difficult to do that with actual designs. You can provide the instructions (and that's why Instructables is so great) but it still requires more equipment/time/capability to follow those instructions than it would do for software.

OK, so how can a business model be developed? Based on that 'barrier to entry' point, I think it comes down to this: even if every consumer product you buy had a full circuit schematic on the box, and a manual detailing exactly how to build it, most people would keep buying the products. They can't make them themselves, or they can't be bothered. They certainly are no threat to the manufactruers. 

In the cases where vast numbers of people do enjoy tinkering with the products they buy (e.g. cars), it was certainly true until a few years ago that all the secrets of the car could be revealed with a bit of dismantling &amp;#38; rebuilding (and the aid of a helpful manual). And plenty of people have built businesses based on this: tuning, customising, restoring, rebuilding vehicles, all based on knowledge gained from examination and dismantling of existing hardware. Want collaborative development? Look at any classic car club or autojumble. 

In this sense, we've had open source hardware for years staring us in the face, just as I believe the 'free software' idea only occurred to Richard Stallman when he saw that software was suddenly being locked up. Up to that point it had been assumed that code would be human-readable.

Pretty much all innovation relies on prior art, hence the ability to examine and understand that prior art. In the sense, all business that is based on innovation must be based on prior art. Therefore most 'traditional' hardware businesses are to a large extent 'open source', even if there is an artificial restriction in terms of patents.</description>
		<content:encoded><![CDATA[<p>Very interesting subject. Forgive me if this is really obvious, but it did occur to me a while ago that, in effect, patents (on hardware) go some way towards &#8216;opening up&#8217; complex technology almost in an open-source way - except that you&#8217;re prohibited from doing anything commercial with the information!</p>
<p>Nevertheless, there&#8217;s nothing to stop prospective innovators learning from reading patents: understanding how devices work, and spotting improvements that could be made, and either waiting until the patents expire, or applying the knowledge gained in another field entirely.</p>
<p>As you say, &#8220;Furthermore, hardware unlike software must be manufactured,&#8221; and I guess this means that the barriers to entry for open source hardware are much higher than for software. Anyone can copy and tweak and deploy open source software with nothing more than a computer, but until everyone has multi-functional desktop RP machines and CNC mills it&#8217;s a lot more difficult to do that with actual designs. You can provide the instructions (and that&#8217;s why Instructables is so great) but it still requires more equipment/time/capability to follow those instructions than it would do for software.</p>
<p>OK, so how can a business model be developed? Based on that &#8216;barrier to entry&#8217; point, I think it comes down to this: even if every consumer product you buy had a full circuit schematic on the box, and a manual detailing exactly how to build it, most people would keep buying the products. They can&#8217;t make them themselves, or they can&#8217;t be bothered. They certainly are no threat to the manufactruers. </p>
<p>In the cases where vast numbers of people do enjoy tinkering with the products they buy (e.g. cars), it was certainly true until a few years ago that all the secrets of the car could be revealed with a bit of dismantling &amp; rebuilding (and the aid of a helpful manual). And plenty of people have built businesses based on this: tuning, customising, restoring, rebuilding vehicles, all based on knowledge gained from examination and dismantling of existing hardware. Want collaborative development? Look at any classic car club or autojumble. </p>
<p>In this sense, we&#8217;ve had open source hardware for years staring us in the face, just as I believe the &#8216;free software&#8217; idea only occurred to Richard Stallman when he saw that software was suddenly being locked up. Up to that point it had been assumed that code would be human-readable.</p>
<p>Pretty much all innovation relies on prior art, hence the ability to examine and understand that prior art. In the sense, all business that is based on innovation must be based on prior art. Therefore most &#8216;traditional&#8217; hardware businesses are to a large extent &#8216;open source&#8217;, even if there is an artificial restriction in terms of patents.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
