Lifecycle
Badge ecosystems keep moving after handout: apps, hexpansions, SAOs, antennas, cases, repair parts, firmware updates, and post-event hardware experiments.
The BOM lists a CR2032 battery holder and the Eagle schematic carries BT1 as a CR2032 holder tied into the badge power rails.
SourceThe board archive and README point to power and MAX17048 schematic material, with dual 14500 battery-holder and fuel-gauge evidence preserved in the CAD tree.
SourceThe CC13 KiCad comments identify LiPo charging, dual 14500 battery holders, and fuel-gauge hardware.
SourceESPlant included a 16340 lithium-cell holder, solar-input-friendly charger interface, and automatic switching between solar input, battery, and USB power.
SourceThe README and firmware document a pushbutton that toggles microphone power and clears the display for standby/low-power behavior.
SourceHackaday describes an 18650 cell and charging circuit as part of the badge hardware package.
SourceThe hardware trail documents lithium-polymer battery power and MCP73831-based charging for portable badge use.
SourceThe README documents Li-ion battery or USB power and USB charging when the power switch is on.
SourceThe SAO spec states that the badge is powered by two AA batteries and that USB-C power-bank operation keeps the badge continuously on.
SourceThe README lists a two-AAA battery holder as the badge power hardware.
SourceDEF CON's official badge-alert post says DEF CON 34 is an electronic badge year, that the badge comes from a hardware hacking legend, and that the SAO spec sheet is early support for add-on projects.
SourceRomHack Camp 2026 is currently advertised with a unique hardware badge and collectible challenge; final challenge mechanics are not yet public in the source set.
SourceThe badge how-to records a hidden pattern concept in the printed design and preserves print-production details for A7 landscape badges.
SourceIain Yarnall's 7-Segment display model is a printable visual add-on in the official showcase, showing the hardware record also needs printables and non-PCB artifact links.
SourceFloppy's Interlocking Brick Hexpansions provide stud-compatible plates in multiple sizes, including versions that account for USB-C clearance.
SourceThe official sponsorship table lists Platinum sponsor logo placement on badges and merchandise, supporting a conservative conference-badge artifact record.
SourceThe 2021 walkthrough says the badge challenge started from text printed on the back of the Kākācon sticker.
SourceThe 2022 walkthrough says the second Kākācon badge challenge again started from text printed on the back of the sticker.
SourceEach badge transmitted a random 9-bit ID about five times a second, showed the ID on LEDs A-I at power-up or with the ID button, and allowed users to clear the ID by holding Erase.
SourceGreat Scott Gadgets credits OSH Park sponsorship and the repository preserves the badge hardware designs and kit photo trail.
SourceBadge Pirates documents a batch of 250 fully electronic badges built around ESP32 boards with touch screens, Wi-Fi, and SD card slots.
SourceThe tariff writeup records customs scrutiny, opened packaging, delayed delivery, and roughly a 20 percent tariff hit on the production order.
SourceThe public HackerHotel Badge talk captures the badge-team process, challenge integration, and lessons learned as part of the badge's post-event record.
SourceThe attendee report quotes Penten crediting volunteers, global parts-shortage effort, GME and 4Design support, and Sydney manufacture for delivering the badge to the community.
SourceThe Army article says Capt. Richard Shmel personally developed and made more than 300 electronic badges for AvengerCon VIII.
SourceA late GPIO0 buffer design caused battery-powered badges to enter Download boot mode until the team fixed DTR with an R19 pull-up resistor before conference shipment.
SourceAn attendee report says factory firmware left LEDs blindingly bright, requiring all badges to be reflashed just before the conference.
SourceThe talk title and abstract preserve local production lore around how the idea evolved and what problems occurred while creating the badges.
SourceThe production story documents planned mesh networking and audio streaming, with final event success framed around a room-scale mesh LED demo rather than complete audio broadcast behavior.
SourceMog noticed the exposed pad spacing lined up well enough with DB9/DE9 connector pins, leading to a pogo-pin cable and CC Debugger flashing workflow.
SourceThe Wi-Fi and pick-and-place log documents CR123A cells and holders, diode validation, stencil-holder work, eight early hand-built badges, and pick-and-place setup six days before the conference.
SourceThe H2HC card-printing posts document CR80 85.6 x 53.98 mm card sizing, a DASCOM DC-7600 600 DPI full-duplex re-transfer printer, front/back artwork preparation, on-site pickup workflow, and optional UV-ribbon capability rather than electronic badge firmware.
SourceThe official post documents panelized boards, solder-paste stencil work, reflow, inspection, through-hole soldering, and testing.
SourceThe building-badges log says kits were made, speaker and staff badges were built, and LED badges were being assembled with a TM-220A pick-and-place shortly before the conference.
SourceThe first-hand writeup names Xometry as the injection-molding partner and describes design-for-manufacturing tradeoffs around wall thickness, sink marks, lens geometry, and schedule pressure.
SourceThe badge-team notes describe USB device support, USB host, HID or CDC behavior, and ST-Link V2/SWD programming expectations.
SourceThe official page identifies the ATTINY85 pin mapping for SAO data pins and names the Amphenol programming-port and male-connector parts with 1.27 mm pitch.
SourceThe README documents Microchip Studio or avr-gcc build paths, `L12024POV.hex`, avrdude flashing to `t4313`, and Kraken or Arduino ISP programmer options for attendees.
SourceThe hardware-hacking guide documents AVRISP wiring and commands for initialization, target identification, flash reads/programming, and fuse access.
SourceThe badge could be programmed through an FTDI header, giving attendees a direct Arduino-style code-loading path.
SourceThe project is publicly shown in staged progress from idea collection through prototyping, electronic design, firmware, and delivery, with budget fit called out as the next challenge.
SourceThe repository BadUSB notes document HID report framing, script loading, command bytes, and custom-HID interface context for writing scripts to the badge.
SourceJake Walker's Protoboard Hexpansion gives badge owners a small general-purpose prototyping surface in the official connector shape.
SourceHackaday reports BLE and NFC alongside the low-power badge design, while the hardware archive identifies the nRF52832-based MDBT42Q module.
SourceThe RSSI sketch and HugQuest command path scan channels 11 through 26 and display channel signal-strength readings on the SMART Response XE screen.
SourceThe official Tildagon hexpansion guide preserves jasonalexander-ja's DECTspansion as a community-made radio expansion example for the reusable EMF 2024 badge platform.
SourceThe 2013 development post lists 2.4 GHz radio as one of the headline badge features, placing Hackover in the same radio-badge experimentation era as other early European badges.
SourceRadioFunctions.h initializes the ATmega128RFA1 2.4 GHz transceiver and constrains channels to 11 through 26 for packet send/receive and RSSI reads.
Source