Hackerspaces Are Hard: Safety

October 11, 2017 by John Baichtal 64 Comments

Safety is one of those topics that often elicits a less-than-serious response from some tool users. For these folks, they assume their elite skills will protect them and as long as they pay attention, they never will get hurt. This explains the prevalence of the nickname “Stubby” among this population. On the opposite end of the spectrum, safety is also one of those areas where people who don’t know a lot about tools can overreact. Imagine a whole table of kids wearing goggles as one of them gingerly melts some solder. You don’t want solder in your eye, but that’s just not going to happen under normal circumstances.

And then there are freak accidents, which are a reality. On September 20th, a leaking propane tank exploded at Sector67’s new workshop, severely injuring Chris Meyer. Far from a noob, Chris is one of the most experienced people in the shop and was a co-founder of the space. He has a long road of healing ahead of him, and as seems to be the sad necessity these days, he has a GoFundMe campaign to help both with his medical expenses and to help refurbish the workshop. The Foothills Community Workshop also burned to the ground recently, although fortunately no one was injured.

All in all, hackerspaces seem to be reasonably safe, particular considering the challenges they face — or more fairly, the risks associated with the typical hackerspace’s openness. Most hackerspaces allow anyone who pay dues to be a member. There is a wide range of backgrounds, competencies, and judgments represented with, how shall I put it, some unusual viewpoints that might hinder rule-following. And once the member has a fob or key, it’s open season on any kind of tool in the place right? Not everything can have a lock on it.

Here are a few simple rules that have emerged over the years, and may help your hackerspace navigate the twin dangers of complacency and paralyzed fear while preparing for the freak accidents that may simply come to pass.

Continue reading “Hackerspaces Are Hard: Safety” →

Friday Hack Chat: The Incredible BeagleBoard

October 11, 2017 by Brian Benchoff 12 Comments

Over the last year or so, the BeagleBoard community has seen some incredible pieces of hardware. The BeagleBone on a Chip — the Octavo OSD335x — is a complete computing system with DDR3, tons of GPIOs, Gigabit Ethernet, and those all-important PRUs stuffed into a single piece of epoxy studded with solder balls. This chip made it into tiny DIY PocketBones and now the official PocketBeagle is in stock in massive quantities at the usual electronic component distributors.

For this week’s Hack Chat, we’re talking about the BeagleBoard, BeagleBone, PocketBeagle, and PocketBone. [Jason Kridner], the co-founder of BeagleBoard and beagle wrangler, will be on hand to answer all your questions about the relevance of the Beagle platform today, the direction BeagleBoard is going, and the inner workings of what is probably the best way to blink LEDs in a Linux environment.

Topics for this Hack Chat will include the direction BeagleBoard is going, the communities involved with BeagleBoard, and how to get the most out of those precious programmable real-time units. As always, we’re taking questions from the community, submit them here.

As an extra special bonus, this week we’re giving away some hardware. Digi-Key has offered up a few PocketBeagle boards. If you have an idea for a project, put it on the discussion sheet and we’ll pick the coolest project and send someone a PocketBeagle.

Our Hack Chats are live community events on the Hackaday.io Hack Chat group messaging. This Hack Chat will be going down noon, Pacific time on Friday, October 13th. Wondering why the Brits were the first to settle on a single time zone when the US had a more extensive rail network and the longitude so time zones made sense? Here’s a time zone converter! Use that to ponder the mysteries of the universe.

Click that speech bubble to the right, and you’ll be taken directly to the Hack Chat group on Hackaday.io.

You don’t have to wait until Friday; join whenever you want and you can see what the community is talking about.

The Bane Of Aftermarket Car Alarms

October 10, 2017 by Zoe Skyforest 79 Comments

The humble car alarm has been around almost as long as the car itself, first being developed by an unknown prisoner in Denver, circa 1913. To the security-conscious motorist, they make a lot of sense. The noise of a car alarm draws attention which is the last thing a would-be thief wants, and the in-built immobilizers generally stop the car being moved at all without a time-consuming workaround. Both are a great deterrent to theft.

