OAK Vision Modules Help You See The Forest And The Trees

August 9, 2020 by Roger Cheng 13 Comments

OpenCV is an open source library of computer vision algorithms, its power and flexibility made many machine vision projects possible. But even with code highly optimized for maximum performance, we always wish for more. Which is why our ears perk up whenever we hear about a hardware accelerated vision module, and the latest buzz is coming out of the OpenCV AI Kit (OAK) Kickstarter campaign.

There are two vision modules launched with this campaign. The OAK-1 with a single color camera for two dimensional vision applications, and the OAK-D which adds stereo cameras for that third dimension. The onboard brain is a Movidius Myriad X processor which, according to team members who have dug through its datasheet, have been massively underutilized in other products. They believe OAK modules will help the chip fulfill its potential for vision applications, delivering high performance while consuming low power in a small form factor. Reading over the spec sheet, we think it’s fair to call these “Ultimate Myriad X Dev Boards” but we must concede “OpenCV AI Kit” sounds better. It does not provide hardware acceleration for the entire OpenCV library (likely an impossible task) but it does cover the highly demanding subset suitable for Myriad X acceleration.

Since the campaign launched a few weeks ago, some additional information have been released to help assure backers that this project has real substance. It turns out OAK is an evolution of a project we’ve covered almost exactly one year ago that became a real product DepthAI, so at least this is not their first rodeo. It is also encouraging that their invitation to the open hardware community has already borne fruit. Check out this thread discussing OAK for robot vision, where a question was met with an honest “we don’t have expertise there” from the OAK team, but then ArduCam pitched in with their camera module experience to help.

We wish them success for their planned December 2020 delivery. They have already far surpassed their funding goals, they’ve shipped hardware before, and we see a good start to a development community. We look forward to the OAK-1 and OAK-D joining the ranks of other hacking friendly vision modules like OpenMV, JeVois, StereoPi, and AIY Vision.

Ask Hackaday: Why Did GitHub Ship All Our Software Off To The Arctic?

July 29, 2020 by Ben James 95 Comments

If you’ve logged onto GitHub recently and you’re an active user, you might have noticed a new badge on your profile: “Arctic Code Vault Contributor”. Sounds pretty awesome right? But whose code got archived in this vault, how is it being stored, and what’s the point?

Continue reading “Ask Hackaday: Why Did GitHub Ship All Our Software Off To The Arctic?” →

Home Automation Covers Everything

July 13, 2020 by Bryan Cockfield 29 Comments

When starting out on a project, it’s accepted best practice to try to avoid feature creep. Of course, we can’t all say that we follow this guideline completely every time. In fact, sometimes it can get away from us, and in rare situations it might actually turn out pretty well. That appears to be what happened with [superczar]’s home automation project which now covers basically everything possible in home automation.

The build started in 2013, so we assume that features have been added periodically and that the system wasn’t designed and built all in one furious weekend. Either way, though, it covers a lot: lights, switches, media players in several rooms, includes sensors and logging for temperature, smoke, fire, and power, supports a number of cameras, the doorbell, and the locks. It also includes voice control for most of the systems.

That’s an impressive list, but what really drew our attention to this project is that it used to be based on domoticz, but that community has waned over the years and [superczar] had kept his system patched together with self-built scripts. An accidental upgrade recently broke the entire setup, so rather than rebuild everything a migration was made to home-assistant, an open-source platform that has a more active community. We’ve seen plenty of projects around here that use it as a platform, for ceiling fans, custom remotes, and doorbells.

Thanks to [pradeepmur] for the tip!

Your Own Open Source ASIC: SkyWater-PDK Plans First 130 Nm Wafer In 2020

June 30, 2020 by Al Williams 51 Comments

You might have caught Maya Posch’s article about the first open-source ASIC tools from Google and SkyWater Technology. It envisions increased access to make custom chips — Application Specific Integrated Circuits — designed using open-source tools, and made real through existing chip fabrication facilities. My first thought? How much does it cost to tape out? That is, how do I take the design on my screen and get actual parts in my hands? I asked Google’s Tim Ansel to explain some more about the project’s goals and how I was going to get my parts.

The goals are pretty straightforward. Tim and his collaborators would like to see hardware open up in the same way software has. The model where teams of people build on each other’s work either in direct collaboration or indirectly has led to many very powerful pieces of software. Tim’s had some success getting people interested in FPGA development and helped produce open tools for doing so. Custom ASICs are the next logical step.

Continue reading “Your Own Open Source ASIC: SkyWater-PDK Plans First 130 Nm Wafer In 2020” →

FDA Approves Ventilator Designed By NASA’s Jet Propulsion Laboratory

May 1, 2020 by Mike Szczys 28 Comments

Yesterday NASA’s Jet Propulsion Laboratory announced that their ventilator design has received Emergency Use Authorization from the US Food and Drug Administration. This paves the way for the design to be manufactured for use in the treatment of COVID-19 patients.

JPL, which is tightly partnered with the California Institute of Technology, designed the ventilator for rapid manufacturing to meet the current need for respiratory tools made scarce by the pandemic. The design process took only 37 days and was submitted for FDA approval around April 23rd. They call it VITAL — Ventilator Intervention Technology Accessible Locally — a nod to NASA’s proclivity for acronyms.

Continue reading “FDA Approves Ventilator Designed By NASA’s Jet Propulsion Laboratory” →

Make It Easier For Your Software Project To Accept Contributions

April 29, 2020 by Donald Papp 30 Comments

[Flameeyes] has heard complaints (and at times, he admits, has complained himself) about big companies not contributing improvements to projects they seem to find useful, or rolling their own implementation rather than use and contribute to an existing code base. Having recently left Google after seven years, he has some insights into some of the reasons big corporations (at least Google, anyway) may sometimes seem to eschew making code contributions, and some of the reasons might come as a surprise.

There are things a corporation can do differently, but there are also some things that can be done on the project’s end to make accepting contributions easier. [Flameeyes] took some time to write out a few pointers on how to make it easier for others (particularly large corporations) to contribute code to a software project.

The biggest issue is the software license. Without one, there is no legal structure to use, distribute, or contribute to the code, and no corporate entity will want to touch it. Google specifically forbids creating patches for projects with either no license, or incompatible licenses. An example of an incompatible license is one that forbids commercial use, because everything a corporation like Google does — even research –is considered a commercial endeavor. In addition, on the corporate side making contributions might trigger a code review process of some kind for some licenses, but not for others. [Flameeyes] suggests the MIT license as one that is acceptable to pretty much everyone with a minimum of fuss. Another caution: if a project’s code resides in an online repository, make sure the repository is licensed as well.

A few other small suggestions (such as maintaining an AUTHORS file to track contributors in a tidy way) rounds out the advice. It sounds simple, but software licensing is so critical to the whole affair that it’s important to get it right — he suggests the REUSE tool for anyone wanting to make sure a project’s licensing is tidy.

[Flameeyes] makes a point that none of this guidance is based on secret or institutional knowledge. Google has a public document detailing exactly how they use and deal with open source, and it’s a solid guide for how to make your project more accepting of contributions from a corporate entity like Google. (Or, if you prefer, a guide on how to set up as many barriers as possible for your project.)

In case you missed it, we just want to remind you that our favorite recent open source project from Google is definitely Pigweed.