Hybrid mode: tool + reportCanonical URL onlyAlias covered: 3 wheel holonomic drive
Holonomic Wheels Checker for 3 Wheel Holonomic Drive Decisions
Start with an executable pre-screen tool, then move directly into the evidence layer: method, boundaries, risks, and architecture trade-offs in one canonical page.
Canonical path: /learn/holonomic-wheels
Published · Last updated
Input: 3 wheel holonomic drive pre-screen
Fill the mission profile. The checker returns fit band, torque demand, and next-step action.
| Input field | Range |
|---|---|
| Total moving mass (kg) | 80 - 5000 (step 10) |
| Drive wheel diameter (mm) | 100 - 350 (step 5) |
| Wheel center radius (mm) | 220 - 900 (step 5) |
| Target speed (m/s) | 0.2 - 2.2 (step 0.05) |
| Route grade (%) | 0 - 18 (step 0.5) |
| Duty hours per day | 4 - 24 (step 1) |
| Stop-start events per minute | 0 - 45 (step 1) |
| Safety factor | 1.05 - 1.9 (step 0.05) |
Result and action guidance
Output includes interpretation, uncertainty boundary, and next action.
Empty state: run the tool to generate a fit class for your 3 wheel holonomic drive profile.
Executive summary for mixed do/know intent
Core conclusions first, then deep rationale. This section bridges tool output and procurement decision.
Conclusion 1
3 wheel holonomic drive is efficient for narrow-lane indoor missions when torque utilization stays below 70%.
Conclusion 2
Stop-start frequency and floor shock can outweigh nominal payload and should be screened before RFQ.
Conclusion 3
Borderline cases should move to short pilot instrumentation instead of immediate architecture switch.
Suitable profile
Payload envelope: 300-1800kg with predictable route grade and controlled stop-start profile.
Best for: warehouse transfer, line-side replenishment, and indoor shuttle tasks.
Not suitable profile
Harsh floor seams, extreme slope, and heavy-duty around-the-clock operations with minimal maintenance windows.
Use reinforced drive or alternative steering architecture evaluation.
Stage1b research delta and decision impact
Verified incremental facts only. Last updated 2026-04-28.
| Topic | New fact / data point | Decision impact | Source |
|---|---|---|---|
| Safety scope boundary | ISO 3691-4:2023 was published in 2023-06 and applies to driverless industrial trucks and their systems. | Use this checker only as pre-screen for industrial AGV/AMR workflows, not as substitute for final safety validation. | S1 |
| 3-wheel holonomic kinematics boundary | ROS2 kinematics docs describe omnidirectional velocity mapping as geometry-dependent; wheel radius and wheel-center geometry must be consistent. | If geometry assumptions are wrong, the reported fit can look positive while lateral drift rises in production. | S2 |
| Controller fail-safe timing | ROS2 mecanum controller docs keep explicit command-timeout handling (0.5 s default pattern) and wheel geometry parameters. | Three-wheel holonomic programs should validate timeout and stale-command fallback during pilot before procurement lock. | S3 |
| Public envelope contrast | Public omnidirectional AMR brochures (2025-2026 snapshots) show payload classes rising while max speed and slope envelopes usually shrink. | Do not extrapolate light-duty top-speed claims into mid/heavy payload classes without revalidation. | S4 |
| Interoperability standard freshness | VDA announced VDA 5050 version 3.0.0 in March 2026 and marks earlier versions as no longer recommended. | Mixed-fleet holonomic deployments should freeze interface version targets before integration starts. | S5,S6 |
Applicability boundaries and counterexamples
Each boundary includes a concrete failure mode if ignored.
| Condition | Boundary | If ignored | Source |
|---|---|---|---|
| Public road or non-industrial route | Outside ISO 3691-4 intended scope for driverless industrial trucks. | Screening result can appear valid but still fail legal and system safety requirements. | S1 |
| Potentially explosive / freezer / corrosive environments | Explicitly excluded in ISO scope notes for this profile. | Torque fit can be correct while certification path is fundamentally wrong. | S1 |
| Invalid wheel geometry parameterization | Holonomic mapping depends on wheel radius and wheel-center geometry consistency. | Controller can command unstable wheel speeds and produce lateral drift under load. | S2 |
| Stale motion command handling not tested | Controller auto-stop is timeout driven (0.5 s default pattern). | Unexpected stop behavior or drift can emerge during communication jitter. | S3 |
| Floor has oil/water/dirt contamination | Public omnidirectional platform specs typically assume clean and dry floors. | Traction and braking assumptions can collapse even when torque utilization looks safe. | S4 |
Public benchmark snapshot (not acceptance test)
Directional market reference from official product pages, checked 2026-04-28.
| Platform | Payload | Max speed | Grade / mobility limit | Environment limit | Implication | Source |
|---|---|---|---|---|---|---|
| Compact omni AMR class | 200-500 kg | 1.5-2.0 m/s | 2-5% slope (reduced speed band) | Usually clean indoor floor assumptions | Useful for high-maneuverability cells, but top speed claims are often under light payload. | S4 |
| Mid-load omni AMR class | 800-1500 kg | 1.0-1.4 m/s | 1-3% slope in rated mode | Requires stricter floor-flatness and traction control | Payload increase tends to shrink acceleration and grade margins. | S4 |
| Heavy omni platform class | 1500-3000 kg | 0.6-1.1 m/s | <=2% slope in practical operation | Pilot validation required for seam/shock floors | Architecture remains maneuverable, but duty-cycle thermal risk becomes the dominant gate. | S4 |
Methodology and assumptions
Transparent formulas and assumptions so the output can be challenged and reused.
| Assumption | Value / formula | Reason |
|---|---|---|
| Traction force model | F_total = (F_roll + F_grade) × shock × transient × safety | Separates physics baseline from duty amplification to avoid hidden multipliers. |
| 3-wheel torque split | T_wheel = F_total × radius / 3 | Three wheel modules share longitudinal force and lateral correction in kiwi/omni geometry. |
| Reference wheel torque envelope | T_ref(Nm) = 0.38 × wheel diameter(mm) | Internal pre-screen heuristic for alias intent triage, not a substitute for supplier thermal curves. |
| Thermal duty index (relative) | duty_hours × transient × shock × (power_kw / 3.2) | Flags high cycle stress before full thermal simulation is available. |
| Holonomic yaw envelope check | omega_max = sqrt(3)v / wheel_center_radius | Approximates 120-degree wheel geometry; smaller wheel-center radius increases rotational demand at the same target speed. |
Evidence status and data source map
Known vs unknown evidence is explicit to avoid false certainty.
| Source | Scope | Date | Status |
|---|---|---|---|
| [S1] ISO 3691-4:2023 safety scope for driverless industrial trucks | Applicability and exclusion boundaries for AGV/AMR deployment decisions | published 2023-06, checked 2026-04-30 | Known |
| [S2] ROS2 mobile robot kinematics documentation | Omnidirectional geometry constraints and velocity-to-wheel mapping logic | master docs, checked 2026-04-30 | Known |
| [S3] ROS2 mecanum drive controller documentation | Fail-safe timeout pattern and controller parameter hygiene for omni-style motion stacks | rolling docs, checked 2026-04-30 | Known |
| [S4] Public omnidirectional AMR brochure aggregation | Directional payload/speed/slope envelope contrasts by platform class | 2025-2026 snapshots, checked 2026-04-30 | Partially known |
| [S5][S6] VDA 5050 version update and certification signals | Interface version freshness and interoperability risk for multi-vendor fleets | version 3.0.0 and 2026-04-20 release, checked 2026-04-30 | Partially known |
- [S1] ISO 3691-4:2023 safety scope for driverless industrial trucks: Used as scope boundary; not used as direct torque equation source.
- [S2] ROS2 mobile robot kinematics documentation: Used to explain why wheel-center geometry must be modeled explicitly in 3-wheel holonomic planning.
- [S3] ROS2 mecanum drive controller documentation: Used for timeout and control-fallback evidence pattern, not for mechanical sizing claims.
- [S4] Public omnidirectional AMR brochure aggregation: Useful for directional benchmarks only; cross-vendor test methods are not harmonized.
- [S5][S6] VDA 5050 version update and certification signals: Version direction is public, but project-level compatibility matrix still needs integrator confirmation.
Architecture comparison and trade-offs
Compare alternatives before locking drivetrain architecture.
| Architecture | Control complexity | CAPEX | Floor tolerance | Best fit | Main risk |
|---|---|---|---|---|---|
| 3-wheel holonomic drive (omni/kiwi) | Medium to high | $$$ | Low to medium | Tight cells that need lateral correction and rotation in place | Higher slip sensitivity and controller tuning burden |
| 4-wheel skid differential | Medium | $$$ | High load, medium precision | Heavy payload with limited precision requirement | Tire wear and floor marking increase in tight turns |
| Steering axle + drive axle | High | $$$$ | High | Long straight runs and higher travel speed | Packaging and maintenance complexity rises |
| 4-wheel mecanum layout | High | $$$$ | Low to medium | High maneuverability with broader payload range | Efficiency and debris sensitivity penalties |
Risk register and mitigation
Covers misuse risk, cost risk, and scenario mismatch risk.
| Risk | Trigger | Impact |
|---|---|---|
| Traction collapse during dusty shift | High stop-start frequency + rough floor | High |
| Torque saturation and motor overheating | Torque utilization > 95% with long duty hours | High |
| Lateral drift from asymmetric wheel friction | CG offset + contaminated floor + mismatched wheel wear | Medium |
| Procurement mismatch from nominal-only comparison | Vendor selection based only on diameter and peak torque | Medium |
- Mitigation: Reduce command acceleration, increase wheel diameter band, and add traction monitoring.
- Mitigation: Switch gear ratio or larger wheel module, then verify continuous torque at temperature.
- Mitigation: Add periodic calibration, per-wheel current monitoring, and lateral-error alarm thresholds.
- Mitigation: Demand duty-specific load curve, bearing life data, and thermal report in RFQ.
Scenario cases with assumptions and outcomes
Scenario outcomes are generated with the same tool model so decisions remain consistent.
Case A: compact transfer AMR
900kg, coated concrete, moderate duty
Fit for 3-wheel holonomic pre-screenConfidence High
Torque utilization 32.7% · Thermal index 5.1
Move to RFQ with route map, wheel-center load sheet, and requested torque duty cycle.
Case B: high-cycle sorter cell
1200kg, epoxy floor, high stop-start
Fit for 3-wheel holonomic pre-screenConfidence Medium
Torque utilization 44.3% · Thermal index 11.1
Move to RFQ with route map, wheel-center load sheet, and requested torque duty cycle.
Case C: mixed-floor tug task
1800kg, rough concrete, medium speed
Out of envelope: redesign drive moduleConfidence Medium
Torque utilization 146.4% · Thermal index 27.1
Switch to reinforced module or architecture alternative, then rerun selection with revised assumptions.
Case D: steep route launch
1500kg, 13% grade, long shifts
Out of envelope: redesign drive moduleConfidence Low
Torque utilization 172.0% · Thermal index 32.3
Switch to reinforced module or architecture alternative, then rerun selection with revised assumptions.
FAQ by decision intent
Questions are grouped by route scope, reliability, and procurement actions.
Alias intent and route scope
Calculation reliability
Decision and procurement actions
Source registry for core conclusions
Human-readable references for S1-S6. Last updated 2026-04-28.
| Tag | Source | Publisher | Version / date | Checked |
|---|---|---|---|---|
| S1 | ISO 3691-4:2023 Industrial trucks - Safety requirements and verification - Part 4 | ISO | Published 2023-06 | Checked 2026-04-30 |
| S2 | ROS2 mobile robot kinematics (omnidirectional mapping) | ros2_control | Master docs (checked 2026-04-30) | Checked 2026-04-30 |
| S3 | ROS2 mecanum drive controller user documentation | ros2_control | Rolling docs (checked 2026-04-30) | Checked 2026-04-30 |
| S4 | Public omnidirectional AMR product brochure aggregation | Multi-vendor (industry brochures) | 2025-2026 public snapshots | Checked 2026-04-30 |
| S5 | VDA 5050 interface overview and version status | VDA | Version 3.0.0 published March 2026 | Checked 2026-04-30 |
| S6 | VDA 5050 certification press release | OTTO by Rockwell Automation | Published 2026-04-20 | Checked 2026-04-30 |
Open evidence gaps
When evidence is insufficient, conclusion is intentionally marked as pending.
| Data still needed | Status | Impact | Minimum action |
|---|---|---|---|
| Vehicle-level thermal rise and regeneration profile by duty cycle | No reliable public dataset | Public specs do not provide route-specific heat accumulation risk for 3-wheel holonomic layouts. | Run a 2-4 week instrumented pilot and require temperature/current logs before release. |
| Supplier continuous torque curve at operating temperature | Pending confirmation | Brochure peak torque does not show sustained omni-vector duty capability for long shifts. | Require torque-vs-speed-vs-temperature curve in RFQ acceptance package. |
| Wheel-floor friction map by contamination state | Pending confirmation | Friction uncertainty can invalidate lateral-control assumptions even when longitudinal torque looks safe. | Add controlled contamination test cases to pilot protocol before acceptance. |
Final action path
If your output is fit, proceed to RFQ. If borderline or out-of-envelope, move to pilot or custom engineering without route split.
This page intentionally keeps both immediate tool intent and deep report intent under one canonical URL to avoid duplicate intent pages.
Related engineering resources
Continue with drivetrain architecture checks, wheel-product context, and direct RFQ actions.
