Quick answer
If nobody on the team is an EE, how you start matters more than which tool you pick: start from a proven circuit, either an open motor controller design or the typical application circuit in your driver's datasheet, then use one tool that carries the board from schematic to order files. KiCad (free, open source) and EasyEDA (free, browser based, wired to JLCPCB and LCSC) both do that by hand. ProtoFlow does it with AI built in: describe the board in plain English, get an editable schematic with real LCSC, DigiKey and Mouser parts, lay it out, run ERC and DRC, export Gerbers plus JLCPCB BOM and CPL files, and open JLCPCB's review and order page from the export menu. Whatever you use, have someone who has built power electronics review the board before you pay for it.
Before the software
The bigger risk is the missing EE, not the tool
A motor controller is power electronics. It switches high current, it gets hot, and an undersized trace or part shows up as a failed board on the bench. Design rule checks catch broken rules, not wrong decisions. ProtoFlow's own review guide says DRC "cannot see what a part is for, how much current a trace carries, where heat goes".
If an off the shelf ESC or driver module fits the motor and the frame, fly that first and design your own board for the next build.
Start from the driver datasheet's typical application circuit or an open design below, and change as little as you can.
Trace width and via count come from the real current, not from the default track width.
Have someone who has built a motor board read the schematic and layout, order a few boards, and power them up at low voltage with a current limit.
The tools
KiCad, EasyEDA, Flux and ProtoFlow for this team
These are the four tools a small hardware team usually weighs for a first board. Each row comes from the vendor's own pages, read on 12 November 2026.
| Tool | How a design starts | Getting to an order | Where it runs | Free option |
|---|---|---|---|---|
| ProtoFlow | You describe the board in plain English; AI drafts an editable schematic with real LCSC, DigiKey and Mouser parts. | Gerber X2, Excellon, JLCPCB BOM and CPL; Order on JLCPCB uploads the board and opens JLCPCB's review and order page. | Desktop app for Windows, macOS and Linux; design files stay local; opens and saves KiCad projects. | Free plan with the full editor, 5 Basic + 10 Pro AI messages a day, no card, no expiry. |
| KiCad | Schematic capture by hand, no built-in AI. | Gerber and IPC-2581 output, sent to any fab. | Desktop: Windows, Linux and macOS. | Free and open source (GNU GPL v3). |
| EasyEDA | Schematic drawn by hand in the online editor or the desktop client. | One-click ordering with JLCPCB; parts from LCSC. | Browser, plus a desktop client. | Core features free forever, commercial use allowed. |
| Flux | An AI hardware engineer in a browser workspace; its robotics page covers motor-drive boards, harnesses, mounts and firmware. | Manufacturing files and assembly diagrams, with cost and lead time on every part before you order. | Browser. | Free trial with limited AI usage, then a paid plan per editor. |
- Pick Flux if you want the motor board, the wiring harness, mounts and firmware kept in one browser project; its robotics page is built around exactly that.
- Pick KiCad if you want a fully open source, offline toolchain and are happy to draw every symbol and route by hand.
- Pick EasyEDA if you want to design in a browser and stay inside the JLCPCB and LCSC pipeline.
- Pick ProtoFlow if you want AI to draft the first schematic from your spec, real parts attached, then lay out, check and export in one free desktop app with local files and KiCad projects you can hand to anyone.
Worked path
One motor controller board, from spec to a JLCPCB order in ProtoFlow
Write the spec before you open any tool
Motor type (brushed DC, BLDC or stepper), battery voltage, continuous and peak current, how the flight controller or MCU talks to the board (PWM, UART or CAN), board size and mounting holes, and the connectors. Those numbers decide the circuit, the parts and how wide the copper has to be. Write them down once and paste them into every later step.
Pick a proven reference to start from
Open ProtoFlow's motor control & robotics reference designs (69 open boards) or the narrower motor controller and drone and flight controller pages. For a board published with KiCad source, select Edit in ProtoFlow, download the source and open the KiCad files in the desktop app, then strip it back to the sub-circuit you need. Read the licence first: several of these boards declare no licence or a custom one, and as ProtoFlow's own pages put it, "publishing files publicly is not the same as granting permission to reuse them".
Describe the board in plain English
ProtoFlow drafts an editable schematic from a written description. Vague prompts get vague boards, so name the parts and the power path. ProtoFlow's prompt guide gives this example for a small BLDC motor:
"STM32G431 MCU. Add a DRV8313 three-phase gate driver connected to the MCU timer outputs for a small BLDC motor. Power input is 12V; add a buck converter to 3.3V for the MCU. Add bulk and decoupling capacitance on the 12V rail, and a 3-pin motor connector plus a 2-pin power connector."
Swap in your own voltage, motor and connectors from step 01, and check the driver's datasheet rating against your motor's peak current before you build on it. A drone propulsion motor is not a small BLDC motor until the datasheet says so.
Attach real parts, then run ERC
Search LCSC, DigiKey and Mouser from inside ProtoFlow so every symbol carries a real, orderable part with its footprint. Run ERC to catch unconnected pins and missing power drivers. The prompt guide's rule is the right one: never ship the first pass.
Simulate the blocks that deserve it
Run SPICE (ngspice) straight from the schematic: operating point, transient, AC and DC sweep, with a waveform viewer. The buck converter and the current sense path are the usual candidates.
Lay the board out for current, not for looks
Sync the schematic into the PCB editor. Give the power nets a net class with a target current and ProtoFlow works out the IPC-2221 width from your stackup's copper, then flags any class that is too narrow. For scale, IPC-2221 gives about 2.77 mm for 5 A and 7.19 mm for 10 A on an outer layer of 1 oz copper at a 10 °C rise, and one 0.3 mm via with 25 µm plating carries about 1.9 A, so 5 A needs three of them (ProtoFlow's free trace width and via current calculators).
Route the high current paths by hand, let the auto-router (presets and layer filters) take the signal nets, and pick the JLCPCB preset so DRC flags any via below that fab's minimums. Refill every copper zone, then clear DRC.
Export the files and send the board to JLCPCB
Export Gerbers writes one ZIP: Gerber X2 in metric with a .gbrjob job file and an Excellon drill file, plated and non-plated holes separated. Export BOM + CPL writes the two CSV files JLCPCB's assembly service expects, after a review dialog that marks each part ready, missing LCSC or needs review. Before anything is written, a preflight blocks geometry that cannot be translated and open DRC errors ask for a review.
Order on JLCPCB uploads the Gerbers to JLCPCB's API, waits for their automated audit and opens the JLCPCB review page in your browser with the detected board dimensions. You confirm the board, finish checkout on JLCPCB's site and attach the BOM and CPL there for assembly. It needs your JLCPCB OpenAPI keys. For a second opinion, save the design as a KiCad project and run KiCad's DRC with your fab's rules before you pay.
Reference designs
Open motor control boards to start from
ProtoFlow indexes public motor control and robotics boards from GitHub, each with a design page and an Edit in ProtoFlow button. The designs and their copyright belong to their authors; ProtoFlow does not host or verify them.
Licensed for reuse (MIT)
You can fork, change, manufacture and sell, keeping the copyright and licence notice.
ESCs to study (read the licence first)
Real brushless ESC layouts. Custom, copyleft or missing licences: learn from them, ask the author before you build on them.
A 6S AM32-compatible ESC built as a proof of concept for learning how to design an ESC from scratch.
ESC BLDC HARDWARE by ckflightBLDC 3 phase motor speed controller hardware working with open source BLHeli_S firmware.
tinyPEPPER by fishpepperA tiny 16x16 mm hole-to-hole 4in1 brushless ESC running BLHeli_S.
Rosmo ESC by rosmo-robotDual brushless motor ESC in M5Stack module format (STM32, SimpleFOC).
BlueESC by blueroboticsSimple, open-source ESC that uses the SimonK firmware.
Flight controllers for the same airframe
What the motor board talks to.
FAQ
Frequently asked questions
What software gets a mechanical engineer from idea to an order for a motor controller board?
One tool that carries the board from schematic to order files, used on top of a proven reference circuit. KiCad and EasyEDA do it by hand; ProtoFlow drafts the schematic from a written description with real parts, then lays out the board, runs ERC and DRC, exports Gerbers and JLCPCB BOM and CPL files, and opens JLCPCB's review and order page from the export menu. The tool matters less than starting from a proven circuit and getting the board reviewed.
Can a team with no electrical engineer design a motor controller board?
Yes for a simple board, if you lean on proven circuits and get a review. Start from the typical application circuit in the driver's datasheet or an open design, size every power trace and via for the real current, bring the first boards up at low voltage with a current limit, and have someone who has built power electronics look at the schematic and layout before you pay for the order.
KiCad or EasyEDA for a drone motor controller?
Both are free and both reach Gerbers. KiCad is open source desktop software and leaves the fab choice to you; EasyEDA runs in a browser and orders from JLCPCB in one click with LCSC parts. Either way the schematic is drawn by hand. If you want AI to draft the first schematic and still finish with JLCPCB files, ProtoFlow covers that and saves KiCad projects, so you can move between them.
Can ProtoFlow send the board to JLCPCB?
Yes. Order on JLCPCB uploads the Gerbers to JLCPCB's API, waits for their automated audit and opens the JLCPCB review page in your browser with the detected board dimensions. Checkout, and attaching the BOM and CPL for assembly, happen on JLCPCB's site. You need your JLCPCB OpenAPI keys connected.
Can we start from an open source ESC design?
You can learn from any of them, and you can build on the MIT ones as long as you keep the copyright and licence notice. Boards with no declared licence or a custom licence need the author's permission before you reuse them in a product. Boards with KiCad source open in ProtoFlow through Edit in ProtoFlow; EAGLE designs need converting first.
Should we design our own board at all?
Only if nothing off the shelf fits the motor, the current and the frame. For a first build, an existing ESC or driver module gets the airframe flying while you design the board you actually need.
Keep reading
Related resources
Try it on the board you actually need
Paste your motor controller spec into ProtoFlow, start from one of the open boards above, and see how far the first draft gets before you hand it to a reviewer.
Download ProtoFlow →Free plan · no card · macOS, Windows & Linux