MOSFETs, controllers, and cutouts
Between your battery and your motor sits the controller - a circuit board packed with power transistors, current sensors, and a microcontroller running the balance algorithm. It’s the brain and the muscle of your EUC. When it works, you ride. When it fails, you fall. Understanding what’s on that board changes how you think about reliability and safety margins.
What the controller does
The controller has two jobs running simultaneously:
Balance computation. The microcontroller (MCU/DSP) reads the IMU, estimates tilt, and computes how much torque the motor needs. This runs at kilohertz rates - thousands of decisions per second.
Motor drive. The power stage converts the torque command into electrical current flowing through the motor’s three phases. This requires switching high-voltage, high-current DC from the battery into precisely timed AC waveforms.
Both jobs must work perfectly, continuously, without interruption. A failure in either means loss of balance.
MOSFETs: the power switches
The power stage uses MOSFETs (Metal-Oxide-Semiconductor Field-Effect Transistors) - semiconductor switches that can turn on and off millions of times per second while handling hundreds of amps.
A three-phase motor needs six switches minimum - two per phase (high-side and low-side), forming an H-bridge for each phase. In practice, EUC controllers use many more, wired in parallel, to share the current load.
Why MOSFET count matters. Each MOSFET has a maximum continuous current rating and a resistance when turned on (Rds_on). More MOSFETs in parallel means: lower resistance per phase (less heat), higher total current capacity (more torque available), and better load sharing (each transistor runs cooler).
A 12-MOSFET controller (the original KingSong S22, early Inmotion V11) has 4 per phase. Each one handles a larger share of current. Under peak loads - hill climbing, hard acceleration, sudden balance corrections - they run hot.
A 36-MOSFET controller (Begode Blitz, Lynx) has 12 per phase. Each transistor handles 1/3 the current of the 12-FET design. They run significantly cooler. The controller can sustain higher loads longer before thermal limits kick in.
A 42-MOSFET controller (Inmotion V13 Challenger, V14 Adventure “Raptor”) has 14 per phase. A 48-MOSFET controller (LeaperKim Oryx, KingSong F22 Pro) has 16 per phase. The trend is clear: more MOSFETs = more headroom = more reliable under stress.
Heat: the controller’s enemy
MOSFETs dissipate power as heat: P = I² × Rds_on. Double the current, quadruple the heat. This is why sustained high-current riding - climbing long hills, riding in deep field weakening, heavy riders accelerating hard - pushes controllers to thermal limits.
When MOSFETs overheat, their resistance increases, which generates more heat, which increases resistance further - thermal runaway at the component level. Well-designed controllers have temperature sensors that reduce power output (thermal throttling) before this spiral starts. Poorly designed ones burn.
Thermal management varies by manufacturer. Inmotion uses sealed controllers with thermal paste and multi-layer heat dissipation. LeaperKim separates the power layer (with copper bus bars) from the logic layer to reduce heat interference. Begode has historically run hotter - the Blitz represents their first serious thermal redesign.
Heatsinks, thermal pads, copper traces, and sometimes active fans all contribute to keeping the controller alive under sustained load.
The three-phase inverter and FOC
The MOSFET array forms a three-phase inverter. It chops the DC battery voltage into three overlapping AC waveforms that drive the motor’s stator windings. The timing and magnitude of these waveforms determine how much torque the motor produces and in which direction.
Modern EUC controllers use Field-Oriented Control (FOC) - a vector control method that decomposes motor current into two components: q-axis current (which produces torque) and d-axis current (which controls magnetic flux). The controller independently adjusts each, allowing precise torque control at any speed with minimal ripple.
FOC requires knowing the rotor’s position. EUC motors usually still have Hall sensors; the newer capability is in the controller, which can fall back to sensorless estimation from back-EMF if the Hall signal fails. This remains a significant safety feature on the Oryx and newer LeaperKim wheels, but the capability level is model-specific: Sherman-L is cited for hall-less operation from a complete stop, Oryx and Patton-S for hall-failure safe-operation/stop fallback, and the original Lynx for mitigation above roughly 7 km/h rather than from-stop operation.
Motor types: what’s in the hub
Every EUC uses a permanent-magnet brushless motor built into the wheel hub. Magnets on the rotor (the outer spinning shell), copper windings on the stator (inner, fixed). No brushes, no gears, no belt - direct drive. But not all hub motors are the same.
Surface-mount (SPM/SPMSM): magnets glued to the outside of the rotor, directly facing the air gap. Strong magnetic field, simple construction. The downside: the fixed flux path limits field weakening. The controller can’t easily reduce the magnetic field to extend speed range. Older and budget EUC motors use this design.
Interior permanent magnet (IPM/IPMSM): magnets embedded inside the rotor steel. This creates two torque sources - magnet torque and reluctance torque from the rotor geometry. The embedded position lets the controller manipulate flux paths effectively, making field weakening work well with meaningful speed extension. Most modern high-performance EUC motors use IPM. The field-weakening article covers why this matters for speed and safety margin.
You’ll also see “BLDC” vs “PMSM” in discussions. In EUC context, this usually refers to the control method, not the motor hardware. Trapezoidal commutation (6-step, “BLDC style”) is simpler but produces torque ripple - you can feel it as vibration at low speed. Sinusoidal commutation via FOC (“PMSM style”) is smooth at all speeds. Modern EUC controllers run FOC regardless of what the motor is called in marketing.
Induction motors (no permanent magnets - used in some Tesla models) aren’t used in EUCs. They’re heavier for the same power, less efficient at the partial loads typical in EUC riding, and harder to package in a hub.
For riders: if your wheel runs FOC with an IPM motor, you have the best current combination for smooth torque and effective field weakening. If you’re on an older surface-mount motor with basic commutation, your field weakening range is limited and torque at low speed may feel rougher.
Current sensing
The controller needs to know how much current is flowing through each phase. This comes from either:
Shunt resistors - small precision resistors in the current path. The voltage across them is proportional to current. Simple, cheap, adds some power loss.
Hall-effect current sensors - measure the magnetic field around the conductor without physical contact. No power loss, but more expensive and sensitive to interference.
Current sensing serves two purposes: feeding the FOC algorithm (it needs real-time current to compute the transforms) and protecting the system (overcurrent triggers shutdown before MOSFETs burn).
What causes a cutout
A cutout is the moment the controller can’t maintain balance. The pendulum tips. You fall. There are several distinct failure modes:
Torque demand exceeds supply
The most common “cutout” isn’t a hardware failure - it’s physics. The controller commands torque that the motor/battery system can’t deliver. Causes:
- Overlean at high speed. You’re in deep field weakening. Torque reserve is thin. A bump or gust demands more correction than the motor can provide. The pedals dip. You overlean past recovery
- Voltage sag at low battery. The battery can’t maintain voltage under load. The controller can’t push enough current through the motor. Same effect
- Hill + speed + weight. All three demand sustained high current simultaneously. The system runs out of headroom
This isn’t a “broken” controller. It’s the controller reaching the physical limits of the system. The solution is riding within margins - not faster, lighter on the battery, understanding field weakening.
MOSFET failure
A MOSFET shorts or opens. If it shorts, the phase is shorted to the bus voltage - massive current surge, usually burning the board instantly. If it opens, the motor loses a phase - torque drops to near-zero on that commutation step.
Causes: sustained overcurrent, thermal stress, voltage spikes from inductive switching, manufacturing defects. Prevention: more MOSFETs per phase (lower stress per device), proper gate driving, thermal management, voltage clamping.
The early Inmotion V12 had documented MOSFET failures. The Raptor controller (V11Y, V13 Challenger, V14 Adventure) was a direct response - 42 MOSFETs, 18 capacitors, sealed design with better thermal management.
Hall sensor failure
If a Hall sensor reports incorrect position, the controller commutates at the wrong timing. The motor produces torque in the wrong direction - or produces no torque at all. On a self-balancing vehicle, this means instant loss of balance.
Mitigation: redundant Hall sensor systems (Inmotion, LeaperKim), controller-side fallback algorithms that estimate position from back-EMF.
Firmware failure
A software bug causes incorrect torque output. Watchdog timers and safety limits (maximum angle, maximum current) are supposed to catch this. In practice, firmware bugs have caused cutouts on every brand at some point. This is why manufacturers increasingly add OTA updates, data logging, and app diagnostics - to make it easier to diagnose what went wrong after an incident. These are not always the same feature set: they depend on brand, model, and firmware version.
Board-level failure
Cracked solder joints, failed capacitors, corroded connectors. Usually from vibration, water ingress, or crash damage. Sealed controller designs (Inmotion, some Begode newer models) resist this better than open-board designs.
Reading the specs
When you see “36 MOSFET controller” - now you know what it means. More MOSFETs = more current capacity per phase = more torque headroom = less thermal stress = higher reliability.
When you see “Raptor controller” or “dual-layer board” - that’s thermal engineering. Separated power and logic layers reduce heat interference.
When you see “hall-less operation” - check the model-specific claim. The controller may be able to survive a Hall sensor failure, but from-stop operation and rolling safe-stop fallback are different capabilities.
When you see “data logging” - that’s diagnostics. After a problem, the manufacturer can read the logs to determine if it was rider error, hardware fault, or firmware bug.
555 take
The controller is the least visible and most critical component. You can see the battery size and motor power in specs. You can’t see whether the controller has enough thermal headroom for your riding style.
The industry trend - more MOSFETs, sealed designs, redundant sensors, data logging - is the right direction. But hardware alone doesn’t prevent cutouts. Most cutouts aren’t hardware failures. They’re the controller running out of torque because the rider demanded more than the battery/motor/field-weakening state could deliver.
Understanding the controller means understanding the limits. The MOSFETs, the current sensing, the thermal management, the FOC - all of it exists to deliver one thing: torque on demand. When the demand exceeds the supply, the pendulum falls. Every safety feature, every firmware alarm, every design choice exists to keep you on the right side of that equation.