open hardware

72 Articles

These Twenty Amazing Projects Won The Open Hardware Design Challenge

May 2, 2018 by 20 Comments

Right now, we’re running the greatest hardware competition on the planet. The Hackaday Prize is the Academy Awards of Open Hardware, and we’re opening the gates to thousands of hardware hackers, makers, and artist to create the next big thing.

Last week, we wrapped up the first challenge in this year’s Hackaday Prize. We’re now happy to announce twenty of those entries that have been selected to move to the final round and have been awarded a $1000 cash prize. Congratulations to the winners for the Open Hardware Design Challenge portion of the Hackaday Prize. Here are winners, in no particular order:

Open Hardware Design Challenge Hackaday Prize Finalists:

These projects are fantastic

The Oasis 3D Printer repurposes HP ink cartridges to build a powder-baseed 3D printer

Just take a look at these projects. They are the best of the best, and there’s still more to come. We enjoyed seeing projects that repurpose off-the-shelf technology to vastly extend the capabilities of home manufacturing with the Oasis 3DP. This project from [Yvo de Haas] takes ink cartridges from HP printers and uses it to build a powder-based 3D printer. That’s something that really hasn’t been done in the world of homebuilt 3D printers, and the Oasis 3DP already has working hardware. It truly is one of the more interesting projects we’ve ever seen, and not just because [Yvo] is dealing with dozens of tiny micro pumps squirting binder out of microscopic nozzles.

But that’s not all. There were hundreds of projects entered in the Hackaday Prize for this round, and our only regret is that we could only pick twenty winners for the Open Hardware Design Challenge. Just check out Semiconductors @ Home, a project from [Nixie] — it’s a project trying to make sand blink. [Nixie] is building all the tools to make semiconductors at home. Being able to build a simple FET is amazing, and to do that you need a fume hood to contain the dangerous hydrofluoric acid, a vacuum chamber for sputtering deposition, and a fancy oven with a controlled atmosphere. These tools are [Nixie’s] entry in the design challenge. This isn’t your garden variety hardware hacking; this is advanced hardware hacking.

Semiconductors @ home is turning ions into FETs

Not impressed with DIY semiconductors? You’re a terrible person, but okay. How about an easy way to read rotary encoders? [fattore.saimon] and [Atikaimu] are building an I2C Encoder, an easy way to read multiple rotary encoders with just two microcontroller pins. Reading rotary encoders is one of the deceptively difficult tasks in electrical engineering; you really need some interrupts to do it right, and a microcontroller really only has a few of those to spare. [fattore] and [atikaimu]’s project does away with that problem, and puts rotary encoders on a board that can be read with a normal I2C bus. This means anyone can add a dozen rotary encoders to any project easily. Did anyone say MIDI controllers? Yes, that is possible. Everything from musical instruments to impressive control panels is possible with the I2C encoder, and it’s all Open Hardware.

Are you still not entertained? [Carl Bugeja] built a motor out of a PCB. Over the last decade, the price of custom fabricated printed circuit boards has dropped precipitously, and that means anyone can experiment with copper foil and fiberglass. [Carl] figured that since you can put coils on a PCB, you could also make a motor. While we’re only looking at a 1 Watt motor here, this is a brushless motor made out of printed circuit boards. It’s amazing, you’ve never seen it before, and we have absolutely no idea how many uses people will find a use for this amazing technology.

These are the winners of the Open Hardware Design Challenge in the Hackaday Prize, and we have a fondness for Open tools that are capable of building even more open hardware. If you want an example of that, you need only look at the Arcus-3D-P1 from [Daren Schwenke]. This is a project to add a lightweight pick and place head to any 3D printer. Below a certain size, a pick and place machine is necessary to create electronics, and almost everyone has a 3D printer these days. The Arcus-3D-P1 is an attachment for any 3D printer to turn it from a CNC hot glue gun into a machine that builds electronics. It’s Open Hardware, and hardware that creates hardware. It’s astonishing, and it’s happening on Hackaday.io.

Congratulations to all who entered the first challenge, and the twenty excellent entries that are moving to the finals. We can’t wait to see what other projects will make it to the finals in the Hackaday Prize, the greatest hardware competition on the planet.

 

