Clocks For Social Good

Over the past five days we’ve been challenging the Hackaday community to build a clock and show it off. This is to raise awareness for electronics design in everyday life and hopefully you found a non-hacker to join you on the project. The point is that our society — which has pretty much universally accepted everyday carry of complex electronics — has no idea what goes into electronic design. How are we supposed to get kids excited about engineering if they are never able to pull back that curtain and see it in action?

Build something simple that can be understood by everyone, and show it off in a way that invites the uninitiated to get excited. What’s simpler than a clock? I think of it as the impetus behind technology. Marking the passage of time goes back to our roots as primitive humans following migratory herds, and betting on the changing seasons for crop growth. Our modern lives are governed by time more than ever. These Clocks for Social Good prove that anyone can understand how this technology works. And everyone who wants to learn to build their own electronic gadget can discover how to do so at low-cost and with reasonable effort. This is how we grow the next generation of engineers, so let’s take a look at what we all came up with over the weekend.

Continue reading “Clocks For Social Good”

Hacking Eating Tracking

There’s a great hackathon going on this weekend in the Boston area. Hacking Eating Tracking challenges participants to develop technology that will help guide personal behavior toward a healthier lifestyle.

The event in hosted in Cambridge, MA by Harvard University. It isn’t focused on giving you a diet that you need to follow. It looks instead at how some more abstract behavior changes will cause your body to do this for you. One really quick example is to change the hand in which you hold your fork, or swap out the fork for a different utensil. Going “lefty” while you eat can change the cadence of your consumption and my impact how many calories you consume before feeling full. This is a really fun type of hacking to delve into!

Hackaday is one of the Hackathon sponsors and [Sophi] is headed out to participate in the weekend of building. She’s planning to work with a Pixy Camera which can measure depth data and can separate colors. Of course decisions on the build direction won’t be made until she and her teammates put their heads together, but she did have a few preliminary ideas. Several of these cameras might be used in a supermarket to gather data on where customers tend to congregate and how aisle flow and stock choices might be able to change behavior.

If you’re not in the area you should still be able to follow along as the event helps to improve people’s lives through behavior. The hackathon will be using the Hackaday.io Hackathon framework. Teams will register and update their projects throughout the weekend. We’re looking forward to seeing what is built using the crate of LightBlue Bean boards we sent along from the Hackaday Store.

I Built A Clock To Spread Awareness. Now It’s Your Turn

I spent an evening building a clock. It’s not about keeping time, or even about the clock. This is about raising awareness that people actually build electronics as a hobby. Promoting wide understanding of this can have a profound effect on our society. On the one hand, it can avoid drama like we’ve seen with the clock incident this week at a school in Texas. The far more important result is to get more people interested in STEM fields.

If you think back to 10-20 years ago, everyone knew that “computer person” who always had interesting technology, spent tons of time on the computer, and was the go-to when people needed help. Fast forward to today and everyone is that computer geek to one extent or another. Smartphones, tablets, and laptops have been universally adopted. We need everyone today to know that “hardware person” who is building electronics in their basement, garage, or hackerspace. I don’t have any illusions that everyone will be bootstrapping a clock in 10 years. But there are enough of us out there already that raising our profile will let everyone discover they already have a hardware hacker in their social circles.

Get started this weekend by building a Clock for Social Good. Grab a non-hacker friend and build a clock with anything you have lying around. Document it on Hackaday.io and send me a message with the link so I can add it to the already-growing list of clock builds.

This will break down the barriers your non-hacker acquaintances have about cracking open the case on something, or about seeing a bunch of loose wires hanging off of a board. Getting our projects out into the community will help people learn that building hardware is a thing, and one that they should get their kids excited about. The more engineers we can create in middle and high school, the better our future outlook becomes.

Now, if you want to know more about my clock, check out the video after the break. I do have a project page started, with plenty more information coming later today as I find carve out some time to update it. I can’t wait to see what you come up with for your own project!

Continue reading “I Built A Clock To Spread Awareness. Now It’s Your Turn”

Why You Should Build A Clock For Social Good This Week

We’ve seen a wide range of emotional responses regarding [Ahmed Mohamed]’s arrest this week for bringing a clock he built to school. No matter where you fall on the political scale, we can all agree that mistaking a hobby engineering project for a bomb is a problem for education. People just don’t understand that mere mortals can, and do, build electronics. We can change that, but we need your help.

Our friends at NYC Resistor came up with a great idea. Why don’t we all build a clock? I want you to take it one step further: find a non-hacker to partner with on the project. Grab a friend, relative, or acquaintance and ask them to join you in building a clock from stuff you have on hand in order to promote STEM education.

Clocks have long been one of my favorite projects, and like the one shown above, most of my builds didn’t look anything like traditional clocks. Once you start getting into how clocks are built, you’ll be amazed at how accurate dirt-cheap clocks are and how difficult it can be to replicate that accuracy. Pass this knowledge on to your teammates. Teach them how to solder, or how to draw a schematic, or just how to open the case on some electronics without fear.

