PCB Design Requirements

flux

I inspected the live DRC airwire report and mapped the flagged IDs back to the layout components.
Airwire findings

Table

DRC flagMapped componentExact pad most likely involvedNet
pad 39ce6c47C2C2 P1VIN
pad 21b6c03fC1C1 1VIN
pad 21b6c03fC1C1 2GND
Why I mapped them that way
  • The airwire checker reported pads tied to IDs 39ce6c47 and 21b6c03f.
  • In the PCB layout, those IDs map to:
    • C2 uid 39ce6c47...
    • C1 uid 21b6c03f...
  • The schematic confirms the only pads on those components are:
    • C2: P1 on VIN, P2 on GND
    • C1: 1 on VIN, 2 on GND
Net context

Table

NetConnected pads/components
VINJ2:1, D1:K, C2:P1, C1:1
GNDJ1:1, J3:1, J4:1, D1:A, C2:P2, C1:2
Important caveat
Flux’s DRC output is exposing the flagged pad/component IDs, but not the full airwire pair geometry in the review text itself. So I can identify the three unresolved pads confidently, but the review output does not explicitly name the opposite endpoint of each unrouted connection.
So the practical read is:
  • one unrouted connection is at C2 on the VIN side
  • two unrouted connections are at C1, one on VIN and one on GND
If you want, I can do one more read-only pass focused on the PCB geometry around C1 and C2 and tell you which nearby trace segment each one is supposed to join.
List all airwires
Show first airwire
Check missing footprints

flux

nets {
net GND = GND:GND, J4:1, J1:1, J3:1, D1:A, C1:2, C2:P2;
net VIN = C2:P1, J2:1, C1:1, D1:K;
}
Sign up to send

Files

Schematic

Layout

3D View

J1
C2
Capacitance
0.1uF
D1

Inline Power Protection PCB

Inline Power Protection PCB thumbnail