Skip to the content
2 layers27.9 × 83.8 mmBusy indicator, the printed circuit board in 3D

A wireless status indicator system built with the XIAO ESP32C3. Designed for pairs who want to communicate their availability without interrupting each other's flow state.

Size
27.9 × 83.8 mm
Copper layers
2
Thickness
1.6 mm
Parts
10
Nets
21
Pads
36
Tracks, vias
22, 0
Pours
1
Routed
Yes
KiCad
KiCad 9.0 (file 20241229)
Created
12 Jul 2025
Updated
15 Mar 2026

Overview

Busy indicator is an open-source printed circuit board by brancengregory, from the brancengregory/busy-indicator repository on GitHub. It is a 2-layer board of 27.9 × 83.8 mm with 10 parts on 21 nets, routed with 22 tracks and 0 vias.

Its parts include 4 resistors, 4 diodes, 1 IC and 1 switch. It belongs with the ESP32 and RISC-V boards of this library.

README

README.md

Busy Indicator

A wireless status indicator system built with the XIAO ESP32C3. Designed for pairs who want to communicate their availability without interrupting each other's flow state.

Overview

The Busy Indicator is a simple, elegant solution to a common problem: knowing when your partner or colleague is available without the social pressure of asking. Each device has two sets of red/green LEDs:

  • Local LEDs: Show your current status (controlled by you)
  • Remote LEDs: Show your partner's status (received wirelessly)

When your partner presses their button to change status, your remote LEDs update automatically via ESP-NOW wireless communication.

Features

  • Dual Status Display: Four LEDs total - two for your status, two for your partner's
  • Simple Controls: Single button press toggles your status (red = busy, green = available)
  • Sleep Mode: Long press (2 seconds) to enter light sleep for power saving
  • Wake on Button: Press button to wake from sleep and resume operation
  • Wireless Sync: ESP-NOW protocol provides instant status updates between devices
  • Visual Feedback: Amber blinking confirms long press and wake events
  • Debounced Input: Reliable button detection with 50ms debounce
  • Power Efficient: Light sleep mode consumes minimal power when not in use

Hardware

The PCB is designed around the Seeed Studio XIAO ESP32C3 with:

  • Microcontroller: XIAO ESP32C3 (RISC-V, WiFi + Bluetooth)
  • LEDs: 4x 3mm through-hole LEDs (2 red, 2 green)
  • Current limiting: 4x axial resistors
  • Input: 12mm push button
  • Power: USB-C via XIAO board (or external battery via battery pads)

GPIO Pinout

FunctionGPIO
Local Red LEDGPIO3
Local Green LEDGPIO4
Remote Red LEDGPIO21
Remote Green LEDGPIO20
ButtonGPIO10

PCB Design Files

The hardware design is in KiCad 9.0 format:

  • hardware/busy-indicator/busy-indicator.kicad_sch - Schematic
  • hardware/busy-indicator/busy-indicator.kicad_pcb - PCB layout
  • hardware/busy-indicator/busy-indicator.kicad_pro - Project settings
  • hardware/libs/XIAO_ESP32C3/ - XIAO ESP32C3 footprint and symbol library (git submodule)

Firmware

The firmware is written in Rust using the Embassy async framework:

  • Language: Rust (embedded no-std)
  • Framework: Embassy (async/await for embedded)
  • HAL: esp-hal for ESP32-C3
  • Networking: esp-radio (ESP-NOW over WiFi)
  • Target: riscv32imc-unknown-none-elf

Architecture

The firmware uses an actor-model architecture with Embassy tasks:

  1. State Manager (state_manager): Pure state machine handling all state transitions
  2. LED Controller (led_controller): Handles LED output with retry logic
  3. Button Task (button_task): Button debouncing, press detection, and sleep control
  4. ESP-NOW Task (esp_now_task): Wireless communication between devices

Key Components

  • ButtonHandler: Debounced button input with short/long press detection
  • LedPair: Abstraction for red/green LED pairs with color mixing (red + green = amber)
  • SystemState: Tracks local status, remote status, and sleep state
  • Pure Transitions: State changes are pure functions (no side effects), making testing easy

Building

Prerequisites

  • Rust toolchain with riscv32imc-unknown-none-elf target
  • espflash or cargo-espflash for flashing
  • KiCad 9.0+ (for hardware modifications)

Flashing Firmware