Who will win the 2018 Hackaday Prize?

Who will win the Hackaday Prize? These finalists in the Open Hardware design challenge are now in the running for the final round of the Hackaday Prize where they will have the chance to win the Grand Prize $50,000 USD. That doesn’t mean you still can’t get in on the action; there are four more challenges left in the Hackaday Prize.

Right now, we’re in the middle of the Robotics Module Challenge, and after that, we’ll launch into the Power Harvesting Challenge, the Human Computer Interface Challenge, and finally the Musical Instrument challenge. There’s still time to win your place among the hardware greats, so start your Hackaday Prize entry now.

The HackadayPrize2018 is Sponsored by:

The Anxiety Of Open Source: Why We Struggle With Putting It Out There

May 1, 2018 by 60 Comments

You’ve just finished your project. Well, not finished, but it works and you’ve solved all the problems worth solving, and you have a thing that works for you. Then you think about sharing your creation with the world. “This is cool” you think. “Other people might think it’s cool, too.” So you have to take pictures and video, and you wish you had documented some more of the assembly steps, and you have to do a writeup, and comment your code, and create a repository for it, maybe think about licensing. All of a sudden, the actual project was only the beginning, and now you’re stressing out about all the other things involved in telling other people about your project, because you know from past experience that there are a lot of haters out there who are going to tear it down unless it’s perfect, or even if it is, and even if people like it they are going to ask you for help or to make one for them, and now it’s 7 years later and people are STILL asking you for the source code for some quick little thing you did and threw up on YouTube when you were just out of college, and of course it won’t work anymore because that was on Windows XP when people still used Java.

Take a deep breath. We’ve all been there. This is an article about finding a good solution to sharing your work without dealing with the hassle. If you read the previous paragraph and finished with a heart rate twice what you started, you know the problem. You just want to share something with the world, but you don’t want to support that project for the rest of your life; you want to move on to new and better and more interesting projects. Here are some tips.

Continue reading “The Anxiety Of Open Source: Why We Struggle With Putting It Out There” →

Stecchino Game Is All About Balancing A Big Toothpick

March 23, 2018 by 5 Comments
Stecchino demo by the creator

Self-described “Inventor Dad” [pepelepoisson]’s project is called Stecchino (English translation link here) and it’s an Arduino-based physical balancing game that aims to be intuitive to use and play for all ages. Using the Stecchino (‘toothpick’ in Italian) consists of balancing the device on your hand and trying to keep it upright for as long as possible. The LED strip fills up as time passes, and it keeps records of high scores. It was specifically designed to be instantly understood and simple to use by people of all ages, and we think it has succeeded in this brilliantly.

To sense orientation and movement, Stecchino uses an MPU-6050 gyro and accelerometer board. An RGB LED strip gives feedback, and it includes a small li-po cell and charger board for easy recharging via USB. The enclosure is made from a few layers of laser-cut and laser-engraved material that also holds the components in place. The WS2828B WS2812B LED strip used is technically a 5 V unit, but [pepelepoisson] found that feeding them direct from the 3.7 V cell works just fine; it’s not until the cell drops to about three volts that things start to glitch out. All source code and design files are on GitHub.

Games are great, and the wonderful options available to people today allow for all kinds of interesting experimentation like a blind version of tag, or putting new twists on old classics like testing speed instead of strength.

Friday Hack Chat: How Do You Collaborate With Hardware?

February 7, 2018 by 6 Comments

The world of Open Source software is built on collaboration. In one corner of the world, someone can fix a bug in a piece of software, and push it up to the gits. In another part of the world, someone else can put that fix into the next release, and soon everyone has newer, better software. The Internet, or the ability to rapidly transmit text and binary files, has made this all possible.

Hardware is another story. There’s a financial barrier to entry. Not only do you need a meter and a good iron, you’re probably going to need oscilloscopes, logic analyzers, and a bunch of other expensive tools. You’ll need to buy your BOM. If you’re using a PIC, it might be a good idea to buy the good compiler. Hardware is hard and expensive, and all those software devs who complain don’t know what they’re talking about. Collaborating on hardware is much more difficult than pushing some code up to the cloud.

