An AGV drive unit is an integrated electromechanical package in which an onboard motion controller, a brushless servomotor, a planetary gearbox, and a drive wheel share a common flange and a single I/O and communications link back to the vehicle computer, replacing the older discrete amplifier + motor + reducer + wheel stack [S4].
The traction-side power chain is composed of a battery pack feeding an inverter or motor control unit, which drives a traction motor through a gearbox to a polyurethane or rubber drive wheel; navigation sensors, wireless comms, and safety scanners sit on separate buses but are typically sequenced by the same vehicle-level controller [S6][S7].
What an onboard motion controller actually does in an AGV
The onboard controller handles wheel-axis servo loops, trajectory generation, and the I/O linking drive motors, steering motors, LiDAR, and safety stops; on integrated designs it is configured through vendor tooling such as Q Programmer and exposes motion, I/O, and network commands without a separate external drive amplifier [S4].
AGV motion control historically paired a DC traction motor for forward and reverse run with a separate servomotor for steering, an architecture still cited in classic four-wheel-drive reference designs [S1]. Modern integrated drives collapse the amplifier into the wheel-hub housing, so the vehicle controller only has to issue high-level velocity, position, and brake commands over EtherCAT, CANopen, or a vendor-specific bus [S2][S5].
Trajectory planning, anti-collision, and fleet dispatch are pushed to a higher-level vehicle or fleet controller, while the onboard controller focuses on sub-millisecond current and velocity loops at the wheel; PC-based motion controllers are still common on AMRs that pair frameless torque motors with LiDAR spinners, which require their own precision rotary motion profile [S4].
Traction motor options: brushed DC, brushless DC, stepper, AC
Brushless DC motors dominate modern AGV drive units because of their high torque density, low rotor inertia, and ability to integrate directly with a planetary gearhead and drive wheel on a single flange [S2][S4]. Brush DC motors remain in use on legacy and very low-cost vehicles where the simpler commutation electronics offset brush wear [S2].
Stepper motors appear in low-speed, open-loop AGV and AMR drives where holding torque without a brake is useful, but they lose efficiency at the higher road speeds typical of warehouse tractors [S2]. AC synchronous and asynchronous induction motors are reserved for heavier AGV classes (fork trucks, container handlers) where regen braking into a 48 V to 96 V DC bus, or higher, is required and where three-phase inverter maturity is already proven in industrial drives [S2][S6].
Compact hub gear motors and integrated wheel-hub units now ship as pre-engineered traction and steering modules, with the motor stator, gearbox, wheel bearing, and encoder in one housing, which removes drivetrain alignment work and cuts moving-parts count on the vehicle chassis [S5].
Sizing the drive: load, peak torque, and braking
AGV motor sizing starts from the loaded vehicle mass shared between active drive wheels and passive casters, then converts worst-case acceleration, incline, and rolling friction into peak torque, while average running torque is set by the steady-state duty cycle [S2]. Slick narrow tires on smooth warehouse floors need far less torque than wide tires on dusty or gravel-surfaced logistics yards, so the same AGV payload can require a one- to two-frame-size motor difference depending on the operating surface [S2].
Static and dynamic braking are sized separately: a holding brake is selected for power-off parked loads, while the dynamic brake handles emergency stops and regenerative energy, and must be coordinated with the battery management system to respect cell current limits [S2]. Wheel diameter is bounded by the vehicle clearance envelope, and a smaller wheel pushes the motor toward higher rpm and a higher gearbox ratio to hit the same tractive effort [S2].
Power-source decisions are coupled to motor choice: a 24 V to 96 V battery rail with given current limits and a target operating time per charge defines the average power budget, and brushless servo drives are typically the most efficient way to convert that budget into wheel torque at variable duty cycles [S2][S4].
Onboard controller and traction motor integration points
The mechanical integration is a flange-mounted wheel hub: the traction drive is a brushless servomotor with a planetary gearbox and a drive wheel bolted directly to the gearbox output, so the wheel bearing carries both radial load and cornering forces [S3][S4]. A typical Allied Motion or Applied Motion Products integrated wheel assembly places the encoder inside the housing, giving the onboard controller closed-loop commutation without external feedback hardware [S4].
The electrical integration is a single cable harness carrying DC bus, logic power, fieldbus, and safety I/O into the wheel-hub unit, so the vehicle harness becomes a star from each wheel rather than a tree running to a centralized drive cabinet [S4][S5]. For functional safety, STO (safe torque off) and SS1 profiles are usually implemented in the drive firmware, with the onboard controller hosting the higher-level safety logic and the AGV safety scanner feeding it via a dual-channel safety bus [S5].
On the software side, motion parameters such as acceleration limits, jerk profiles, and brake engagement are programmed into the drive (for example via Q Programmer-style tooling) so the vehicle controller can treat the drive as a velocity or torque source, which simplifies fleet-level path planning [S4].
Criteria-based comparison of traction motor families
Across the four mainstream families, the decision axes that matter most for AGV specifiers are torque density, efficiency at variable load, controllability for low-speed holding, and integration cost. The table below lines them up against those axes using the qualitative picture consistent with the source material [S2][S4].
Brushless DC servo motors score high on torque density and efficiency, can hold position with closed-loop control, and integrate cleanly into a flange-mounted wheel-hub package, which is why they dominate new AGV drive units [S2][S4]. Brush DC motors are cheap and simple to drive but lose points on efficiency, brush life, and dust exposure in logistics environments [S2]. Stepper motors hold position open-loop and tolerate stall, but waste energy at speed and are usually confined to small-payload AMRs [S2]. AC induction motors offer robust regen and proven inverter stacks for heavy AGV classes, at the cost of more complex control and lower torque density at low speed [S2].
For most warehouse and light-manufacturing AGVs in the 50 kg to 2,000 kg payload range, the brushless servo + planetary gearhead + drive wheel combination is the default, with hub gear motors from suppliers such as STXI GLOBAL and integrated servo wheel drives from Applied Motion Products covering the bulk of the design space [S3][S4][S5]. Related motion components used elsewhere on the same vehicle, such as AGV robot navigation scanners and steering motors, run on their own small servo or stepper axes typically commanded from the same onboard controller.
Failure modes, environment, and standards to watch
The dominant failure modes on integrated AGV drive units are encoder contamination, gearbox backlash growth after shock loading, and tire wear on abrasive floors, all of which are visible to the onboard controller as torque ripple, following error, or wheel-speed mismatch between redundant encoders [S2][S4]. Holding-brake failure on inclines is a recurring safety incident root cause, which is why the controller-side safety chain (STO, SS1, scanner interlock) must be specified independently of the motion chain [S2][S5].
Environment sets the IP rating and gearbox lubrication: indoor warehouse units typically run IP54 to IP65 with grease-lubricated planetary gearboxes, while outdoor or cold-storage units demand IP65 or higher, low-temperature grease, and often stainless hardware on the drive wheel [S2][S5].
Standards relevant to AGV drive selection include EN ISO 3691-4 for driverless industrial trucks (safety requirements for AGVs), IEC 61800-5-2 for the functional-safety functions embedded in the drive (STO, SS1, SS2), and ISO 13849-1 for the safety-related control architecture that ties the onboard controller to the vehicle's e-stops and scanners. For traction motor control loops, IEC 61800-2 and the broader IEC 61800 family cover adjustable-speed electrical power drive systems, while EMC compliance generally falls under IEC 61800-3 for the drive and EN 12895 for the industrial truck as a whole.
Selection checklist for an onboard controller + traction motor pair
A practical selection flow starts with payload and duty cycle, fixes the battery voltage rail, and then matches a wheel diameter to the chassis envelope, which sets the motor rpm and gearbox ratio needed to hit the required tractive effort [S2]. The onboard controller is then chosen to match the drive's native bus (EtherCAT, CANopen, or vendor-specific) and to host the required safety functions (typically STO at minimum, SS1 for heavier vehicles) [S4][S5].
For plants already using industrial motion-control ecosystems, sticking with a vendor whose drives expose standard IEC 61131-3 or CiA 402 profiles reduces integration effort; for greenfield AGV fleets, the pre-engineered hub gear motor packages now on the market remove most of the mechanical sizing work [S5]. Where the AGV shares a fleet manager with other motion controller driven equipment, confirm that the drive supports the same fieldbus, safety profile, and firmware update path before locking the bill of materials.
Two trackable signals for the next planning cycle: the rollout of integrated safety functions directly inside hub gear motor firmware (reducing external safety relay count), and the convergence of AGV and AMR drive platforms onto common CiA 402 or EtherCAT profiles, which would let a single onboard controller software image run on a wider range of traction hardware. Buyers who want a broader frame of reference on adjacent plant equipment can compare traction sizing notes against the construction machinery and equipment duty-cycle logic, where peak versus average torque is sized in the same way. For facilities also evaluating end-of-line automation, the same fieldbus and safety-function discipline carries over to case packing machine sizing and selection, which is a useful cross-check on integrator capability.