Home

PCController Wiki

PCController combines the ATmega328P firmware, native Go host, embedded WebUI, protocol/API surfaces, safe programming, and Virtual Board.

Important

Repository Markdown is canonical. This Wiki is a generated, branded mirror; edit the linked source documentation through a pull request rather than changing a Wiki page by hand.

🧭 Choose a path

Goal	Start here
Run or connect for the first time	Getting started and operations
Find the owning source, test, asset, or generated output	Repository and file map
Program or recover a board safely	Toolchain and safe programming
Integrate an app or another host	Protocol and network API
See feature parity and remaining gaps	Control-surface matrix and requirements backlog

🧱 One system, shared ownership

⚙️ Firmware	🖥️ Host	🌐 Interfaces	🧪 Verification
Deterministic safety, I/O, menus, RF, EEPROM	One primary serial owner and command dispatcher	WebUI, TUI, CLI, native shell, APIs and libraries	Virtual Board, local gates, CI and explicit hardware acceptance

📚 Maintained knowledge base

🚀 Start here

	Guide
🚀	Getting started and operations
🗺️	Repository and file map
🎛️	Front panel and menus
🔧	Hardware initialization and tuning
⚙️	Host configuration and integrations

🔌 Use and integrate

	Guide
🧭	Hosted front-panel menus
🌐	Portable WebUI
🔌	Protocol and network API
🧩	C library API
↔️	Control-surface capability matrix

🛠️ Build and test

	Guide
🏗️	Build and packaging tool
💾	Firmware tool
🖥️	Host Controller
🧪	Virtual Board
📦	Dependency maintenance
🛡️	Toolchain bootstrap and safe programming
🧠	Memory and feature tradeoffs
🚦	CI/CD and releases
🔩	Urboot-Custom reproducible fork

📋 Project tracking

	Guide
🔍	Audit and traceability tools
✅	Project acceptance
📋	Requirements backlog
🧬	Local-library variant comparison

🔄 Work and review

• Project board — status, domain, priority, and milestone overview.
• Issues — requirements and acceptance evidence.
• Pull requests — reviewable implementation and work in progress.
• Actions — build, repository-health, security, and release evidence.

Contributor rule: source before mirror

1. Use the repository map to find the authoritative file.
2. Reconcile the change with its issue and existing pull requests.
3. Update source, tests, capability matrix, and relevant guide together.
4. Preview the Wiki from source; never preserve a hand-edited Wiki fork.