For this week’s Hack Chat, we’re going to be talking about collaborating on hardware projects. This is a deep dive on how to make collaboration with physical objects work, and this week we’re going to be learning from some of the best.

Our guests for this week’s Hack Chat are Pete Dokter and Toni Klopfenstein of SparkFun Electronics. Pete is formerly the Director of Engineering at SparkFun and now the Brand Ambassador for SparkFun Electronics. He hosts the According to Pete video series expounding on various engineering principles and seriously needs a silverburst Les Paul and a Sunn Model T. Toni is currently the product development manager at SparkFun. She’s served on the Open Source Hardware Association Board and participates in the Open Hardware Summit yearly. In her free time, she spends fifty weeks out of the year finding dust in her art and electronics projects.

During this chat, we’re going to be discussing what makes a collaborative hardware project, how to make distributed development work for your team, and the limits of what you can do with several hardware engineers separated by thousands of miles. This is a hard problem, much harder than a distributed team of software engineers, and a fantastic discussion for all.

join-hack-chat

Our Hack Chats are live community events on the Hackaday.io Hack Chat group messaging. This Hack Chat is going down Friday, February 9th at noon, Pacific time. Time Zones got you down? Here’s a handy countdown timer!

Click that speech bubble to the left, and you’ll be taken directly to the Hack Chat group on Hackaday.io.

You don’t have to wait until Friday; join whenever you want and you can see what the community is talking about.

Making The Case For Open Source Medical Devices

January 30, 2018 by 53 Comments

Engineering for medical, automotive, and aerospace is highly regulated. It’s not difficult to see why: lives are often at stake when devices in these fields fail. The cost of certifying and working within established regulations is not insignificant and this is likely the main reason we don’t see a lot of work on Open Hardware in these areas.

Ashwin K. Whitchurch wants to change this and see the introduction of simple but important Open Source medical devices for those who will benefit the most from them. His talk at the Hackaday Superconference explores the possible benefits of Open Medical devices and the challenges that need to be solved for success.

Continue reading “Making The Case For Open Source Medical Devices” →

Let’s Talk Intel, Meltdown, And Spectre

January 5, 2018 by 150 Comments

This week we’ve seen a tsunami of news stories about a vulnerability in Intel processors. We’re certain that by now you’ve heard of (and are maybe tired of hearing about) Meltdown and Spectre. However, as a Hackaday reader, you are likely the person who others turn to when they need to get the gist of news like this. Since this has bubbled up in watered-down versions to the highest levels of mass media, let’s take a look at what Meltdown and Spectre are, and also see what’s happening in the other two rings of this three-ring circus.

Meltdown and Spectre in a Nutshell

These two attacks are similar. Meltdown is specific to Intel processors and kernel fixes (basically workarounds implemented by operating systems) will result in a 5%-30% speed penalty depending on how the CPU is being used. Spectre is not limited to Intel, but also affects AMD and ARM processors and kernel fixes are not expected to come with a speed penalty.

Friend of Hackaday and security researcher extraordinaire Joe Fitz has written a superb layman’s explanation of these types of attacks. His use of the term “layman” may be a little more high level than normal — this is something you need to read.

The attack exploits something called branch prediction. To boost speed, these processors keep a cache of past branch behavior in memory and use that to predict future branching operations. Branch predictors load data into memory before checking to see if you have permissions to access that data. Obviously you don’t, so that memory will not be made available for you to read. The exploit uses a clever guessing game to look at other files also returned by the predictor to which you do have access. If you’re clever enough, you can reconstruct the restricted data by iterating on this trick many many times.

For the most comprehensive info, you can read the PDF whitepapers on Meltdown and Spectre.

Update: Check Alan Hightower’s explanation of the Meltdown exploit left as a comment below. Quite good for helping deliver better understanding of how this works.

Frustration from Kernel Developers

These vulnerabilities are in silicon — they can’t be easily fixed with a microcode update which is how CPU manufacturers usually workaround silicon errata (although this appears to be an architectural flaw and not errata per se). An Intel “fix” would amount to a product recall. They’ve already said they won’t be doing a recall, but how would that work anyway? What’s the lead time on spinning up the fabs to replace all the Intel chips in use — yikes!

