A brushless DC (BLDC) motor can run smoothly on the bench, then cut out the moment a battery-powered machine accelerates under load. The motor spins, the controller powers up, the battery pack shows a healthy voltage at rest. Yet something trips, and it is not obvious whether to blame the battery, the controller, or the motor.
In most cases the answer is that no single component is faulty. The components were selected against nameplate figures that do not describe how they behave together. This guide covers the key selection steps, from the battery’s output limits and the motor’s requirements to controller compatibility, thermal management, and real-world testing.
Start with what the battery can actually deliver
Nominal voltage is a label, not an operating condition. A pack described as 48 V spends its working life across a range, from its full-charge voltage down to the point where the BMS (Battery Management System) or controller cuts off, and it sags further whenever current is drawn. The controller’s input range has to cover that entire span, including the transient dips during acceleration, not just the nominal figure.
As an illustration, take a 13-series lithium-ion pack. Fully charged, it sits around 54.6 V (13 cells at 4.2 V). Near the low end, depending on the cell chemistry and the BMS cutoff, it might be closer to 39–42 V, and it will read lower still for a moment when a heavy load is applied. A controller specified for a narrower window can shut down on undervoltage well before the pack is truly empty. The actual operating range depends on the cells and BMS settings.
Current capability needs the same scrutiny, and it is limited by more than the cells. The battery cells, BMS, connectors, and wiring all limit how much current the system can safely draw. The lowest limit sets the maximum available current. A pack that handles the normal running current can still trip its protection when the motor draws a brief surge during acceleration. So compare the BMS and cell limits with the expected demand during acceleration, not only steady running, and check whether the connectors and cable gauge add enough voltage drop to push the controller toward its undervoltage threshold.
Work out what the load demands of the motor
Selecting a brushless DC motor starts from the load rather than from a power rating. Torque at the required speed, the torque needed to get the load moving, how quickly it must accelerate, and how the demand repeats over a work cycle together decide whether a motor is adequate. Rated power alone hides most of this: a motor that comfortably sustains the cruising load may have little margin for starting a heavy mechanism or climbing a grade.
It helps to separate three questions. What continuous torque does the application require at its normal speed? What peak torque is needed, and for how long? And does the motor’s winding suit the pack voltage?
A motor’s speed constant indicates how its no-load speed relates to applied voltage, while the torque required by the application largely determines the current needed to produce that torque. Check the manufacturer’s speed-torque data at the intended supply voltage rather than using the speed constant alone to judge whether a motor will meet the application’s requirements.
A rough estimate of battery-side current can be made from mechanical output power, overall system efficiency, and battery voltage. For example, if a motor delivers 1 kW of mechanical power at an assumed overall efficiency of 90%, the battery must supply about 1.11 kW. That corresponds to approximately 28 A at 40 V or 21 A at 54 V, before accounting for transient effects and voltage sag. If acceleration briefly doubles the power requirement, the current roughly doubles too, and it does so at the lowest, sagging voltage, which is the figure the pack, BMS, and wiring have to survive.
What is the Difference Between Battery DC Current and Motor Phase Current?
A brushless DC motor controller sits between a DC source and a three-phase motor, and its current limits apply to two different places. Battery-side (DC input) current and motor phase current are not the same quantity, and comparing them directly is a common source of error. At low speed, a controller can deliver a high phase current to the motor while drawing noticeably less current from the battery, because the duty cycle is small. At high speed and high duty, the two figures move much closer together. The controller’s continuous and peak ratings for each need to be read from its documentation and matched against what the motor and the battery can accept.
Beyond current, confirm the practical compatibility items: the supported voltage range against the pack’s working range, the sensor type the motor uses (Hall sensors, encoder, or sensorless operation), the commutation method, and the speed or torque command interface the rest of your system will use. A mismatch in sensor wiring or commutation setup tends to show up as rough starts, jitter, or a motor that will not spin up cleanly rather than as an obvious fault.
Once the voltage range, torque requirements, and current limits are clear, it becomes easier to select a motor and controller that work across the full operating range. Brushless.com offers brushless DC motors and compatible controllers for applications with different voltage, torque, and current requirements.
Account for heat and duty cycle
A system that works for thirty seconds has not been shown to work for thirty minutes. Copper losses in the motor windings increase approximately with the square of current when winding resistance is held constant, and the controller’s power stage adds conduction and switching losses, so how hot the system gets also depends on cooling. Sustained load, frequent start-stop cycles, high ambient temperature, and a cramped enclosure can each push a design into thermal protection that never appeared during a short test.
Start by describing the duty cycle honestly. A motor that spends most of its time near its continuous rating has little thermal reserve; one that sees brief peaks separated by long idle periods can often use its short-time capability. Installation matters as much as the rating: mounting a controller to a metal frame, allowing airflow, or leaving it sealed in a small box can change its sustainable output substantially. Battery temperature also matters, as the permitted charge and discharge current can change with cell temperature.
Selection mistakes that tend to appear late
A few errors recur because they are invisible on a spec sheet and only show up in service.
A controller with a generous peak current rating is a common trap when the battery or BMS cannot supply that peak. The pack becomes the limit, and the cutout arrives at the moment of hardest acceleration. Sizing the motor for cruising conditions is another: starting or climbing torque then pushes the system into current limit, with sluggish response or repeated protection events. Connector and cable voltage drop causes a third kind of surprise, because a marginal connector can look fine at idle and then drop enough voltage under load to trigger an undervoltage fault that is easily mistaken for a failing battery.
None of these argues for simply buying the largest motor or the highest-current controller. Oversizing can add cost and weight, move the operating point to a less efficient region, and still leave the battery as the bottleneck.
Validate the complete system under real conditions
Bench specifications cannot replace testing with the real load. Run the full system through its actual duty: starting from rest under load, accelerating, running at sustained load, operating at low state of charge, and, where relevant, running in the intended enclosure at realistic ambient temperature. While doing so, log battery voltage at the pack terminals and at the controller input, DC input current, any controller fault codes, BMS status, and temperatures of the motor, controller, and battery.
If the system stops during acceleration, the useful question is which limit was reached first: pack voltage sag, a BMS discharge limit, a controller current setting, or a mechanical load higher than expected. Use the symptoms below to narrow the investigation, then confirm the cause with voltage, current, temperature, and fault-code data.
| Symptom | Initial checks |
|---|---|
| System resets when the motor starts | Battery voltage drop, BMS protection, wiring and connector voltage drop |
| Sudden stop during acceleration | Peak current demand, controller current limit, BMS discharge limit |
| Stops after running for a while | Motor and controller temperature, continuous load, cooling and enclosure |
| Motor jitters or fails to start smoothly | Sensor wiring, commutation configuration, controller and motor compatibility |
| Runtime shorter than expected | Actual load and duty cycle, motor efficiency, mechanical drag, usable battery capacity |
Checking these in sequence avoids the expensive habit of replacing the motor or controller before the real constraint has been identified.
Putting the sequence together
A reliable match comes from checking the battery, motor, and controller as one system. Start with the pack’s usable voltage and discharge limits, confirm that the motor can meet the application’s torque and speed demands, and verify that the controller supports both the battery and motor. Then test under realistic loads and temperatures. If a system still cuts out, recorded voltage, current, temperature, and fault data can help identify which limit is being reached instead of relying on guesswork or replacing parts unnecessarily.
