A mind is a terrible thing to waste – but an awesome thing to hack. We last visited brain hacks back in July of 2015. Things happen fast on Hackaday.io. Miss a couple of days, and you’ll miss a bunch of great new projects, including some awesome new biotech hacks. This week, we’re checking out some of the best new mind and brain hacks on Hackaday.io
We start with [Daniel Felipe Valencia V] and Brainmotic. Brainmotic is [Daniel’s] entry in the 2016 Hackaday Prize. Smart homes and the Internet of Things are huge buzzwords these days. [Daniel’s] project aims to meld this technology with electroencephalogram (EEG). Your mind will be able to control your home. This would be great for anyone, but it’s especially important for the handicapped. Brainmotic’s interface is using the open hardware OpenBCI as the brain interface. [Daniel’s] software and hardware will create a bridge between this interface and the user’s home.
Next we have [Angeliki Beyko] with Serial / Wireless Brainwave Biofeedback. EEG used to be very expensive to implement. Things have gotten cheap enough that we now have brain controlled toys on the market. [Angeliki] is hacking these toys into useful biofeedback tools. These tools can be used to visualize, and even control the user’s state of mind. [Angeliki’s] weapon of choice is the MindFlex series of toys. With the help of a PunchThrouch LightBlue Bean she was able to get the EEG headsets talking on Bluetooth. A bit of fancy software on the PC side allows the brainwave signals relieved by the MindFlex to be interpreted as simple graphs. [Angeliki] even went on to create a Mind-Controlled Robotic Xylophone based on this project.
Next is [Stuart Longland] who hopes to protect brains with Improved Helmets. Traumatic Brain Injury (TBI) is in the spotlight of medical technology these days. As bad as it may be, TBI is just one of several types of head and neck injuries one may sustain when in a bicycle or motorcycle accident. Technology exists to reduce injury, and is included with some new helmets. Many of these technologies, such as MIPS, are patented. [Stuart] is working to create a more accurate model of the head within the helmet, and the brain within the skull. From this data he intends to create a license free protection system which can be used with new helmets as well as retrofitted to existing hardware.
Finally we have [Tom Meehan], whose entry in the 2016 Hackaday Prize is Train Your Brain with Neurofeedback. [Tom] is hoping to improve quality of life for people suffering from Epilepsy, Autism, ADHD, and other conditions with the use of neurofeedback. Like [Angeliki ] up above, [Tom] is hacking hardware from NeuroSky. In this case it’s the MindWave headset. [Tom’s] current goal is to pull data from the TAGM1 board inside the MindWave. Once he obtains EEG data, a Java application running on the PC side will allow him to display users EEG information. This is a brand new project with updates coming quickly – so it’s definitely one to watch!
If you watch a lot of TV just after Christmas, you will be familiar with partworks. Or at least, you will if you live in the part of the world this is being written from, and if you aren’t you should count yourself lucky. The premise is simple: buy this magazine once a month, and in each issue you will receive a fresh component which you can assemble over time into a beautiful model of a galleon, a Lancaster bomber, or a patchwork quilt.
The value for money offered by such publications is highly suspect, the quality of the finished item is questionable, and though the slick TV adverts make them sound alluring you’re much better off buying the Airfix model kit or just cutting your own patches.
There’s a partwork that caught our eye which may be worth a second look. It’s probably unfair on reflection to call it a partwork though as it doesn’t deserve to be associated with the scammier end of the publishing business. Swansea Hackspace are currently running a six-week all-inclusive course designed to introduce the participant to robotics through a step-by-step assembly of an Arduino based robot. Tickets were £60 ($85) to hackspace members, and all parts were included in that price.
At first sight it might seem a little odd to feature a course. It’s not a hack, you’ll say. And though the little Arduino robot is a neat piece of kit, you’d be right. It’s hardly ground-breaking. But the value here doesn’t lie in the robot itself, but in the course as an exercise in community engagement. If you are involved in the running of a hackspace perhaps you’ll understand, it can sometimes be very difficult to persuade timid visitors to come along more than once, or to join the space. Hackspaces can be intimidating places, after all.
The Swansea course holds the promise of addressing that issue, to say to an interested but non-expert newcomer that they needn’t worry; if they have an interest in robotics then here’s a way to learn. This community engagement and spreading of knowledge reveals an aspect of the hackspace movement that sometimes remains hidden, and it’s something we’d like to see more of in other spaces.
The more tools you have the better. Unfortunately, not everyone has the space, or the money for full-size equipment. Looking to expand his maker capabilities, [Bruno] had the clever idea to turn a hand-tool, into a power tool. One we’ve never even seen before — a powered hacksaw.
Using his 3D printer he designed a linkage system, not unlike a steam locomotive drive to turn rotary motion from a geared motor into linear motion. Not only that, it also angles the hacksaw as it goes. 3D printed brackets hold the hacksaw in place, and weight can be added to the top to adjust the cutting speed. He even 3D printed a guide for his vice to line up the material to where the blade will cut.
Bare feet, bare hands, and bare chest – if it weren’t for the cargo shorts and the brief sound of a plane overhead, we’d swear the video below was footage that slipped through a time warp. No Arduinos, no CNC or 3D anything, but if you doubt that our Stone Age ancestors were hackers, watch what [PrimitiveTechnology] goes through while building a tile-roofed hut with no modern tools.
The first thing we’ll point out is that [PrimitiveTechnology] is not attempting to be (pre-)historically accurate. He borrows technology from different epochs in human history for his build – tiled roofs didn’t show up until about 5,000 years ago, by which time his stone celt axe would have been obsolete. But the point of the primitive technology hobby is to build something without using any modern technology. If you need a fire, you use a fire bow; if you need an axe, shape a rock. And his 102 day build log details every step of the way. It’s fascinating to watch logs, mud, saplings, rocks and clay come together into a surprisingly cozy structure. Especially awesome if a bit anachronistic is the underfloor central heating system, which could turn the hut into a lovely sauna.
Software hackathons are an old hat these days. They’re a great scouting opportunity for talented candidates looking for a job, and they provide the battleground for coding enthusiasts to prove themselves by developing a project from start to finish overnight, albeit, with a few kinks. Hardware hackathons are an entirely different beast. By trading APIs for components and Python libraries for soldering irons, they pull the excitement out of the text editor and onto the workbench for everyone to see.
While hardware hackathons might be “the next big thing” with you and your four best DIY-pals, the broad range of physical components, from Arduinos to CNC milling time, makes rule-establishment, safety enforcement, and winning criteria far more difficult to constrain within a single night. Enter Muddhacks. This past October, three students from Harvey Mudd College set out to deliver a hardware hackathon that would open their student community’s mind to the thought of tinkering-for-fun in their spare time outside the lab and beyond their homework.
Students [Benjamin Chasnov], [Apoorva Sharma], and [Akhil Bagaria] had just finished their experimental engineering class: E80. Along the way, they designed a custom sensor payload into a meter-long rocket and launched both rocket and payload to measure the rocket’s fundamental frequencies in flight. With a victory behind them, they were ready for their next big project.
As the next semester waned onwards, however, they realized that any big project–no matter how modular–would be a serious time commitment. After some thought, they refactored their idea entirely. Tinkering was a passion shared by each of them; why not spread the love school-wide and bring together a community of engineers-by-night? To resolve their craving for after-hours engineering and to inspire a culture of collaborative tinkering, they set out to bootstrap a hardware hackathon; an event where many projects could be realized by many students in a single night.
Everyone Says Hardware is Hard
For the unitiated, hardware looks hard. Breadboards, LEDs, r`esistors? To those who have never put together a simple circuit before, taking that first leap is a challenge set by a box of components that almost seems to glare back menacingly. The three teammates took this first-timer roadblock as a challenge unto themselves to break down that barrier. Thus, HackWeek was born.
HackWeek was the MuddHacks teams’ answer to get students comfortable gluing modules together to produce a functional project in a short time. How do I make things move? How do I connect things to the internet? What parts do I choose? All of these questions-worth-answering became topics of the three-day event before the hackathon. The idea behind HackWeek was simple: give eager students enough theory and a functional demo that they could probe, tweak, and recompile so that they could feel more comfortable developing their own ideas into projects. On day one, the MuddHacks team brought functional demos of various motors into the hands of eager students. By day two, the three teammates actually assembled a functional hack of their own before the eyes of their listeners: an internet-enabled microwave that could remotely start warming up that cup of ramen on your way back from class.
Unlike software hackathons, a successful hardware hackathon involves parts, and the MuddHacks team was well-prepared to bring the participants the parts that they wanted. With ten days to go before the event, [Ben] took orders from each team’s desired list of parts. With a day to go, all parts arrived before the event and made it to their respective user’s hands in “goodie bags” on the last day of HackWeek. On this last day, teams opened their bags and explored the parts given to them and to other teams while taking advice from the mentors present to offer tips for using various components. This time for “open-exploration” ensured that the following night spent hacking would be more fruitful, now that teams had cleared the starting questions for various parts on the previous day.
On the night of MuddHacks, [Ben], [Apoorva], and [Akhil] had completely turned their original aim to build their own project into a night spent mentoring the projects of others. Throughout the night, they became the “ground crew,” bringing advice to debugging teams and keeping the night culture alive with two waves of snacks. “We felt that if students were going to come to our event, it was our responsibility to keep them both awake and happy,” Apoorva mentioned. Classrooms refilled for the night with students eager to bring their robots, LEDs, and gantries to life, but other parts of the school came to life as well. The machine shops reopened, and old oscilloscopes and test equipment emerged from the engineering stock room for loan to any teams that needed them. Even a few professors happened to wander into classrooms and offer advice.
For [Ben], [Apoorva], and [Akhil], fostering a sense of community in tinkering became their top priority. As they wandered between teams, they encouraged stellar performers to take a brief break and help out another team through a bug. At the night’s end, a number of early-rising professors joined the crowd of students to judge the winners. Oddly enough, the MuddHacks team didn’t spend any money on the prizes–but no one seemed to notice or care. For the eighth of the entire undergraduate student body that attended, these students weren’t coming for the prizes. They came to join that culture of tinkerers–to be a fellow hardware-hacker-by-night–eager to do their part to make the world blink.
When was the last time you burned yourself downloading someone else’s API? Probably never. With a hardware hackathon, comes a new wave of challenges not seen before in the software variant. With one successful hackathon under their belt, we asked the MuddHacks Team to share some insights for other teams looking to assemble their own hardware hackathon. Here’s what they came up with.
Charging participants an entrance fee may solve the problem of funding, but for the thrifty, starving student, entrance fees may also weed out people who had a slight curiosity but weren’t eager to throw a few bucks down to support it. The solution? Bring participants in for free and support the hackathon with external funding. The MuddHacks team reached out to a number of companies and encouraged them to take a sincere look at their website and cause.
The Muddhacks team handled most of their administrative work online. Among the tools they chose were
Google Forms for parts orders and feedback
Slack and email lists for real-time updates during the event
Google Spreadsheets for keeping track of order requests
Bootstrap for deploying a website
The Muddhacks team mandated that students form teams to enter the hackathon, mostly to foster community and collaboration. They reasoned: “If you already build things for fun on your own, you don’t need a hackathon to get you excited about hardware for the first time.” Most teams self-assembled, but the Muddhacks team also suggests a submission form for stragglers to pair up.
Ten days before the hackathon, [Ben] put out a call to order parts in a $100 budget range. Each team made part requests, and [Ben] then ordered each of these parts in time for the hackathon. In addition, the Muddhacks team also ordered a collection of additional stock hardware (think: Arduinos and shields).
Setting the Stage
The Muddhacks team received permission to host the night event on the third floor of one of their buildings filled with classrooms. Among points to consider for the setting are:
reliable Wi-Fi connectivity
power outlet access
Soldering irons and sleep-deprivation don’t mix well. Among the points to consider for safety are tools that will keep users safe (safetly glasses and ventilation in this case). The MuddHacks team also recommends a safety waiver.
Advertising and Swag
Getting people excited is key. Logos, T-shirts, and Mugs all add to the authenticity of the one-night event. The Muddhacks Team brought in each of these to its participants. In addition, they printed posters, deployed a website and facebook page, and pitched to students directly in their computer science and engineering classes.
Keeping the Night Moving
Feed the masses. The MuddHacks team reminds us that, as the hosts and organizers of the event, it’s your responsibility to make sure that attendees are both awake and enjoying their time. Not only did the team provide two rounds of food, they also walked around and engaged participants that needed some help debugging, effectively becoming an extra set of eyes to track down bugs as mentors throughout the night.
The MuddHacks team brought in their favorite professors to judge teams’ projects. At this event, the MuddHacks team stresses that all participants deserve to see all projects. Not only can they witness something awesome, they can also engage their peers with questions, effectively learning a few extra tricks that they didn’t discover while working on their own project.
Priming for Next Year
From the MuddHacks Team: “Take pictures!” While the first website and facebook page were filled with images of the tools and the setting, next years website and advertisements could be filled with pictorial proof of the promise to participants of a genuine experience. As the first hackathon closes, they also stress that you, the organizers and founders, learn too; and the best way to do so is to collect feedback with some manner of online form. At the same time, this form could also recruit additional hands for assembling next year’s hackathon.
We hope these tips from a stellar hackathon serve as a starting point for developing one of your own. To learn more about MuddHacks, take a quick visit to their website: MuddHacks.com, or follow them on their Facebook page.
This article was specifically written for the Hackaday Omnibus vol #02. Order your copy of this limited edition print version of Hackaday.
Halloween is when the ghouls start haunting and the hackers start hacking. All hallows eve is the perfect holiday for eerie blinking LEDs, spooky audio oscillators, and wild animatronics. We had a double dose of Halloween hacks last year on the Hacklet. This year we’re bringing you even more of the best Halloween hacks on hackaday.io!
We start with [dougal] and Halloween Blinky Eyes. [Dougal] wanted to create the effect of creatures peeking at you from the dark corners of the room, and he’s certainly nailed it. A strip of WS2812 LEDs is the trick here. Pairs of LEDs light up, blink, and fade away like spooky eyes. The Strip is controlled by a Particle Core using Adafruit’s NeoPixel Library, though [Dougal] plans to move to the FastLed library. Everything is powered by a USB power pack. This hack isn’t much to look at with the lights on, so check out the video to see these eyes really shine!
Next up is [controlmypad] with Blair the Witch Project. A normal trip to Home Depot turned paranormal when [controlmypad] spotted an awesome witch decoration. The free-standing mannequin had some basic animatronics and the all important manual trigger. [controlmypad] already had a discarded electric wheelchair. After replacing the chair batteries he modified it with a Sabertooth 2×32 Motor Controller and a standard radio control receiver. A spare channel was connected to Blair’s manual trigger. An aluminum tube joins the witch and the scooter. The hardest part of this hack was keeping Blair’s skirt out of the scooter wheels. Home Depot to the rescue! A simple hoop made of lawn edging plastic keeps the fabric and wheels apart.
[Alex Cordonnier] and his team participated in Boilermake 2015, a 24 hour Hackathon at Purdue University. The fruit of their labor is Trick or Tweet, the tweeting Jack-o’-lantern. Yes folks, we now have the internet of gourds. Hiding inside Trick or Tweet is a Raspberry Pi and a Pi Camera. The pumpkin itself is also a giant capacitive touch switch. Touching the pumpkin triggers a count down after which Trick or Tweet snaps a photo. It then adds some spooky Halloween overlays, a pun or two, and throws the whole thing up on twitter @PumpkinPiPics. [Alex] hasn’t uploaded the code yet, but we’re guessing it consists of a few Python scripts. Pretty awesome for 24 hours of work!
Sometimes Halloween hacks take on a life of their own. That’s exactly what happened when [Hari Wiguna] sat down with a few parts he ordered from China. Happy Halloween 2015 is the result. [Hari’s] order included some potentiometers, a two color OLED display, and some Arduino clones. In no time [Hari] had three pots wired up to the Arduino’s analog inputs. The OLED quickly followed, displaying graphics via the Arduino’s I2C bus. He really wanted a Jack-o’-lantern though. It took a bit more tweaking, but eventually [Hari] was successful. The first pot sets eye size. The second controls eye rotation. The third pot changes the width of Jack’s mouth. [Hari] has all the code for this hack up on his most recent project log.
Not spooked enough? If you want to see more Halloween projects, check out our newly updated Halloween hacks list! Did I miss your project? Don’t be shy, just drop me a message on Hackaday.io. That’s it for this week’s Hacklet; As always, see you next week. Same hack time, same hack channel, bringing you the best of Hackaday.io!
With the summer’s big security conferences over, now is a good time to take a look back on automotive security. With talks about attacks on Chrysler, GM and Tesla, and a whole new Car Hacking village at DEF CON, it’s becoming clear that autosec is a theme that isn’t going away.
Up until this year, the main theme of autosec has been the in-vehicle network. This is the connection between the controllers that run your engine, pulse your anti-lock brakes, fire your airbags, and play your tunes. In most vehicles, they communicate over a protocol called Controller Area Network (CAN).
A number of talks were given on in-vehicle network security, which revealed a common theme: access to the internal network gives control of the vehicle. We even had a series about it here on Hackaday.
The response from the automotive industry was a collective “yeah, we already knew that.” These networks were never designed to be secure, but focused on providing reliable, real-time data transfer between controllers. With data transfer as the main design goal, it was inevitable there would be a few interesting exploits.