bash
# Build and flash
cargo run --release

# Or flash pre-built binary
espflash flash target/riscv32imc-unknown-none-elf/release/busy-indicator

Hardware Manufacturing

  1. Open hardware/busy-indicator/busy-indicator.kicad_pcb in KiCad
  2. Generate Gerber files for fabrication
  3. Order PCBs from your preferred manufacturer (JLCPCB, PCBWay, etc.)
  4. Solder components according to the schematic

Usage

  1. Power on: Both LED pairs will blink amber 3 times, then show red (default busy state)
  2. Toggle status: Short press the button to switch between red (busy) and green (available)
  3. Check partner status: Look at the "remote" LED pair - it mirrors your partner's device
  4. Enter sleep: Long press the button (hold for 2 seconds until LEDs blink) to enter low-power mode
  5. Wake up: Press the button to wake from sleep - LEDs will blink amber to confirm

Wireless Pairing

Devices automatically discover each other via ESP-NOW broadcast on channel 11. No manual pairing required - just power on two devices within range and they'll sync automatically.

Project Structure

text
busy-indicator/
├── src/
│   ├── bin/main.rs       # Firmware entry point and task definitions
│   └── lib.rs            # Library (currently empty, no_std marker)
├── hardware/
│   ├── busy-indicator/   # KiCad PCB design files
│   └── libs/             # Component libraries (XIAO_ESP32C3 submodule)
├── Cargo.toml            # Rust dependencies
├── build.rs              # Build script with helpful linker errors
└── .gitignore            # Git ignore patterns for Rust + KiCad

License

This project is open source. See individual component licenses:

  • Firmware: See LICENSE file in repository root
  • XIAO_ESP32C3 library: See hardware/libs/XIAO_ESP32C3/LICENSE

Acknowledgments

Parts

10
QtyValueFootprintReferences
4LEDLED_THT:LED_D3.0mmD1, D2, D3, D4
4R_USResistor_THT:R_Axial_DIN0207_L6.3mm_D2.5mm_P10.16mm_HorizontalR1, R2, R3, R4
1SW_PushButton_Switch_THT:SW_PUSH-12mmSW1
1XIAO ESP32C3XIAO_ESP32C3:xiao_esp32c3U1

Similar boards

  • 2 layers57 × 55.2 mmLogicAnalyzer, the printed circuit board in 3D

    LogicAnalyzer

    gusmanb/logicanalyzer

    24 channel, 100Msps logic analyzer hardware and software

    10 parts5.1kGPL-3.0
  • 2 layers32.2 × 15.4 mmProtector, the printed circuit board in 3D

    Protector

    byrantech/laptop

    anyon_e, a highly integrated, high end, open source laptop. Attempt the impossible.

    10 parts4.3kMIT
  • 2 layers26 × 18 mmConn, the printed circuit board in 3D

    Conn

    yaqwsx/KiKit

    Automation tools for KiCAD

    10 parts2.1kMIT
  • 2 layers44.3 × 30.5 mmLime2-SATA RevA, the printed circuit board in 3D

    Lime2-SATA RevA

    OLIMEX/OLINUXINO

    OLINUXINO is Open Source / Open Hardware, low cost from EUR 24 Linux Industrial grade Single Board Computer capable to operate -25+85C

    10 parts1.5k
  • 2 layers17.8 × 43.2 mmNano Adapter, the printed circuit board in 3D

    Nano Adapter

    VoronDesign/Voron-Hardware

    Cool Hardware designed by the Voron Design group

    10 parts1.1kGPL-3.0
  • 2 layers53.9 × 23.2 mmBuffer, the printed circuit board in 3D

    Buffer

    hoglet67/RGBtoHDMI

    Bare-metal Raspberry Pi project that provides pixel-perfect sampling of Retro Computer RGB/YUV video and conversion to HDMI

    10 parts1kGPL-3.0

Questions

How big is the Busy indicator PCB?

It measures 27.9 × 83.8 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Busy indicator use?

10 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Busy indicator KiCad files?

From the brancengregory/busy-indicator repository on GitHub, at the commit this page was made from: the board is hardware/busy-indicator/busy-indicator.kicad_pcb and its schematic hardware/busy-indicator/busy-indicator.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Busy indicator design in my own project?

Its repository states no licence, so its author keeps all rights: ask brancengregory before reusing the design.