Reference schematic

Pico Trainer

suikan4github-Akashi-18-Akashi-18-schematic

Loading the viewer…

suikan4github-Akashi-18-Akashi-18-schematic

Take the project archive: a schematic is a root sheet plus every sub-sheet beside it, and the root alone opens with its hierarchy missing. The archive is zstd-compressed (tar.zst).

1Sheets
13Placed parts
4Net labels
KiCad 7File format

Bill of materials

13 distinct parts

8 resolve to something in the catalog — click through to the component.

RefValueSymbolQty
C10.1uDevice:C
D1OSTAMA5B31AMy_LED:LED_GBAR
Q1DTC143ZMy_Digital_Tr:DTC143Z_1
Q2DTC143ZMy_Digital_Tr:DTC143Z_1
Q3DTC143ZMy_Digital_Tr:DTC143Z_1
R11.5kDevice:R
R22.7kDevice:R
R31kDevice:R
RV1RK09D117000CDevice:R_Potentiometer_MountingPin
SW1B3FSSwitch:SW_Omron_B3FS
SW2B3FSSwitch:SW_Omron_B3FS
SW3B3FSSwitch:SW_Omron_B3FS
U1PicoMy_RPi_Pico:Pico

Provenance

Commit
fd8323dbcd608962f4409aa1773da015b9c9278a
Licence
MIT

How it is used

Trace's agent reads this design as context — what parts a board like this carries, how they are grouped across sheets, what a plausible layer stack and board size look like for the job. It is not copied. The licence above is permissive, and it, the repository and the commit are recorded so the origin of anything derived from it is always answerable.