Fri3d Vzw
The Arduino guide identifies Fri3d Vzw as the publisher of the custom fri3d-esp32 boards package.
SourceFri3d Camp 2024 · Belgium · 2024
ESP32-S3 badge with blaster and communicator add-ons
A Fri3d ESP32-S3 badge with LCD, joystick/buttons, SD card, USB-C, LiPo power, MicroPython/Arduino docs, and blaster/communicator add-ons.
People
The Arduino guide identifies Fri3d Vzw as the publisher of the custom fri3d-esp32 boards package.
SourceFri3d 2024 is a well-documented modern camp badge with first-party docs that explicitly cover applications, add-ons, firmware reset, and multiple programming stacks.
Fri3d documentation and repositories describe ESP32-S3, 2 inch 320x240 IPS LCD, joystick, buttons, SD card, USB-C, LiPo support, and add-on connectors.
Docs include getting started, applications, add-ons, MicroPython, Arduino, BadgeLink, USB, WiFi, and reset-to-factory paths.
Blaster and communicator add-ons make the badge part of camp play, while reset and update docs make it recoverable for workshop use.
Lifecycle
The official Arduino guide provides a custom fri3d-esp32 board package, Fri3d Badge 2024 board target, examples, upload flow, and a path for sketches launched through the default firmware.
SourceThe Flamingo blaster uses an IR LED, two IR receivers, four WS2812 LEDs, a buzzer, trigger, team selector, LANA TNY module, and a 3.5 mm BadgeLink connector to turn the badge into a camp game peripheral.
SourceThe communicator add-on is documented as part of the 2024 badge ecosystem.
SourceFri3d 2024 documentation includes a blaster add-on for camp play and badge interaction.
SourceFri3d 2024 docs expose BadgeLink, MicroPython, Arduino, USB, WiFi, update, and reset workflows as first-class extension paths.
SourceOperational history
Fri3d 2024 has multiple programming paths, but they are not equivalent: users need to understand whether they are using the managed MicroPython partition or replacing the default firmware.
The public badge page, image archive, and API point at a licensed original-photo derivative with source and attribution preserved.
Good recovery docs reduce the risk that app or firmware experiments permanently strand an attendee's badge.