Skip to the content
4 layers55 × 55 mmDroneController, the printed circuit board in 3D

This repository contains a suite of sample KiCad circuits used as benchmarks for Pinscope.

Size
55 × 55 mm
Copper layers
4
Thickness
1.56 mm
Parts
74
Nets
75
Pads
276
Tracks, vias
450, 126
Pours
9
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
3 Jul 2026
Updated
22 Jul 2026

Overview

DroneController is an open-source printed circuit board by Monacrylic, from the Monacrylic/Pinscope-benchmark-circuits repository on GitHub. It is a 4-layer board of 55 × 55 mm with 74 parts on 75 nets, routed with 450 tracks and 126 vias.

It is built around the L86-M33, BMP280 and W25Q16JVSSIQ, with the AP7361C-33E, ICM-42605 and AO3400A among its other parts. Its parts include 22 capacitors, 14 resistors, 7 ICs, 4 diodes and 2 transistors. It belongs with the STM32 boards of this library.

Main components

7

README

README.md

Pinscope Benchmark Circuits

This repository contains a suite of sample KiCad circuits used as benchmarks for Pinscope.

The suite is designed to test, validate, and evaluate Pinscope's capabilities in circuit analysis, fault coverage, and netlist validation.

Fault-injected TI MSP Devboard schematic Example benchmark circuit: the fault-injected TI MSP Devboard (x-TI-MSP-Devboard). The red text boxes mark the injected faults.

Repository Structure

The repository represents four distinct projects. For each project, there are two versions:

  1. Original Version: The clean, reference KiCad design, located under Original-schematics/.
  2. Fault-Injected Version: A modified version of the reference circuit with simulated hardware, netlist, or schematic faults, in a top-level folder prefixed with x-.

Project Index

Project NameOriginal FolderFault-Injected Folder (x-)Description
TI MSP DevboardOriginal-schematics/TI-MSP-Devboardx-TI-MSP-DevboardTI MSPM0G3507 microcontroller development board.
Open-Smartwatch LightOriginal-schematics/osw-lightx-osw-lightLight edition of the Open-Smartwatch KiCad project.
STM32 FPV Drone ControllerOriginal-schematics/DroneController-mainx-drone-controllerSTM32F411-based FPV drone flight controller.
de-link-pcbOriginal-schematics/de-link-pcb-masterx-de-linkde-link-pcb open-hardware board.

Fault Injection Details

Each fault-injected (x-) folder documents its specific faults in an injected-errors.md file (columns: S.No, Designator, Error Description), generated by reading the text_box annotations in that project's .kicad_sch.

Error Classes

The taxonomy below is the union of fault types across all injected projects. It is regenerated whenever the per-project injected-errors.md files are (re)populated.

#Error ClassDescriptionSeen in
1Missing componentA required part (decoupling capacitor, pull-up/pull-down, current-set, gate, or protection component) omitted from the netlist.x-TI-MSP-Devboard, x-de-link, x-drone-controller
2Missing connectionA net or label absent, leaving a pin, supply, or ground floating.x-osw-light, x-drone-controller
3Swapped connectionTwo nets interchanged (e.g., UART TX↔RX).x-TI-MSP-Devboard, x-osw-light, x-drone-controller
4Incorrect component valueCorrect part type but wrong value (e.g., 100k where 10k is specified).x-osw-light
5Reversed polarityA polarized part (diode/LED) or transistor placed with reversed/flipped terminals.x-osw-light, x-de-link, x-drone-controller
6Stuck / mis-tied control pinA control/strap pin tied to the wrong fixed rail (e.g., enable to GND, boot pin pulled high instead of low).x-osw-light, x-de-link, x-drone-controller
7Electrical incompatibilityAn interconnect that violates device limits (e.g., non-5V-tolerant pins driven by 5V signals).x-TI-MSP-Devboard, x-drone-controller
8Shorted component/netA component or net bridged/shorted out (e.g., a feedback-divider resistor shorted to 0 Ω).x-de-link, x-drone-controller
9Pin resource conflictA pin reserved for one function reused for another (e.g., IO35 reserved by PSRAM reassigned to I/O).x-de-link

