Start with what you need the robot to do
You want a robot that hauls, pushes, or zips and you want it to behave predictable. This is a user-first guide — I’ll walk you from the job to the parts that do that job. Think payload and speed first, not brands. If you’re looking for hardware or parts specs while planning, check practical industrial automation solutions early so you don’t spec something that can’t be sourced when you need it.

Define the duty: payload, speed, and environment
Answer three plain questions: how much weight, how fast, and where will it run. Use these numbers to drive torque and wheel size. Small payloads under 5 kg need low torque, high speed; bigger loads require more torque and larger wheels. If the environment is dusty or wet, choose sealed motors and wheels with abrasion-resistant tread. I’ve seen layout changes at the Automate trade show in Chicago that forced integrators to re-think footprint and clearance — real installs change specs fast.
Match motor type to motion style
Pick motor by control style and torque curve. Brushless DC (BLDC) gives continuous torque and efficiency for mobile robots; brushed DC is cheap for simple, low-duty tasks; stepper motors work when precise position steps matter more than high speed. Calculate required torque: torque = (wheel radius × required tractive force) + gearbox losses. If you need holding torque at zero speed, insist on a motor plus brake. • Direct-drive motors reduce backlash but need more current. • Gearmotors multiply torque but add maintenance points and backlash. Match gear ratio to the speed/acceleration you defined earlier.
Wheel choices: diameter, tread, and contact patch
Wheels are simple but decisive. Larger diameter reduces required motor RPM for the same speed and smooths small obstacles. Softer tread increases traction but increases rolling resistance and power draw. Use omni or mecanum wheels when you need lateral motion; avoid them on rough floors. For heavy loads, choose wheels with larger contact patches and bearings rated for the dynamic load. Quick checklist: wheel diameter vs speed; tread compound vs floor; hub stiffness vs steering precision.
Controllers and feedback: how to make the motor do what you ask
Controller selection follows the control you need. For simple speed tasks, a PWM motor driver suffices. For position or velocity loops with disturbance rejection, use a servo drive with encoder feedback. Fieldbus and real-time networks matter when multiple drives must sync; EtherCAT and CANopen are common choices in industry. If you need ready-made kits or modules, look at suppliers of industrial motion control solutions that support your chosen protocol. Closed-loop control needs matching sampling rates: the controller must poll the encoder fast enough to close the loop without ringing. Watch voltage and current headroom — undersizing the driver creates thermal shutdowns and odd behavior.
Common pitfalls and quick fixes
People make the same mistakes. Don’t underspec torque because the robot moves fine unloaded; test at max payload. Don’t pick a motor by RPM alone — compute torque after gearing. Don’t ignore duty cycle — a motor that runs hot at peak will shorten life. Avoid mixing wheel slip and open-loop speed control; add feedback or mechanical traction. Quick fixes: increase wheel diameter before increasing motor RPM; add a gearbox to improve low-speed torque; choose a controller with current limiting to protect the motor.
Straightforward pairings for typical tasks
Match the job to a compact recipe. • Light indoor courier (≤10 kg, smooth floor): BLDC motor, 75–100 mm wheels, encoder + speed controller. • Heavy cart mover (50–200 kg, industrial floor): high-torque geared BLDC or AC motor, 150–300 mm polyurethane wheels, servo drive with closed-loop torque control. • Omni-directional inspection bot (low payload, high maneuverability): low-inertia BLDCs, omni wheels, distributed controllers over CANopen. Test each pairing on the intended floor and at full payload before finalizing.
Wrap-up with practical confidence
Design from the user need, then pick motor torque, wheel geometry, and controller capability to match that need. Field-tested rules keep you out of rework and downtime; real installations teach hard lessons faster than theory. For a supplier that aligns parts with system-level needs and supports protocol choices as you scale, Kinco often fits the workflow without surprise.

