This weekend is the Vintage Computer Festival East in Wall, New Jersey. Every year is different, but there’s a general plan for each day. On Saturday and Sunday, the exhibits rule the con, the consignment shop is busy, and the keynotes bring down the house. Friday is a little different. This is the day for ‘in the trenches’ talks from the commodore crew, classes on recapping 30-year-old computers, and this year – for the first time – a retro hackathon. It’s basically the same format as any other hackathon, but instead of bringing MacBooks and building something cool, Apple IIs and Commodore 64s were provided. This is the report on the first retro hackathon we’ve ever been to.
First off, no one remembers how to program in BASIC. If you’re looking for a population that should remember the vagaries of the different dialects of BASIC, you would think it would be the people who came out to the middle of Jersey on Friday to talk about old CPUs. Apparently, this is not the case and several people were confused about single and double quotes in PRINT statements. Luckily, a few programming manuals for the C64 and Apple II were available, so everyone could still have fun with PEEKs and POKEs.
If you want to get people programming on some old machines, you need to give them some inspiration. The first half hour of the retro hackathon didn’t see any teams programming. Given this demographics proclivity to say, ‘I can do that better’, I typed a few BASIC one-liners in the C64 (random Truchet tiles in PETSCII) and Apple II (a SIN graph), and the people started pouring in. Yes, they could program something better than a single line of BASIC.
Sound on an Apple IIc.
What came of an impromptu retro hackathon? Hangman, in BASIC. No, it didn’t quite work, and there were only three or four possible words hardcoded into the program. Still, text mode graphics are a lost art. The Apple IIc was programmed to make fart noises. The original plan for this project was to program music. What would have been the winning entry was a line-drawing program on the C64 that looked like the enemy in Qix. That guy wasn’t there during judging. The winner of a $50 credit to the consignment shop was a kid who programmed zero-player Pong on Apple II basic. He bought a Mac Portable (non-backlit) with that prize.
We’ve gone to hackathons, we’ve waded through the sea of MacBooks, and had a Red Bull drip installed. This retro hackathon was completely different, but somehow familiar. No, no one is going to create something new – everything that can be done on these machines in a few hours of BASIC programming has already been done. That’s not the point, though. It’s a geek pride of proving your mettle, putting your money where your mouth is, and doing it in a casual environment where everyone is friendly. This is the first retro hackathon we’ve gone to, and it won’t be the last. We’re going to do this again, once we get an Apple IIc+, a few Commodores, a Speccy, and a few good monitors. We already have the banner, anyway.
Troy New York’s Tech Valley Center of Gravity is following up their January IoT Hackathon with another installment. The April 16-17 event promises to be a doozy, and anyone close to the area with even a passing interest in gaming and AR/VR should really make an effort to be there.
Not content to just be a caffeine-fueled creative burst, TVCoG is raising the bar in a couple ways. First, they’re teaming up with some corporate sponsors with a strong presence in the VR and AR fields. Daydream.io, a new company based in the same building as the CoG, is contributing a bunch of its Daydream.VR smartphone headsets to hackathon attendees, as well as mentors to get your project up and running. Other sponsors include 1st Playable Productions and Vicarious Visions, game studios both located in the Troy area. And to draw in the hardcore game programmers, a concurrent Ludum Dare game jam will be run by the Tech Valley Game Space, with interaction and collaboration between the AR/VR hackers and the programmers encouraged. Teams will compete for $1000 in prizes and other giveaways.
This sounds like it’s going to be an amazing chance to hack, to collaborate, and to make connections in the growing AR/VR field. And did we mention the food? There was a ton of it last time, so much they were begging us to take it home on Sunday night. Go, hack, create, mingle, and eat. TVCoG knows how to hackathon, and you won’t be disappointed.
Thanks to [Duncan Crary] for the heads up on this.
What’s not to love about a hackathon? The junk food and caffeine that fuel the weekend; the highs that come with success and the lows that come when the blue smoke is released; the desperate search for inspiration as the clock ticks away; nerve-wracking pitches to the judges, hoping against hope that everything works in the demo. Hackathons are the contact sport of the hacker world, bringing in top competitors and eager upstarts, and when done well you just might attract interested “civilians” and other newbies that will catch the hacking bug from what they witness.
Such was the scene at the Tech Valley Center of Gravity in Troy, NY over the last weekend of January. New for 2016, the CoG is hosting a series of four hardware hackathons this year, each with a different theme. This event’s theme was “Internet of Things”, and the call went out to any and all to come compete for bragging rights and over $1,000 in prizes. Incentives to compete included some big name corporate sponsors, like AT&T, and judging and mentoring provided by the likes of SparkFun’s [Jeff Branson]. There was also a steady stream of food and drink, saturation coverage by local media outlets, and your humble Hackaday writer and his son, who made the trip up to Troy with a small passel of Hackaday swag and a curiosity to see how the CoG has fared since our last visit at the grand opening of their glorious new home. We were not disappointed.
Measuring the body’s electrical signals is a neat trick… if you can get your equipment dialed in enough to establish dependable measurements. The technique is called Surface ElectroMyography (SEMG) though you’ll hear many call this ECG. They’re essentially the same technology; the Electro CardioGraph instruments monitor the activity of the heart while SEMG Instruments monitor electrical signals used to control other muscles. Both types of hardware amount to an instrumentation type amplifier and some form of I/O or display.
This topic has been in my back pocket for many months now. Back in May we Hackaday’ites descended on New York City for the Disrupt NY Hackathon event. We arrived a day or so early so that we might better peruse the Korean BBQ joints and check out the other electronics that NY has to offer. On Saturday we gathered around, each shouting out the size of his or her t-shirt preference as we covered up our black Hackaday logo tees with maroon maroon ones (sporting the Hackaday logo of course) for a 24-hour craze of hardware hacking.
There were two individuals at our tables who were both hacking away on hardware to measure the electrical field produced by the body’s muscles in some form or another. The electrical signals measured from the skin are small, and need careful consideration to measure the signal despite the noise. This is a fun experiment that lets you work with both Instrumentation Amplifiers and OpAmps to achieve a usable signal from the movement of your body.
Big-name corporate sponsors, top-notch judges and mentoring, 36 hours to play in a huge new hackerspace, and all the Cheetos and Red Bull you need to stoke the creative fires. Sounds like a hackathon, and it’ll roll into The Tech Valley Center of Gravity in Troy, New York next month. And from the look of it, it’s going to be a big deal. You should be there.
You might recall the TVCoG from a story we did this summer on the grand opening of their amazing newly renovated space in downtown Troy. Occupying an entire city block in a historic department store building and housing not only a huge hackerspace but a tech company incubator with manufacturing capabilities and a STEM outreach space, the CoG now has the room to reach out into the community and host big events. The hackathon scheduled for January 30 and 31 and is only the first of four events planned for 2016. This one has the theme “Internet of Things” and will feature SparkFun’s Jeff Branson as mentor and judge.
Here’s a call to arms for Hackaday readers in the northeast: let’s pack this hackathon and make it huge. There’s already a bunch of Jolly Wrencher stickers scattered all over from our last visit, so you’ll feel right at home. Head over to the TVCoG site and sign up for this one. We’d really like to see HaD take home bragging rights. And you can be sure we’ll be covering the event and bringing some swag of our own.
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.
The concept behind crop squares is to make a graphical user interface using Dizmo that clearly shows the status of your crops in a grid system. For the prototype they used an Arduino Pro Mini with moisture sensors in potted plants to detect moisture levels, while a Raspberry Pi also collected weather data for the area being watched. The Arduino used an ESP8266 WiFi module to transmit the data remotely. To demonstrate how the system could be used in an automated sense, they hooked up another Arduino (this time a Leonardo), to pour water once the moisture levels dropped below a certain threshold.
Crop Squares won the Best Pitch Award as well as the Best Integration of Dizmo — good job guys!