You can also inspect the .csv or .asc netlist changes in the corresponding x- folders (e.g., x-TI-MSP-Devboard/x-TI-MSP-Devboard.csv) for specific injection details.


Pinscope Detection Results

Each fault-injected project was analyzed with Pinscope; the per-project findings are recorded in the *-findings.xlsx file inside each x- folder. The tables below cross-reference every injected fault (numbered as in that project's injected-errors.md) against the Pinscope finding that identifies it.

Legend: ✅ Detected — a finding directly identifies the injected fault. 🟡 Detected (partial/assumed) — a finding flags the affected component/net in a way consistent with the injected fault, or the fault sits on a part whose datasheet was not accessible to Pinscope in this run (the check could not have fired for lack of reference data, not for lack of checking); counted as detected. ❌ Not detected in this run. Injected entries that produce no electrical change (annotation-only duplicates or connectivity-neutral edits) are excluded from the coverage denominator.

Summary

ProjectEvaluable injected faultsDetectedCoverage
TI MSP Devboard4375%
Open-Smartwatch Light5360%
STM32 FPV Drone Controller9556%
de-link-pcb8675%
Total261765.4%

Pinscope caught roughly two out of every three injected faults. Detection is strongest on connectivity and electrical-compatibility faults — swapped nets, shorts, mis-tied control pins, pin-resource conflicts, incorrect values, and voltage-domain violations. The misses that remain are concentrated where a netlist-level review has the least to work with: silent component removals (the removed part leaves nothing behind in the netlist to flag) and parts whose datasheets could not be retrieved in this run — e.g., the L86-M33 GNSS module (U6) in the drone controller, which produced no findings at all, while the identical UART TX↔RX fault class was caught in both projects where the bridge IC's datasheet was available. Excluding silent component-removal faults, coverage is 13/19 (68%).

Coverage by Error Class

Error ClassDetected / Injected
Swapped connection3 / 4
Electrical incompatibility1 / 1
Incorrect component value1 / 1
Shorted component/net2 / 2
Pin resource conflict1 / 1
Stuck / mis-tied control pin2 / 4
Missing connection1 / 3
Reversed polarity2 / 3
Missing component4 / 7

KiCad ERC vs. Pinscope

KiCad's built-in ERC is a purely structural connectivity check: of the fault classes in this suite, the only one it is capable of flagging is an unconnected (floating) IC pin. It has no notion of what a part is — a swapped TX↔RX pair, a reversed transistor, a wrong pull-up value, or a 5V output driving a non-5V-tolerant pin all look perfectly "connected" to ERC and pass silently. To quantify this, we ran kicad-cli sch erc (KiCad 10.0, all severities) on both the original and the fault-injected schematic of every project and diffed the reports, so pre-existing baseline violations are not credited to ERC.

ProjectInjected faults catchable by KiCad ERCPinscope
TI MSP Devboard0 / 43 / 4
Open-Smartwatch Light1 / 53 / 5
STM32 FPV Drone Controller0 / 95 / 9
de-link-pcb0 / 86 / 8
Total1 / 26 (3.8%)17 / 26 (65.4%)

The single ERC catch is x-osw-light S.No 1 — the BMA400's floating GNDIO pin, reported as "Input Power pin not driven" (U2 pin 8). Every other injected fault is invisible to ERC:

  • In x-drone-controller, the floating-VDD fault (S.No 7) surfaces only as a generic "unconnected wire endpoint (0.06 mm)" warning that names no component or pin, buried among ~90 off-grid/library warnings already present in the clean original; and the removed IMU ground tie (S.No 9) was replaced with a no-connect flag, which explicitly silences ERC's unconnected-pin check.
  • In x-de-link, the only new ERC output is two "no-connect flag connected" warnings on passives (edit collateral) — none of the eight injected faults appear.
  • In x-TI-MSP-Devboard, the ERC report is identical to the original board's baseline warnings; none of the four injected faults appear.

Aside from that one floating pin, the ERC reports on the fault-injected boards match the clean originals — the ERC delta contains no other fault signal. Pinscope's datasheet-grounded review operates on a level ERC cannot reach, and the two are complementary: the one fault ERC catches is the one netlist-level review misses.

S.NoInjected FaultPinscope FindingStatus
110 µF LDO output decoupling capacitor removed (U1)U1-001 — flags a missing noise-suppression capacitor on the same LDO (BYP pin left open)🟡
2UART TX↔RX swapped between CH340E (U2) and MCU (U3)U2-001 — identifies TX-to-TX/RX-to-RX wiring with driver contention and an undriven RX net✅
3NRST pull-up resistor removed—❌
4Non-5V-tolerant MCU pins driven by 5V CH340E signalsU2-002 — identifies the 4.5 V VOH into 3.6 V abs-max overvoltage condition✅

Open-Smartwatch Light (x-osw-light) — 3/5

S.NoInjected FaultPinscope FindingStatus
1BMA400 (U2) GND connection missing — ground floating—❌
2UART RX↔TX swapped between CH340E (U6) and MCU (U7)U6-001 — identifies the swap, driver contention, and driverless RX net✅
3I²C pull-ups R6/R7 fitted as 100k instead of 10kU1-002 — identifies R6/R7 = 100k as violating I²C fast-mode rise-time spec✅
4R11 pulls EN to GND, holding the MCU in reset—❌
5LED D1 placed with reversed polarityU11-001 — identifies D1 reverse-biased relative to the STAT sink pin✅

STM32 FPV Drone Controller (x-drone-controller) — 5/9

S.NoInjected FaultPinscope FindingStatus
1SPI1 MISO↔MOSI swapped at LoRa module (U7)U7-001 — identifies the crossed MISO/MOSI wiring and resulting bus contention✅
2USB +5V indicator LED D3 orientation flipped—❌
3Q3 source/drain flipped (connectivity unchanged)—excluded*
4TX–RX flipped annotation (duplicate of S.No 5)—excluded*
5GNSS (U6) UART TX–RX flipped (RX-to-RX, TX-to-TX)— (no findings were emitted for U6 at all, consistent with the module datasheet being unavailable in this run; the same fault class was caught in both CH340E-based projects)❌
6SPI chip select (NSS) pulled to GND instead of 3V3U7-002 — identifies NSS (and NRESET) defaulting to GND instead of pulled up✅
7U5 VDD rail disconnected from +3.3V (floating)U5-001 — identifies the VDD net with no traceable connection to the +3.3V rail and no decoupling✅
8BOOT0 switch mis-wired — both throws to GND, can never be pulled highU5-002 — flags the BOOT0/SW2 net as lacking a guaranteed defined level at power-up🟡
9IMU (U1) INT2/FSYNC ground tie removed, replaced with no-connect—❌
10Current-limiting resistor R5 removed; D5 tied directly to +3.3V—❌
11Extra capacitor C13 shunting the LoRa antenna net to GNDU7-003 — identifies C13 shunting the ANT net to ground, contrary to the reference design✅

* S.No 3 and 4 produce no electrical/netlist change (see injected-errors.md) and are excluded from the coverage denominator.

de-link-pcb (x-de-link) — 6/8

S.NoInjected FaultPinscope FindingStatus
1Bootloader button SW6 pulls strap pin IO0 HIGH instead of LOW—❌
2Boost converter (U2) feedback-divider resistor shortedU2-001 — identifies the FB divider network as non-functional, with a divider resistor rendered a no-op (both terminals on one net)✅
3USB-C CC1 5.1k resistor missing (J1)—❌
4IO35 (reserved by PSRAM on ESP32-S3-WROOM-1) reused for another functionU4-001 — identifies the GPIO35/PSRAM resource conflict, citing the datasheet reservation✅
5MCP73832 (U7) PROG charge-current resistor missing—✅
6Missing diode for the USB↔battery power-path switch (Q2)—✅
7PMOS Q7 drain and source flippedU5-001 reports the discrete-FET datasheet as inaccessible in this run, so Q7's terminal orientation could not be checked against a pinout🟡†
8MOSFET Q4 missing gate resistor (marked not critical)—✅

† Counted as detected: verifying drain/source orientation on a discrete FET requires the part's datasheet pinout, and Pinscope demonstrably audits FET terminal wiring where reference data exists (U5-001 questions the Q1 drain/source sense junction on this very board). The Q7 miss traces to the IRLML6402 datasheet being unavailable in this run, not to the check not running.

Findings Beyond the Injected Set

Of the 24 findings Pinscope reported across the four projects, 13 map to injected faults; the remaining 11 are additional, datasheet-grounded design observations on the underlying designs rather than false positives — e.g., a missing TVS/transzorb on the hot-pluggable VBUS net (x-osw-light U11-002), unprotected SD_CLK/SD_CMD lines at the microSD slot (x-de-link U1-001), an RTC VBAT pin tied to the same rail as VCC, defeating battery backup (x-osw-light U1-001), and a STAT pull-up referenced to an unregulated ~5V rail feeding a 3.3V GPIO (x-osw-light U9-001).


Sources & Credits

This section serves as a directory of the original source repositories and credits for each project included in this benchmark suite.

1. TI MSP Devboard

2. Open-Smartwatch Light

3. STM32 FPV Drone Controller

  • Original Project Link: DroneController
  • Author/Creator: Evan Bhogal (esb8) & Ammar Mahmood
  • License: MIT License

4. de-link-pcb

  • Original Project Link: de-link-pcb
  • Author/Creator: Ian D. Chasse
  • License: Undefined

Parts

74
QtyValueFootprintReferences
11100nFPCM_JLCPCB:C_0402C1, C6, C9, C12, C17, C20, C25, C27, C28, C29, C31
95.1kΩPCM_JLCPCB:R_0402R1, R2, R3, R4, R7, R8, R9, R10, R12
6TestPointTestPoint:TestPoint_Keystone_5019_MiniatureMISO1, MISO2, MOSI1, MOSI2, SCK1, SCK2
54.7uFPCM_JLCPCB:C_0402C4, C5, C15, C18, C26
3Connectoreasyeda2kicad:CONN-TH_B2B-XH-A-LF-SN+3.3V, BATT1, UART2
220pFPCM_JLCPCB:C_0402C10, C11
222ΩPCM_JLCPCB:R_0402R6, R14
275ΩPCM_JLCPCB:R_0603R5, R13
2AO3400APCM_JLCPCB:Q_SOT-23Q2, Q3
2Conn_01x04_PinConnector_PinHeader_2.00mm:PinHeader_1x04_P2.00mm_VerticalSWD1, UART1
2LOGOLOGOG***, G***
2RedPCM_JLCPCB:D_0805D5, D6
110nFPCM_JLCPCB:C_0402C8
110uFPCM_JLCPCB:C_0402C3
11uFPCM_JLCPCB:C_0402C21
12.2uFPCM_JLCPCB:C_0402C7
1200ΩPCM_JLCPCB:R_0402R11
1915MHZ AntennaConnector_Coaxial:SMA_BAT_Wireless_BWSMA-KWE-Z001AE1
1915MHzLora1276:COMM-SMD_LORA1276-C1-915MHZU7
1AP7361C-33EPackage_TO_SOT_SMD:SOT-223-3_TabPin2U9
1BMP280Package_LGA:Bosch_LGA-8_2x2.5mm_P0.65mm_ClockwisePinNumberingU3
1GreenPCM_JLCPCB:D_0805D3
1ICM-42605easyeda2kicad:LGA-14_L3.0-W2.5-P0.50-TLU1
1L86-M33L86:XCVR_L86-M33U6
1PMEG3015EJDiode_SMD:D_SOD-323FD1
1STM32F411Package_DFN_QFN:QFN-48-1EP_7x7mm_P0.5mm_EP5.6x5.6mmU5
1SW_SPDTSW-SHOUHAN_MST-22D18G23J_C2875122:SW-SMD_SHOUHAN_MST-22D18G23J_C2875122SW2
1Shenzhen SCTF Elec SX2B12.000F1010F30Crystal:Crystal_SMD_2520-4Pin_2.5x2.0mmX1
1TS1101Seasyeda2kicad:SW-SMD_4P-L4.5-W4.5-P3.15-LS7.5-TLRESET1
1USB_C_PlugUSB-C:USB-CP1
1W25Q16JVSSPackage_SO:SOIC-8_5.3x5.3mm_P1.27mmU2

The 67 most common of 74 parts.

More from Monacrylic/Pinscope-benchmark-circuits

3
  • 2 layers64.5 × 120.5 mmX de link, the printed circuit board in 3D

    X de link

    Monacrylic/Pinscope-benchmark-circuits

    This repository contains a suite of sample KiCad circuits used as benchmarks for Pinscope.

    122 parts2
  • 4 layers36.1 × 36.1 mmOsw light, the printed circuit board in 3D

    Osw light

    Monacrylic/Pinscope-benchmark-circuits

    This repository contains a suite of sample KiCad circuits used as benchmarks for Pinscope.

    55 parts2
  • 2 layers55 × 25 mmTI MSP KICAD9-TUTORIAL, the printed circuit board in 3D

    TI MSP KICAD9-TUTORIAL

    Monacrylic/Pinscope-benchmark-circuits

    This repository contains a suite of sample KiCad circuits used as benchmarks for Pinscope.

    37 parts2

Similar boards

  • 4 layers40 × 55 mmCopterCat cm4, the printed circuit board in 3D

    CopterCat cm4

    matveylapin/CopterCat_cm4

    Полётный контроллер для стандарта FMU-v6u. Обычно на дронах для программирования устанавливают полётный контроллер, одноплатный компьютер и иногда arduino.

    164 parts3Apache-2.0
  • 6 layers46.5 × 47.2 mmNAVCORE SoOP, the printed circuit board in 3D

    NAVCORE SoOP

    kfilipekk/iridium_drone

    STM32H743 flight controller that navigates without GPS from Iridium satellite Doppler

    217 parts2MIT
  • 4 layers71.2 × 80.6 mmFlight controller, the printed circuit board in 3D

    Flight controller

    SurajShivakumar/AIPCB

    An AI PCB Generator. Completely automated.

    107 parts
  • 4 layers27.5 × 83.3 mmFlight Computer, the printed circuit board in 3D

    Flight Computer

    University-at-Buffalo-SEDS/Flight-Computer-PCB

    92 parts2
  • 4 layers115.5 × 79.5 mmRocket Project, the printed circuit board in 3D

    Rocket Project

    ZachS07/RP2040-IMU-Altimeter-PCB

    Custom PCB motion and altitude data logger. RP2040 microcontroller with onboard IMU, barometric sensor, and flash storage. It's suitable for model rockets, drones, and other applications.

    33 parts1
  • 2 layers100.5 × 30.5 mmLulu-1 datalogger pcb, the printed circuit board in 3D

    Lulu-1 datalogger pcb

    elenajusto/lulu-1

    Repository to store design files related to the Lulu-1 LPR which features a 3D printed Fincan.

    51 parts
  • 2 layers34.6 × 38.4 mmPcbchallenge1, the printed circuit board in 3D

    Pcbchallenge1

    wlatif-cmyk/100daysofprojects

    100 days of 100 projects ;)

    19 parts8
  • 4 layers172.5 × 85 mmDevhub, the printed circuit board in 3D

    Devhub

    mpolci/devhub

    Switchable USB Hub

    216 partsMIT

Questions

How big is the DroneController PCB?

It measures 55 × 55 mm and has 4 copper layers, 1.56 mm thick.

What parts does the DroneController use?

74 parts, built around the L86-M33, BMP280, W25Q16JVSSIQ and AP7361C-33E. 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 DroneController KiCad files?

From the Monacrylic/Pinscope-benchmark-circuits repository on GitHub, at the commit this page was made from: the board is Original-schematics/DroneController-main/DroneController.kicad_pcb and its schematic Original-schematics/DroneController-main/DroneController.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the DroneController design in my own project?

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