Does this page answer 3 wheel holonomic drive questions?

Yes. It explains the three-wheel layout scope, but the interactive calculator models an ideal equal-share four-wheel layout. Do not use its load or torque results to size a three-wheel chassis; request a layout-specific engineering review.

Does "4 wheel holonomic drive" always mean a valid omnidirectional drivetrain?

Not always. Wheel orientation, roller type, and control mapping still decide whether true omnidirectional behavior is achieved.

Why is there no separate route for 4 wheel holonomic drive?

The keyword is treated as an alias merge into the canonical route /learn/holonomic-wheels to avoid duplicate intent pages.

Is this checker enough for final vehicle release approval?

No. It is an engineering pre-screening layer. Final release still requires supplier evidence and vehicle-level validation.

What is the first action when the output exceeds the screening boundary?

Check mission inputs first, then compare each wheel load and the supplier’s continuous torque and thermal data before deciding whether to redesign.

How should teams use this result in RFQ workflow?

Attach tool output, route map, floor-condition notes, and duty-cycle profile so suppliers can return comparable test evidence.

Can this page be used as a safety compliance sign-off?

No. Safety compliance interpretation must remain with your designated compliance owner and applicable standards process.

Hybrid mode: tool + reportCanonical URL onlyAlias covered: 4 wheel holonomic drive3-wheel layout scope

Holonomic Wheels: 4-Wheel Drive Pre-Screen

Looking for a 3 wheel holonomic drive? This page explains its sizing boundary; the tool below screens four-wheel layouts only. Estimate four-wheel load and torque needs from your route profile, then verify the result against supplier data.

Run 4-Wheel Pre-Screen Read Method & Evidence

Canonical path: /learn/holonomic-wheels

Published 2026-04-30 · Last updated 2026-10-01

Input: 4 wheel holonomic drive pre-screen

Fill the mission profile. The checker returns an internal screening band, proxy torque estimate, and next-step action.

Total moving mass (kg)

Drive wheel diameter (mm)

Wheel center radius (mm)

Captured for geometry screening; this checker does not calculate a maximum yaw rate without a wheel-speed limit.

Target speed (m/s)

Route grade (%)

Duty hours per day

Stop-start events per minute

Safety factor

Floor condition

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 screening band for your 4 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

Holonomic motion depends on wheel geometry and controller mapping; confirm the exact layout before inferring lateral motion capability.

Evidence: S2, S3, S4 (checked 2026-05-13)

Conclusion 2

Public product specifications use different load, speed, grade, and floor conditions; compare the mission against the exact model limits.

Evidence: S11, S12, S13 (checked 2026-05-13)

Conclusion 3

Inference from the published model pages: they do not establish duty-cycle thermal margin, so request continuous ratings and validate representative shifts before procurement.

Evidence: S11, S12, S13 (checked 2026-05-13)

Suitable profile

Payload and grade limits depend on the exact chassis, wheel, center of gravity, and duty profile; use model-level supplier data.

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.

3 wheel holonomic drive: use a three-wheel model

Three-wheel omni layouts can provide planar motion when the wheel directions and controller mapping support it. ROS 2 Control describes omnidirectional kinematics with wheel count, spacing, wheel radius, and orientation as explicit inputs. This page’s calculator is for an ideal equal-share four-wheel layout; its load and torque outputs must not be applied to a three-wheel chassis. See the ROS 2 Control kinematics reference (S14).

Decision input	Three-wheel layout	This checker
Geometry	A model needs each wheel’s mounting angle and center radius; verify wheel type and roller direction.	Assumes four drive wheels and one wheel-center radius.
Load and torque	Check individual wheel loads, center-of-gravity offset, and each motor’s continuous torque.	Uses an ideal one-quarter load/force split and an internal torque proxy; not component ratings.
Next step	Validate the three-wheel kinematic model and loaded pilot data for the actual chassis.	Use the checker only for four-wheel screening, then request supplier and vehicle-level evidence.

Request a three-wheel layout review

Stage1b research delta and decision impact

Stage1b evidence snapshot checked 2026-05-13; the added three-wheel reference is dated in the source registry.

