I couldn’t find relevant documentation for direct PCB trace-routing instructions in Flux. That probably means this specific workflow is not currently documented as a supported feature in Flux.
I can’t inspect or fix the project right now because AI execution is unavailable due to no available ACUs, so I’m unable to run checks, route traces, or resolve errors in the design.
What I can see from the project context:
Project: ESP32-WROOM-32E Reference Design
It includes ESP32-WROOM-32E, USB-C, CH340C USB-serial, AMS1117-3.3, headers, protection parts, and passives.
Recent work updated wiring across multiple commits, so remaining issues may be ERC/DRC, unrouted nets, or connection mistakes.
What remains to do when ACUs are available:
Run schematic/design review to identify exact errors.
Fix ERC issues such as missing power, floating pins, or incorrect net connections.
Check PCB airwires and route remaining nets.
Run DRC after routing to confirm the board is clean.
Once ACUs are available, ask me to “run review and fix errors” and I can inspect, repair, and verify the design.
Wirelessly connects nets on schematic. Used to organize schematics and separate functional blocks. To wirelessly connect net portals, give them same designator. #portal
General Purpose Thick Film Standard Power
and High-Power Chip Resistor
47 kOhms ±5% 0.125W, 1/8W Chip Resistor 0805 (2012 Metric) Automotive AEC-Q200 Thick Film
Features:
- RMCF – standard power ratings
- RMCP – high power ratings
- Nickel barrier terminations standard
- Power derating from 100% at 70ºC to zero at +155ºC
- RoHS compliant, REACH compliant, and halogen free
- AEC-Q200 compliant