Electric Drive System Design Guide from Battery to Wheels

I design an electric drive system by treating the battery, inverter or motor controller, motor, reduction gear, differential, wheels, and control software as one connected system. The correct design starts with vehicle requirements such as mass, target speed, gradeability, acceleration, range, duty cycle, and operating environment. I then convert those requirements into wheel torque and power, select a motor and motor controller, size the battery and protection hardware, and validate thermal, electrical, mechanical, and software performance. This battery-to-wheels approach helps buyers avoid selecting components independently that later fail to work together.

Read more

For a practical design, I recommend defining the duty cycle before requesting quotations. A motor may deliver high peak power for a short acceleration event but require a lower continuous rating for sustained operation. I also distinguish nominal voltage from maximum pack voltage, peak current from continuous current, and laboratory performance from the actual vehicle operating profile.

Key Takeaways

• Start with vehicle load, speed, slope, acceleration, range, and duty-cycle requirements.
• Calculate wheel torque and power before choosing the motor controller or motor.
• Match battery voltage, motor-controller current, motor phase requirements, cooling, and communication protocols.
• Use continuous ratings for thermal design and peak ratings only for defined operating periods.
• Ask QEXPAND for a system-level review when component compatibility, customization, or production support is required.

Who This Electric Drive System Guide Is For

This guide is intended for OEMs, vehicle integrators, engineering teams, and purchasing managers developing electric vehicles or industrial mobile equipment. Typical applications include electric utility vehicles, low-speed transporters, agricultural machines, warehouse vehicles, small commercial vehicles, and other battery-powered platforms. It is also useful when a buyer has selected a motor but still needs to confirm the controller, battery, gearbox, and cooling architecture.

I use a system-level method because the motor controller is not an isolated purchasing item. It manages battery energy, regulates motor current, responds to accelerator and brake commands, and protects the drivetrain under abnormal conditions. A controller that appears suitable by voltage alone may still be unsuitable because of current limits, sensor type, communication protocol, cooling, enclosure, or software requirements.

Basic Battery-to-Wheels Architecture

Energy path

The electrical path normally begins with the battery pack and its battery management system. Energy passes through protection and switching hardware, such as fuses, contactors, pre-charge components, and service disconnects, before reaching the motor controller. The controller converts battery-side DC power into controlled motor phase currents, while the motor converts electrical energy into mechanical torque.

Mechanical power then passes through a coupling, reduction gearbox, axle, or differential before reaching the wheels. Regenerative braking reverses part of this path: the motor operates as a generator, and the controller directs acceptable energy back toward the battery. The battery, BMS, controller, and braking strategy must therefore be designed together rather than treated as separate subsystems.

Core design equations

I begin with the force required at the tire contact patch. A simplified calculation includes rolling resistance, aerodynamic drag, road grade, and acceleration force. Wheel torque can then be estimated from force multiplied by effective tire radius, while motor torque depends on the selected gear ratio and drivetrain efficiency.

For example, a 1,500 kg vehicle on a 10% grade requires approximately 1,472 newtons of grade force before rolling resistance and acceleration are added, using gravitational acceleration of 9.81 m/s². If the effective tire radius is 0.30 m, the grade-only wheel torque is approximately 442 N·m. This is an engineering example, not a performance guarantee; real sizing must include tire, road, temperature, gear, and duty-cycle conditions.

Electrical input power also needs a margin for losses. If the required mechanical output is 30 kW and the combined drivetrain efficiency is assumed to be 90% for preliminary sizing, the battery-side requirement is about 33.3 kW. At a 400 V operating point, that corresponds to approximately 83 A before considering transient demand, voltage variation, auxiliary loads, and control limits.

Types and Specification Options

Motor and controller combinations

Permanent-magnet synchronous motors are often considered where high power density and efficient speed control are important. Induction motors can be attractive where magnet-free construction or a different operating strategy is preferred. Brushless DC systems may suit compact or lower-power applications, but the correct controller must match the motor’s commutation and feedback requirements.

Motor-controller selection depends on more than nominal battery voltage. I review maximum DC voltage, continuous and peak battery current, phase-current capability, motor speed range, resolver or Hall sensor compatibility, encoder requirements, regenerative braking control, cooling method, and communication interfaces such as CAN. Functional safety, diagnostic behavior, and fault handling should also be considered according to the vehicle’s risk assessment.

Battery and mechanical options

The battery pack should be specified by usable energy, voltage range, allowable charge and discharge current, thermal limits, packaging, and expected duty cycle. A higher nominal voltage can reduce current for the same power, but it may introduce different insulation, service, protection, and regulatory requirements. I do not recommend selecting pack capacity from range alone; energy consumption, reserve policy, payload, temperature, and route profile must be included.

