Chat
Welcome to Flux
Treat Flux like your intern. Tell it what you'd like to build and it'll get to work. You can also ask it questions, brainstorm ideas, and teach it your preferences. Learn More
Explain project
Write a project description
Find schematic issues
Create a test plan
Simulate a circuit
Prepare for Manufacturing
Component Selection Workflow
New Subsystem Wizard
Write I2C initialization code
Generate firmware skeleton
Refine this doc
Ask about this doc
LionCircuits Clearance Fix Summary
Date: 2026-07-23
Requirement
LionCircuits requires at least 0.15 mm / 6 mil copper clearance for pad-to-trace and pad-to-pad spacing. The requested constraints were:
- Check every copper layer for pad-to-trace and pad-to-pad gaps under 0.15 mm.
- Preserve the schematic/netlist.
- Do not shrink trace widths, especially motor/power traces.
- Add a design rule enforcing the 0.15 mm minimum.
Before-edit findings
Flux DRC did not expose a separate numeric clearance report, but it did report 7 overlapping-copper pad-to-trace errors in the same class as the LionCircuits clearance failure. No pad-to-pad clearance errors were exposed by the current Flux checks.
Table
| # | Component / pad | Too close to trace/net | Before status | Action taken | After status |
|---|---|---|---|---|---|
| 1 | C3 P1 | Trace cd712066... on Net 15 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
| 2 | C3 P1 | Trace d02b852d... on Net 15 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
| 3 | C1 P1 | Trace 48eeabd7... on Net 21 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
| 4 | C4 P1 | Trace 7f6388a9... on Net 20 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
| 5 | C4 P1 | Trace 8031d960... on Net 20 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
| 6 | C2 P1 | Trace d6cf88d0... on Net 17 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
| 7 | C1 P1 | Trace e08dab08... on Net 21 | Under 0.15 mm / overlapping copper | Removed dangling/stub trace segment | Cleared; no overlapping-copper error |
Two dangling remnants left by the clearance cleanup were also removed:
- Trace
23a0420b.../5369d7e1...on Net 17 - Trace
b22bea57...on Net 15
These were layout-only cleanup edits; the schematic netlist was not changed.
Rule changes
Updated project PCB rulesets:
-
LionCircuits 0.15mm pad clearance (
selector: pad)keepOut: routeSegment(0.15mm) pad(0.15mm) !importantminKeepOut: routeSegment(0.15mm) pad(0.15mm) !important
-
LionCircuits 0.15mm trace-to-pad clearance (
selector: routeSegment)keepOut: pad(0.15mm) !importantminKeepOut: pad(0.15mm) !important
Verification after edits
Final DRC check results:
- Overlapping Copper: no errors returned.
- Pad Access Clearance: no errors returned.
- Floating Copper: no errors returned.
- Airwires: no errors returned in the requested verification set.
- Dangling Traces: 5 warnings remain, all pre-existing and not part of the LionCircuits pad-to-trace / pad-to-pad clearance failure:
- Trace 16d9
- Trace 6106
- Trace 740d
- Trace 7932
- Trace d682
Logical netlist verification after edits shows the affected nets still exist with the same schematic endpoints:
- Net 15: D3, P6, Q3
- Net 17: D2, P4, Q2
- Net 20: D4, P8, Q4
- Net 21: D1, P2, Q1
- Net 23: Vbat / battery / C1-C4 / D1-D4 / J1 / terminals / R8
Notes
The exact old numeric gap values for each Flux-reported item were not available from the current DRC output; Flux reported them as overlapping-copper errors. The post-fix pass verifies that the pad-to-trace/pad-to-pad overlap class is cleared and that the new 0.15 mm clearance rules are present for future checks.
Requirement
Before-edit findings
Rule changes
Verification after edits
Notes
