After The Con: Da Bomb Badge Post Mortem

We’ve reported on the world of electronic badges here at Hackaday since their earliest origins in [Joe Grand]’s work for DEF CON 14 in 2006. In that time we’ve seen an astonishing variety of creations, covering everything from abstract artwork to pure functionality in a wearable device. But it’s not been quite so often that we’ve looked at the other side of the BadgeLife coin, so it’s fascinating to read [John Adams]’ account of the work that went into the production of this year’s 500-piece run of the Da Bomb DEF CON indie badge.

In it, [John] goes over scheduling worries, component sourcing issues, PCB assembly delays, and an in-depth look into the finances of such a project. In case anyone is tempted to look at Badgelife as the route to millions, it rapidly becomes apparent that simply not losing too much money is sometimes the best that can be hoped for. There were a few design problems, one of them being that the SAO I2C bus was shared with the LED controller, resulting in some SAOs compatibility issues. In particular the AND!XOR DOOM SAO had its EEPROM erased, creating something of a headache for the team.

A surprise comes in the distribution: obviously shipping is expensive, so you’d think badge pick-ups at the con would be straightforward alternative. Unfortunately, they became something of a millstone in practice, and organising them was a Herculean task. Astoundingly, some paying customers didn’t bother turn up for their badges. Which was especially infuriating since the team lost valuable conference time waiting for them.

Some of you are BadgeLife creators and will nod sagely at this. Still more of you will wish you were BadgeLife creators and find it a useful primer. For everyone else it’s a fascinating read, and maybe makes us appreciate our badges a bit more.

The images may have departed, but just to return to the origins of BadgeLife, here’s our coverage of that first [Joe Grand] badge.

Hands-On: CCCamp2019 Badge Is A Sensor Playground Not To Be Mistaken For A Watch

Last weekend 5,000 people congregated in a field north of Berlin to camp in a meticulously-organized, hot and dusty wonderland. The optional, yet official, badge for the 2019 Chaos Communication Camp was a bit tardy to proliferate through the masses as the badge team continued assembly while the camp raged around them. But as each badge came to life, the blinkies that blossomed each dusk became even more joyful as thousands strapped on their card10s.

Yet you shouldn’t be fooled, that’s no watch… in fact the timekeeping is a tacked-on afterthought. Sure you wear it on your wrist, but two electrocardiogram (ECG) sensors for monitoring heart health are your first hint at the snoring dragon packed inside this mild-mannered form-factor. The chips in question are the MAX30001 and the MAX86150 (whose primary role is as a pulse sensor but also does ECG). We have high-res ADCs just waiting to be misused and the developers ran with that, reserving some of the extra pins on the USB-C connector for external devices.

There was a 10€ kit on offer that let you solder up some electrode pads (those white circles with gel and a snap for a solid interface with your body’s electrical signals) to a sacrificial USB-C cable. Remember, all an ECG is doing is measuring electrical impulses, and you can choose how to react to them. During the workshop, one of the badge devs placed the pads on his temples and used the card10 badge to sense left/right eye movement. Wicked! But there are a lot more sensors waiting for you on these two little PCBs.

Continue reading “Hands-On: CCCamp2019 Badge Is A Sensor Playground Not To Be Mistaken For A Watch”

Hello: A Mini Badge For CCCamp

Badgelife culture is our community’s very own art form, with a plethora of designs coming forth featuring stunning artwork, impressive hardware, and clever software tricks. But sometimes a badge doesn’t need a brace of LEDs or a meme-inspired appearance to be a success, it just needs to be very good at what it does.

A perfect example is [Gavan Fantom]’s Hello mini badge. The hardware is fairly straightforward, it’s just a small square PCB sporting a LPC1115 microcontroller, 8Mb Flash chip, piezo speaker, and an OLED display. Its functionality is pretty simple as well, in that it exists to display text, images, or short animations. But the badge hides a very well-executed firmware that provides a serial terminal and zmodem file upload capability as well as an on-device interface via a small joystick. Power comes from a 500 mAh lithium-polymer cell, for which the badge integrates the usual charger and power management hardware.

There’s a variety of possibilities for the badge, but we’d guess that most owners will simply use it to display their name with perhaps a little animation. A bit of nifty processing of some video could perhaps get something approaching watchable video on it though, opening up the entertaining possibility of displaying demos or other video content.

[Gavan] will have some of the Hello badges at the upcoming CCCamp hacker camp in Germany if you’re interested, and should be easy enough to find in the EMF village.

Fail Of The Week: How Not To Light Pipe

You’d think that something made out of glass and epoxy would transmit a decent amount of light. Unfortunately for [Jeremy Ruhland], it turns out that FR4 is not great light pipe material, at least in one dimension.

The backstory on this has to do with #badgelife, where it has become popular to reverse mount SMD LEDs on areas of PCBs that are devoid of masking, allowing the light to shine through with a warm, diffuse glow – we’ve even featured a through-PCB word clock that uses a similar technique to wonderful effect. [Jeremy]’s idea was to use 0603 SMD LEDs mounted inside non-plated through-holes to illuminate the interior of the board edgewise. It seems like a great idea, almost like the diffusers used to illuminate flat displays from the edge.

Sadly, the light from [Jeremy]’s LEDs just didn’t make it very far into the FR4 before being absorbed – about 15 mm max. That makes for an underwhelming appearance, but all is certainly not lost. Valuable lessons about PCB design were had, like exactly how to get a fab to understand what you’re trying to do with non-plated holes and why you want to fence the entire edge of the board in vias. But best of all, [Jeremy] explored what’s possible with Oreo construction, and came away with ideas for other uses of the method. That counts as a win in our book.