On the mechanical side, the gear ratio determines the compromise between wheel torque and maximum vehicle speed. A large reduction ratio can support stronger launch performance, while a smaller ratio may favor high-speed operation. The final decision should be based on the motor efficiency map and the actual operating points, not only on the motor’s maximum speed.

You will get efficient and thoughtful service from QEXPAND.

Step-by-Step Design and Selection Framework

1. Define the vehicle duty cycle

I first collect vehicle mass, payload, tire size, maximum speed, acceleration target, maximum grade, operating hours, ambient temperature, and expected stop-start behavior. For work vehicles, I also ask whether the machine will tow, climb repeatedly, operate on loose ground, or remain stationary while auxiliary equipment consumes power. These details determine continuous thermal demand and peak torque events.

2. Convert requirements into wheel demand

Next, I calculate wheel force, wheel torque, and wheel power across the important operating points. I include drivetrain efficiency, tire radius, rolling resistance, grade, and acceleration. The result is a torque-speed envelope that provides a more useful basis for selecting the motor and controller than a single peak-power number.

3. Match the motor controller

I then compare the torque-speed envelope with controller voltage, current, speed, feedback, and communication limits. Continuous current should support sustained operation at the most demanding thermal point, while peak current should be tied to a defined duration and cooling condition. I also confirm whether the controller supports the requested accelerator, brake, reverse, limp-home, regenerative braking, and diagnostic functions.

4. Size battery, protection, and cooling

The battery must support both energy demand and instantaneous power demand. I check voltage sag, peak discharge current, charge acceptance during regeneration, BMS limits, contactor ratings, pre-charge behavior, and fuse coordination. Cooling design should consider the battery, controller, and motor together because heat generated in one subsystem can affect the available performance of another.

5. Validate integration and production needs

Before production, I recommend checking connector definitions, wiring length, grounding, electromagnetic compatibility, mounting strength, enclosure protection, service access, and software calibration. Prototype tests should represent the intended duty cycle rather than only a short unloaded run. For production planning, I also confirm documentation, traceability, sample approval, change control, and after-sales technical support.

Key Buyer Decision Points

Common Design Mistakes and Optimization Advice

A frequent mistake is sizing from peak motor power while ignoring continuous load. This can produce a system that accelerates well but overheats during climbing, towing, or repeated operation. I avoid this problem by mapping the full duty cycle and checking thermal limits at the actual motor speed and torque points.

Another mistake is treating regeneration as free recovered energy. Regenerative braking depends on battery state of charge, temperature, BMS charge-current limits, motor speed, tire traction, and braking control. I therefore design friction braking and regenerative braking as coordinated functions, with safe fallback behavior when regeneration is unavailable.

Buyers can also reduce project risk by freezing interface requirements early. A clear specification should include voltage range, current definitions, sensor type, CAN requirements, cooling, ingress expectations, mounting, test conditions, and acceptance criteria. When requirements remain incomplete, I recommend using a controlled engineering assumption list instead of presenting uncertain values as final specifications.

How QEXPAND Can Support Your Project

At QEXPAND, I approach the motor controller as part of the complete electric drive system from battery to wheels. Our support can begin with requirement clarification and preliminary matching, then continue through controller selection, motor-controller compatibility review, interface definition, sample coordination, and production communication. The exact scope depends on the application, available drawings, requested specifications, and customization requirements.

For a meaningful quotation, I recommend preparing the battery voltage range, motor type and power, peak and continuous torque needs, maximum speed, duty cycle, communication protocol, cooling method, target quantity, and installation environment. If some information is not available, I can help identify the missing inputs and separate confirmed requirements from preliminary assumptions. This approach gives purchasing and engineering teams a clearer basis for comparison.

Conclusion: A Practical Next Step

The answer to how to design an electric drive system from battery to wheels is to size and validate the complete energy, control, mechanical, and thermal chain together. Start with the vehicle duty cycle, calculate wheel demand, match the motor and motor controller, verify battery and protection limits, and then validate cooling, software, safety, and production interfaces. A nominal voltage or peak power label alone is not enough to confirm system suitability.

My recommended next step is to create a one-page system requirement sheet and send it to QEXPAND for a preliminary technical review. Include the vehicle mass, target speed, grade, tire radius, battery range, motor data, duty cycle, and quantity expectation. With those inputs, we can discuss a practical motor-controller solution and identify the technical decisions that should be resolved before sampling or volume purchasing.

Are you interested in learning more about Electric Drive System Design Guide from Battery to Wheels? Contact us today to secure an expert consultation!