ESP32 Camera with OLED


Can you run the checks is saying there's a ton of overlapping copper
I checked your board’s reviews. Summary:
  • Overlapping Copper: 26 errors
  • Airwires (unrouted connections): 23 errors
  • Invalid Layer: none
  • Floating Copper: none
What Flux docs say about DRC and where to see results (verbatim):
“In Flux, DRCs run in real-time, and their results can be accessed from the messages menu.”
“Overlapping Traces: Triggers a DRC violation when two traces from different nets overlap each other.”
Source
How to fix these quickly:
  • Overlapping copper
    • Remove or reshape any duplicate traces or short stubs that sit on top of other-net traces or pads.
    • If you drew any custom copper shapes/polygons, delete or trim the ones that bridge different nets.
    • Around dense parts (soft-latch, boost, USB-C area), pull traces back from pad edges to respect clearance.
  • Airwires
    • Route each reported pair until the airwire disappears. Prioritize power rails first (USB-C VBUS to charger IN, charger OUT to boost VIN, boost 5V to ESP32-CAM VIN, LDO 3V3 to OLED header), then I2C and buttons.
Want me to walk through the first few errors and propose exact edits for each hotspot? If yes, I’ll start with the top 3 Overlapping Copper items and outline the specific traces or shapes to move or remove.
Ask for step-by-step on first error
Request hotspot prioritization
Ask about polygons vs traces
Clarify airwires handling
Ask for net-specific guidance

Waiting for input


Schematic of WiFi Camera with Motion Detection Reference Design
U2
ESP_RX
BOOT
ESP_TX
BOOT
ESP_RX
ESP_TX
+5V
+3V3
+5V
C1
Capacitance
Capacitance
R3
Resistance
1kΩ
+5V
R4
Resistance
10kΩ
+3V3
+3V3
J1
+5V
+5V
Q1
ESP32-CAM1
J2

WiFi Camera with Motion Detection Reference Design