Topic	New fact / data point	Decision impact	Source
Safety scope boundary (official publication date)	ISO 3691-4:2023 (Edition 2) was published in 2023-06. Its public abstract scopes driverless industrial trucks (including AGV/AMR examples), while mechanically guided or remote-only variants are out of scope in this part.	Treat this tool as industrial pre-screen only. If project scope extends beyond ISO abstract boundaries, escalate to a dedicated safety standards review.	S1
US terminology and acceptance baseline	ANSI/ITSDF B56.5-2024 was published on 2024-01-26; OSHA federal register text still cites B56.5-2019 terminology for AGV/AGVS definitions.	For US deployments, lock which B56.5 revision procurement and EHS acceptance will use, then avoid mixed-version wording in RFQ and FAT/SAT documents.	S8,S9
4-wheel holonomic kinematics boundary	ROS2 kinematics documentation for omnidirectional robots explicitly couples wheel radius (r) and robot radius (R) in wheel-speed inverse kinematics.	If wheel geometry or radius is mis-parameterized, the tool may still show acceptable torque while field tracking drift and wheel saturation increase.	S2
Three-wheel omni kinematics require a separate geometry model	ROS 2 Control documents an inverse-kinematics model parameterized by wheel count, spacing, radius, and wheel orientation for omni-wheel layouts with three or more wheels.	This page checker assumes an equal-share four-wheel layout. Do not reuse its per-wheel load or torque estimates for a three-wheel layout.	S14
Controller generation and fail-safe boundary	Humble mecanum docs expose reference timeout reset behavior (default 0.0), while latest Kilted omni-wheel controller docs expose cmd_vel timeout default 0.5s for command-loss handling.	Freeze ROS distribution + controller package version before pilot, otherwise stop behavior and acceptance test outcomes can shift between software stacks.	S3,S4
Interoperability standard freshness	VDA 5050 Version 3.0.0 was published in March 2026; VDA now marks older versions as no longer recommended and highlights further free-navigation zone work for end-2026.	Mixed-fleet projects should lock protocol version and zone behavior expectations before interface integration starts.	S5,S6,S7
Counterexample: 4-wheel does not always mean holonomic	KUKA KMP 1500P publishes 1.5 t payload and 1.8/1.5 m/s no-load/loaded speeds, but the same page states differential-drive architecture; by contrast, omni platforms (SEER/DF) publish lateral-capable models with explicit slope and floor constraints.	Do not infer omnidirectional capability from wheel count or payload class alone; verify drive topology and passability limits from model-level specs.	S10,S11,S12,S13

Standards boundary matrix (what this page can and cannot decide)

Scope boundary and applicability are explicit so pre-screen output is not misused as release approval.

Framework	Latest public state	Scope boundary	Required action	Source
ISO 3691-4:2023 (Edition 2)	Published 2023-06	Public abstract scope: driverless industrial trucks and systems. Out-of-scope examples include mechanically guided or remote-only non-predetermined-path trucks.	If your route/control mode sits outside this scope, treat this checker as exploratory only and escalate safety review.	S1
ANSI/ITSDF B56.5	2024 edition listed; OSHA text references 2019 terms	Safety terminology and acceptance language can diverge by revision across procurement and regulatory documents.	Freeze one revision baseline in RFQ, FAT, SAT, and EHS sign-off artifacts.	S8,S9
VDA 5050 interface	Version 3.0.0 (March 2026)	Defines fleet-control communication semantics, but is not itself a functional safety standard.	Lock version and zone semantics before mixed-fleet integration to avoid late protocol drift.	S5,S6,S7

Applicability boundaries and counterexamples

Each boundary includes a concrete failure mode if ignored.

Condition	Boundary	If ignored	Source
Safety scope mismatch	VDA 5050 itself is non-binding communication guidance and explicitly not a safety standard.	A project may pass interface tests but still fail safety acceptance.	S6
Ambiguous standards revision usage	B56.5 terminology appears in multiple revisions (2019 in OSHA text vs 2024 publication).	Contract and compliance teams may validate against different definitions, delaying launch.	S8,S9
Invalid wheel geometry parameterization	Omnidirectional inverse kinematics requires consistent wheel radius and robot geometry parameters.	Controller can command unstable wheel speeds and produce lateral drift under load.	S2
Stale motion command handling not tested	Controller timeout behavior is stack-dependent (Humble mecanum vs Kilted omni-wheel).	Unexpected stop distance or delayed halt can emerge during communication jitter.	S3,S4
Floor contamination and passability mismatch	Published omni specifications often include explicit floor assumptions and passability ceilings.	Trajectory tracking can degrade even when torque utilization appears acceptable.	S11,S12,S13

Public benchmark snapshot (not acceptance test)

Model-level public data points from official pages, checked 2026-05-13.

