Hackaday Prize 2022: Saving The World, One Brew At A Time

August 5, 2022 by Elliot Williams 10 Comments

OK, so maybe [satanistik] is overreaching with his project title “Save the Coffee, Save the World” but keeping an otherwise working coffee machine out of the landfill by hacking around its broken display is nonetheless a worthy pursuit. The juice must flow!

The busted display used a SSD1303 controller OLED module, for which the SSD1305Z is an almost-compatible module. Almost. The one glitch is that the screen is filled in the opposite direction by default. Digging through the manuals, there is a screen-direction bit to set, and tracing out the communication with a logic analyzer, it’s set the wrong way with every screen refresh. If only he could flip that one bit while it’s in transit. Time to man-in-the-middle!

While we certainly would have put a microcontroller in the game, [satanistik] goes old-school. A two-IC logic solution can do exactly the same thing, trading wires for code. The final iteration of the converter board is correspondingly spartan, but it does its one job.

So if you’ve got a Nivona coffee machine with a bum display, or perhaps an Agilent U1273A multimeter, or any other piece of equipment that needs a hard-to-find SSD1303 controller, now you have a ready-made solution. But if not, and you find yourself looking for a display that you can’t find, let this serve as an example to you – with a little (fun) effort, you can hack it back.

Demonstrate Danger, Safely

July 30, 2022 by Elliot Williams 67 Comments

Dan Maloney and I were talking about the chess robot arm that broke a child’s finger during the podcast, and it turns out that we both have extreme respect for robot arms in particular. Dan had a story of a broken encoder wheel that lead to out-of-control behavior that almost hit him, and I won’t even get within striking distance of the things unless I know they’re powered off after seeing what programming errors in a perfectly functioning machine can do to two-by-fours.

This made me think of all the dangerous things I’ve done, but moreover about all the intensely simple precautions you can to render them non-risky, and I think that’s extremely important to talk about. Tops of my list are the aforementioned industrial robot arm and high powered lasers.

Staying safe with an industrial robot arm is as easy as staying out of reach when it’s powered. Our procedure was to draw a line on the floor that traced the arm’s maximum radius, and you stay always outside that line when the light is on. It’s not foolproof, because you could hand the ’bot a golf club or something, but it’s a good minimum precaution. And when you need to get within the line, which you do, you power the thing down. There’s a good reason that many industrial robots live in cages with interlocks on the doors.

Laser safety is similar. You need to know where the beam is going, make sure it’s adequately terminated, and never take one in the eye. This can be as simple as putting the device in a box: laser stays in box, nobody goes blind. If you need to see inside, a webcam is marvelous. But sometimes you need to focus or align the laser, and then you put on the laser safety glasses and think really hard about where the beam is going. And then you close the box again when you’re done.

None of these safety measures are particularly challenging to implement, or conceptually hard: draw a line on the floor, put it in a box. There were a recent series of videos on making Lichtenberg figures safely, and as a general rule with high voltage projects, a great precaution is a two-button deadman’s switch box. This at least ensures that both of your hands are nowhere near the high voltage when it goes on, at the cost of two switches.

If all of the safety precautions are simple once you’ve heard them, they were nothing I would have come up with myself. I learned them all from other hackers. Same goes with the table saw in my workshop, or driving a car even. But since the more hackery endeavors are less common, the “common-sense” safety precautions in oddball fields are simply less commonly known. It’s our jobs as the folks who do know the secrets of safety to share them with others. When you do something dangerous, show off your safety hacks!

2022 Hackaday Prize: Make Your World More Disaster Resistant, More Engaged

July 25, 2022 by Elliot Williams 10 Comments

Following along with the 2022 Hackaday Prize theme on building a better world by doing what we all do best – hacking together solutions – the fourth round of the Prize focuses on making our local communities more resilient against and sensitive to severe weather and environmental disasters. Whether it’s an early warning system for wildfires or a distributed communication network that will keep working even when the cell phone service goes down, we’re challenging you to help make your world safer by reacting sooner and better. Get your project entered now!

Sensing

We love systems that help us monitor our environments, and not just for idle curiosity or citizen science. Sometimes it’s critical. We’ve seen monitors aimed at giving you a personal particulate air quality indicator, especially helpful for people with respiratory problems when downstream of a forest fire.