So the fixes fall on the operating systems at the kernel level. Intel should be (and probably is behind the scenes) bowing down to the kernel developers who are saving their bacon. It is understandably frustrating to have to spend time and resources patching these vulnerabilities, which displaces planned feature updates and improvements. Linus Torvalds has been throwing shade at Intel — anecdotal evidence of this frustration:

“I think somebody inside of Intel needs to really take a long hard look at their CPU’s, and actually admit that they have issues instead of writing PR blurbs that say that everything works as designed.”

That’s the tamest part of his message posted on the Linux Kernel Mailing List.

Stock Sales Kerfuffle is Just a Distraction

The first thing I did on hearing about these vulnerabilities on Tuesday was to check Intel’s stock price and I was surprised it hadn’t fallen much. In fact, peak to peak it’s only seen about an 8% drop this week and has recovered some from that low.

Of course, it came out that back in November Intel’s CEO Bryan Krzanich sold off his Intel stock to the tune of $24 Million, bringing him down to his contractual minimum of shares. He likely knew about Meltdown when arranging that sale. Resist the urge to flame on this decision. Whether it’s legal or not, hating on this guy is just a distraction.

What’s more interesting to me is this: Intel is too big to fail. What are we all going to do, stop using Intel and start using something else? You can’t just pull the chip and put a new one in, in the case of desktop computers you need a new motherboard plus all the supporting stuff like memory. For servers, laptops, and mobile devices you need to replace the entire piece of equipment. Intel has a huge market share, and silicon has a long production cycle. Branch prediction has been commonplace in consumer CPUs going back to 1995 when the Pentium Pro brought it to the x86 architecture. This is a piece of the foundation that will be yanked out and replaced with new designs that provide the same speed benefits without the same risks — but that will take time to make it into the real world.

CPUs are infrastructure and this is the loudest bell to date tolling to signal how important their design is to society. It’s time to take a hard look at what open silicon design would bring to the table. You can’t say this would have been prevented with Open design. You can say that the path to new processors without these issues would be a shorter one if there were more than two companies producing all of the world’s processors — both of which have been affected by these vulnerabilities.

Friday Hack Chat: Contributing To Open Source Development

December 6, 2017 by 13 Comments

Open Source is how the world runs. Somewhere, deep inside the box of thinking sand you’re sitting at right now, there’s code you can look at, modify, compile, and run for yourself. At every point along the path between your router and the horrific WordPress server that’s sending you this webpage, there are open source bits transmitting bytes. The world as we know it wouldn’t exist without Open Source software.

That said, how does someone contribute to Open Source? Maintainers do like to build their own little kingdoms, so how does anyone break into developing Open Source hardware and software?

Our guest for this Hack Chat will be Robert Wolff, technical writer, and Open Source evangelist who has a history of working in and around STE*M-based educational programs. Right now, Robert is the community manager for 96Boards at Linaro. 96Boards is a hardware specification to make the latest ARM-based processors available at a reasonable cost. This open specification defines a standard board layout for SoC-agnostic platforms that can be used by any application, device, and kernel by system software developers.

The questions we’ll be looking at during this Hack chat is how to contribute to Open Source projects, how to do that using 96Boards, the technical challenges involved in documenting an Open system, the difficulty in designing a processor-agnostic system, and general questions about the 96Boards community, ecosystem, and resources.

As always, we’re going to be taking questions from the hackaday.io community, so if you have a question, drop it on the Hack Chat event page.

join-hack-chat

Our Hack Chats are live community events on the Hackaday.io Hack Chat group messaging. These Hack Chats usually happen at Noon, Pacific time, on Friday. This week, everything is going down on Noon, PST, Friday, December 8th. Don’t have any idea what time that is on your meridian? Here’s a handy countdown timer!

Click that speech bubble to the left, and you’ll be taken directly to the Hack Chat group on Hackaday.io.

You don’t have to wait until Friday; join whenever you want and you can see what the community is talking about.