Hands-On: Queercon 16 Hardware Badge Shows Off Custom Membrane Keyboard

Year over year, the Queercon badge is consistently impressive. I think what’s most impressive about these badges is that they seemingly throw out all design ideas from the previous year and start anew, yet manage to discover a unique and addictive aesthetic every single time.

This year, there are two hardware badges produced by the team composed of Evan Mackay, George Louthan, Tara Scape, and Subterfuge. The one shown here is nicknamed the “Q” badge for its resemblance to the letter. Both get you into the conference, both are electronically interactive, but this one is like a control panel for an alternate reality game (ARG) that encourages interactivity and meaningful conversations. The other badge is the “C” badge. It’s more passive, yet acts as a key in the ARG — you cannot progress by interacting with only one type of badge, you must work with people sporting both badge types so that Queercon attendees who didn’t purchase the Q badge still get in on the fun.

The most striking feature on this badge is a custom membrane keyboard tailored to playing the interactive game across all badges at the conference. But I find that the eInk screen, RJ12 jack for connectivity, and the LED and bezel arrangements all came together for a perfect balance of function and art. Join me after the break for a closer look at what makes this hardware so special.

Continue reading “Hands-On: Queercon 16 Hardware Badge Shows Off Custom Membrane Keyboard”

Hackaday Podcast 031: Holonomic Drives, Badges Of DEF CON, We Don’t Do On-Chip Debugging, And Small Run Manufacturing Snafus

Mike Szczys and Kerry Scharfglass recorded this week’s podcast live from DEF CON. Among the many topics of discussion, we explore some of the more interesting ways to move a robot. From BB-8 to Holonomic Drives, Kerry’s hoping to have a proof of concept in time for Supercon. Are you using On-Chip Debugging with your projects? Neither are we, but maybe we should. The same goes for dynamic memory allocation; but when you have overpowered micros such as the chip on the Teensy 4.0, why do you need to? We close this week’s show with a few interviews with badge makers who rolled out a few hundred of their design and encountered manufacturing problems along the way. It wouldn’t be engineering without problems to solve.

Take a look at the links below if you want to follow along, and as always tell us what you think about this episode in the comments!

Take a look at the links below if you want to follow along, and as always, tell us what you think about this episode in the comments!

Direct download (60 MB or so.)

Continue reading “Hackaday Podcast 031: Holonomic Drives, Badges Of DEF CON, We Don’t Do On-Chip Debugging, And Small Run Manufacturing Snafus”

Hackaday Links Column Banner

Hackaday Links: August 11, 2019

By the time this goes to press, DEFCON 27 will pretty much be history. But badgelife continues, and it’d be nice to have a way of keeping track of all the badges offered. Martin Lebel stepped up to the challenge with a DEF CON 27 badgelife tracker. He’s been tracking the scene since March, and there are currently more than 170 badges, tokens, and shitty add-ons listed. Gotta catch ’em all!

Nice tease, Reuters. We spotted this story about the FAA signing off on beyond-visual-line-of-sight, or BVLOS, operation of a UAV. The article was accompanied by the familiar smiling Amazon logo, leading readers to believe that fleets of Amazon Prime Air drones would surely soon darken the skies with cargoes of Huggies and Tide Pods across the US. It turns out that the test reported was conducted by the University of Alaska Fairbanks along an oil pipeline in the Last Frontier state, and was intended to explore medical deliveries and pipeline surveillance for the oil industry. The only mention of Amazon was that the company reported they’d start drone deliveries in the US “in months.” Yep.

Ever wonder what it takes to get your widget into the market? Between all the testing and compliance requirements, it can be a real chore. Nathaniel tipped us off to a handy guide written by his friend Skippy that goes through the alphabet soup of agencies and regulations needed to get a product to market – CE, RoHS, WEEE, LVD, RED, CE for EMC. Take care of all that paperwork and you’ll eventually get a DoC and be A-OK.

A French daredevil inventor made the first crossing of the English Channel on a hoverboard on Sunday. Yes, we know it’s not an “actual” hoverboard, but it’s as close as we’re going to get with the physics we have access to right now, and being a stand-upon jet engine powered by a backpack full of fuel, it qualifies as pretty awesome. The report says it took him a mere 20 minutes to make the 22-mile (35-km) crossing.


We had a grand time last week around the Hackaday writing crew’s secret underground lair with this delightful Hackaday-Dilbert mashup-inator. Scroll down to the second item on the page and you’ll see what appears to be a standard three-panel Dilbert strip; closer inspection reveals that the text has been replaced by random phrases scraped from a single Hackaday article. It looks just like a Dilbert strip, and sometimes the text even makes sense with what’s going on in the art. We’d love to see the code behind this little gem. The strip updates at each page load, so have fun.

And of course, the aforementioned secret headquarters is exactly what you’d picture – a dark room with rows of monitors scrolling green text, each with a black hoodie-wearing writer furiously documenting the black arts of hacking. OpenIDEO, the “open innovation practice” of global design company IDEO, has issued a challenge to “reimagine a more compelling and relatable visual language for cybersecurity.” In other words, no more scrolling random code and no more hoodies. Do you have kinder, gentler visual metaphors for cybersecurity? You might win some pretty decent prizes for your effort to “represent different terms and ideas in the cybersecurity space in an accessible and compelling way.”