But even better is networking these together to generate an air quality map, or to log long-run trends over time and space. CanAirIO, for instance, has both a fixed and mobile unit that can help map out CO2 and particulate matter quality. Or maybe it’s not wildfires that invade your airspace, but rather pollution from car use. We’ve seen projects like that before too, and anything along these lines would make a great entry into this challenge round. Could you predict local air quality? Continue reading “2022 Hackaday Prize: Make Your World More Disaster Resistant, More Engaged” →

Patents And The Missing Museum

July 23, 2022 by Elliot Williams 38 Comments

A beautiful chapter of the history of invention in the United States ended with a fire in 1880. Well, the fire took place in 1877, but the wheels of government turn slowly. For the first 90 years that patents were granted in the USA, applications were required to be accompanied by a working model – to prove that the idea works and rule out “the perpetual motion cranks”.

During this time, the US Patent Office put all of these models on display, or at least as many of them as they could. The idea was that, alongside the printed documents, people would learn from seeing the inventions in the flesh. This tremendous resource got the Patent Office nicknamed the “Temple of Invention”, and rightly so. Many of the crucial innovations of the industrial revolution were there, in miniature. From Samuel Morse’s model telegraph, through Eli Whitney’s cotton gin, to more than a thousand inventions of Thomas Edison’s, working models were to be seen in the flesh, if in the small. We can only imagine how awe-inspiring it would have been to walk through those halls.

Two fires put significant dents in this tremendous collection. First in 1836, in a fire that consumed most of the approximately 10,000 patents that had been issued to that date, models and paper copies alike. Ironically, these included the patent for the first cast-iron fire hydrant. This fire was so devastating that it led to a dramatic patent reform in that same year, and to the building of a new fireproof Patent Office.

And the “new” Patent Office building still stands today, and proudly displayed patent models until the fire that broke out inside the building in 1877. (The contents of the building weren’t fireproof.) In this second fire, brave employees saved many of the works by staying and battling the fire from inside, but the second demoralizing beatdown, and the accelerating number of patent applications, it became obvious that there just wasn’t enough space to store a model of each patentable invention, and the requirement was dropped in 1880.

A small portion of the remaining patent models were put on display in one wing of the National Portrait Gallery, housed in the Patent Office building, and I had the wonderful opportunity to see it live in the early 2000s. I have no idea if the exhibit is still there – I’m guessing it’s not. The Smithsonian owns the lion’s share of the existing models, and we imagine they are in a warehouse somewhere, like at the end of Raiders of the Lost Ark.

A shame, because seeing a real 3D model of a thing is different from seeing line drawings. Maybe in the future, 3D CAD drawings will take their place? They’d be a lot easier to save in event of a fire.

Ortur Laser Will Go Open-Source

July 18, 2022 by Elliot Williams 74 Comments

Well, that was fast! Last week, we wrote about a video by [Norbert Heinz] where he called out the Ortur laser engravers for apparently using the GPL-licensed grbl firmware without providing the source code and their modifications to it, as required by the license. Because open source and grbl are dear to our hearts and CNC machines, we wrote again about Norbert’s efforts over the weekend, speculating that it might just be unfamiliarity with the open source license requirements on Ortur’s part.

Because of [Norbert]’s persistance and publicity around the issue, the support ticket finally reached the right person within Ortur, and within two or three days [Gil Araújo], Support Admin at Ortur, managed to convince the company that going fully open source was the right thing to do. What remains is the question of how to do it, operationally.

So [Gil] asked [Norbert] to ask Hackaday: what do you want from Ortur on this, and how should they proceed? Via e-mail, he asked in particular for best practices on setting up the repository and making the code actually useful to non-programmer types. He said that he looked around at the other laser engraver companies, and didn’t find any good examples of others doing the Right Thing™, so he asked [Norbert] to ask us. And now we’re asking you!

Have you got any good examples of companies using open-source firmware, modifying it, and making it available for their users? Is a simple Github repo with a README enough, or should he spend some time on making it user-friendly for the non-coders out there? Or start with the former and work toward the latter as a goal? I’m sure [Gil] will be reading the comments, so be constructive! You’ll be helping a laser engraver company take its first steps into actually engaging with the open source community.