Platform	Payload	Max speed	Grade / mobility limit	Environment limit	Implication	Source
SEER SOS-1000 (omnidirectional stack)	1000 kg rated	1.0 / 1.5 m/s (full load / no load)	<5% slope; step 10 mm; gap 30 mm	Narrow aisle focus (1.8 m lateral maneuver claim)	Speed and passability degrade with load. Use load-conditioned speed, not no-load top speed, for cycle planning.	S11
SEER SBA-400EU (base omni robot)	400 kg rated	<=1.5 m/s	<=5% slope; step 5 mm; gap 30 mm	Certified profile published with ISO 3691-4 mention	Light-load omni platforms can keep higher speed bands, but slope/step ceilings remain explicit.	S12
DF Automation ZOEI-S (mecanum)	300 kg carry payload	0.76 m/s	7% max gradeability	Indoor, level/concrete, no water/oil/dirt	Even lower-payload omni models can publish strict floor constraints; contamination risk should not be inferred as tolerable.	S13
KUKA KMP 1500P (differential-drive counterexample)	1.5 t	1.8 / 1.5 m/s (no load / loaded)	No explicit public slope figure on page	Internal logistics heavy-load transfer	High payload and high speed do not imply holonomic capability; architecture class must be verified directly.	S10

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.
Ideal equal-share 4-wheel load and torque	Static load ≈ mass / 4; T_wheel ≈ F_total × wheel radius / 4	Assumes equal support and traction at all four wheels. CG offset, suspension, wheel unloading, and per-wheel limits are not modeled.
Reference torque proxy (not a component rating)	T_ref(Nm) = 0.38 × wheel diameter(mm)	Unvalidated internal comparator only. No supplier continuous-torque rating is entered, so the resulting percentage is not hardware utilization.
Relative thermal indicator (not a temperature prediction)	duty_hours × transient × shock × (power_kw / 3.2)	Internal scale for prioritizing evidence collection; thresholds are not calibrated to a motor or thermal test.
Ideal traction power estimate	P ≈ F_total × target speed	This is a mechanical traction-side estimate and excludes drivetrain, motor, and controller losses.
Yaw-rate limit	Not calculated by this checker	Requires a per-wheel speed limit and the exact wheel geometry/control mapping. Wheel-center radius alone is insufficient.
Screening bands	Internal thresholds: torque proxy 70% / 95%; relative thermal indicator 18 / 24; grade 8% / 12%	These thresholds are prompts for review, not evidence-derived pass/fail limits or release criteria.
Illustrative floor coefficients	Epoxy 0.015 / 1.00; coated concrete 0.022 / 1.08; rough concrete 0.032 / 1.18 (rolling resistance / shock)	Assumed screening inputs only. Replace them with measured route data and supplier guidance for project decisions.

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 scope summary (public abstract)	Published scope boundary for driverless industrial truck context and exclusions	published 2023-06, checked 2026-05-13	Known
[S2][S3][S4] ROS2 kinematics and controller docs	Geometry coupling and controller timeout behavior across controller generations	Humble/Kilted docs, checked 2026-05-13	Known
[S5][S6][S7] VDA 5050 official pages and specification document	Version status, protocol scope, and communication-standard boundary	v3.0.0 (March 2026), checked 2026-05-13	Known
[S8][S9] ANSI + OSHA public references	US-side terminology and revision-trace requirements	2022-2024 publications, checked 2026-05-13	Partially known
[S10][S11][S12][S13] Model-level product pages (KUKA/SEER/DF)	Concrete payload/speed/passability/floor assumptions plus architecture counterexample	checked 2026-05-13	Partially known
[S14] ROS 2 Control omnidirectional kinematics	Kinematic model inputs for omni-wheel layouts with three or more wheels	Rolling development documentation, checked 2026-09-30	Known

[S1] ISO 3691-4:2023 scope summary (public abstract): Used for high-level scope gating only; clause-level environment mapping still requires full-text access.
[S2][S3][S4] ROS2 kinematics and controller docs: Used for kinematic boundary and fail-safe configuration evidence, not for mechanical sizing.
[S5][S6][S7] VDA 5050 official pages and specification document: Used to separate interoperability protocol decisions from safety-standard decisions.
[S8][S9] ANSI + OSHA public references: Terminology linkage is public, but project-specific legal interpretation still needs compliance counsel.
[S10][S11][S12][S13] Model-level product pages (KUKA/SEER/DF): Useful for directional decision deltas only; no cross-vendor harmonized test protocol is disclosed.
[S14] ROS 2 Control omnidirectional kinematics: Used to support the configuration boundary only; it does not provide vehicle load, traction, motor torque, or thermal ratings.

Architecture comparison and trade-offs

Directional engineering considerations, not normalized vendor ratings. Validate cost, floor response, and control effort with model-specific supplier data and pilot evidence.

Architecture	Control complexity	Cost evidence	Floor tolerance	Best fit	Main risk
4-wheel holonomic drive (omni/mecanum)	Medium to high	Supplier quote required; no normalized dataset	Depends on wheel type and floor; test required	Tight cells that need lateral correction and rotation in place	Higher slip sensitivity and controller tuning burden
4-wheel skid differential	Medium	Supplier quote required; no normalized dataset	Depends on tire and floor; test required	Heavy payload with limited precision requirement	Tire wear and floor marking increase in tight turns
Steering axle + drive axle	High	Supplier quote required; no normalized dataset	Depends on tire and floor; test required	Long straight runs and higher travel speed	Packaging and maintenance complexity rises
4-wheel mecanum layout	High	Supplier quote required; no normalized dataset	Depends on roller design and floor; test required	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
Unverified continuous torque and thermal capacity	Reference torque proxy ratio is near its internal boundary or the duty cycle is long	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

