Supported hardware
VESC firmware supports a large and growing set of hardware targets. The build system discovers targets automatically by scanning thehwconf/ directory for hw_*.h files, so the authoritative list always comes from your local checkout.
Selecting a target when building
Pass your target name directly tomake:
build/<target>/. Some boards also expose a _no_limits variant that disables the hardware protection limits — use these only if you know what you are doing.
Trampa
Trampa manufactures the reference VESC hardware and produces a broad range from entry-level to high-power EV targets.VESC (official branded boards)
Thevesc/ directory covers officially branded VESC controllers separate from the Trampa line.
FlipSky (official)
Official FlipSky boards with full hardware support files.FlipSky (community)
Community-supported FlipSky variants in theflipsky/ directory.
MakerX (GO-FOC series)
Makerbase
Ubox
Ubox targets span 75 V, 100 V, and 126 V power levels.Stormcore
Team Triforce UK
Shaman
Floatwheel
JetFleet
Fungineers
Repas
Tronic
ENNOID
Luna Cycle
ITR
IPM
Other community boards
Theother/ directory contains additional community-contributed targets:
Adding a new target
If your hardware is not listed, thehwconf/example/ directory contains a template you can use as a starting point. Create a hw_<yourboard>.h and hw_<yourboard>.c following the existing pattern — the build system will pick it up automatically on the next make run.
Some targets expose both a standard variant and a
_no_limits variant (for example 100_250 and 100_250_no_limits). The _no_limits build disables hardware protection thresholds and should only be used by experienced developers who understand the risks.