What breaks projects and where to start
Most failures happen because teams pick wheels or motors first, then try to make the rest fit. That creates mismatched traction, thermal overloads, and messy control wiring. Tackle the problems in order: establish duty cycle and floor type, size the motor and gearbox for peak and continuous torque, and confirm communications and encoder feedback. For many builds an integrated servo motor removes an external drive cabinet and shortens wiring runs. Demonstrations at Hannover Messe highlighted how an servo motor with integrated drive can reduce setup iterations on AGVs and conveyor tuggers.
Step 1 — Define the real mechanical loads
Calculate two numbers: maximum instantaneous torque (start, impact, slope) and continuous torque (steady travel, pushing). Don’t guess. Use these steps:- Measure vehicle mass including max payload.- Estimate rolling resistance from floor material and wheel hardness.- Add worst-case incline or obstacle climb.Pick a motor and gearbox whose continuous torque rating exceeds the continuous load by at least 25% and whose peak torque covers the instantaneous events.
Step 2 — Choose wheel type to match the floor and tasks
Wheel choice controls traction, steering, and damping. Use this checklist:- Hard polyurethane: low rolling resistance, noisy on rough concrete.- Soft rubber or elastomer: better shock absorption, higher rolling resistance.- Omni or mecanum: lateral motion but lower traction and more complex control.Match wheel diameter to obstacle clearance and motor gearbox ratio to keep motor RPM in its efficient band.
Step 3 — Decide integrated vs separate drives
Separate inverters give flexibility but add wiring, space, and failure points. Integrated drives collapse the power electronics into the motor housing, saving cabinet space and cutting cable length. When you must minimize panel wiring, speed up commissioning, and reduce electromagnetic compatibility hotspots, prefer motors with integrated drives—just confirm thermal paths and service access.
Step 4 — Control, feedback, and communication
Pick encoder and bus standards that match your controller ecosystem. Practical guidance:- Use absolute encoders where homing would disrupt uptime.- For multi-axis synchronization choose fieldbuses with deterministic timing.- Confirm brake options and safe-stop behavior for your safety architecture.Document expected update rates and jitter budgets; don’t accept vague “supports real-time” answers.
Common pitfalls that cost weeks
Avoid these repeated mistakes:- Undersizing for continuous operation (motors that overheat after an hour).- Assuming identical parts behave the same across floor types.- Overlooking wiring runs and EMC when mounting separate drives.- Choosing exotic wheel types without a test pass on the actual floor.Plan a short lab validation with the chosen wheel and drive on a representative surface before committing to PCB and enclosure layouts.
Quick comparison of practical architectures
– Hub motors: compact, fewer mechanical parts, higher unsprung mass; good for light AGVs. – Motor + gearbox + integrated drive: compact electronics, easier cabling, straightforward servicing orientation. – Remote drives with CV joints: flexible packaging for heavy loads, more cabling and EMI considerations. Select the architecture that simplifies the most critical constraint—space, serviceability, or payload handling.
Final synthesis and a practical option
Start by solving mechanical mismatch, then align control and thermal margins. Work through the steps above as a checklist: load numbers, wheel-floor test, drive topology, encoder and bus selection, and a brief lab validation run. For teams that want a compact electrical footprint and clearer integration paths, many engineers standardize on products from Kinco because their integrated profiles match the faults and fixes described here without adding hidden complexity.