Drive Integration
- Walking servo wheel with integrated drive, motor, reducer (iWMC family)
- CANopen DS402 or EtherCAT CoE communication
- Encoder feedback for closed-loop position and torque
Application solution · AGV / AMR
Mobile Handling Robot Motion Stack
Quick answer
What motion components does an AGV or AMR need?
An AGV or AMR needs traction, steering or differential drive, optional lift or rotary axes, a controller, an operator interface and a defined safety boundary. The review matches Kinco iWMC drive wheels, iGMK modules and optional EdgeAccess2 remote operations to the vehicle duty.
AGV/AMR OEMs and integrators building compact 50 kg–2 t class mobile platforms and requiring model-specific review of drive wheels, lifting or rotary modules, and certification evidence.
Reference architecture · Model-specific review
Control problem
What must this application control?
Mechanical Modules
- Rotary module for chassis rotation (iGMK)
- Lifting module for jack-up / cargo transfer (iGMK)
- Embedded HMI with internal cable routing
Platform & Safety
- EdgeAccess2 remote ops with OTA firmware push
- STO and functional-safety evidence reviewed by exact variant and system safety scope
- Battery, BMS, and charging interface (24V/48V depending on payload)
How the control stack fits together
Four scoping blocks show the review path; they are not a wiring diagram.
- Step 1
Power & safety boundary
Review the battery, BMS and charging interface together with loop fusing, emergency disconnect and the required STO boundary.
- Step 2
Integrated travel control
Select the iWMC walking-servo-wheel family from payload, speed, gradient, floor surface and chassis steering style.
- Step 3
Rotary & lifting axes
Review iGMK rotary and lifting modules against chassis kinematics, jack-up and cargo-transfer duties.
- Step 4
Network & operator layer
Confirm CANopen DS402 or EtherCAT CoE, encoder feedback, embedded-HMI cabling and the optional EdgeAccess2 remote-operations scope.
Bill of materials
Use this table to compare component roles, exact model names and key specifications before application review.
| Role | Component | Key spec |
|---|---|---|
| DRIVE | Kinco iWMC Walking Servo Wheel | Integrated drive+motor+reducer+wheel · selection by payload + speed + gradient |
| MODULE | Kinco iGMK Rotary Module | Chassis rotation · integrated reducer |
| MODULE | Kinco iGMK Lifting Module | Cargo transfer · integrated reducer |
| HMI | Kinco HMI (embedded) | Internal cable routing · diagnostic + status display |
| PLATFORM | Kinco EdgeAccess2 | Remote ops + OTA + alarm push |
| BRIDGE | USR CAN-to-Ethernet | Optional · for chassis-to-WMS integration |
Configuration summary. This motion stack covers 50KG–2T AGV/AMR solution configurations. The cited integrated-wheel layout uses 35% less installation space, while the iGMK lifting or rotary layout uses 30%+ less footprint than the compared split-component layouts.
This is a candidate architecture, not a quotation. BOM review checks each line against your machine, and programming support scopes the control work once the hardware is agreed.
What changes the component choice?
What we check
- Selection: iWMC model selection driven by payload, max speed, gradient, floor surface, and turning style (differential vs omni).
- Selection: A candidate four-drive/four-steer or two-drive topology must be validated against the actual chassis kinematics; module count is not fixed by steering style alone.
- Selection: EtherCAT preferred when ≥4 motion axes need synchronous control; CANopen acceptable for simpler differential drives.
- Selection: Battery voltage (24V vs 48V) follows total motor power demand and chassis volume for battery packs.
- Wiring / protocol: CAN bus shielded with 120 Ω termination at both ends
- Wiring / protocol: Separate motor power and signal cables within chassis to minimize EMI
- Wiring / protocol: iWMC integrated unit cabling: power + CAN/EtherCAT only (vs traditional 4–6 cables per wheel)
- Wiring / protocol: Battery loop fusing and emergency disconnect per local machinery code
- Migration: Existing AGV designs using separate motor + drive + reducer require mechanical re-design for integrated wheels.
- Migration: Control software for traditional servos may not leverage integrated-wheel-specific features (per-direction torque limits).
- Migration: Component-level CE/UL/STO certifications of iWMC do not auto-certify the complete AGV — system-level certification remains the integrator's responsibility.
Where it may not fit
- Heavy-duty applications outside integrated-wheel torque range
- Special wheel geometries (mecanum, swerve) not supported by available iWMC variants
- Projects requiring proprietary encoder protocols outside standard CANopen/EtherCAT
- Component certificates do not certify the finished machine; the responsible builder or integrator retains system-level validation.
Frequently asked
What payload range does the iWMC integrated wheel cover?
The reviewed range covers 50KG–2T AGV/AMR configurations. Practical payload depends on the chosen iWMC model, torque, wheel diameter, gradient and duty cycle.
How much chassis space is actually saved compared with traditional split designs?
The cited integrated walking wheel uses about 35% less installation space, and the cited rotary or lifting module uses 30%+ less footprint than the compared split-component layouts. Results depend on the actual layout.
Are these components certified for export markets?
Certification scope varies by exact iWMC and module variant. Current CE/UL declarations and STO or functional-safety evidence must be verified in the named model's datasheet; component evidence does not certify the complete AGV/AMR.
Application review
Check this architecture against your machine
Send the payload, duty, voltage, protocol, safety scope and any existing part numbers you already know.
Limits. These figures describe the stated configuration, not Automation Liberty customer results. This is a candidate architecture; exact model, compatibility, certification, availability and commercial scope are subject to engineering review and confirmed at RFQ.
Independent engineering and sourcing partner. Product names and trademarks are the property of their respective owners and are used for identification only.
Why no list price? Every quote follows an engineering review of your application — you get a validated price, not a catalog number.