Slashdot Mirror


Open Source Hardware Approaching Critical Mass

angry tapir writes: The Open Compute Project, which wants to open up hardware the same way Linux opened up software, is starting to tackle its forklift problem. You can't download boxes or racks, so open-source hardware needs a supply chain, said OCP President and Chairman Frank Frankovsky, kicking off the Open Compute Project Summit in San Jose. The companies looking to adopt this kind of gear include some blue-chip names: Bank of America, Goldman Sachs and Capital One are members. The idea is that if a lot of vendors build hardware to OCP specifications, IT departments will have more suppliers to choose from offering gear they can easily bring into their data centers. Standard hardware can also provide more platforms for innovative software, Frankovsky said. Now HP and other vendors are starting to deliver OCP systems in a way the average IT department understands. At the same time, the organization is taking steps to make sure new projects are commercially viable rather than just exercises in technology.

64 comments

  1. I knew I should never by Chrisq · · Score: 4, Funny

    Open Source Hardware Approaching Critical Mass

    I knew I should never have tried 3d printing with plutonium.

    1. Re:I knew I should never by Anonymous Coward · · Score: 1

      Open source therefore means Iran is 2 WEEKS from having the BOMB!

    2. Re:I knew I should never by rossdee · · Score: 1

      Its not that 3D printers use Plutonium, its just that the cartridges cost as much as Plutonium.

  2. One Loongson Per Neckbeard by Anonymous Coward · · Score: 0

    The world owes me for all the free stuff I gave away to anyone who can use it.

  3. OCP? by Anonymous Coward · · Score: 0

    Do they have plans for New Detroit?

    1. Re:OCP? by Anonymous Coward · · Score: 0

      It's called Delta City, numb nuts.

  4. Beautiful Disaster by Anonymous Coward · · Score: 0

    Today seems like a good day to burn a bridge or two
    The one with old wood creaking that would burn away right on cue
    I try to be not like that but some people really suck
    Some people need to get the axing chalk it up to bad luck

    I know a drugstore cowgirl so afraid of getting bored
    She's always running from something so many things ignored
    I might do that stuff if it didn't make me feel like shit
    I'm on some old reality tip so many trips in it

    Beautiful disaster
    Flyin' down the street again
    I tried to keep up
    You wore me out and left me ate up
    Now I wish you all the luck
    You're a butterfly in the wind without a care
    A pretty train crash to me and I can't care
    I do I don't whatever

    I know a drugstore cowgirl so afraid of getting bored
    She's always running from something so many things ignored
    I try to be not like this but I thought it'd make a good song
    There's nothing to see shows over people just move along

    Beautiful disaster
    Flyin' down the street again
    I tried to keep up
    You wore me out and left me ate up
    Now I wish you all the luck
    You're a butterfly in the wind without a care
    A pretty train crash to me and I can't care
    I do I don't whatever

  5. There it goes... by Anonymous Coward · · Score: 0

    Yes, let's get BoA, HP and the others into it so we can screw up OSH.

  6. Patenting by CurryCamel · · Score: 4, Interesting

    With HW going open source, shall we now start hating HW patenting similar to how we hate SW patenting?

    What is the fundamental difference between e.g. python and pyhdl http://pyhdl.net/?
    Or have we (secretly) hated HW patenting all along, just as bad as SW patenting?
    Or is it just the current setup of the patent system that is the problem?

    1. Re:Patenting by Anonymous Coward · · Score: 0

      The people who invented patents are the problem. We need to get rid of them. Join the cult to build a doomsday machine with open source hardware and eradicate all humans. When it's done, so are they!

    2. Re:Patenting by Chrisq · · Score: 1

      The people who invented patents are the problem. We need to get rid of them. Join the cult to build a doomsday machine with open source hardware and eradicate all humans. When it's done, so are they!

      I'd aim at eradicating all life. It is not a huge step for some slime to evolve into patent lawyers.

    3. Re:Patenting by Anonymous Coward · · Score: 0

      One problem for open source hardware is that hardware is typically not covered by copyright. There is a similar protection available for silicon devices though (search for "maskworks"), but the protection is not as strong as copyright.

      This is most likely going to be perfectly fine for people who are satisfied with BSD-like licenses, but for people who like GPL-like licenses this will be a huge problem as it is unclear how the GPL will work on HDL source code. (The FSF even claims in their FAQ that GPL doesn't work for hardware.)

    4. Re:Patenting by Anonymous Coward · · Score: 0

      The FSF even claims in their FAQ that GPL doesn't work for hardware.

      Without testing it in court they can't know that for sure.

      Heck, look at the first sentence of section 1 in GPLv3:

      The "source code" for a work means the preferred form of the work for making modifications to it.

      First of all the preferred form is subjective and dependent on what modification I intend to make. If I want to link with an alternative library the compiled objects may be the preferred form.
      If the project is originally written in perl or brainfuck or any other esoteric language then no preferred form for modification is available and has to be written first.
      With subjective phrasing like that you can't just rely on the judgment of FSF. It has to be tested in court.

    5. Re: Patenting by Anonymous Coward · · Score: 1

      You shouldn't ban patented algorithms. After all, they are used together with systemd by foxconn for their robots.

    6. Re:Patenting by gl4ss · · Score: 1

      we aren't hating on people doing hw patenting?

      most hw patents nowadays are pretty dang trivial or "obvious to people in the trade" - done essentially as copyrighting excercises rather than as disclosure of vital information how the patented device works. furthermore, the same patents don't have enough information to replicate the device anyhow. a modern day car patent wouldn't describe how the car moves and steers but instead would describe that it has chairs to sit in.

      --
      world was created 5 seconds before this post as it is.
    7. Re:Patenting by SpzToid · · Score: 1

      Ars Technica just published an excellent piece on Microsoft's contribution to Open-Source data center designs: http://arstechnica.com/informa...

      If the Facebook's and Microsoft's of the world are being so proactive in this space, it'll only be a matter of time until their lawyer's get to work. That's what they're there for, right? Gotta do something to keep earning those fat retainers.

      --
      You can't be ahead of the curve, if you're stuck in a loop.
    8. Re:Patenting by JaredOfEuropa · · Score: 1

      We (for certain values of "we") hate obvious or overly broad patents, and those exist for hardware as well as software. The purpose of patents is (or at least was) to benefit society. Rewarding inventors with a temporary monopoly in exchange for sharing their inventions is a means to achieve that benefit and not a goal in itself. And the rewards should be for brilliant ideas or difficult/expensive research, not for stuff that anyone can come up with ("obvious to a person skilled in the art").

      --
      If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
    9. Re:Patenting by business_kid · · Score: 1

      Or have we (secretly) hated HW patenting all along, just as bad as SW patenting? Or is it just the current setup of the patent system that is the problem?

      HW patenting isn't as bad. Let me illustrate: The PAL tv colour circuitry had essential patents, many owned by Telefunken. The Japanese competitors could not use these patents in their equipment, so they developed ways around the patents, and, ultimately, better televisions. Unless you're breaking new ground, you can only get a patent to cover direct copies of your device in hardware. One company slavishly copied the day/night car mirror design of another. I worked briefly for the copyists, and their legal advice was that they could copy the circuit exactly. They did. They could not copy the mechanical action, however, and had to avoid using an eccentric to do it. The problem with software patents is that applications of known techniques to new areas are patentable, whereas in fact they really are 'prior art.'

    10. Re:Patenting by Anonymous Coward · · Score: 0

      The difference between software and hardware patents is time to market and what you have to do to even get there.

      HW patents were created to make the lifes of inventors easier as they couldn't push their invention to market as quick as the big dragons and had to show their designs to people that could help with construction and related. These helpers could in turn be part of companies looking to solve the very same problem and then get "inspired" by the inventors sulotion. Patents protected against this xerox inspiration.

      With software on the other hand you are a git push (or favored publishing platform) from publishing. And your project doesn't ever have to leave your computer until it's done.

      If we could make it possible for an individual to be as fast as a megacorp to set up the tool- and manufacturing-chain of an device we would be able to take away patents.

      The other thing patents do is to make you the only one allowed to manufacture something which only leads to monopoly prices and cheap copys from countries that doesn't care about "your silly patents".

      If you didn't have this timelimit but hade suficient op sec*. The dragons would have to either buy the idea from you, steal it (op sec) or wait until they can buy the finished product and then reverseengineer it.

      This is just parts of a personal opinion of mine that is under construction and can actually change if I find good arguments against it.

      If it isn't obvious, I'm strongly against software patents and copyright law. But I'll leave the whys for another wall of test.

      *(don't post pictures of your blueprints on facebook/twitter/whatever)

    11. Re:Patenting by Anonymous Coward · · Score: 0

      It is not a huge step for some slime to evolve into patent lawyers.

      Evolution rarely goes backwards.

  7. open source hardware by Anonymous Coward · · Score: 0

    How can you have open source hardware? Is it just hardware that has the schematics available?

  8. Open source hardware? by sberge · · Score: 3, Insightful

    Can you download their schematics and PCB layouts? Not that it would be terribly useful, but it would bring the use of the term "open source hardware" in line with how others use it.

    1. Re:Open source hardware? by fuzzyfuzzyfungus · · Score: 5, Informative

      As best I can tell, 'open source hardware'(in the sense used by the Open Compute Project, and their ilk, not the sense implied by users of the gear logo, who are much closer to OSS in meaning and intent) is much closer to what would be open/cooperative development of APIs in the software world.

      The Open Compute Project doesn't really care, certainly not enough to compromise the list of vendors willing to work with them; about your PCB layouts, or your firmware code, or your mask rights; but they are very clear that they don't want to pay for your fancy proprietary blade chassis, or get locked into your 'management ecosystem' with your vendor-specific LOM card and management dashboard: they want servers that comply with mechanical and electrical standards that make them interchangeable, and support specific(usually fairly bare-bones; but standard across vendors) hardware management interfaces. They don't care how you do that, or what is inside your box, they just want your box to slot into their infrastructure, rather than attempting to dictate it.

      They definitely aren't 'open hardware' in the GNU sense of 'open' as a moral imperative, and they are only weakly similar to 'open' in the OSS sense of 'open, because it has turned out to be a productive development model as well as allowing internal customization'. They are really much closer to discerning buyers of proprietary components: They don't really care how the black box works, you can keep your secrets if you want; but they want to be in control of what interfaces and features the black box requires and provides. Like buying a GPU: most customers don't care about the silicon, or the firmware, or even the drivers(so long as they are available and not a total pile of shit); but they definitely expect it to support OpenGL, and DirectX if on Windows.

      Given that the Open Compute Project people are mostly large scale operators of servers, this focus isn't really a surprise: OEMs are already pretty good at silicon development(and you'd have to have very specific needs, or substantial talent and fab capability, to beat what you can get off the shelf), and they can fabricate sheet metal and design and stuff PCBs as efficiently as you'd expect given the brutal margins in the business; but (in part because of those brutal margins), they've historically tried to gain control over the customer at the interface/API layer. Their cheap crap simply won't promise, and often won't implement, any mechanical, airflow, electrical, or management interface standardization whatsoever(so even if bolting rack ears to consumer desktops seemed like a plan just crazy enough to work, even getting all of them to PXE boot might not happen); and their classy stuff is usually designed to work best when everything else in the datacenter is also purchased from them or their buddies.

      The OCP and the companies it represents have little to gain by trying to displace the OEMs at building silicon or stuffing PCBs, they just want to change the game so that they call the shots on how the datacenter fits together, and OEMs compete to be chosen to build the interchangeable modules, rather than OEMs using partially or wholly proprietary interfaces in order to drive vendor lock in.

    2. Re:Open source hardware? by sberge · · Score: 1

      Open standards then, not open source.

    3. Re:Open source hardware? by Bing+Tsher+E · · Score: 1

      So basically, it's the same thing as the original IBM PC.

      Where IBM published the schematic diagrams and the source code in commented ASM for the BIOS chip ('poisoning' anybody who read that source code from being able to write a compatible BIOS and necessitating the 'clean room' approach). It was all available in the Technical Reference Manual which anybody could purchase (it was fairly expensive).

      They published this same material, and used all COTS components, all the way up to the PC-AT.

    4. Re:Open source hardware? by Anonymous Coward · · Score: 0

      Both are important. I would say that open standards is a bit more important.
      With an open standard it is possible to write your own implementation, even if you don't have the source.
      With the source but not the standard you don't know if your modifications will break anything.

    5. Re:Open source hardware? by fuzzyfuzzyfungus · · Score: 1

      Pretty much(it's not entirely clear why they even brought 'open source' into it). The only difference I can see, at least from some 'open standards' initiatives in hardware, is that they are particularly interested in avoiding the bane of 'standards based' not-really-standards, which tend to crop up with things like IPMI, DASH, ASF, and so on.

      They don't just want "Well, yeah, it's unique to my hardware and only really works with management consoles I've blessed; but it transfers all its blobs with totally compliant SOAP or whatever!", they are really aiming at 'I shouldn't even know who I bought this from without checking the vendor portion of the MAC address or looking up the serial number". Whether they'll get that, I don't know.

    6. Re:Open source hardware? by Anonymous Coward · · Score: 0

      This is exactly how the Open Compute folks are thinking. They want to control the computers they need for they're business instead of IBM, Oracle, Sun and others pushing their interfaces down their throats.

      We as End Users need to push back at Intel/AMD/Nvidia and the others to help get our desktops into the same condition.

      As an End User I'd love to have hardware with standard API's such as OpenGL support and drivers that actually work instead of the hostile attitude that some companies have. I don't give a damn how the hardware works internally, so long as it does what it's stated to do. If you want to provide more features though a Windows Only Driver, then fine - just follow the standard and if I'm not using Windows, as long as it does what it was selected for, I'm good.

    7. Re: Open source hardware? by joelsherrill · · Score: 1

      I actually saves of of those blue IBM PC Technical References from a garbage bin years ago when someone was cleaning out their office. I think that was also when I got my VAX assembly language guide. :)

  9. Are there open source tools... by amalcolm · · Score: 1

    ...to go with this? I'm aware of various schematic/pcb/mechanical packages, but I've yet to find any FPGA tools such as each vendor gives away to get you to use their devices.

    --
    Time for bed, said Zebedee - boing
    1. Re:Are there open source tools... by sberge · · Score: 2

      There are several open source vhdl / verilog projects, including tools for simulation and synthesis, mapping, placing and routing. Examples: HANA, yosys, Icarus. But I guess you usually get better results with the free-as-in-beer tools from the fpga manufacturers. Which is a shame, since it would be nice to have some open source tools. Although everyone use the same hardware definition languages, it is a pain in the neck to switch between FPGA brands, mostly because the build tools are different and all pretty quirky.

    2. Re:Are there open source tools... by jones_supa · · Score: 1

      You are talking like open sourcing some software would automatically improve its quality.

    3. Re:Are there open source tools... by sberge · · Score: 1

      I have no such illusions. But I would expect open source tools to at least function equally across FPGA brands, at least to the extent that people are able to reverse engineer the bitstream formats of the various architectures. The quality of software in general correlates strongly with the amount of manpower that is put into it, which again correlates strongly with funding. On that note, I think the case could be made that some FPGA producers would benefit from an open source and cross-platform toolstack, particularly those that are not currently market leaders.

  10. Why fret about a supply chain when it can exist on by darkstar019 · · Score: 1

    I am a newbie when it comes to open source hardware but doesn't things like arduino and raspberry pi do not need any chain (owing to non proprietary nature) for distribution and ebay/alibaba can do the rest.

    --
    Fuck Beta
  11. R5 by bloodhawk · · Score: 2

    Perhaps this time they will get Robocop right!

  12. Re:Why fret about a supply chain when it can exist by fisted · · Score: 1

    The raspi is full of proprietary. The ATmega's on the Arduino are not exactly open either, AFAIK (but at least properly documented)

  13. today i learned... by Anonymous Coward · · Score: 0

    Hewlett Packard was still around.

  14. Only to a point by ThatsNotPudding · · Score: 1

    The TLAs will never allow 100% transparency of all the silicon that would expose their mandated backdoors.

  15. Re:Why fret about a supply chain when it can exist by fuzzyfuzzyfungus · · Score: 4, Informative

    The hardware that the OCP, and companies it represents, are interested in tends to be the slightly bigger stuff: They are outfits whose business depends on running a lot of servers and switches and storage; who have gotten large enough that they are trying to push back against the convenient; but expensive and lock-in prone, vendor-specific tools, interfaces, chassis designs, etc. provided by HP, Dell, Cisco, etc.

    When they say that they 'need a supply chain', it's because they are really only interested in partially killing off the traditional enterprise hardware vendor. Being able to call, say, Dell, order however many R730s, with the level of warranty support(from 'statutory minimum, if any, to '4+ years of on-site-within-4-hours) you want; and have them all show up, assembled as ordered, on the loading dock is extremely convenient. Practically essential if you don't want to set up an in-house whitebox assembly line.

    They still want that sort of supplier service: call up, tell them what you want and what, if any, warranty you want, have them arrive at your door; but they want to standardize, as much as possible, hardware between vendors, so you would barely notice whether you are popping in HP, Dell, Supermicro, etc. modules, everything will just fit and they'll all report the same values and respond to the same commands from your management system.

    That's more customer service than hobbyist procurement(which has its place, random pacific rim vendors on ebay have their quirks; but they sure are cheap, and often do have what you require); they just want to be able to get that logistics expertise; but decoupled from the traditional branded faceplates and ill-standardized LOM intefaces and various other delightful aspects of dealing with hardware vendors.

  16. Re:Why fret about a supply chain when it can exist by Bing+Tsher+E · · Score: 1

    You can buy tubes of ATmega chips for a fairly trivial amount, though, well below the cost for finished Arduino boards, and if you chose a through-hole version of the Arduino board, you can even use it like a 'development system' emulator and write all your code for the bare processor chip, use the board like a 'burner' for the chips and drop bare chips into your finished design;.

  17. Why open source hardware is not like software by sjbe · · Score: 5, Informative

    The Open Compute Project, which wants to open up hardware the same way Linux opened up software, is starting to tackle its forklift problem.

    That's not the important problem with open source hardware. Actually making hardware is a fairly straightforward, albeit costly, proposition. I should know since I run a manufacturing company. Give me a design and an adequate amount of cash and I can get any product made and delivered wherever you want it. That's not the real obstacle to open source hardware.

    The important problem is that hardware is (generally) protected by patents whereas software is (generally) protected by copyright. It's easy to write a license (see GPL) that does useful things with copyright law for a product like software. It is highly non-trivial to do the same thing with patents for a product like hardware, especially under a first-to-file patent system. To accomplish something similar to the GPL or BSD license you would have to have someone spend the money to patent a technology and then make it available for community use AND be willing and able (read $$$) to fight to protect the community. This costs a LOT of money, takes a lot of time and at the end of the day you probably cannot use it in any meaningful product without infringing on about 20 other patents from potentially uncooperative companies like Apple or Google, not to mention patent trolls.

    Open source software works because of a happy confluence of circumstances. Software is automatically covered by copyright and there is zero cost to get a copyright. Software also has effectively zero marginal cost to reproduce and can be easily improved by someone skilled in development. Hardware is not automatically protected and the costs to get a patent are substantial. Hardware is not at all cheap to reproduce and while it can be improved, it takes still more money to make and distribute and test those improvements.

    1. Re:Why open source hardware is not like software by itzly · · Score: 1

      Actually making hardware is a fairly straightforward, albeit costly, proposition

      And if it involves any custom ASICs, it's a very costly proposition.

    2. Re:Why open source hardware is not like software by Anonymous Coward · · Score: 0

      The problem is that reusing hardware design is just not as easy as code reuse. Its just not viable to take existing PCB layout or intricate mechanical design and slap in onto some other application as is. That is because mostly you can't just divide hardware into individual black boxes and rearrange at will, the connections matter - a lot.

    3. Re:Why open source hardware is not like software by Kjella · · Score: 2

      That's not the important problem with open source hardware. Actually making hardware is a fairly straightforward, albeit costly, proposition. I should know since I run a manufacturing company. Give me a design and an adequate amount of cash and I can get any product made and delivered wherever you want it. That's not the real obstacle to open source hardware.

      That is fine for customization, but not for being able to inspect what the hardware really does. With some effort people are able to reproduce build environments and prove that yes, this source code leads to this binary. Or you can compile it yourself if you need stronger tin foil. Validating that the chip/board I get back from you is the same blueprint I sent in right down to the circuit level is an equally unfeasible task as manufacturing it myself. Would you really trust a chip design sent to say China or USA for manufacture not to be tampered with? I wouldn't.

      Of course that probably means I shouldn't really trust Intel, AMD, nVidia, any of the chipset, motherboard or graphics card manufacturers either but I see that's a risk I can't do much about. And I'm guessing the cost of doing a tiny production run is so high that it'll lose on price/performance every time compared to just running it on a standard CPU/GPU, even Bitcoin miners need to produce custom ASICs in volume. Which means you can't effectively change anything anyway unless you manage to convince 100-1000 other people to join you.

      --
      Live today, because you never know what tomorrow brings
    4. Re:Why open source hardware is not like software by dcooper_db9 · · Score: 1

      We really need some kind of an organization that we could donate hardware designs to that would guarantee any resulting patents would be open. I have an interface device I've been working on for about 15 years. I can't afford to patent it and certainly can't afford to get it to manufacture. I'd be happy to give away the designs but I don't want some patent troll to claim it. So it sits on the shelf gathering dust.

      --
      I do not block ads. I do block third party scripts.
    5. Re:Why open source hardware is not like software by sjbe · · Score: 1

      We really need some kind of an organization that we could donate hardware designs to that would guarantee any resulting patents would be open.

      Doesn't really solve the core problems. 1) It's expensive to get and defend a patent. If you cannot defend a patent then companies with deep pockets will ignore the patent. If you don't have a patent then companies without deep pockets can copy you too. 2) Even if you get a patent that doesn't guarantee you'll be able to produce a useful product without infringing on other patents. Lots of tech products simply cannot be produced without cross-licensing agreements. 3) Manufacturing hardware is expensive even without worrying about patents. Software can be manufactured very cheaply - almost for free. Hardware requires a credible business model and substantial capital investment for even the simplest of products.

      I have an interface device I've been working on for about 15 years. I can't afford to patent it and certainly can't afford to get it to manufacture.

      No disrespect intended (seriously!) but if you cannot afford to get it patented then I have to wonder if it is terribly valuable. Patents cost a few thousand dollars. Costly enough to keep the casual out but it's not a prohibitive amount of money. Defending the patent on the other hand can be very expensive if it is something that others might care to copy. It's not terribly hard to get financing to patent and produce a product with some meaningful market value.

    6. Re:Why open source hardware is not like software by dcooper_db9 · · Score: 1

      Doesn't really solve the core problems. 1) It's expensive to get and defend a patent. If you cannot defend a patent then companies with deep pockets will ignore the patent.

      I'm happy to have people ignore the patent if that were possible. I just don't want someone to claim the patent and then charge others to use it.

      2) Even if you get a patent that doesn't guarantee you'll be able to produce a useful product without infringing on other patents. Lots of tech products simply cannot be produced without cross-licensing agreements.

      I was really hoping there was some way the donatee could fill this role.

      3) Manufacturing hardware is expensive even without worrying about patents. Software can be manufactured very cheaply - almost for free. Hardware requires a credible business model and substantial capital investment for even the simplest of products.

      Agreed. But I think the need for all that is driven by the licensing issues. There's simply no way to put hardware designs into the commons. You can't copyleft a patent.

      No disrespect intended (seriously!) but if you cannot afford to get it patented then I have to wonder if it is terribly valuable. Patents cost a few thousand dollars. Costly enough to keep the casual out but it's not a prohibitive amount of money. Defending the patent on the other hand can be very expensive if it is something that others might care to copy. It's not terribly hard to get financing to patent and produce a product with some meaningful market value.

      None taken. I think it would be useful to a lot of people but I have no interest in patenting it for my own profit. It doesn't make sense to pay $2000 to patent something unless you're going to make your money back. I guess I'm suggesting that a non-profit could patent and protect the donated hardware designs.

      --
      I do not block ads. I do block third party scripts.
    7. Re:Why open source hardware is not like software by Anonymous Coward · · Score: 0

      Manufacturing hardware is expensive even without worrying about patents. Software can be manufactured very cheaply - almost for free. Hardware requires a credible business model and substantial capital investment for even the simplest of products.

      This need not be true.

      There are products which have expensive tooling, like injection molded plastic parts; and there are products that can be made inexpensively at the click of a button, like water-jet cut metal parts, or CNC wirebending.

      Bare electronics (populated PCBs) are somewhere in the middle. PCBs are made every day in one-off or short-runs at the click of a button, as the production processes are mostly maskless now, and a manufacturer doesn't care if it's the same of different design as long as it has the same number of layers and the same other process parameters. Component placement is a bigger deal because it takes on average 30 minutes* to setup an SMT line for a new production run. Testing can be very expensive or not very expensive at all, depending on how custom it is, and how much "Design For Test" was done upfront.

      Open electronic projects that consist of PCB + bag of components can be very cheap to produce. But then it depends on the skill of the customer to solder and assemble it correctly.

      The problem I see in a lot of open source hardware projects is a lack of value engineering (Actually I see this with bloated inefficient opensource software too). I don't know if it comes from ignorance of low-cost manufacturing methods like stamping, waterjet cutting and CNC bending, but whatever the reason, I so often see open source or kickstarter projects which call for expensive injection molded parts, machined aluminum parts or just expensive or unnecessary parts generally.

      * I used to work for an SMT manufacturer, so I know this is accurate for production processes. We didn't have any prototype scale machines, so they might be faster to setup.

    8. Re:Why open source hardware is not like software by Anonymous Coward · · Score: 0

      Agreed. But I think the need for all that is driven by the licensing issues. There's simply no way to put hardware designs into the commons. You can't copyleft a patent.

      Copyleft is not the commons. It's an attempt to force other people to put THEIR hard work into copyleft-not-commons.

      It is entirely easy to put patents into the commons. Infact it is REQUIRED BY LAW that national labs like Sandia and Lawrence Livermore place their patents into the commons.

      Patents even put themselves in the commons after 20 years in most cases. Unlike copyright (as wasn't intended by the framers of the constitution).

      Most of the hardware in the world is in the commons. My espresso machine is in the commons. My drill press is in the commons. My milling machine is in the commons. My screwdrivers, chisels, hammers, spanners and so on are all in the commons. Most CMOS logic families are in the commons. Most standard electrical connectors are in the commons. Ethernet is pretty much in the commons. RS232, RS485, RS488, LVDS, PECL and so on are all in the commons.

      Most of the business and industry in the United States, and around the world is producing products and services whose technology has entered the public domain.

      So I don't really know what you or these "open hardware" guys are talking about.

    9. Re:Why open source hardware is not like software by sjbe · · Score: 1

      I was really hoping there was some way the donatee could fill this role.

      Kind of a catch-22 there. If the donatee is to defend the patent they need to have a revenue stream to do so which presumably would have to come from the product which (probably) necessarily requires that they exclude others from using it. Not really sure how to resolve that conundrum. Patents were designed to combat the Free Rider Problem but in this case the economics of the patent system interfere with the ability of people to put something in the public sphere and keep it there in a manner similar to copyleft.

      None taken. I think it would be useful to a lot of people but I have no interest in patenting it for my own profit. It doesn't make sense to pay $2000 to patent something unless you're going to make your money back. I guess I'm suggesting that a non-profit could patent and protect the donated hardware designs.

      Out of curiosity, what sort of product is it? What does it do in general? You don't have to tell me all the gory details but you've piqued my interest.

    10. Re:Why open source hardware is not like software by sjbe · · Score: 1

      There are products which have expensive tooling, like injection molded plastic parts; and there are products that can be made inexpensively at the click of a button, like water-jet cut metal parts, or CNC wirebending.

      I'm an accountant and an engineer and I run a manufacturing company. There is no such thing as pushbutton manufacturing. It does not exist. And even if it did it would not be cheap. Nothing can be made "inexpensively at the click of a button" unless you are not accounting for all the costs involved. There is FAR more to it than merely the cost of direct manufacturing. Injection molded plastic parts require very expensive die sets and molding machines plus design and engineering time, machine operator time, post processing and more. Not to mention overhead and materials cost. You can usually get the unit cost to be low with enough volume but the up front capital costs involved are not trivial.

      My company deals in small volume production a lot and we cannot really do anything for less than about $500. Even the most basic of production has enough overhead and setup cost that we would lose money on anything smaller than that even if the actual direct manufacturing costs are low.

      The problem I see in a lot of open source hardware projects is a lack of value engineering

      That's because the people doing it usually have a particular domain expertise and have little to no idea about the other domains involved. People that are good at product design tend to be rather terrible at tooling and process engineering and vice-versa. My company manufactures wire harnesses as a contract manufacturer. Most of the designs we see were designed by mechanical engineers with no particular expertise in electronics or process engineering. They also usually do not understand the particular details involved in wire harness manufacturing. As a result the designs are usually flawed in some way and often are too expensive or even cannot be easily made as designed. I'll see things like gold-plated terminals being specified when tin would do just fine for 1/10th the cost.

    11. Re:Why open source hardware is not like software by dcooper_db9 · · Score: 1

      I was really hoping there was some way the donatee could fill this role.

      Kind of a catch-22 there. If the donatee is to defend the patent they need to have a revenue stream to do so which presumably would have to come from the product which (probably) necessarily requires that they exclude others from using it. Not really sure how to resolve that conundrum. Patents were designed to combat the Free Rider Problem but in this case the economics of the patent system interfere with the ability of people to put something in the public sphere and keep it there in a manner similar to copyleft.

      My theory is that some companies would have an interest in fostering an environment where patents could be developed for the common good. Perhaps if it's worthwhile to back a software non-aggression pact it might also be worthwhile to back an organization that independent inventors could donate their designs to. Somewhere I could send my designs to knowing that any resulting patents would be available to anyone to use.

      Out of curiosity, what sort of product is it? What does it do in general? You don't have to tell me all the gory details but you've piqued my interest.

      I'm trying to figure out how I can answer that question. There's nothing about the hardware itself that's particularly sophisticated. It uses technology that was invented decades ago and any patents would have long since expired.

      The opportunities here are not in the hardware but in designing applications to interface with it. The problem is that in today's world it's possible to patent the application of an idea. My concern isn't that someone else could be the first to bring this to market. It's that someone else could patent the idea and prevent anyone else from exploiting it.

      --
      I do not block ads. I do block third party scripts.
  18. Re:Why fret about a supply chain when it can exist by Anonymous Coward · · Score: 0

    You can buy tubes of ATmega chips for a fairly trivial amount

    The ATmega chips are still proprietary and blackboxed. There is a documentation for normal functionality, but the debug protocol isn't very well documented. The regular developer can't really know if the chip contains undocumented ROM areas or if program readout is possible through the debug interface in some way even if it is supposed to be deactivated with fuse bits.

  19. Tooling in general is expensive by sjbe · · Score: 5, Informative

    And if it involves any custom ASICs, it's a very costly proposition.

    It's not just ASICs. Any hardware that would involve custom tooling tends to be VERY expensive. I'm getting a quote right now on a very simple custom molded plastic connector which we are going to produce in modest volumes. The tooling is basically a piece of CNC milled aluminum and it will cost us about $8000. This is to produce a connector that will sell for about $1.00 each and we might make $0.10 profit per unit. That cost doesn't include labor, raw materials, the cost of the machine the tooling will run on, overhead, or delivery costs.

    Everyone is going on and on about 3D printing and it is super cool and useful but not the way a lot of people think. 3D printing is OUTRAGEOUSLY expensive for any kind of volume manufacturing. It eliminates setup costs but the cost/unit of production is far, far higher than with other techniques. If the production volume is sufficient to justify tooling a process like injection molding can produce plastic parts far cheaper than 3D printing could ever hope to achieve. The part that I mention above if I were to have it 3D printed would cost about $40/unit and I couldn't get more than a handful made per day.

    Manufacturing isn't cheap or easy. Software guys (understandably) tend to thing everything works like software when in fact very few industries even remotely resemble software. They tend to fall into the trap of having a hammer and thinking every problem is a nail. Manufacturing hardware could not be more different.

    1. Re:Tooling in general is expensive by Anonymous Coward · · Score: 0

      Manufacturing isn't cheap or easy. Software guys (understandably) tend to thing everything works like software when in fact very few industries even remotely resemble software. They tend to fall into the trap of having a hammer and thinking every problem is a nail. Manufacturing hardware could not be more different.

      Now there is some food for thought for the many process people driving quality concepts into software engineering, concepts that have been developed to serve mass manufacturing. Meanwhile, the low capital service industry which is has better models for software development don't get the same attention for itself. Perhaps it's another money talks, bullshit walks kind of situation.

    2. Re:Tooling in general is expensive by snadrus · · Score: 1

      I thought manufacturers would use 3D printing to create custom tooling. It may not be as reliable, but would have cheaper replacement cost.

      --
      Science & open-source build trust from peer review. Learn systems you can trust.
    3. Re:Tooling in general is expensive by sjbe · · Score: 1

      I thought manufacturers would use 3D printing to create custom tooling.

      Maybe someday but not anytime soon. The tooling we need is made from hardened steel. Even if there were a 3D printer that could make it (there isn't) the cost of the machine would be astronomical right now. We'd have to create a LOT of custom tooling to justify the machine cost even if it were possible. In 10-20 years? Maybe...

    4. Re:Tooling in general is expensive by Anonymous Coward · · Score: 0

      The tooling is basically a piece of CNC milled aluminum and it will cost us about $8000.

      The tooling we need is made from hardened steel.

      Wait, you just said in your previous post that your tooling was made from milled aluminum, now you say hardened steel, which is it?

      There is additive manufacturing processes in aluminum and titanium, but I would still go with milling for producing injection molds. Almost by definition, any injection mold can be made via milling or other subtractive processes, as the mold needs to separate to release the finished part, so each mold die needs to be convex (the exception being peel-out silicone rubber molds).

      If the tooling is costing $8000, it's either fucking massive, or you're counting the design cost in addition to the machining. Design for injection molding or press forming is something that can and is being automated.

      I do some work as a mechanical engineer* and I do some work in VLSI and FPGA, and my experience is that most existing mechanical tools are batfuckstupid. Things like Solidworks and Autodesk Inventor work from the middle. They don't work from design requirements and elaborate towards final part dimensions (top down). They don't work from available materials and technology towards a manufacturable solution (bottom up). They get stuck in the middle with both the design requirements AND the manufacturing requirements left out and needing to be estimated by the user, which can lead to failures on both ends: parts which don't meet requirements and can't be made.

      In VLSI in contrast everything is top-down; you specify the required behavior, then specify the logical implementation, then the tools synthesize the rest of the specification and check the result against the specified behavioral model. You simply would never get there in mechanical engineering if you had to specify 100 million parts in a mechanism and how they are assembled, as the tools require you to micromanage every single part. It's the equivalent to programming in assembler without macros (or with astoundingly primitive macros with Inventor's iPart system).

      I've recently been working on some systems which use model driven approaches to design mechanical parts, but it's painful and slow going, as the entire industry revolves around proprietary software and standards (STEP anyone? Pay the Swiss 10k Francs.), and the open source tools (BRLCad, OpenCascade, FreeCAD, etc.) are cumbersome and in much ways attempting to clone the poor design of commercial tools rather than innovate based on model driven workflows. Every mechanical engineer I know has tables of equations and rules of thumb, but instead of the machine taking these into account and integrating these equations and rules into the design process and mechanically iterating towards a solution, the user is forced to perform these calculations by hand or with external tools, and then put the modified design back into the system.

      And for purely software guys: Mechanical engineering is not just about the part; you also need to design the process or tool that produces it. Designing an airplane is 1/10th about the airplane and 9/10th about the factory and process that builds it. It's as if every time you wrote a program, you had to write the compiler, linker and debugger for it at the same time. This is the level of sophistication that most mechanical engineering is at today.

      *Not a qualified engineer, but I get the job done.

    5. Re:Tooling in general is expensive by sjbe · · Score: 1

      Wait, you just said in your previous post that your tooling was made from milled aluminum, now you say hardened steel, which is it?

      Different tooling. We have presses that use hardened steel for crimping terminals. We have other tooling for moldings that uses aluminum. We have still other tooling that is made from other materials.

      There is additive manufacturing processes in aluminum and titanium, but I would still go with milling for producing injection molds

      Nothing affordable to businesses like ours. I'm well aware of what is out there but it isn't going to be mainstream technology for at least another decade and probably longer.

      If the tooling is costing $8000, it's either fucking massive, or you're counting the design cost in addition to the machining.

      Of course the cost includes design and machining. We don't do it ourselves - we're not a tool & die shop. And $8000 for press tooling is incredibly cheap for a one off design. Even the applicators (different type of tooling) we use for crimping on our presses cost $1500-3000 each and those are standardized. A guy I work with when we need plastics tooling done works for a company that does injection moldings and their tooling is often $20-50,000+ for a die set. My company does not have the expertise to design tooling for injection molds or for our crimping presses. That leaves us with the option of either outsourcing it completely or hiring all the people and buying all the equipment necessary to bring it in house. 3D printing in anything but basic plastics requires a VERY expensive machine which is economically prohibitive and we still would have to hire the engineer with the design expertise. So I can either outsource the project for $8000 or I can spend the better part of $100,000 to do the same thing if I do it in house. Not exactly the toughest economic decision to make.

      I do some work as a mechanical engineer* and I do some work in VLSI and FPGA, and my experience is that most existing mechanical tools are batfuckstupid.

      I would tend to agree with you. I would also say that most mechanical engineers I've worked with are absolutely horrible at process documentation and process design. (I'm an industrial engineer so process engineering is kind of my thing) I can count on my fingers the number of designs in the last 5 years I've gotten from mechanical engineers that could be built directly from the documentation provided. It's not just the tools either. Too many of them simply are terrible at communicating their designs to other people.

      Mechanical engineering is not just about the part; you also need to design the process or tool that produces it. Designing an airplane is 1/10th about the airplane and 9/10th about the factory and process that builds it.

      Quite correct although as a process engineer I wouldn't sell the design short that much. You can do great manufacturing on a shitty design and it's still going to be a shitty product. Probably closer to 50/50 but your general point is valid.

      It's as if every time you wrote a program, you had to write the compiler, linker and debugger for it at the same time. This is the level of sophistication that most mechanical engineering is at today.

      Not really true and the analogy is a severe stretch - to the point where it doesn't really make much sense. Mechanical engineering is NOT like software engineering. It deals in tangible objects and notions like code reuse and other things that are routine in software don't easily translate.

      That said, companies that do mechanical engineering well do tend to standardize a lot of what they do. One thing companies like Honda do very well is that they are incredibly disciplined about standardizing their tooling. This has enormous downstream benefits, both financial and quality. At my company most of our press tooling is standard from one manufacturer and that saves us tremendous amounts of time and money.

  20. a poor business model by swell · · Score: 1

    Suppose you could do the impossible; create a generic computer system that is not burdened with patents. It would cost money to come up with the prototype, and then you would have to consider manufacturing it. A system of hardware devoid of protection from competition.

    Your investment in manufacturing equipment, location, employees etc will have to result in profits or all is lost. But, having laid some of the groundwork, done some of the initial research, you now face competitors who have the benefit of that expensive research.

    The wonderful generic computer is, of course, generic. They are all the same. Any attempt to distinguish your product from another would risk patent wars or compatibility problems. The buyers demand that they be the same. And they will only buy from the lowest bidders.

    So the only way for your business to succeed is to find a way to make them at a lower cost. Foreign labor? Inferior parts? Robotic assembly? It will be a cutthroat price competition. You have wasted vast resources of time, labor and money to enter an unwinnable competition.

    --
    ...omphaloskepsis often...
    1. Re:a poor business model by Anonymous Coward · · Score: 0

      Suppose you could do the impossible; create a generic computer system that is not burdened with patents. It would cost money to come up with the prototype, and then you would have to consider manufacturing it. A system of hardware devoid of protection from competition.

      Are you fucking kidding me. There are companies making billions cranking out nuts and bolts, and bearings and rollers, and steel and aluminum. None of it is burdened or protected by patents.

      This is called a commodity business and makes up the majority of trade worldwide.

      The point and driver of commodities, is that it's good for the consumer of the commodity. Standards and gages. Standard steel exists because the construction and automotive industries wanted interchangeable suppliers so they could make cars and buildings more cheaply. Standard aluminum exists because aircraft and sodapop manufacturers wanted the same. JEDEC memory standards (DDR3, etc) exist because every computer manufacturer wanted cheap interchangeable RAM.

      Now bulk consumers of computers (Facebook, Amazon and so on) are saying they want commodity motherboards and CPUs, because they want cheaper computers, and some kickstarters are calling for the same in consumer computers.

      Guess what? innovation in CPUs has pretty much dried up. Computers are becoming commodities, it was inevitable. It is not the commodity producers who are wasting their money developing standards, it's the consumers, who stand to lose nothing and gain a lot in the way of cheap commodity computers. They're saying "if you make it to our standard, we will buy it, and if you don't we won't", just like any other standardised commodity. I won't buy a resistor or a bolt if it's made to some proprietary standard. If I call for an M6x50 screw, they better supply an M6x50 bolt. Today nobody will accept a screw if it's not made to some standard gage (ISO or ANSI, usually, depending on country), and tomorrow, if things follow the trend of EVERY OTHER TECHNOLOGY, nobody will buy a CPU or a computer if it doesn't confrom to some standard definition of a CPU. Even today people most won't buy a CPU if it doesn't conform to x86 or ARM standard. All that is happening tomorrow is that proprietary and vendor specific standards are being replaced with open interchangeable standards, because the consumers, not the suppliers, are sick of rent seeking for something they've started to realise it would be cheaper for them to standardise once and be done with, than pay rent in perpetuity to make use of the proprietary standard.

  21. Re:Why fret about a supply chain when it can exist by Anonymous Coward · · Score: 0

    They already have all this. Companies like Quanta and Hyve are shipping millions of OCP servers per year. That necessitates that there is solid supply chain.