Motor Control Setup

Because changing to 4 layers only gives you more routing resources - it does not automatically fix bad copper geometry, broken net continuity, or unfinished routes.
For Flux’s PCB workflow, stackup change is just part of setup; you still have to get through placement/grouping/routing, and the route stage is what actually classifies nets and applies routing priorities. In other words, 4 layers helps, but it does not by itself complete routing or resolve all copper conflicts
Why you can still see airwires
Airwires mean there are still nets that do not have continuous copper between the required pads. A stackup change does not remove those - it just gives the router more layer options. Flux review treats airwires as unresolved routed connections, and they stay until the route is actually completed
In your board, the remaining airwires were already concentrated on a few power nets:
So the likely reason is simple: those rails are still not fully connected, even though the board now has inner layers.
Why you can still get overlapping copper
Overlapping copper usually means two copper objects on the same layer occupy the same physical space in a way Flux considers invalid. Going from 2 to 4 layers reduces congestion, but it does not automatically:
  • move old traces out of the way
  • remove stale copper from the previous route
  • fix a floating copper island
  • reassign a trace to a different layer
  • clean up fills that now collide with traces or other fills
That lines up with your earlier state where the board still had a floating copper issue after the 4-layer conversion. A stackup change can leave old geometry behind that still needs cleanup.
The most likely causes on your board
In order of probability:

Table


CauseWhy it happens after 4-layer conversion
Old 2-layer routing still existsExisting traces/fills were not fully reworked for the new layer plan
Partial trace stubs remainSame-net traces exist but don’t quite connect, so airwires stay
Copper fills need refill/recheckPlane/fill geometry may now collide or isolate regions
Router did not reprioritize critical netsThe route stage still needs clear power-net intent and room to work
Some copper is on the wrong layer4 layers help only if the critical routes are actually redistributed onto those layers
What to do next
Short version:
  1. Unroute or delete leftover problem traces/fills
    • Especially any old 2-layer compromises on the power nets.
  2. Refill / recompute copper
    • If there is a floating copper or overlap warning, stale copper geometry is a prime suspect.
  3. Route the board again in order
    • First: main 12 V rails
    • Then: 5 V / 3.3 V
    • Then: motor outputs
    • Last: logic signals
That order matches the recommended PCB workflow: setup first, then route with net-type and current priorities, not the other way around
  1. Use the inner layers intentionally
    • L2 Ground Plane
    • L3 Power Plane
    • Don’t keep forcing everything onto top/bottom just because that’s how the 2-layer version was being solved.
My practical diagnosis
Your 4-layer board is probably not failing because “4 layers didn’t work.” It’s more likely that:
  • you still have unfinished rails creating airwires, and
  • you still have legacy copper/fill geometry creating overlap warnings.
So the fix is usually:
  • clean out the leftover copper that no longer makes sense,
  • then reroute with the 4-layer stackup in mind.
If you want, I can give you a very short “clean reset for 4-layer” checklist specifically for 12V Buck, 5V Buck, U2, U3, U4, U1, and U5.
Give cleanup checklist
Check current DRC
Focus on Net 53
U3
Manufacturer Part Number
TB6612FNG
5V Buck
Manufacturer Part Number
Mini MP1584EN DC-DC
U2
Manufacturer Part Number
TB6612FNG
U4
Manufacturer Part Number
TB6612FNG
12V Buck
Manufacturer Part Number
Mini MP1584EN DC-DC
U1 Blue/Yellow
Manufacturer Part Number
ESP32-DEVKIT-V1
U5 Purple/Green
Manufacturer Part Number
ESP32-DEVKIT-V1
Motor 1a
Motor 4a
Motor 3a
Motor 6b
Servo
Motor 6a
Motor 5b
Motor 3b
Motor 4b
Motor 2b
Motor 2a
Motor 1b
Motor 5a
12V PWR/GND

To get started, talk to Flux or create a New Document.

Documents

    Documents are markdown text files which describe project goals, capture details, or even simulation outputs.

    Assets

    No assets added.

    ESP32 Robot Motor Controller

    ESP32 Robot Motor Controller thumbnail
    Welcome to your new project. Imagine what you can build here.

    Properties

    Properties describe core aspects of the project.

    Pricing & Availability

    Distributor

    Qty 1

    Controls