SAINTCON

SAINTCON 2017

The October 10-13, 2017 SAINTCON edition in Provo, Utah, whose official archive and badge page documented a Raspberry Pi Zero W electronic badge, a custom TFT/button board, MiniBadges, and Hacker Challenge integration.

Utah Valley Convention Center, Provo, Utah · United States · 2017

SAINTCON 2017 Raspberry Pi Badge

The SAINTCON 2017 badge was an electronic conference badge built around a Raspberry Pi Zero W and a custom SAINTCON board with a 2.8-inch TFT display, SNES-style buttons, battery power, MiniBadge expansion, Hacker Challenge registration, and a post-conference RetroPie conversion path.

Lifecycle

Add-ons & Upgrades

assembly workflow

Badge assembly and power kit

The assembly manual documents the LiPo battery, PowerBoost 500C, cable routing, custom board mounting, acrylic shield, screws, standoffs, and lanyard hardware needed to complete the badge.

Compatibility: SAINTCON 2017 Raspberry Pi Badge

badge add-ons

MiniBadge add-on ecosystem

The official badge page and manual preserve MiniBadge support, official MiniBadge and unofficial MiniBadge pages, and visible add-on presentation through the attendee badge.

Compatibility: SAINTCON 2017 MiniBadges

badge interface

PiTFT and SNES-style controls

Official sources describe a 2.8-inch TFT display plus SNES D-pad and buttons, while the assembly manual documents the PiTFT Plus 320x240 display and button-board hardware.

Compatibility: SAINTCON 2017 Raspberry Pi Badge

Operational history

Issues & Camp Impact

missing rights-cleared image · local project policy · needs licensed original replacement

No SAINTCON 2017 Raspberry Pi Badge image is published because the current public source trail has not been paired with a reusable original badge or artifact photo or official upstream raster render with source URL, license or permission basis, attribution, and processing notes.

The United States record remains source-backed and image-free rather than copying source-page media, documentation screenshots, event photos, social media, placeholders, or generated approximations.

source-code gap · official docs but incomplete source recovery · needs image/repository recovery

Official pages and the public manual document badge assembly, flashing, registration, and post-event conversion, but this pass did not recover a public source repository for the badge image, custom PCB design files, challenge daemons, or final production files.

The catalogue records the verified deployed badge and public manual without inventing unrecovered firmware internals or PCB-source details.

Resources

Sources