

Layouts
Raspberry Pi Pico 2W mini Drone Project
- Copper layers
- 2
- Thickness
- 1.6 mm
- Parts
- 21
- Nets
- 64
- Pads
- 118
- Tracks, vias
- 27, 3
- Routed
- Yes
- KiCad
- KiCad 0.12.4 (file 20241229)
- Created
- 14 Sep 2025
- Updated
- 19 Nov 2025
Overview
Layouts is an open-source printed circuit board by pete529, from the pete529/PICO_Drone_Mk1 repository on GitHub, published under the MIT licence. It is a 2-layer board with 21 parts on 64 nets, routed with 27 tracks and 3 vias.
Its parts include 6 ICs, 5 resistors, 5 connectors, 2 capacitors and 2 diodes. It belongs with the robots and motor control boards of this library.
README
README.mdPICO Drone Mk1 – Small Quadcopter
Status: ✅ Hardware design complete and ATO builds are green. BOM is populated (see hardware/build/builds/default/default.bom.csv). All hardware has been procured and is ready for PCB assembly.
New: Complete user stories and GitHub issue management system available. See GitHub Issues Creation below.
Overview
This project is a complete Raspberry Pi Pico 2W based quadcopter featuring:
- Raspberry Pi Pico 2W module (Wi-Fi enabled RP2040 with wireless connectivity)
- Dual DRV8833 motor driver ICs (4 independent brushed motor outputs)
- GY-91 9-DOF IMU (ICM-20948 + BMP280 for orientation, acceleration, and altitude)
- Power management with LiPo Amigo Pro (boost converter + charging circuit)
- Status LEDs (power indicator and user-controllable status)
- User controls (power button and mode switching)
- Robust design with proper power filtering and protection circuits
- An Android application that arms and controls the drone via UDP packets