We said it before, and we’ll say it again. Good job [Norbert] for taking Ortur to task here, but also by doing so in a way that leaves them the option of turning around and doing the right thing. This also highlights that companies aren’t monolithic beasts – sometimes it takes getting your cause heard by just the right person within a company to change the response from a “this is a business secret” to “how should we set up our Github?” And kudos for [Gil] and Ortur for listening to their users!

The 2022 Hackaday Supercon Is On! And The Call For Proposals Is Open

July 18, 2022 by Elliot Williams 42 Comments

After two years in remote mode, we’re very excited to announce that this year’s Hackaday Supercon will be coming back, live! Join us Nov. 4th, 5th, and 6th in sunny Pasadena, CA for three days of hacks, talks, and socializing with the Hackaday community. And we’d love to see and hear in person what you’ve been up to for the last two years – so start brainstorming what you’re going to talk about now and fill out the call for proposals.

Supercon is On!

We’ll be starting off on Friday Nov. 4th with early-bird registration, a mellow afternoon of badge-hacking and workshops, and a party to kick off the con. Saturday and Sunday will be the full enchilada: two tracks of talks, hacking stations and food set up in the alley, and workshops aplenty. (Just thinking about hacking in the alley and sharing tacos afterward again brings a tear of joy to my eye.) We’ll close up Sunday night with the 2022 Hackaday Prize Awards and a chance to demo the weekend’s badge hacking on stage.

If you haven’t ever been to a Supercon before, it’s Hackaday in real life. People bring hacks to show and share, projects to work on, and their ideas that are too big to fit in the overhead compartment anyway. The crowd is awesome. There are seasoned pros, famous YouTubers, and brand-new hackers to boot. But yet it’s not overwhelming – Supercon is too big to fit in your living room, but it’s nonetheless cozy. The folks in attendance are all fantastic and you’ll stumble into the most awesome conversations.

It’s a weekend you don’t want to miss, so start figuring out how you’re going to get to Pasadena now.

We’ll be putting tickets on sale soon, and while we can’t see into the future, they have sold out every year, so keep your eyes on Hackaday to get yours. And of course, speakers don’t need no stinking tickets. Continue reading “The 2022 Hackaday Supercon Is On! And The Call For Proposals Is Open” →

Fighting The Good Fight

July 16, 2022 by Elliot Williams 21 Comments

We here at Hackaday are super-duper proponents of open source. Software, hardware, or firmware, we like to be able to see it, learn from it, modify it, and make it ourselves. Some of this is self-serving because when we can’t see how it was done, we can’t show you how it’s done. But it’s also from a deeper place than that: the belief that the world is made better by sharing and open access.

One of the pieces of open-source firmware that I have running on no fewer than three devices in my house right now is grbl – it’s a super-simple, super-reliable G-code interpreter and stepper motor controller that has stood the test of time. It’s also GPL3 licensed, which means that if you want to use the code in your project, and you modify it to match your particular machine, you have to make the modified version available for those who bought the machine to modify themselves.

So when Norbert Heinz noticed that the Ortur laser engravers were running grbl without making the code available, he wrote them a letter. They responded with “business secrets”, he informed them again of their responsibility, and they still didn’t comply. So he made a video explaining the situation.

Good news incoming! Norbert wrote in the comments that since the post hit Hackaday, they’ve taken notice over at Ortur and have gotten back in touch with him. Assuming that they’re on their way to doing the right thing, this could be a nice win for grbl and for Ortur users alike.

Inside the free software world, we all know that “free” has many meanings, but I’d bet that you don’t have to go far outside our community to find people who don’t know that “free” software can have tight usage restrictions on it. (Or maybe not – it all depends on the license that the software’s author chose.) Reading software licenses is lousy work better left for lawyers than hackers anyway, and I can no longer count how many times I’ve clicked on a EULA without combing through it.

So what Norbert did was a good deed – educating a company that used GPL software of their obligations. My gut says that Ortur had no idea what they needed to do to comply with the license, and Norbert told them, even if it required some public arm-twisting. But now, Ortur has the opportunity to make good, and hackers everywhere can customize the firmware that drives their laser engravers. Woot!

It’s probably too early to declare victory here, but consider following Norbert’s example yourself. While you can’t bring a lawsuit if you’re not the copyright owner, you can still defend your right to free software simply by explaining it politely to companies that might not know that they’re breaking the law. And when they come around, make sure you welcome them into the global open-source hive mind, because we all win. One of us!