Woodworking is the fine art of building jigs. Even though we have Internet-connected toasters, thermostats, cars, and coffee makers, the Internet of Things hasn’t really appeared in the woodshop quite yet. That’s changing, though, and [Ben Brandt]’s Internet of Things box joint jig shows off exactly what cheap computers with a connection to the Internet can do. He’s fully automated the process of making box joints, all with the help of a stepper motor and a Raspberry Pi.
[Ben]’s electronic box joint jig is heavily inspired by [Matthias Wandel]’s fantastic screw advance box joint jig. [Matthias]’ build, which has become one of the ‘must build’ jigs in the modern woodshop, uses wooden gears to advance the carriage and stock across the kerf of a saw blade. It works fantastically, but to use this manual version correctly, you need to do a bit of math before hand, and in the worst-case scenario, cut another gear on the bandsaw.
[Ben]’s electronic box joint jig doesn’t use gears to move a piece of stock along a threaded rod. Stepper motors are cheap, after all, and with a Raspberry Pi, a stepper motor driver, a couple of limit switches, and a few LEDs, [Ben] built an Internet-enabled box joint jig that’s able to create perfect joints.
The build uses a Raspberry Pi 3 and Windows IoT Core to serve up a web page where different box joint profiles are stored. By lining the workpiece up with the blade and pressing start, this electronic box joint jig automatically advances the carriage to the next required cut. All [Ben] needs to do is watch the red and green LEDs and push the sled back and forth.
You can check out [Ben]’s video below. Thanks [Michael] for the tip.
For their entry into the Citizen Scientist portion of the Hackaday Prize, the folks at Arch Reactor, the St. Louis hackerspace, are building a microscope. Not just any microscope – this one is low-cost, digital, and has a surprisingly high magnification and pretty good optics. It’s the Internet of Things Microscope, and like all good apparatus for Citizen Scientist, it’s a remarkable tool for classrooms and developing countries.
When you think of ‘classroom microscope’, you’re probably thinking about a pile of old optics sitting in the back of a storage closet. These microscopes are purely optical, without the ability to take digital pictures. The glass is good, but you’re not going to get a scanning stage when you’re dealing with 30-year-old gear made for a classroom full of sticky-handed eighth graders.
The Internet of Things Microscope includes a scanning stage that moves across the specimen on the X and Y axes, stitching digital images together to create a very large image. That’s a killer feature for a cheap digital microscope, and the folks at Arch Reactor are doing this with a few cheap stepper motors and stepper motor drivers.
The rest of the electronics are built around a Raspberry Pi, Raspberry Pi camera (which recently got a nice resolution upgrade), and a some microscope eyepieces and objectives. Everything else is 3D printed, making this a very cheap and very accessible microscope that has some killer features.
The internet of things is this strange marketing buzzword that seems to escape from the aether and infect our toasters and refrigerators. Now even a hamster is not safe.
[Mifulapirus]’s hamster, Ham, was living a pleasant hamster life. Then his owner heard about another hamster named Sushi, whose running wheel stats were broadcasted to the internet. Not to be left behind, Ham’s wheel was soon upgraded. Now Ham is burdened by the same social pressures our exercise apps try to encourage us to use. No, we are most certainly not going to tell our friends about two fourteen minute miles with a twenty minute coffee break in the middle, MapMyRun, we are not.
The feat of techno enslavement for the little hamster was accomplished with a custom board, an esp8266, and an arduino as described in the instructable. The arduino can be left out of the project now that the libraries have been ported to the esp8266. A hall effect sensor detects when the 3D printed hamster wheel is spinning.
If you’d like to check in on Ham, the little guy is alive and well, and the twitter is here. It looks like it’s been upgraded since the original article was posted. Now it shows when Ham is awake and running around the cage doing hamster errands.
Want something that you’ll try for fifteen minutes before realizing it’s extremely stupid and has limited utility before throwing it in the back of a closet to eventually sell at a yard sale? No, it’s not the Internet of Things, but good guess. I’m speaking, of course, about unicycles.
[retro.moe] is a unicycle and Commodore 64 enthusiast, and being the enterprising hacker he is, decided to combine his two interests. This led to the creation of the Uni-Joysti-Cle, the world’s first unicycle controller for the Commodore 64, and the first video game to use this truly immersive, better-than-an-Oculus unicycle controller.
The build began with the creation of Uni Games, the unicycle-enabled video game for the Commodore 64. This game was coded purely in 6502 assembly and features realistic physics, cutting edge graphics, and two game modes. It’s available on [retro.moe]’s site for the C64 and C128 jin PAL and NTSC formats.
Every game needs a controller, and for this [retro.moe] turned to his smartphone. A simple Android app with a few buttons to send up, down, left, and right commands to an ESP8266 chip attached to the C64’s joystick connector.
While a smartphone transmitting controller commands may seem like a vastly over-engineered joystick, there’s at least one thing a smartphone can do that a joystick cannot: poll an accelerometer. When the joystick senses movement, it transmits movement commands to the video game. Strap this phone to the pedal of a unicycle, and it’s the world’s first unicycle controller for a video game. Brilliant, and [retro.moe] can ride that thing pretty well, too.
Getting software-defined radio (SDR) tools into the hands of the community has been great for the development and decoding of previously-cryptic, if not encrypted, radio signals the world over. As soon as there’s a new protocol or modulation method, it’s in everyone’s sights. A lot of people have been working on LoRa, and [bertrik] at RevSpace in The Hague has done some work of his own, and put together an amazing summary of the state of the art.
LoRa is a new(ish) modulation scheme for low-power radios. It’s patented, so there’s some information about it available. But it’s also proprietary, meaning that you need a license to produce a radio that uses the encoding. In keeping with today’s buzzwords, LoRa is marketed as a wide area network for the internet of things. HopeRF makes a LoRa module that’s fairly affordable, and naturally [bertrik] has already written an Arduino library for using it.
So with a LoRa radio in hand, and a $15 RTL-SDR dongle connected to a laptop, [bertrik] got some captures, converted the FM-modulated chirps down to audio, and did a bunch of hand analysis. He confirmed that an existing plugins for sdrangelove did (mostly) what they should, and he wrote it all up, complete with a fantastic set of links.
There’s more work to be done, so if you’re interested in hacking on LoRa, or just having a look under the hood of this new modulation scheme, you’ve now got a great starting place.
If you’re looking for the quickest way to go from zero to voice-controlled home automation system, you should spend five minutes checking out [Hari Wiguna]’s project on Hackaday.io where he connects up IoT gadgets and services into a functioning lightswitch. (Video below the break.)
[Hari] demonstrates how to set up a complex chain: Amazon Echo to IFTTT to Adafruit.io as a data broker, which is then polled by an ESP8266 unit in his home that controls his X10 setup. (Pshwew.) But each step along the way is designed to be nearly plug-and-play, so it’s really a lot like clicking Lego blocks together. [Hari]’s video is a nice overview.
There’s only one catch if you’re going to replicate this yourself: the X10 system that’s used for the last mile. Unless you have one of these setups already, you’re on your own for controlling the outlets that turn the lights on and off. For price and hackability, we suggest the common 433MHz wireless outlet switches and pairing them with cheap 433MHz transmitters, available at eBay for around $1. We’ve seen a lot of hacks of these systems — they’re quite common both in the US and Europe.
The 900-pound gorilla in the corner of the Internet of Things (IoT) hype that everyone is trying to ignore is interoperability. In the Internet of Internets (IoI) everything works on a few standards that are widely accepted: IP and HTML. The discrepancies are in the details and the standards wars are in the past. Websites are largely interoperable. Not so in the wild-west ethos of the IoT.
Philips makes a line of ZigBee-enabled RGB lightbulbs that took the enthusiast community by storm. And initially, Philips was very friendly to other devices — it makes a ZigBee-to-WiFi bridge that would let you control all of your ZigBee-based lights, regardless of their manufacturer, from your phone. Until now.
Philips has just rolled out a “Friends of Hue” certification process, and has since pushed out a firmware update where their Hue bridges stop interoperating with non-certified devices. You can read Philips’ version of the story here.
Philips Locks Out 3rd Party ZigBee Hardware
The hub shown on the right is what’s being locked down.
The short version is that, ZigBee standards be damned, your future non-Philips lights won’t be allowed to associate with the Philips bridge. Your GE and Osram bulbs aren’t Friends of Hue. DIY RGB strips in your lighting mix? Not Friends of Hue. In fact, you won’t be surprised to know who the “Friends of Hue” are: other Philips products, and Apple. That’s it. If you were used to running a mixed lighting system, those days are over. If you’re not on the friends list, you are an Enemy of Hue.
Their claim is that third party products may display buggy behavior on a Philips network, and that this loads up their customer-response hotlines and makes people think that Philips is responsible. Of course, they could simply tell people to disable the “other” devices and see how it works, putting the blame where it belongs. Or they could open up a “developer mode” that made it clear that the user was doing something “innovative”. But neither of these strategies prevent consumers from buying other firms’ bulbs, which cost only 30-50% of Philips’ Hue line.
While Philips is very careful to not couch it as such, the Friends of Hue program really looks like an attempt to shut out their competitors; Philips got an early lead in the RGB LED game and has a large share of the market. As they say themselves in their own press release “Today these 3rd party bulbs represent a minimal fraction of the total product connected to our bridges so the percentage of our users affected is minimal.” And they’d like to keep it that way, even though the people they’re hurting are probably their most vocal and dedicated customers.
And while we, with our manual light switches, laugh comfortably at the first-world problems of Hue consumers, we have to ask ourselves whether we’re next. Today they come for our RGB lightbulbs, but tomorrow it might be our networked toasters. A chilling thought!
Snark aside, the IoT brings two of the saddest realities of the software world into your home appliances: Where there’s code, there’s vulnerabilities, and when you can’t control the code yourself you aren’t really in control. You may own the lightbulb, but you’re merely licensing the firmware that runs it. The manufacturer can change the rules of the game, or go out of the product line entirely, and you’re high and dry. What can you do? Pull out your JTAG debugger.
Of course it’s insane to suggest that everyone needs to become an embedded-device firmware hacker just to keep their fridge running. As we’ve written before, we need to come up with some solution that puts a little more control in the hands of the ostensible owners of the devices, while at the same time keeping the baddies out. We suggest a press-to-revert-firmware button, for instance. When Philips pushes a non-consumer-friendly upgrade, you could vote with your fingertips — but then you’d miss out on bug fixes as well. Maybe it’s better to just give in an learn to love Windows 10.
There are no easy solutions and no perfect software. The industry is still young and we’ll see a lot of companies staking out their turf as with any new technology. It seems to us that IoT devices leave consumers with even less choice and control than in the past, because they are driven by firmware that’s supposed to be invisible. It’s just a lightbulb, right?
What do you think? Any ideas about how to put the power back in the hands of the “owner” of the device without everyone’s refrigerators becoming botnet zombies? Let us know in the comments.
“We underestimated the impact this would have upon the small number of our customers who currently use uncertified lights from other brands in the Philips Hue system. We have decided to continue to enable our customers who wish to integrate these uncertified products within their Philips Hue system.”