Post your project on hackaday.io and we’ll add it to the Clocks for Social Good list (message me with the link). If you decide to document it elsewhere just leave a link in the comments below. We’ll post a roundup of all these builds next week. I plan to repurpose the soldering workshop board I populated last week as the display for my clock. I’ll be helping a friend of mine learn to solder as part of the build!

Happy hacking, and thanks for helping to dispel fear and teach others about awesome engineering.

Need some inspiration to get going? You can always chat with others about it in the Hacker Channel. If you have an Arduino and some LED strips you can do something like this. Here’s a binary clock built with just a few LEDs. Or if you have a laser cutter at your disposal you can make a unique display with just a pair of motors.

Rubik’s Solver Uses FAC Machine Building System

We love a good Rubik’s Cube solver and the mechanical engineering on this one is both elegant and functional.

This is the first time we remember hearing about the FAC system, which is a standard set of parts which can be used to make any number of mechanical systems. [Wilbert Swinkels] must be a master with the system; the layout of the machine appears simple and uncrowded despite the multiple degrees of freedom built into it. Those include an insertion platform for getting the cube in and out, a gantry for three color sensors, and two axes (three grippers in all) for doing the actual solving. If you’ve used FAC before we want to hear what you think of it in the comments.

[Maxim Tsoy] handled the software which runs on a Rapsberry Pi Compute module. You’ll want to watch the demo video below. First you place the randomized cube on the insertion platform which retracts after the cube is in the grasp of the grippers. These work in conjunction with the color sensor gantry to scan every side of the cube. After a brief pause to compute the solution the grippers go to work.

It is possible to build a solver with just two swiveling grippers. Here’s a really fast way to do it.

Continue reading “Rubik’s Solver Uses FAC Machine Building System”

Hackaday’s DC Meetup And Workshops

Washington DC has a vibrant hardware hacking community and it was out in force on Saturday night. We had over one hundred people through the door at Nova Labs in Reston, Virginia (DC metro area). This sleek and spacious hackerspace opened their doors for a Hackaday Meetup as part of a weekend packed full of activities.

The building that Nova Labs moved into not too long ago is a really well-suited area for a Hackerspace. The front half of the building includes a huge open space which has plenty of room for people to set up the hardware they wanted to show off. The back has a full woodshop, machine shop, and more, with classrooms and conference rooms in between.

Above are a set of hats with addressible LED strings wrapped around them which [ArsenioDev] brought along with him. Several members of the Wyolum team are involved with Nova Labs and they were showing off some LED matrix-based projects like the marquee cube and a 3-player reaction time game. And clacking away all night long is a vintage teletype machine that [Bob Coggeshall] fixed and connected to a Raspberry Pi.

Continue reading “Hackaday’s DC Meetup And Workshops”

Let Skynet Become Self-Aware!

Not so long ago, it was hard to fly. Forget actual manned aircraft and pilots licenses; even flying model aircraft required hours of practice, often under the tutelage of a master at a flying field. But along with that training came an education in the rules of safe flight, including flying at a designated airfield and watching out for obstacles.

We accidentally messed that up. We in the drone industry made aircraft super easy to fly — perhaps too easy to fly. Thanks to smart autopilots and GPS, you can open a box, download an app and press “take off”. The copter will dutifully rise into the air and wait there for further instructions — no skill required. And it will do this even if you happen to be in an NFL football stadium in the middle of a big game. Or near an airport. Or in the midst of a forest fire.

The problem is that along with taking training out of the process of flying a drone, we inadvertently also took out the education process of learning about safe and responsible flight. Sure, we drone manufacturers include all sorts of warning and advisories in our instructions manual (which people don’t read) and our apps (which they swipe past), and companies such as DJI and my own 3DR include basic “geofencing” restrictions to try to keep operators below 400 feet and within “visual line of sight”. But it’s not enough.

Every day there are more reports of drone operators getting past these restrictions and flying near jetliners, crashing into stadiums, and interfering with first responders. So far it hasn’t ended in tragedy, but the way things are going it eventually will. And in the meantime, it’s making drones increasingly controversial and even feared. I call this epidemic of (mostly inadvertent) bad behavior “mass jackassery”. As drones go mass market, the odds of people doing dumb things with them reach the singularity of certainty.

We’ve got to do something about this before governments do it for us, with restrictions that catch the many good uses of drones in the crossfire. The reality is that most drone operators who get in trouble aren’t malicious and may not even know that what they’re doing is irresponsible or even illegal. Who can blame them? It’s devilishly hard to understand the patchwork quilt of federal, state and local regulations and guidelines, which change by the day and even the hour based on “airspace deconfliction” rules and FAA alerts written for licensed pilots and air traffic control. Many drone owners don’t even know that such rules exist.

Drones Themselves Should Know Rules of Each Area

Fortunately, they don’t have to. Our drones can be even smarter — smart enough to know where they should and shouldn’t fly. Because modern drones are connected to phones, they’re also connected to the cloud. Every time you open their app, that app can check online to find appropriate rules for flight where you are, right then and there.