It may then surprise you to know that I, dear readers, consider the aftermarket car alarm to be one of the most heinous devices ever fitted to the modern automobile. Combining the unholy trifecta of being poorly designed, cheaply made, and fitted by only the most untalented or uncaring people to wield a soldering iron, they are a blight that I myself refuse to accept.

It was my very own Mazda that suffered at the hands of a car alarm system. Two days after purchasing the car, the keyfob died, and thus the car would no longer start. My other car was already out of action due to bent valves, and I needed to get to work, so I figured as a competent hacker, I’d be able to quickly disable it.

Continue reading “The Bane Of Aftermarket Car Alarms” →

Hackaday Links: October 8, 2017

October 8, 2017 by Brian Benchoff 40 Comments

On the top of the popcorn pile for this weekend is an ambiguous tweet from Adafruit that was offered without comment or commentary. [Lady Ada] is holding some sort of fancy incorporation papers for Radio Shack. The smart money is that Adafruit just bought these at the Radio Shack auction a month or so ago. The speculation is that Adafruit just bought Radio Shack, or at least the trademarks and other legal ephemera. Either one is cool, but holy crap please bring back the retro 80s branding.

A Rubik’s Cube is a fantastic mechanical puzzle, and if you’ve never taken one apart, oh boy are you in for a treat. Here’s an RGB LED Rubick’s Cube with not enough detail as to how each square is getting powered. Here’s an open challenge for anyone: build an RGB LED Rubick’s Cube, and Open Source the design.

Last weekend, the front fell off the engine of an Air France A380 flying over Greenland. As with all aircraft incidents, someone has to find the missing bits. It only took a week to find a mangled cowling on an ice sheet. This is incredibly impressive; if you want a comparison to another accident, it took three months to find the fan disk for UA 232 in an Iowa cornfield.

Poorly thought out Kickstarters don’t grab our attention like they used to, but this is an exception. The Aire is a mashup of one of those voice-activated home assistants (Alexa, whatever the Google one is named…) and a drone. The drone half of the build is marginally interesting as a ducted fan coaxial thingy, and building your own home assistant isn’t that hard with the right mics and a Raspberry Pi. The idea is actually solid — manufacturing is another story, though. It appears no one thought about how annoying it would be to have a helicopter following them around their house, or if the mics would actually be able to hear anyone over beating props. Here’s the kicker: this project was successfully funded. People want to buy this. A fool and his or her money…

Processing is cool, although we’re old skool and still reppin’ Max/MSP. It looks like the first annual Processing Community Day is coming up soon. The Processing Community Day will be at the MIT Media Lab on October 21st, with talks from the headliners of the Processing community.

Maker Faire NYC was two weekends ago, the TCT show in Birmingham was last week, and Open Hardware Summit was in Denver this weekend. Poor [Prusa] was at all of them, racking up the miles. He did, however, get to ride [James from XRobots.co.uk]’s electric longboard. There’s some great videos from [James] right here and here.

Speaking of Open Hardware Summit, there was a field trip to Sparkfun and Lulzbot this Friday. The highlight? The biggest botfarm in the states, and probably the second largest in the world. That’s 155 printers, all in their own enclosures, in a room that’s kept at 80° F. They’re printing ABS. Control of the printers is through a BeagleBone running Octoprint. These ‘Bones and Octoprint only control one printer each, and there is no software layer ‘above’ the Octoprint instances for managing multiple printers simultaneously. That probably means the software to manage a botfarm doesn’t exist. There have been attempts, though, but nothing in production. A glove thrown down?

Retrotechtacular: Hacking Wartime Mail

October 6, 2017 by Al Williams 33 Comments

I’m guessing you got quite a few e-mails today. But have you ever had a v-mail? That sounds like some new term for video e-mail, but it actually dates back to World War II. If you are in Europe, the term was Airgraph — not much more descriptive.