Project Structure
├── hardware/ # Main atopile project directory
│ ├── main.ato # Top-level quadcopter module with complete wiring
│ ├── ato.yaml # Build configuration with multiple targets
│ ├── atopile/components/ # Custom component definitions
│ ├── layouts/ # KiCad PCB layouts (default + test targets)
│ ├── build/ # Generated build artifacts
│ └── PART_PICKING_GUIDE.md # Troubleshooting and part selection guide
├── firmware/ # Drone firmware & shared protocol utils
│ ├── shared/
│ │ └── control_protocol.py # CSV parser, deadzone/expo, failsafe smoother
│ └── pico/
│ ├── udp_server.py # Pico W MicroPython UDP server (AP + UDP control)
│ └── drv8833_stub.py # DRV8833 test mixer/PWM stub for bring‑up
├── android/ # Android sender app (Compose)
│ ├── app/src/main/
│ │ ├── AndroidManifest.xml
│ │ └── java/com/petedrone/udpsender/MainActivity.kt
│ ├── app/build.gradle.kts
│ ├── settings.gradle.kts
│ ├── build.gradle.kts
│ └── gradle/wrapper/gradle-wrapper.properties
├── user_stories.md # Complete user stories (6 epics, 25+ features)
├── create_github_issues.ps1 # Script to create GitHub issues from user stories
├── create_issues.bat # Windows batch file for easy execution
├── GITHUB_ISSUES_README.md # Documentation for issue management system
└── .github/workflows/ # CI/CD automationCurrent Status
✅ Hardware Design Complete
- PCB Design: Complete atopile design with comprehensive component wiring
- Build System: Successfully builds with
ato build- all stages complete - Component Integration: Pico 2W, dual DRV8833s, GY-91 IMU, power management
- Signal Routing: All motor control, I2C, power, and user interface connections
- Build Artifacts: KiCad files, BOMs, netlists, and manufacturing files generated
✅ Development Infrastructure
- CI/CD: Automated builds on every commit with artifact publishing
- Version Management: Semantic versioning with automated version bumping
- Issue Management: Complete user story system with GitHub issue creation
- Documentation: Comprehensive guides for building, troubleshooting, and development
🔄 Next Steps
- PCB Assembly: Assemble the procured components onto the PCB
- Board Bring-up: Power-on checks, I²C/UART comms, sensor and motor driver validation
- Firmware Development: Flight control algorithms and wireless interface
- Testing & Validation: Bench tests and initial flight validation
Build System
Local Development
Requirements: Python 3.11+, Atopile 0.12.4
# Install atopile (Windows-friendly)
py -m pip install --upgrade atopile==0.12.4
# From repo root, verify and open the design viewer
ato --version
ato view # opens default build (App)
# Build the project (generates KiCad files, BOM, netlist)
ato build
# Build a specific target (pickable resistor demo)
ato build --build test_pickableBuild Output:
build/builds/default/- Main quadcopter design filesbuild/builds/test_pickable/- Component testing files- KiCad PCB files (.kicad_pcb)
- Bill of Materials (.bom.csv)
- Netlists and component reports
Note: The populated BOM is available at hardware/build/builds/default/default.bom.csv after a successful build.
Drone control over Wi‑Fi UDP
This repo includes a MicroPython UDP server for Pico W and an Android sender app.
Pico W (MicroPython) UDP server
Files:
firmware/pico/udp_server.py- Shared helpers in
firmware/shared/control_protocol.py
Behavior:
- Starts Wi‑Fi AP: SSID
PicoDrone, passworddrone1234 - Listens on UDP port 8888
- Accepts CSV packets at ~50 Hz:
DRN,{throttle},{roll},{pitch},{yaw}\n(or withoutDRN,)- Ranges: throttle [0..1], roll/pitch/yaw [-1..1]
- Optional heartbeat
PING\n→ repliesACK\n - Failsafe: if no valid packet for >500 ms, throttle soft-lands to 0 over 1.5 s
Bring-up steps:
- Flash MicroPython to Pico W (UF2 from micropython.org).
- Copy
firmware/to the board; setudp_server.pyas main or run from REPL:- In Thonny: File → Open
udp_server.py→ Run
- In Thonny: File → Open
- Observe console: AP IP in
ap.ifconfig().
Hooking motors: Replace the TODOs in udp_server.py with your motor mixer / ESC driver to apply (throttle, roll, pitch, yaw) each loop.
Server configuration (in udp_server.run_server):
ssid/password: AP SSID/PSK (defaultPicoDrone/drone1234)port: UDP port (default 8888)expect_signature: setTrueto require theDRN,packet prefixdeadzone/expo: attitude axis shaping (roll/pitch/yaw)- PWM test pins: update
mixer.configure_test_pins([2,3,4,5])to your GPIOs (or remove to print only)
Safety / failsafe:
- Link‑loss (>500 ms) triggers a soft throttle ramp to 0 over ~1.5 s (configurable)
- Always bench‑test with props OFF; verify failsafe before first hover
Android sender app
Files:
android/app/src/main/java/com/petedrone/udpsender/MainActivity.ktandroid/app/src/main/AndroidManifest.xmlandroid/app/build.gradle.kts
Controls & UX highlights:
- Dual‑joystick Compose controls (left stick: yaw + throttle; right stick: roll + pitch) with deadzone filtering
- Always‑on Material 3 dark theme so labels remain legible in night operations
- Bright yellow drone launcher icon for quick access on the device home screen
Armedtoggle that forces throttle to0when disabled- Optional signature prefix toggle (
DRN,) to satisfy strict firmware configs - 50 Hz UDP stream with inline
ACKparsing for battery voltage (BAT=) and RSSI telemetry when available
Build & install (Android Studio Hedgehog+ recommended):
- Open the
android/folder in Android Studio - Let Gradle sync dependencies (Compose + Material3)
- Run on a connected device; accept prompts if any
Optional (Gradle wrapper, from android/):
./gradlew assembleDebug # build APK
./gradlew installDebug # install to connected deviceConnect to the Pico:
- On phone, join the AP
PicoDrone(passworddrone1234). - Open the app; Pico IP is typically
192.168.4.1, Port8888. - Toggle Armed and move sliders; the app will emit
DRN,{t},{r},{p},{y}\nat ~50 Hz. - In the Pico console, you should see activity and occasional
ACKin the app.
📘 Documentation: See docs/mobile_app_user_guide.md for a complete walkthrough of installation, controls, telemetry, and troubleshooting tips.
Upcoming enhancements to consider next:
- Arming switch latch / stick combination
- In‑app deadzone/expo tuning (server already supports it)
- Packet signature enforcement by default (
expect_signature=True) - Simple outbound telemetry from Pico to display battery/RSSI history charts
Tests
Run parser/failsafe tests locally (CPython):
py -m pip install pytest
py -m pytestQuick Start (end‑to‑end)
- Build hardware (optional now):
ato build(see Build System above) - Pico W
- Flash MicroPython UF2
- Open
firmware/pico/udp_server.pyin Thonny and Run - Confirm AP
PicoDroneis active; note IP (typically192.168.4.1)
- Phone
- Join
PicoDroneWi‑Fi (drone1234) - Install and open the Android app (from
android/in Android Studio) - Set IP to
192.168.4.1, Port8888, enableDRN,if server expects it, Arm ON - Move sticks — app sends CSV at ~50 Hz and displays
ACKon replies
- Join
- On the bench (NO PROPS)
- Verify throttle response and failsafe (stop app → throttle should ramp to 0)
- Adjust deadzone/expo if needed
Automated CI/CD
✅ GitHub Actions runs on every push:
- Validates atopile syntax and builds
- Generates all build artifacts
- Publishes downloadable artifacts
- Automated version bumping based on commit messages
Download artifacts: Go to any workflow run → Artifacts section
GitHub Issues Creation
This project includes a comprehensive user story system organized into 6 major epics:
- Hardware Design & PCB Development - Complete hardware platform
- Flight Control Software - Stable and responsive flight control
- Wireless Communication & Control - Remote piloting capabilities
- Development Tools & CI/CD - Automated build and test systems
- Testing & Validation - Safety and reliability verification
- Documentation & User Guide - Complete instructions and guides
Creating Issues from User Stories
Prerequisites:
- GitHub CLI installed: https://cli.github.com/
- GitHub Personal Access Token: https://github.com/settings/tokens (with
reposcope)
Quick Start:
# Windows - Double-click the batch file
create_issues.bat
# Or run PowerShell directly
.\create_github_issues.ps1 -GitHubToken "your_token_here"This will create 25+ GitHub issues organized with labels:
epic- High-level business objectivesfeature- Major functional areasstory- Individual user requirementshardware,software,testing,documentation- Work categories
See: GITHUB_ISSUES_README.md for complete documentation
Issue Automation (Advanced Usage)
The script create_github_issues.ps1 is idempotent: it will not recreate issues that already exist (it checks both open and closed issues by exact title match).
Key features:
- Automatic authentication reuse (you only need
-GitHubTokenif not already logged in withgh auth login) - Full backlog coverage (all epics, features, and stories from
user_stories.md) - Label synchronization (missing labels are created on-the-fly)
- Duplicate avoidance (skips existing titles, counts skipped vs created)
- Optional JSON summary output via
-SummaryPath - Safe to re-run any time to add only new backlog items
Parameters
| Parameter | Required | Description |
|---|---|---|
-GitHubToken | No | Personal access token (PAT) with repo scope. Optional if already authenticated. |
-Owner | No | Repository owner (default: preset in script) |
-Repo | No | Repository name (default: preset in script) |
-SummaryPath | No | Path to write JSON summary of run (created, skipped, totals) |
Examples
# 1. First time (no existing gh auth session)
./create_github_issues.ps1 -GitHubToken $env:GITHUB_TOKEN
# 2. Already authenticated via gh
./create_github_issues.ps1
# 3. Capture a summary JSON
./create_github_issues.ps1 -SummaryPath .\issue_summary.json
# 4. Different fork or repo
./create_github_issues.ps1 -Owner YourUser -Repo ForkedRepo -SummaryPath out\summary.jsonSample Output
Checking GitHub authentication...
Verifying repository access (owner/repo)...
Fetching existing issue titles...
Synchronizing labels...
Creating GitHub issues (idempotent)...
↷ Skipping (exists): Epic 1: Hardware Design & PCB Development
✓ Created: Story 2.2.1: Individual Motor Speed Control
...
🚀 Issue creation complete
Created: 57 Skipped: 42 Total Defined: 99 Elapsed: 12.4sSummary JSON Schema
{
"repository": "owner/repo",
"created": 57,
"skipped": 42,
"totalDefined": 99,
"elapsedSeconds": 12.4,
"timestamp": "2025-09-23T14:52:31.210Z"
}Adding New Stories Later
- Append new stories to
user_stories.mdusing the naming pattern (e.g.Story 2.4.1:). - Add corresponding hash entry to the
$issuesarray increate_github_issues.ps1. - Re-run the script – only new titles are created; existing ones are skipped.
Troubleshooting
| Issue | Cause | Resolution |
|---|---|---|
| Auth error | Not logged in & no token | Run gh auth login or pass -GitHubToken |
| Label create warnings | Label exists / insufficient perms | Safe to ignore if labels appear in repo |
| Duplicate creation | Title manually changed on GitHub | Align local script title with existing issue |
| >500 existing issues | Pagination limit | (Future) add paging; currently first 500 open + 500 closed |
Potential Future Enhancements
-DryRunpreview mode- Filtering (e.g.
-OnlyEpic 3or-Match "Motor") - Auto-generated backlog index file
- Changelog-style diff when new stories are added
Open an issue if you need one of these prioritized.
GitHub Issues Creation (v2 Markdown Parser)
A newer v2 script parses a simple Markdown file and syncs GitHub issues idempotently.
- File format:
# Epic,## Feature,### Story - Optional labels inline:
[labels: a, b]in the heading, or aLabels:line in the body - Auto adds a type label:
Epic|Feature|Story
Usage:
# Basic: create missing issues only
./create_github_issues_v2.ps1 -StoriesPath user_stories.md
# Update existing issues (body + labels add). Use -ReplaceLabels to reconcile exactly
./create_github_issues_v2.ps1 -StoriesPath user_stories.md -UpdateExisting
./create_github_issues_v2.ps1 -StoriesPath user_stories.md -UpdateExisting -ReplaceLabels
# Dry run (no changes), plus write summary and markdown report
./create_github_issues_v2.ps1 -StoriesPath user_stories.md -DryRun -SummaryPath issues_summary_v2.json -MarkdownReportPath issues_report_v2.md
# Process a specific chunk (e.g. items 30-44) to avoid long-run hangs
./create_github_issues_v2.ps1 -StoriesPath user_stories.md -UpdateExisting -ReplaceLabels -FromIndex 30 -LimitItems 15 -SummaryPath chunk_30_44.json
# Run all chunks automatically (default size 15)
./run_issue_chunks.ps1 -ChunkSize 15 -UpdateExisting -ReplaceLabelsTips:
- Auth via
gh auth login, or setGH_TOKEN/GITHUB_TOKENenv var - Repo resolution: uses the current repo if
-Owner/-Repoare not provided - Labels referenced in Markdown are ensured (created if missing)
Chunked / Resumable Execution
If very large full runs occasionally stall (external gh CLI hang), you can process the backlog in deterministic chunks:
-FromIndex Nstarts processing at the zero-based index of the parsed markdown items.-LimitItems Kcaps how many items are processed in this invocation.- Together they form a window:
[FromIndex, FromIndex + LimitItems).
Helper script run_issue_chunks.ps1 orchestrates sequential chunks:
# Dry run all chunks (no changes)
./run_issue_chunks.ps1 -ChunkSize 20 -DryRun
# Live update with label reconciliation (body+labels) in 15-item windows
./run_issue_chunks.ps1 -ChunkSize 15 -UpdateExisting -ReplaceLabels
# Resume only remaining tail manually
./create_github_issues_v2.ps1 -UpdateExisting -ReplaceLabels -FromIndex 60 -LimitItems 20Each chunk writes its own summary/report (issues_summary_v2_chunk_#.json). You can merge results later if desired. This strategy avoids losing progress to a mid-run stall.
Additional Resilience & Performance Flags (Advanced)
The v2 script also supports advanced flags to make large synchronizations safer and faster:
| Flag | Purpose | Default | When to Use |
|---|---|---|---|
-GhTimeoutSeconds <n> | Kills and retries any single gh CLI call exceeding n seconds. | 60 | Full runs that occasionally hang mid-call. |
-SkipUnchanged | Skips body update when the existing GitHub issue body already matches the markdown (still reconciles labels). | Off | Re-running frequent syncs where most stories are unchanged. |
Examples:
# Run chunked with a 45s per-call timeout
./run_issue_chunks.ps1 -ChunkSize 15 -UpdateExisting -ReplaceLabels; \
Get-ChildItem issues_summary_v2_chunk_*.json | Select Name
# Direct window with timeout + skip unchanged bodies
./create_github_issues_v2.ps1 -FromIndex 30 -LimitItems 15 -UpdateExisting -ReplaceLabels -GhTimeoutSeconds 45 -SkipUnchanged
# Speedy dry run sanity check
./create_github_issues_v2.ps1 -DryRun -SkipUnchanged -StoriesPath user_stories.mdEffect of -SkipUnchanged:
- Performs a lightweight
gh issue view --json bodyper issue on update. - If trimmed body text matches, body update call is omitted, reducing API/process usage.
- Labels are still reconciled (added/removed) respecting
-ReplaceLabels.
Timeout Behavior (-GhTimeoutSeconds):
- Each
ghinvocation is launched in a separate process. - If it exceeds the timeout, the process is terminated and retried (subject to
-RetryCount/ backoff). - Exit codes
-999(timeout) and other non-zero values are treated as transient until retries exhausted.
See user_stories.template.md for a sample structure.
GitHub Issues Creation (v2 REST Variant)
To eliminate occasional external gh CLI stalls, a REST-native script create_github_issues_v2_rest.ps1 provides near feature parity plus extra optimization options.
Why REST?
| Concern | CLI Variant | REST Variant |
|---|---|---|
| External process hangs | Possible on long runs | None (direct HTTP) |
| Per-call timeout | Manual wrapper | Native via Invoke-RestMethod timeout |
| Label ensure | Yes | Yes |
| Skip unchanged bodies | String compare | String or hash compare (optional) |
| Hash-based change detection | No | Yes (-UseBodyHash) |
| Parse-only mode | Yes (-ParseOnly in CLI via earlier improvements) | Yes (-ParseOnly) |
| Chunk window | Yes | Yes |
| Replace labels exactly | -ReplaceLabels | -ReplaceLabels |
Key Additional Flags
| Flag | Purpose |
|---|---|
-ParseOnly | Parse markdown and write summaries/reports without any API calls (no token required). |
-UseBodyHash | Appends an HTML comment <!-- sync-hash:SHA256 --> to each issue body. Future runs compare only the hash for fast unchanged detection. |
-SkipUnchanged | When used with -UseBodyHash, hash comparison avoids fetching or diffing large bodies; otherwise falls back to canonical text compare. |
-HttpTimeoutSeconds | Timeout for each REST call (default 40s) with retries/backoff. |
-FilterTitle "regex" | Process only items whose title matches the supplied case-insensitive regex (applied before chunk window). |
Usage Examples
# 1. Parse-only (no token required) with body hashing to preview generated issues
./create_github_issues_v2_rest.ps1 -ParseOnly -UseBodyHash -StoriesPath user_stories.md -SummaryPath rest_parse.json
# 2. First real creation pass (creates missing issues only)
./create_github_issues_v2_rest.ps1 -GitHubToken $env:GITHUB_TOKEN -UseBodyHash -SummaryPath rest_create.json
# 3. Update existing issues (body + label reconciliation) but skip unchanged using hashes
./create_github_issues_v2_rest.ps1 -UpdateExisting -SkipUnchanged -UseBodyHash -ReplaceLabels -GitHubToken $env:GITHUB_TOKEN -SummaryPath rest_update.json
# 4. Process a specific window (items 30-44) safely
./create_github_issues_v2_rest.ps1 -UpdateExisting -ReplaceLabels -FromIndex 30 -LimitItems 15 -SkipUnchanged -UseBodyHash -GitHubToken $env:GITHUB_TOKEN -SummaryPath rest_chunk_30_44.json
# 5. Pure dry run (no create/update) but still exercise label ensure logic
./create_github_issues_v2_rest.ps1 -DryRun -UpdateExisting -ReplaceLabels -UseBodyHash -SkipUnchanged -GitHubToken $env:GITHUB_TOKEN -SummaryPath rest_dryrun.json
# 6. Only sync WiFi or telemetry related items
./create_github_issues_v2_rest.ps1 -UpdateExisting -ReplaceLabels -FilterTitle "WiFi|Telemetry" -SkipUnchanged -UseBodyHash -GitHubToken $env:GITHUB_TOKEN -SummaryPath rest_wifi.jsonHash Logic Details
- Canonical body removes any existing
<!-- sync-hash:... -->marker before hashing. - Hashing uses SHA-256 over UTF-8 bytes of canonical text.
- The hash marker is appended as a final line to persist change fingerprint.
- On
-SkipUnchanged -UseBodyHash, if existing and new hashes match, body update is skipped (labels still reconciled).
When to Use Hashing
| Scenario | Recommended? | Benefit |
|---|---|---|
| Large bodies with frequent re-sync | Yes | Fast equality check, minimal diff noise |
| Many runs with few edits | Yes | Avoids repeated PATCH calls |
| One-off initial import | Optional | Adds marker but no harm |
| Bodies manually edited on GitHub | Caution | Manual edits outside canonical format change hash; script will patch body to restore canonical + marker |
Summary JSON (REST)
Adds useBodyHash boolean to previous schema:
{
"repository": "owner/repo",
"dryRun": true,
"updateExisting": false,
"replaceLabels": false,
"useBodyHash": true,
"createdCount": 0,
"updatedCount": 0,
"skippedCount": 0,
"failedCount": 0,
"totalFromMarkdown": 71,
"elapsedSeconds": 0.4
}Migration Tips
- Run a
-ParseOnly -UseBodyHashto preview and inject hashes locally (no API calls). - Perform a creation run without
-UpdateExistingto add any new issues. - Follow with
-UpdateExisting -SkipUnchanged -UseBodyHashfor maintenance cycles. - Use chunk windows (
-FromIndex/-LimitItems) only if you anticipate extremely large future backlogs; REST calls are typically stable without chunking. - Narrow scope with
-FilterTitlewhen iterating on a subset (e.g.,-FilterTitle "^Story 3\\.|WiFi").
Troubleshooting (REST)
| Symptom | Cause | Resolution |
|---|---|---|
| Token error | Missing PAT | Provide -GitHubToken or set GH_TOKEN / GITHUB_TOKEN |
| 403 rate limit | Excessive rapid updates | Add -ThrottleMs 250 or re-run later |
| Skips expected update | Hash unchanged | Change markdown body or omit -SkipUnchanged once |
| Marker visible in UI | Expected | It's a harmless HTML comment; remove -UseBodyHash for future runs to stop adding it |
The legacy CLI script remains available; prefer the REST variant for reliability on large sets.
Merging Multiple Runs
Use merge_issue_summaries.ps1 to consolidate JSON summaries from both CLI and REST scripts.
# Basic merge (auto-glob issues_summary_v2*.json)
./merge_issue_summaries.ps1
# Specify explicit files
./merge_issue_summaries.ps1 -Paths issues_summary_v2_rest_parseonly.json,rest_update_live.json
# Include distinct title lists and write to custom output
./merge_issue_summaries.ps1 -IncludeDetails -Output merged_detailed.json
# Dry run (print to console only)
./merge_issue_summaries.ps1 -DryRun -Glob "rest_*.json"Merged output fields:
files,totalFilesrepositories(file count per repo)totals(created/updated/skipped/failed/defined/filtered)rollup(net summary)distinctTitles(only when-IncludeDetails)
Roadmap & Development Status
| Phase | Goal | Status | Issues |
|---|---|---|---|
| ✅ Phase 1 | Repository + CI/CD infrastructure | Complete | Epic 4 |
| ✅ Phase 2 | Hardware design + component integration | Complete | Epic 1 |
| ✅ Phase 3 | Atopile build system + PCB generation | Complete | Epic 1 |
| 🔄 Phase 4 | Component sourcing + BOM population | In Progress | Feature 1.2 |
| 📋 Phase 5 | Flight control software development | Planned | Epic 2 |
| 📋 Phase 6 | Wireless communication + web interface | Planned | Epic 3 |
| 📋 Phase 7 | Testing + validation + safety systems | Planned | Epic 5 |
| 📋 Phase 8 | Documentation + user guides | Planned | Epic 6 |
| 📋 Phase 9 | PCB manufacturing + assembly | Future | Feature 1.3 |
| 📋 Phase 10 | Flight testing + tuning | Future | Epic 2 |
Current Focus: Component sourcing and part selection for automated BOM generation
Technical Specifications
Hardware
- Microcontroller: Raspberry Pi Pico 2W (RP2040 + WiFi)
- Motor Drivers: 2x DRV8833 (4 independent brushed DC motor outputs)
- IMU: GY-91 (ICM-20948 9-DOF + BMP280 barometer)
- Power: LiPo Amigo Pro (boost converter + charging)
- Connectivity: WiFi 802.11n, I2C sensors, GPIO controls
- Indicators: Status LEDs, user button, power management
Software (Planned)
- Flight Control: PID stabilization loops, sensor fusion
- Communication: WiFi AP/STA modes, real-time telemetry
- Interface: Web-based control panel, mobile-friendly
- Safety: Fail-safe landing, emergency stop, range limiting
Dual Push (GitHub + GitLab)
Configured by adding GitLab remote earlier. Optional combined push strategy (if desired) can be a script or additional push URL.
To add GitLab as additional push target on origin (alternative approach):
git remote set-url --add origin https://gitlab.com/pete529/PICO_Drone_Mk1.git(We kept a distinct gitlab remote instead to keep fetches clean.)
Push both manually:
git push origin main
git push gitlab mainVersioning
We'll start semantic versioning now. Create a new tag after meaningful milestones:
git tag -a v0.1.0 -m "Initial CI + scaffolding"
git push origin v0.1.0An automated workflow (.github/workflows/bump-version.yml) inspects commit messages on main and will bump the version file (VERSION) using these rules:
feat:→ minor (unless major bump triggered)BREAKING CHANGEor!:→ major- otherwise → patch
To disable auto bump for a commit, include [skip bump] in the commit message.
Contributing
Currently private / personal R&D. Future contribution guidelines may include:
- Atopile component style guide
- Pin mapping validation steps
- CI footprint linting
License
MIT – see LICENSE.
Disclaimer
Electronics provided as-is; verify footprints, clearances, and power integrity before fabrication. Use at your own risk.
Parts
21| Qty | Value | Footprint | References |
|---|---|---|---|
| 4 | Connector_2Pin_JST_PH:JST_PH_B2B-PH-SM4-TB | J1, J2, J3, J4 | |
| 4 | 10kΩ ±1% 62.5mW | UNI_ROYAL_0402WGF1002TCE:R0402 | R1, R2, R3, R5 |
| 2 | TI_DRV8833:TI_DRV8833 | U2, U3 | |
| 2 | 100nF ±10% 16V X7R | Samsung_Electro_Mechanics_CL05B104KO5NNNC:C0402 | C1, C2 |
| 1 | GY-91:GY-91 | U5 | |
| 1 | UBlox_NEO6M:UBlox_NEO6M | U4 | |
| 1 | Bosch_Sensortec_BMP280:LGA-8_L2.5-W2.0-P0.65_AMP6127 | U1 | |
| 1 | Hubei_KENTO_Elec_KT_0603G:LED0603-RD | LED1 | |
| 1 | ALPSALPINE_SKTDLDE010:KEY-SMD_SKTDLDE010 | SW1 | |
| 1 | AmigoPro_PIM485:AmigoPro_PIM485 | J5 | |
| 1 | Hubei_KENTO_Elec_KT_0603R:LED0603-RD | LED2 | |
| 1 | Raspberry_Pi_Pico_2W:Raspberry_Pi_Pico_2W | U6 | |
| 1 | 1kΩ ±1% 62.5mW | UNI_ROYAL_0402WGF1001TCE:R0402 | R4 |
More from pete529/PICO_Drone_Mk1
10- 2 layers

- 2 layers

- 2 layers

- 2 layers

- 2 layers

- 2 layers

- 2 layers

- 2 layers

- 2 layers

- 2 layers

Similar boards
- 2 layers28.3 × 39.8 mm

LevelShifter
gusmanb/logicanalyzer
24 channel, 100Msps logic analyzer hardware and software
21 parts5.1kGPL-3.0 - 2 layers171.2 × 72.9 mm

Amiga gfxcard before pour
mntmn/amiga2000-gfxcard
MNT VA2000, an Open Source Amiga 2/3/4000 Graphics Card (Zorro II/III), written in Verilog
21 parts1k - 2 layers93.9 × 46 mm

- 2 layers45.5 × 42.9 mm

Esphome han reader
hackclub/OnBoard
💡 Join 1,000 teenagers and make your first PCB with a $100 grant!
21 parts915 - 2 layers31.8 × 14.5 mm

Esp prog
drandyhaas/KiCadRoutingTools
A set of Python/Rust tools to aid routing in KiCad
21 parts744MIT - 2 layers23.5 × 15.8 mm

QuiverAttachPCB
Arrow-air/project-quiver
Project Quiver documentation, designs, and project artifacts.
21 parts617CERN-OHL-S-2.0 - 2 layers69.9 × 41.3 mm

- 2 layers161.3 × 111.8 mm

Questions
What parts does the Layouts use?
21 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 Layouts KiCad files?
From the pete529/PICO_Drone_Mk1 repository on GitHub, at the commit this page was made from: the board is hardware/hardware/layouts/default/default.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.
Can I use the Layouts design in my own project?
Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).