Within internal screening band

Heuristic torque proxy ratio 24.6% · Relative thermal indicator 5.1

Ask suppliers for continuous torque-versus-speed data and validate wheel loads against the actual center of gravity.

Case B: high-cycle sorter cell

1200kg, epoxy floor, high stop-start

Within internal screening band

Heuristic torque proxy ratio 33.3% · Relative thermal indicator 11.1

Ask suppliers for continuous torque-versus-speed data and validate wheel loads against the actual center of gravity.

Case C: mixed-floor tug task

1800kg, rough concrete, medium speed

Above internal screening boundary

Heuristic torque proxy ratio 109.8% · Relative thermal indicator 27.1

Compare measured wheel loads and supplier continuous-duty ratings before deciding whether a redesign is needed.

Case D: steep route launch

1500kg, 13% grade, long shifts

Above internal screening boundary

Heuristic torque proxy ratio 129.0% · Relative thermal indicator 32.3

Compare measured wheel loads and supplier continuous-duty ratings before deciding whether a redesign is needed.

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-S14. Dates are recorded per source; S1-S13 were checked 2026-05-13.

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-05-13
S2	ROS2 mobile robot kinematics (omnidirectional mapping, Humble docs)	ros2_control	Humble docs (May 2026)	Checked 2026-05-13
S3	ROS2 mecanum drive controller user documentation (Humble)	ros2_control	Humble docs (May 2026)	Checked 2026-05-13
S4	ROS2 omni-wheel drive controller user documentation (Kilted)	ros2_control	Kilted docs	Checked 2026-05-13
S5	VDA 5050 interface overview and version status	VDA	Version 3.0.0 published March 2026	Checked 2026-05-13
S6	VDA 5050 Recommendation PDF	VDA	Version 3.0.0, March 2026	Checked 2026-05-13
S7	VDA5050 official GitHub repository (versioning and support notes)	VDA5050 working group	Main branch states Version 3.0.0	Checked 2026-05-13
S8	ANSI/ITSDF B56.5-2024 update note	ANSI Blog	Published 2024-01-26	Checked 2026-05-13
S9	OSHA Federal Register (references ANSI B56.5-2019 terms)	OSHA	Published 2022-02-16	Checked 2026-05-13
S10	KUKA KMP 1500P diff-drive product page	KUKA	Public product page snapshot	Checked 2026-05-13
S11	SEER SOS-1000 omnidirectional stack product page	SEER Robotics	Public product parameter page	Checked 2026-05-13
S12	SEER SBA-400EU base robot product page	SEER Robotics	Public product parameter page	Checked 2026-05-13
S13	DF Automation ZOEI-S omni-directional AMR page	DF Automation	Public product parameter page	Checked 2026-05-13
S14	ROS 2 Control: omnidirectional wheel kinematics (three or more wheels)	ROS 2 Control documentation	Rolling development documentation	Checked 2026-09-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 4-wheel holonomic layouts.	Run an instrumented pilot across representative duty cycles and require temperature/current logs before release.
Model-level continuous torque curve at operating temperature (not only peak torque)	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.
Cross-vendor, same-protocol benchmark for omni/differential comparison	No reliable public dataset	Vendor pages use different test protocols, so direct speed/slope comparisons can be misleading.	Build one internal acceptance protocol and require each shortlisted vendor to rerun against it.
Full-text clause mapping for extreme environments and special atmospheres	Pending confirmation	Public summaries do not expose all normative clauses; legal/compliance conclusions can be under-specified.	Procure the full standard text and map each project scenario to a clause-level compliance checklist.

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.

Submit Holonomic Wheels RFQ Re-run tool with updated assumptions Copy canonical URL intent path

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.

Holonomic Wheels: 4-Wheel Drive Pre-Screen

Executive summary for mixed do/know intent

3 wheel holonomic drive: use a three-wheel model

Scenario cases with assumptions and outcomes

FAQ by decision intent

Does this page answer 3 wheel holonomic drive questions?

Is this canonical page the answer for "4 wheel holonomic drive" intent?

Does "4 wheel holonomic drive" always mean a valid omnidirectional drivetrain?

Why keep tool and report on one page?

Can this page replace full vehicle simulation and certification?

What does torque utilization actually tell me?

Why does the checker not show a confidence score?

How should I set safety factor?

What if my numbers are outside the allowed input range?

When should I choose redesign instead of pilot?

What data should be attached to RFQ?

How long should a pilot run for borderline results?

Can I compare vendors with this page alone?

Final action path

Related engineering resources