Robotics / Motor Control
Robotic arm controller board: STM32WB six-axis motor-control schematic and pre-layout audit
We designed the schematic of a six-axis robotic-arm evaluation board (STM32WB55 with BLE, three DRV8833 dual H-bridges) and audited it before layout, fixing 14 critical or high-severity errors. Status: schematic complete (2026); PCB layout next.
What we did: We captured the KiCad schematic and ran a pre-layout electrical audit, fixing 14 critical or high-severity errors; the DRV8833 motor-supply voltage is an open item to settle before layout.
Robotics evaluation-board projectSchematic phase: 2026Rapid Circuitry hardware team
Published Last reviewed:
Illustrative imageThe challenge
An evaluation board for a small robotic arm has to drive six brushed DC motors, talk over Bluetooth, and be easy to probe and debug. Mistakes in the schematic of a motor board are expensive: they show up as smoke, dead drivers or boards that never boot, and each fix costs a respin.
Six motor channels
Six axes need three dual H-bridge drivers, each with sleep and fault lines that must be wired correctly to the MCU.
Mixed voltages on one board
A 12 V rail sits next to battery and 3.3 V logic rails, so a single wrong connection can short a rail or destroy a driver. The DRV8833's motor supply (VM) is rated only 2.7–10.8 V (11.8 V absolute maximum), so it must never see the 12 V rail.
Debuggability
An evaluation board must be easy to measure: test points, debug access and clear signal flow matter as much as function.
Readable schematic
A clean, non-overlapping schematic with left-to-right signal flow was a hard requirement, not a preference.
Impact figures describe the situation before the project, as the client reported it to us; we did not measure them.
Our solution
We captured the full schematic in KiCad, then ran a structured electrical audit before any layout. The audit found 14 critical or high-severity errors; all were fixed and the sheet was reorganised into seven functional zones so the board is easy to review, lay out and debug.
System architecture
A wireless MCU driving six brushed DC axes, organised into seven schematic zones.
Control and wireless
- STM32WB55 MCU with BLE 5 and Zigbee radio
- MCU at the centre of the sheet with its passives
- Debug passives and a column of test points
Motor drive
- 3× TI DRV8833 dual H-bridge: six brushed DC channels
- Drivers stacked vertically with their charge-pump decoupling
- Open-drain fault lines with pull-ups to the MCU
- Motor connectors grouped on the right edge
Power and inputs
- 12 V and battery inputs
- DRV8833 motor supply (VM) must stay at or below 10.8 V: open item before layout
- Power-management zone on the left of the sheet
- Input connectors grouped in their own zone
Board facts
- MCU
- STM32WB55 (BLE 5 / Zigbee)
- Motor drivers
- 3× TI DRV8833 dual H-bridge (VM 2.7–10.8 V)
- Open item
- Feed VM from a rail at or below 10.8 V (e.g. a 2S battery, ≤ 8.4 V), or change to a higher-voltage dual driver such as the DRV8847 (2.7–18 V) if the motors need 12 V
- Axes
- 6 brushed DC
- Components / nets
- 65 / 48
- Target size
- 100 × 80 mm
- Design standards
- IPC-2221, IPC-2152, IPC-7352 (formerly IPC-7351B) land patterns, IEEE 315 symbols
What we delivered
- Complete KiCad schematic: 65 components on 48 nets, all placed and labelled
- Pre-layout electrical audit with 14 critical/high findings
- All 14 findings fixed in the schematic
- Schematic reorganised into seven functional zones
- Test-point column for bring-up and debugging
What the audit found
Examples of the 14 critical and high-severity errors fixed before layout.
Rail short
Critical
Battery rail (VBAT) shorted to ground
Would have failed at first power-up
Driver sleep pins on 12 V
Critical
DRV8833 nSLEEP pins shorted to the 12 V rail
Far above the logic-input rating
Fault line misrouted
High
Open-drain nFAULT outputs wired wrongly; pull-ups missing
Faults would never reach the MCU
Missing parts
High
Charge-pump (VCP) decoupling and test points absent; one LED reversed
Drivers would not run reliably; board hard to debug
Outcome and status
The schematic is complete, audited and cleanly organised. One open design item remains before layout: the DRV8833's motor supply is rated 2.7–10.8 V, so VM must come from a rail at or below that (such as the battery), or the drivers must change to a higher-voltage part if the motors need 12 V. PCB placement and routing on the 100 × 80 mm board follow, so no hardware results are reported here. The lesson is the reason the audit exists: fourteen errors that would have caused a failed bring-up, a damaged driver or a respin were removed before any copper was committed.
How to read the labels: Client-reported baseline = the client's own figure for the situation before the project; we did not measure it. Figures without a label are specifications or project scope.
Errors removed before layout
14
Critical and high-severity findings, all fixed in the schematic
Schematic
65 parts / 48 nets
Organised into seven functional zones with left-to-right signal flow
Next step
PCB layout
Placement and routing on a 100 × 80 mm board
Technologies used
- STM32WB55
- DRV8833
- BLE 5
- Zigbee
- KiCad
- IPC-2221
- IPC-2152
- IPC-7352
- IEEE 315
Related case studies
Drones / Hydrogen Power / Aerospace
Hydrogen drone power system: 5 kW fuel-cell powerpack integration, thermal and mass study
Logistics / Warehousing / Robotics