If you make a study of war, you’ll find one thing. Over the long term, the winning side is almost always the side that can keep their troops supplied. Many historians think World War II was not won by weapons but won by manufacturing capability. That might not be totally true, but supplies are critical to a combat force. Other factors like tactics, doctrine, training, and sheer will come into play as well.

On the other hand, morale on the front line and the home front is important, too. Few things boost morale as much as a positive letter from home. But there’s a problem.

While today’s warfighter might have access to a variety of options to communicate with those back home, in World War II, communications typically meant written letters. The problem is ships going from the United States to Europe needed to be full of materials and soldiers, not mailbags. With almost two million U.S. soldiers in the European Theater of Operations, handling mail from home was a major concern.

British Mail Hack

The British already figured out the mail problem in the 1930s. Eastman Kodak and Imperial Airways (which would later become British Airways) developed the Airgraph system to save weight on mail-carrying aircraft. Airgraph allowed people to write soldiers on a special form. The form was microfilmed and sent to the field. On the receiving end, the microfilm was printed and delivered as regular mail.

Continue reading “Retrotechtacular: Hacking Wartime Mail” →

BOM Cost Optimization And Tindie Badge Engineering

October 6, 2017 by Brian Benchoff 16 Comments

For the last few months, I’ve been up to my neck in electronic conference badges. This year, I created the single most desirable badge at DEF CON. I also built a few Tindie badges, and right now I’m working on the logistics behind the Hackaday SuperConference badge. Sit tight on that last one — we’re doing something really, really special next month.

Most badge projects are one-off production runs. This is to be expected from a piece of hardware that’s only meant to be distributed at a single event. The Tindie badge is different. It’s now a thing, and we’re building multiple badges for all the cons and conferences Hackaday and Tindie are attending for the rest of the year. This means I have the opportunity to do hardware revisions on the Tindie badge. Right now I’ve built three versions of the Tindie and we’ve distributed about two thousand of these kits at DEF CON, Maker Faire New York, and the Open Hardware Summit.

After about two thousand units, I think we finally have this down. This is how I designed three versions of hardware in as many months and cut the BOM cost of each badge in half. This is bordering on a marginally impressive piece of engineering, and a great lesson on BOM cost optimization.

Continue reading “BOM Cost Optimization And Tindie Badge Engineering” →

A 3D Printer Alone Doesn’t Make A Hackspace

October 5, 2017 by Jenny List 75 Comments

There was a time when hackspaces were few and far between — legendary environments that you’d read about online, where amazing projects were made by people who had come together to form communities of creative technology enthusiasts. Of course, they were always in places far afield, California, or Germany, never in provincial England where I call home. Eventually our movement spread its tentacles into the county towns, and several years later with a stint as a hackspace director behind me I sense that it is on the cusp of escaping its underground roots. Every month seems to bring news of yet another organisation wanting to open a makerspace of their own, be they universities, co-working spaces, enterprise centres, libraries, or even banks. It’s evident that our movement has attracted an aura of edginess when it comes to getting things done, and that these entities are anxious to secure a little piece of that for themselves.

So within a few miles of most hackspaces will be several places where you can find a 3D printer, maybe a vinyl cutter, a CAD workstation, and a soldering iron. There will be a fancy hipster coffee machine and some futuristic furniture, and probably some kind of enclosed meeting pod of dubious design. All of which can no doubt be viewed through a glass wall, so that people in suits can watch all that raw #innovation sizzling away.

Viewed from within the movement, it’s easy to see all this activity on the edges of the world of making as a threat. A struggling community organisation survives on its wits alone, it doesn’t have a multi-million pound (or dollar) university or investor behind it. Its tools are hard-won and patched up, and its coffee machine is a battered electric kettle and a jar of supermarket instant coffee. When it comes to gleaming innovation spaces, a group of assorted makers simply can’t compete. Surely the arrival of these spaces will tempt members away, and the hackspace will inevitably wither, and die.

It’s worth taking a step back at this point, and considering what makes a hackspace. Specifically, what makes a good hackspace.

Continue reading “A 3D Printer Alone Doesn’t Make A Hackspace” →