Botaniq V2
Thought for 12 sec
You can transfer the project to KiCad, but the best path depends on what you want to finish there:
Best option: export manufacturing/layout files
From Flux, export:
- Gerber ZIP — PCB copper, solder mask, silkscreen, drill, board outline
- BOM CSV — parts list
- Pick-and-place CSV — placement data
- Netlist if available — helps cross-check connectivity
Then in KiCad:
- Open KiCad → GerbView.
- Load the Gerber ZIP/drill files to inspect or manually recreate routing.
- Use the BOM and placement CSV as references.
- If you need editable KiCad PCB data, you’ll likely need to manually rebuild/import from these references, because Gerbers are manufacturing outputs, not fully editable design files.
Gerbers do not convert cleanly back into a KiCad schematic + editable PCB. They preserve the board artwork, but not design intent like components, nets, rules, or schematic symbols.
Better practical workflow
Use Flux to export:
- PDF schematic or schematic screenshots for reference
- BOM
- Gerbers
- Pick-and-place
- IPC/netlist if available
Then recreate the schematic in KiCad using the same parts and use the Flux routed board/Gerbers as a visual reference.
Before exporting
Your board still had unresolved routing cleanup issues last time:
- remaining airwires/unrouted connections
- copper overlap conflicts may need final verification
So I would not manufacture directly from the current Gerbers without checking them in a Gerber viewer first.
Export Flux files
Fix routing first
KiCad rebuild guide
Run final review
Explain Gerbers
Refine this doc
Ask about this doc
Power Budget
Loads on 3.3 V Rail
Table
| Load | Sleep/Idle | Typical Active | Peak / Design Case |
|---|---|---|---|
| ESP32-C3-MINI-1 module | low-uA sleep target | Wi-Fi/BLE active varies by firmware | 500 mA design allowance for Wi-Fi transmit bursts |
| SHT40 T/RH sensor | nA/uA class idle | sub-mA measurement | 0.35 mA design allowance |
| Status LED | 0 mA off | 2 mA when on | 2 mA |
| Regulator/control margin | - | 1 mA allowance | 1 mA |
| Total 3.3 V rail | firmware-dependent | firmware-dependent | 503.35 mA peak design allowance |
Input Current Reflected to USB 5 V
Using a buck regulator and 90% efficiency assumption:
Input current = (3.3 V * 0.50335 A) / (5 V * 0.90) = 0.369 A.
Sizing Decisions
- The node is designed to operate below a conservative 500 mA USB source limit in normal use.
- USB-C 5 V default sources advertising 1.5 A or 3 A are supported electrically, but this design does not need to draw that much current.
- Input eFuse/current limit target: about 1 A, leaving margin above the ~0.37 A calculated peak input while protecting cables/connectors and downstream circuitry.
- 3.3 V regulator target: at least 600 mA output; 750 mA class selected to cover radio bursts with margin.
- A buck regulator is preferred over a small LDO because an LDO at 5 V to 3.3 V and ~500 mA would dissipate about 0.85 W, which is too high for many compact packages.
Notes
Actual average power depends heavily on firmware duty cycle, Wi-Fi transmit interval, BLE advertising interval, and sleep mode configuration.
Loads on 3.3 V Rail
Input Current Reflected to USB 5 V
Sizing Decisions
Notes