Here’s how it works. The app sends four data fields to a cloud service: Who (operator identifier), What (aircraft identifier), Where (GPS and altitude position) and When (either right now or a scheduled time in the case of autonomous missions). The cloud service then returns a “red light” (flight not allowed), a “green light” (flight allowed, with basic restrictions such as a 400 feet altitude ceiling), or “yellow light” (additional restrictions or warnings, which can be explained to the operator in context and at the point of use).

image01

Right now industry groups such as the Dronecode Foundation, the Small UAV Coalition (I help lead both of them, but this essay just reflects my own personal views) and individual manufacturers such as 3DR and DJI are working on these “safe flight” standards and APIs. Meanwhile, a number of companies such as Airmap and Skyward are building the cloud services to provide the up-to-date third-party data layer that any manufacturer can use. It will start with static no-fly zone data such as proximity to airports, US national parks and other banned airspace such as Washington DC. But it will quickly add dynamic data, too, such as forest fires, public events, and proximity to other aircraft.

(For more on this, you can read a white paper from one of the Dronecode working groups here and higher level description here.)

There’s Always a Catch

Of course, this system isn’t perfect. It’s only as good as the data it uses, which is still pretty patchy worldwide, and the ways that the manufacturers implement those restrictions. Some drone makers may choose to treat any area five miles from an airport as a hard ban and prohibit all flight in that zone, even at the cost of furious customers who had no idea they were five miles from an airport when they bought that toy at Wal-mart (nor do they think it should matter, since it’s just a “toy”). Other manufacturers may choose to make a more graduated restriction for the sake of user friendliness, adding a level of nuance that is not in the FAA regulation. They might ban, say, flight one mile from an airport, but only limit flight beyond that to something like 150ft of altitude (essentially backyard-level flying).

That’s a reasonable first step. But the ultimate safe flight system would go a lot further. It would essentially extend the international air traffic control system to millions of aircraft (there are already a million consumer drones in the air) flown by everything from children to Amazon. The only way to do that is to let the drones regulate themselves (yes, let Skynet become self-aware).

Peer-to-peer Air Traffic Control

There’s a precedent for such peer-to-peer air traffic control: WiFI. Back in the 1980s, the FCC released spectrum in the 2.4 Ghz band for unlicensed use. A decade later, the first 802.11 standards for Wifi were released, which was based on some principles that have application to drones, too.

  1. The airspace used is not otherwise occupied by commercial operators
  2. The potential for harm is low (in the case of WiFi, low transmission power. In the case of drones, low kinetic energy due to the weight restrictions of the “micro” category)
  3. The technology has the capability to self-”deconflict” the airspace by observing what else is using it and picking a channel/path that avoids collisions.

That “open spectrum” sandbox that the FCC created also created a massive new industry around WiFi. It put wireless in the hands of everyone and routed around the previous monopoly owners of the spectrum, cellphone carriers and media companies. The rest was history.

Quadcopter ThumbWe can do the same thing with drones. Let’s create an innovation “sandbox” with de minimus regulatory barriers for small UAVs flying within very constrained environments. The parameters of the sandbox could be almost anything, as long as they’re clear, but it should be kinetic energy and range based (a limit of 2kg and 20m/s at 100m altitude and 1,000m range within visual line of sight would be a good starting point).

As in the case of open spectrum, in relatively low risk applications, such as micro-drones, technology can be allowed to “self-deconflict the airspace” without the need for monopoly exclusions such as exclusive licences or regulatory permits. How? By letting the drones report their position using the same cellphone networks they used to get permission to fly in the first place. The FAA already has a standard for this, called ADS-B, which is based on transponders in each aircraft reporting their position. But those transponders are expensive and unnecessary for small drones, which already know their position and are connected to the cloud. Instead, they can use “virtual ADS-B” to report their position via their cell network connections, and that data can be injected into the same cloud data services they used to check if their flight was safe in the first place.

Once this works, we’ll have a revolution. What WiFi did the telecoms industry, autonomous, cloud-connected drones can do to the aerospace industry. We can occupy the skies, and do it safely. Technology can solve the problems it creates.


About the Author

judge-thumb-AndersonChris Anderson (@Chr1sa) is the CEO of 3D Robotics and founder of DIY Drones. From 2001 through 2012 he was the Editor in Chief of Wired Magazine. Before Wired he was with The Economist for seven years in London, Hong Kong and New York.

The author of the New York Times bestselling books The Long Tail and Free as well as the Makers: The New Industrial Revolution.

His background is in science, starting with studying physics and doing research at Los Alamos and culminating in six years at the two leading scientific journals, Nature and Science.

In his self-described misspent youth [Chris] was a bit player in the DC punk scene and amusingly, a band called REM. You can read more about that here.

Awards include: Editor of the Year by Ad Age (2005). Named to the “Time 100,” the newsmagazine’s list of the 100 most influential people in the world (2007). Loeb Award for Business Book of the Year (2007). Wired named Magazine of the Decade by AdWeek for his tenure (2009). Time Magazine’s Tech 40 — The Most Influential Minds In Technology (2013). Foreign Policy Magazine’s Top 100 Global Thinkers (2013).