This excellent content from the Hackaday writing crew highlights recurring topics and popular series like Linux-Fu, 3D-Printering, Hackaday Links, This Week in Security, Inputs of Interest, Profiles in Science, Retrotechtacular, Ask Hackaday, Teardowns, Reviews, and many more.
I tried my best to see every badge and speak with every badge maker at DEF CON 26. One thing’s for sure, seeing them all was absolutely impossible this year, but I came close. Check out the great badges shown off in volume 1 and in volume 2 of this series. The game is afoot, and if you are headed to a hacker conference there’s never been a better time to build your own hardware badge — whether you build 5 or 500!
Everyone knows that space is an incredibly inhospitable place, but the surface of Mars isn’t a whole lot better. It’s a dim, cold, and dry world, with a wisp of an atmosphere that provides less than 1% of Earth’s barometric pressure. As the planet’s core no longer provides it with a magnetosphere, cosmic rays and intense solar flares bathe the surface in radiation. Human life on the surface without adequate environmental shielding is impossible, and as NASA’s fleet of rovers can attest, robotic visitors to the planet aren’t completely immune to the planet’s challenges.
Opportunity Mission Patch
As a planet-wide dust storm finally begins to settle, NASA is desperately trying to find out if the Red Planet has claimed yet another victim. The agency hasn’t heard from the Opportunity rover, which landed on Mars in 2004, since before the storm started on June 10th; and with each passing day the chances of reestablishing contact are diminished. While they haven’t completely given up hope, there’s no question this is the greatest threat the go-kart sized rover has faced in the nearly 15 years it has spent on the surface.
Opportunity was designed with several autonomous fail-safe systems that should have activated during the storm, protecting the rover as much as possible. But even with these systems in place, its twin Spirit succumbed to similar conditions in 2010. Will Opportunity make it through this latest challenge? Or has this global weather event brought the long-running mission to a dramatic close?
Today is the start of the Musical Instrument Challenge. This newest part of the 2018 Hackaday Prize asks you to go far beyond what we’re used to seeing from modern musical instrumentation. Twenty entries will be awarded $1,000 each and go on to compete in the final round of the Hackaday Prize.
Imagine music without the electric guitar amp, violin, two turntables and a microphone, the electric drum pad, or in the absence of autotune. Maybe that last one made you groan, but autotune is a clever use of audio manipulation and when used to augment the music (rather than just to correct off-key voices) it shows its value as a new tool for creativity.
Musicians have always been hackers. The story of Brian May’s handmade guitar — the Red Special — is one of not being able to buy it, so he built it. Unlocking emotion in the listener has always meant finding new and different ways to use sound. This is a natural motivator to re-imagine and invent new ways of doing that. That first hand-built guitar got him in the door, but iterative improvements to the tremolo bar, the pickups, and even just the mechanical engineering of the neck made it a new instrument that you’ve heard in every Queen performance since.
So what’s next? What does a brand new instrument, interface, tool, or trick look like? That’s what we want to see from this Hackaday Prize challenge. From instrument makers to the people who write software for sampling, synthesizing, sequencing, and manipulating sound, we’re looking for things that let others make music. These creations are the tools of the trade that help more people unlock their musical creativity. Show off your work by sharing all the details of your design, and demonstrate the music you can make with it.
You have until October 8th to put your entry up on Hackaday.io. The top twenty entries will each get $1,000 and go on to the finals where cash prizes of $50,000, $20,000, $15,000, $10,000, and $5,000 await.
It’s often said that necessity of the mother of invention, but as a large portion of the projects we cover here at Hackaday can attest, curiosity has to at least be its step-mother. Not every project starts with a need, sometimes it’s just about understanding how something works. That desire we’ve all felt from time to time, when we’ve looked at some obscure piece of hardware or technology and decided that the world would be a slightly better place if we cracked it open and looked at what spilled out.
That’s precisely the feeling Eric O’Callaghan had when he looked out the window of his Philadelphia apartment a few years back and saw something unusual. Seemingly overnight, they had built an automated Indego bike sharing station right across the street. Seeing the row of light blue bicycles sitting in their electronic docks, he wondered how the system worked, and what kind of data they might be collecting. He didn’t need to rent a bike, he hadn’t even ridden one in years, but he suddenly had a strong urge to go across the street and learn as much as he could about this system.
He recently presented those findings during FOSSCON 2018 at the International House in Philadelphia, in the hopes that others might be interested in getting involved. Currently Eric is one of the only people who’s investigating the public data Indego offers, and as his personal MySQL database has now surpassed 15 million rows of data, he’s hoping to get some developers with big data experience into the fray. His approach to making this data useful is an interesting one which I’ll dive into after the break.
We’re living in the world of connected devices. It has never been easier to roll your own and implement the functionality you actually want, rather than live with the lowest common denominator that the manufacture chose.
In a previous article I walked though a small python script to talk to a BLE light and used it to cycle through some colors. Now I want to delve deeper into the world of Internet Connected BLE devices and how to set up a simple Internet-Of-Things light. With this example in hand the sky’s the limit on what you can build and what it will be able to do.
Join me after the break as I demonstrate how to use NodeJS to bridge the digital world with the physical world.
A lot of times these days, it seems like we hackers are a little like kids in a candy store. With so many cool devices available for pennies at the click of a mouse, it’s temptingly easy to order first and ask questions about quality later. Most of the time that works out just fine, with the main risk of sourcing a dodgy component being a ruined afternoon of hacking when a part fails.
The stakes are much higher when you’re connecting your project to the house mains, though, as [Mattias Wandel] recently learned when the solid-state relay controlling his water heater failed, with nearly tragic results. With aplomb that defies the fact that he just discovered that he nearly burned his house down, [Mattias] tours the scene of the crime and delivers a postmortem of the victim, a Fotek SSR-25DA. It appears that he mounted it well and gave it a decent heatsink, but the thing immolated itself just the same. The only remnant of the relay’s PCB left intact was the triac mounted to the rear plate. [Mattias] suspects the PCB traces heated up when he returned from vacation and the water heater it was controlling came on; with a tank full of cold water, both elements were needed and enough current was drawn to melt the solder build-up on the high-voltage traces. With the solder gone, the traces cooked off, and the rest is history. It’s a scary scenario that’s worth looking at if you’ve got any SSRs controlling loads anywhere near their rated limit.
The morals of the story: buy quality components and test them if possible; when in doubt, derate; and make sure a flaming component can’t light anything else on fire. And you’ll want to review the basics of fire protection while you’re at it.
Usually, with Circuit VR we look at some circuit in detail with simulation — usually LTSpice. This one will be a little meta because I wanted to look at a capability in LTSpice which ironically is very useful, but not often used. Along the way, though, we’ll look at why you get maximum power transfer when your source impedance matches your load impedance. This is something you probably already know about, but it is interesting to look at in simulation if you know how to coax LTSpice — no pun intended — into showing you a meaningful graph.
The circuit is super simple. An AC source and a 50-ohm resistor stand-in for a 40-meter ham transmitter. With 100 volts into a 50-ohm load. So far, so good.