sibios
The repository history credits sibios with README errata and update work.
SourceDC503 Wagon Party 2017 · United States · 2017
nRF52832 BLE OLED wagon-game badge
The DC503 Wagon Party badge is a source-backed party badge documented by the no-visible-license `pdxbadgers/wagonparty` repository, whose README calls the target a badge and whose firmware advertises a `503WAGON` BLE device with OLED game modes.
People
The repository history credits sibios with README errata and update work.
SourceThe firmware carries the Adafruit SSD1306 example header crediting Limor Fried / Ladyada and Adafruit; the README also requires Adafruit SSD1306 and GFX libraries.
SourceRepository commits by Dean Pierce / pierce403 cover the initial README, initial code publication, image-resource addition, and flashing-instruction updates.
SourceThe README links SparkFun's nRF52832 Breakout hookup guide as the Arduino compatibility setup path for the badge target.
SourceThe repository metadata describes the project as dc503 wagon party.
SourceGitHub organization publishing the public Wagon Party source tree.
SourceIt preserves an early DC503/PDX Badgers party-badge branch that used a Nordic nRF52832 Arduino target, BLE-writeable party text, an SSD1306 screen, and Oregon Trail-themed local game behavior before the later Banglet and 5ohBEE party artifacts.
The README instructs builders to connect a 3.3V USB-serial cable to the badge, install SparkFun nRF52832 Breakout Arduino support, set I2C SDA/SCL pins to 24 and 25, configure Adafruit SSD1306 for 128x64, and hold the center of the left wagon wheel during power cycling to enter programming mode. The firmware initializes an SSD1306 display at I2C address 0x3C and configures ten input pull-up pins for the control surface.
The Arduino firmware uses BLEPeripheral, Adafruit_GFX, and Adafruit_SSD1306, advertises device/local name `503WAGON`, exposes BLE service and writable characteristic UUID `0503`, defaults the banner to `503.PARTY!`, and switches between wagon, hunt, and party modes. The BLE characteristic updates the on-screen banner; special strings trigger DYSENTERY and WannaCry death screens, while the hunt mode moves a hunter sprite and scores hits on a Bender sprite.
The repository metadata describes the project as `dc503 wagon party`. Its code and sprites make the badge a 503 Party/Oregon Trail riff: a wagon-and-mountains animation prints live banner text and mileage, the party mode scrolls the banner with display inversion, and the source tree keeps generated sprite assets as evidence only rather than as publishable catalogue imagery.
Lifecycle
The hunt loop moves a hunter sprite, tracks laser direction from input pins, draws a Bender sprite, and increments score on hits.
SourceThe wagon loop draws wagon and mountain sprites, prints the current banner, and increments a displayed score in miles.
SourceThe main loop cycles between wagon, hunt, and party modes when the mode input changes, keeping the badge centered on local interactive display behavior.
SourceThe party loop displays the BLE banner, flips display inversion, and periodically chooses random scroll directions.
SourceThe README requires SSD1306 128x64 configuration, and the firmware initializes an Adafruit_SSD1306 display at I2C address 0x3C.
SourceThe README says holding the center of the left wagon wheel while power cycling enters programming mode for Arduino SDK upload.
SourceThe README directs builders through SparkFun nRF52832 Breakout Arduino compatibility and variant-file changes for the badge target.
SourceThe firmware advertises 503WAGON and exposes a BLE service and writable characteristic UUID 0503 that updates the on-screen banner text.
SourceOperational history
Hardware claims stay limited to the README programming workflow, nRF52832 target, SSD1306 display setup, I2C pin mapping, and firmware-observed inputs.
The entry remains source-backed and image-free rather than copying repository sprites, image assets, social photos, generated art, screenshots, or placeholder visuals.
The record links to upstream files while leaving the hero image empty and avoiding local copies of sprites or image assets.
The catalogue models the artifact as a DC503 party badge and keeps it separate from DEF CON, BSidesPDX, and later DC503 Banglet/5ohBEE lineages.
Sprites remain source evidence for firmware behavior only and are not promoted into `Public/images/`.