Finding Schottky Diode Component


Based on Flux’s knowledge base guidance, an airwire is the visual indicator of an unrouted electrical connection in your PCB layout.
When you see an “airwire error” (DRC category design_rule_check_airwires), it means:
  • There are nets defined in your schematic that haven’t yet been routed as copper traces on the board.
  • You’ll see thin lines (airwires) between pads or pins that need a physical trace.
To resolve airwire errors:
  1. Switch to the PCB layout view.
  2. Route each airwire by drawing a trace between the connected pads (manually or via Auto-Layout).
  3. Re-run DRC to confirm that no unrouted nets remain.
check drc , as all the connection are connected but it still says ariwires
The DRC “Airwires” report shows 44 unrouted net segments still present on the PCB. Each check lists two pads that belong to the same net but are not yet connected by a copper trace.
Key findings:
  • Power-rail nets (e.g., VIN→U6, VOUT→C23, +9 V rail nets) have airwires
  • Decoupling capacitor nets (e.g., C17↔C16, C13↔C12) are unrouted
  • I2C pull-up and gyro interface nets (e.g., U7↔R_I2C_PULL1, U1 SDA/SCL) are still airwires
  • Switching regulator pins and associated inductor/capacitor nets (U4 SW→L1/C14, U5 SW→L2/C18) are unrouted
Next Steps:
  1. Switch to the PCB layout view.
  2. Route each net listed above, either manually or via Auto-Layout:
    • Use the Route tool (R) to draw traces between each pad pair.
    • Ensure you route power nets with adequate trace width for current.
  3. Re-run DRC (right-hand panel → DRC tab) to confirm airwire counts drop to zero.
Let me know if you’d like guidance on using Auto-Layout or manual routing strategies.
Auto-route instructions
Trace width calculation
Define net class rule
Routing priority
Decoupling pad guidelines

Flight_controller

Flight_controller thumbnail