What is AGV navigation?

AGV navigation is the method an automated guided vehicle uses to determine its position and follow a path. Common methods include magnetic tape, QR/fiducial markers, LiDAR SLAM, vision SLAM, and reflective beacons. Each trades off accuracy, flexibility, cost, and reconfiguration effort differently.

What is the difference between AGV navigation and AMR navigation?

AGV navigation typically follows a fixed physical or virtual path and stops when blocked, waiting for clearance. AMR navigation uses SLAM to localize against a map and dynamically replans around obstacles. The navigation selector on this page covers both, because the alias "agv amr navigation" refers to the same technology cluster.

Does this page explicitly answer "agv amr navigation" intent?

Yes. The canonical URL /learn/agv-navigation treats "agv amr navigation" as an alias of "agv navigation" and answers both on one hybrid page without creating a duplicate route.

Why is there no separate page for "agv amr navigation"?

"agv amr navigation" and "agv navigation" belong to the same intent cluster. A separate route would create near-duplicate content risk, so the alias is merged into this single canonical page.

What is VDA 5050 and does my AMR need it?

VDA 5050 is an interface for exchanging job and status data between mobile robots and fleet control. Version 3.0.0 (March 2026) adds a zone concept for robots with higher autonomy. It does not replace onboard navigation or the safety case. Consider it when mixed-vendor fleet control is a requirement, and confirm that the vehicle and fleet-control products support the same version and features.

How do I choose between magnetic tape and SLAM navigation?

Use magnetic tape when routes are stable, throughput is high, and budget is tight. Use SLAM (LiDAR or vision) when layouts change often and the fleet needs to reroute without physical infrastructure changes. The selector above scores both against your exact constraints.

Which navigation method has the best repeatability?

The selector shows indicative planning bands of ±3–8 mm for reflective beacons, ±5–12 mm for QR markers, ±8–15 mm for magnetic tape, and ±15–40 mm for SLAM methods. These are illustrative screening inputs, not a verified cross-vendor benchmark or performance estimate. Confirm the exact vehicle specification and test it in your environment.

Is QR marker navigation better than magnetic tape?

The indicative repeatability bands overlap, so they do not prove that QR is universally more precise than tape. QR markers can provide discrete relocalization points and a grid-based route; tape offers continuous line guidance at low relative hardware cost. Compare the exact vehicle specifications and maintenance needs for your floor.

When should I avoid SLAM navigation?

Avoid pure SLAM in long, feature-poor corridors (e.g. cold storage aisles with uniform walls), highly symmetric environments, or when per-vehicle sensor cost must stay low for a large fleet. In those cases, hybridise SLAM with fiducial markers or beacons.

What is the cheapest AGV navigation method?

Magnetic tape is often a low-cost fit for stable routes because the vehicle guidance hardware and floor infrastructure are relatively simple. Reconfiguration and maintenance can change lifecycle cost, so compare site-specific supplier quotations.

How does navigation cost scale with fleet size?

There is no universal fleet-size crossover. Compare vehicle sensors, shared infrastructure, integration, maintenance, and expected layout changes over the planned operating life using site-specific supplier quotes. Hybridising methods may help when some routes are stable and others change often.

How long does it take to deploy each navigation method?

There is no reliable duration that applies to every site. Ask suppliers to scope survey, infrastructure installation or mapping, integration, commissioning, and acceptance testing against your route layout and operating constraints.

Can I mix navigation methods in one fleet?

Yes. Hybrid fleets are common: SLAM for flexible zones and markers/beacons for fixed high-throughput loops. Ensure your fleet manager supports multi-method vehicles and that handoff zones are tested for localization continuity.

Are the repeatability ranges on this page guaranteed?

No. They are illustrative planning inputs, not verified field repeatability or absolute positioning accuracy. Confirm the exact metric and specification with the vehicle supplier, then validate it in an on-site pilot before procurement lock.

What happens if my aisles are feature-poor?

SLAM localization degrades in long uniform corridors. Mitigate by adding fiducial markers as localization anchors, installing reflective beacons, or introducing geometric features (racking end-caps) to enrich the scan.

How often should I remap a SLAM environment?

Review the map after documented layout changes, then version-control it and run the agreed localization and route acceptance checks before returning vehicles to service. Set any recurring review interval from site change frequency and validation results.

Is the navigation selector a final engineering approval?

No. It is a deterministic pre-screen for architecture and sourcing decisions. Final selection still requires supplier evidence, an on-site pilot, and internal safety validation per ISO 3691-4 or your local standard.

What safety standard governs AGV/AMR navigation?

ISO 3691-4:2023 is the published Type-C safety standard for driverless industrial trucks and their systems; ISO also lists a technically revised third edition in draft. Required protective measures and performance levels depend on the truck, operating conditions, applicable edition, and risk assessment. ISO 13849-1 does not prescribe a PLr for every application, and IEC 61496-3 applies to a specific class of electro-sensitive protective equipment rather than requiring that device for every vehicle. Confirm current standards and the complete safety case with a qualified machinery-safety engineer.

Why does wheel odometry matter if I use SLAM?

Many mobile-robot localization stacks combine sensor data with a motion model that uses wheel odometry. Slip, effective wheel diameter, wheelbase calibration and encoder resolution can affect that estimate, although some guidance methods do not rely on odometry in the same way. The cited study evaluates a slip-aware calibration method in simulation and does not establish one field drift rate for all vehicles. Measure the chosen vehicle and tire set on representative floors, then validate the combined localization stack.

AGV / AMR navigation method selector

AGV navigation selector

Compare five AGV navigation methods for AGV and AMR fleets. Treat the repeatability ranges as screening assumptions; verify each vehicle specification with suppliers and a site pilot.

Set constraints Read the method report

Methods scored

tape · QR · LiDAR · vision · beacon

Indicative planning bands

±3-40 mm

not comparable supplier data

Decision mode

4 criteria

repeatability · flex · cost · env

Validation

Site scoped

supplier + pilot evidence

Navigation method selector inputs

Your inputs are screened by a capped heuristic: repeatability 30, flexibility 25, budget 20, environment 25. Fleet size and layout changes adjust the rank. Cost tiers are relative, not project quotations.

Fleet size (vehicles)

Range 1-500

Maximum acceptable repeatability deviation (mm)

A method passes only when the upper end of its listed repeatability band meets this target. Absolute position accuracy is not checked here.

Path flexibility needed

Layout change frequency

Budget tier

Environment type

Recommendation & fit band

Scored output with matched criteria, alternatives, and next action.

Enter your constraints and press Run selector to see the recommended navigation method.

Canonical path: /learn/agv-navigation · covers the alias agv amr navigation

Published 2026-06-17 - Last updated 2026-10-13

Key conclusions on AGV & AMR navigation

Eight decision conclusions for fleet architects evaluating navigation methods. Each is traceable to the method, repeatability, and source tables below.

1. No single method wins on all axes

Tight repeatability, high flexibility, and low cost can conflict. The indicative bands show different trade-offs; use them to shortlist methods, then validate a named vehicle.

2. SLAM flexibility costs per-vehicle

SLAM can reduce fixed floor infrastructure while adding per-vehicle sensor and compute cost. There is no universal fleet size where one approach becomes cheaper; compare vehicle, infrastructure, integration, maintenance, and layout-change costs with site-specific quotes.

3. Repeatability claims need field validation

The listed planning bands are not a cross-vendor benchmark or guarantee. Feature-poor aisles, lighting, floor condition, and calibration affect results. Confirm specifications and pilot.

4. AGV vs AMR is a behavior split, not a sensor split

The core difference is dynamic replanning (AMR) vs stop-and-wait (AGV). Both can use SLAM sensors; the navigation logic decides the category.

5. Hybrid fleets are the pragmatic norm

Mixing SLAM (flexible zones) with markers or beacons (fixed loops) balances cost and flexibility. Test handoff zones for localization continuity.

6. Include reconfiguration in TCO

Frequent layout changes can increase the labour and downtime associated with physical route updates. Lower reconfiguration effort does not guarantee lower total cost: compare site-scoped vehicle, infrastructure, integration, maintenance, and change costs over the planned operating life.

7. Odometry is one input to localization

Many mobile-robot stacks use wheel odometry, which can drift from slip, tire mismatch, encoder quantisation, and calibration error. The cited study evaluates calibration with slip in simulation, not a universal field drift rate. Validate the drive-wheel, encoder, tire, and localization stack on representative floors.

8. Safety is set by ISO 3691-4, not the nav method

The protective measures and required performance level depend on the truck, operating conditions, governing standard, and risk assessment. Navigation sensing and the safety case are separate engineering decisions.

Suitable for

Indoor AGV/AMR programs that can define repeatability, flexibility, budget, and environment constraints and run a mapping pilot before fleet-wide procurement.

Not suitable for

Frozen specs demanding ±5 mm repeatability, free roaming, and low cost simultaneously; outdoor-only fleets without beacon infrastructure; programs that cannot pilot.

AGV navigation vs AMR navigation

The alias "agv amr navigation" spans both categories. The distinction is behavioral (replanning logic), not just the sensor hardware.

Dimension	AGV navigation	AMR navigation
Path definition	Fixed path (tape, wire, markers)	Computed dynamically from a map
Obstacle response	Stop and wait for clearance	Replan around the obstacle
Typical sensor	Magnetic / camera line follower	LiDAR or camera SLAM stack
Reconfiguration	Physical infrastructure change	Software remap
Positioning performance	Depends on guidance method, calibration, and floor	Depends on localization stack, map, and environment
Best deployment	Predictable, high-throughput loops	Variable, human-shared spaces
Fleet comms	VDA 5050 can exchange orders and status with fleet control	VDA 5050 v3 adds a zone concept for free navigation
Safety sensor	Select protective measures from the risk assessment	Select protective measures from the risk assessment

Method, repeatability & evidence

How each navigation method works, its illustrative repeatability inputs, and the evidence basis. These ranges are not vendor medians, independent benchmark results, or performance estimates.

Indicative repeatability ranges

Lower bars are better. These planning bands are not guaranteed absolute positioning accuracy and are not directly comparable across vendors.

Reconfiguration effort by method

Directional, site-dependent assessment; no comparable cross-vendor benchmark was identified. Confirm route edits, mapping, validation, and staffing with the supplier.

Method	Indicative repeatability range (mm)	Drift behavior (qualitative)	Relocalization	Evidence
Reflective beacon	3-8	Re-anchors at a visible beacon; installation error remains	Instant on beacon sighting	indicative planning band
QR marker	5-12	Re-anchors at each readable marker; spacing matters	Per-marker reset	indicative planning band
Magnetic tape	8-15	Tracks the tape; floor and sensor condition matter	Continuous on tape	indicative planning band
LiDAR SLAM	15-30	Can accumulate between successful scan matches	Scan-match relocalization	indicative planning band
Vision SLAM	20-40	Can accumulate between visual matches; lighting matters	Visual feature re-detect	indicative planning band

Method	Per-vehicle hardware	Infrastructure	Fleet scaling	Evidence
Magnetic tape	Low (line sensor)	Tape / embed full route	Low marginal cost	relative cost assumption
QR marker	Low-mid (camera)	Marker stickers on floor	Low marginal cost	relative cost assumption
LiDAR SLAM	High (2D/3D LiDAR + compute)	Mapping only	High per-vehicle cost	relative cost assumption
Vision SLAM	Mid-high (cameras + compute)	Mapping only	Mid per-vehicle cost	relative cost assumption
Reflective beacon	Mid-high (laser scanner)	Wall/column reflectors	Beacons shared across fleet	relative cost assumption

Odometry: the foundation every method builds on

These methods may combine localization with wheel odometry. Slip, tire wear, calibration, and sensor fusion affect the result. The diagram is qualitative and unscaled; no universal odometry drift rate or safe re-localization distance applies to every vehicle.

Error source	Type	Effect	Mitigation
Wheel slip / skid	Non-systematic	Measured wheel travel exceeds ground travel; position overestimated, worst on smooth/wet floors and hard acceleration.	High-traction tires, gentler acceleration profiles, and IMU/LiDAR fusion via an EKF.
Wheel diameter mismatch	Systematic	Unequal effective radii produce a scale bias that curves every straight path.	Calibrate kinematic parameters (e.g. UMBmark test); use matched drive wheels.
Wheelbase uncertainty	Systematic	Heading bias on every turn; accumulates as lateral drift.	Measure the effective track precisely, or use unloaded passive encoder wheels.
Encoder quantisation	Systematic	Distance per count depends on wheel circumference, gearbox ratio, encoder location, and whether resolution is stated as pulses or decoded counts.	Calculate count resolution from the actual drivetrain and required measurement tolerance; validate it against the selected encoder datasheet.
Floor roughness / unevenness	Non-systematic	Random heading and distance noise that grows with distance.	Periodic relocalization on markers, beacons, or SLAM scan-match.

Standards & safety framework

Choosing a navigation method and passing the safety case are separate decisions. The standards below govern AGV/AMR deployments regardless of whether you run tape, markers, SLAM or beacons.

Reference	Scope	Key requirement	Evidence
ISO 3691-4 (2023)	Industrial trucks — safety of driverless trucks (AGV/AMR) — Type-C safety standard for driverless industrial trucks and their systems. ISO lists the 2023 edition while a technically revised third edition is in draft.	Use the applicable published edition for the truck, operating environment, safeguarding and commissioning requirements. Confirm the latest edition and jurisdictional adoption before freezing a safety specification.	primary-standard
EN ISO 13849-1	Safety-related parts of control systems (performance levels) — Functional-safety framework assigning performance levels a–e from severity, exposure and avoidability.	Provides design principles for safety-related control parts; it does not prescribe a required PLr for every application. Determine the required level from the applicable product standard and risk assessment.	primary-standard
IEC 61496-1 / -3	Electro-sensitive protective equipment (ESPE), Type 3 — IEC 61496-3:2025 covers AOPDDR equipment that detects persons using diffuse reflection as part of a safety-related system.	Applies when this class of protective equipment is selected. It does not mandate this device type or specify the detection-zone layout for every application.	primary-standard
VDA 5050 v3.0 (Mar 2026)	AGV/AMR ↔ master-control communication interface — Interface for exchanging job and status data between mobile robots and fleet control; V3.0 adds a zone concept for robots with higher autonomy.	Check the supported interface version and feature set across every vehicle and fleet-control endpoint. VDA 5050 does not replace onboard navigation or the safety case.	primary-standard

Safety requirements depend on the vehicle and application

ISO 3691-4 and the applicable machinery-safety standards set requirements for the truck and system. The required performance level and protective-device type depend on the risk assessment and configuration; IEC 61496-3 covers one specific class of electro-sensitive protective equipment. A navigation sensor is not automatically a safety-rated protective device. Confirm the current standard edition, exact device certification, and complete safety chain with a qualified machinery-safety engineer.

Research basis reviewed 2026-10-13. VDA 5050 v3.0.0 is dated March 2026. ISO lists ISO 3691-4:2023 and a technically revised third edition in draft; confirm the published edition and local adoption before fixing safety requirements.

Need to validate a shortlist?

Bring the vehicle specification and site constraints into a navigation architecture review.

Request an architecture review

Comparison, trade-offs & risks

Side-by-side comparison, the cost-repeatability trade-off, deployment scenarios, and the risks of mis-selecting a navigation method.

Method	Repeatability band	Flexibility	Cost	Reconfig	Best for	Main limit
Magnetic tape	±8–15 mm	Fixed line only	$ (lowest)	High (re-tape floor)	High-throughput repeatable loops	Tape wear; no dynamic rerouting
QR / fiducial marker	±5–12 mm	Grid-based, semi-flexible	$$	Medium (re-stick markers)	Dense warehouses with shelf aisles	Markers can be obscured or damaged
LiDAR SLAM	±15–30 mm	Free roaming	$$$$ (highest)	Low (remap only)	Dynamic, frequently changing layouts	Feature-poor aisles degrade localization
Vision SLAM	±20–40 mm	Free roaming	$$$	Low (remap only)	Cost-sensitive free-roaming indoor fleets	Sensitive to lighting and visual symmetry
Reflective beacon	±3–8 mm	Open-area triangulation	$$$	Medium (relocate beacons)	Large open bays needing high repeatability	Line-of-sight to beacons required

Cost vs repeatability trade-off

The positions are illustrative, not measured vendor data. Lower repeatability error generally carries a cost or infrastructure trade-off.

High-throughput pallet loop

FIT

Fixed route, large fleet, tight budget

Input: 24 vehicles · repeatability ≤ ±15 mm · fixed · low budget

Recommended: Magnetic tape navigation (100/100)

Magnetic tape navigation meets all four rule-based screening criteria against the listed repeatability planning bands. This is a shortlist signal, not a validated performance guarantee or a check of absolute positioning accuracy.

Dynamic e-commerce fulfilment

REVIEW

Frequent layout change, free roaming

Input: 12 vehicles · repeatability ≤ ±25 mm · free-roaming · high budget

Recommended: Vision SLAM / VSLAM (82/100)

Vision SLAM / VSLAM is the closest rule-based match but misses at least one constraint. Verify the supplier's repeatability and absolute-accuracy specifications, then run a representative pilot before fleet-wide procurement.

Precision assembly feed

REVIEW

High accuracy, semi-flexible, mid budget

Input: 6 vehicles · repeatability ≤ ±5 mm · semi-flexible · mid budget

Recommended: QR / fiducial marker navigation (70/100)

QR / fiducial marker navigation is the closest rule-based match but misses at least one constraint. Verify the supplier's repeatability and absolute-accuracy specifications, then run a representative pilot before fleet-wide procurement.

Conflicting spec (over-constrained)

RECONSIDER

High accuracy + free roaming + low budget

Input: 8 vehicles · repeatability ≤ ±5 mm · free-roaming · low budget

Recommended: Vision SLAM / VSLAM (62/100)

Your repeatability target, flexibility, and budget constraints conflict. No single navigation method satisfies all criteria at once. Relax at least one constraint before sourcing navigation hardware.

Risk	Trigger	Impact	Mitigation
Accuracy gap in feature-poor aisles	Long straight corridors with few geometric features	High	Add fiducial markers as localization anchors, or fall back to reflective beacons in those aisles.
Tape / marker damage	Forklift traffic, floor cleaning, spills	Medium	Schedule marker inspection, use recessed tape, and keep a replacement-marking runbook.
Map drift after layout change	Racking moved or pallets repositioned without remap	High	Trigger a remap after any documented layout change and version-control the map.
Cost overrun as per-vehicle hardware scales	Fleet growth or layout changes make vehicle hardware, shared infrastructure, or maintenance costs diverge from the original plan	Medium	Compare lifecycle quotes; consider SLAM for flexible zones and markers for fixed high-throughput loops.
Lighting sensitivity (vision SLAM)	Aisles with strobe, glare, or low-light shifts	Medium	Add active illumination or switch those zones to LiDAR SLAM.
Over-specifying accuracy	Requesting ±5 mm when pick faces tolerate ±25 mm	Low	Map accuracy to the actual docking tolerance, not a round number.

Frequently asked questions

Grouped by topic. Covers both "agv navigation" and the alias "agv amr navigation".

AGV/AMR navigation basics

Choosing a navigation method

Cost and deployment

Repeatability, risk, and validation

Evidence basis & sources

The rows below distinguish published sources from screening assumptions. Repeatability and cost inputs are not backed by a comparable cross-vendor data set, so validate them against supplier specifications and site-specific quotes.

Source	Scope	Date	Status	Note
Navigation method repeatability planning bands	Illustrative selector ranges; no comparable manufacturer dataset	Reviewed 2026-10-13	Partially known	These are unverified screening inputs, not vendor medians, independent benchmark results, or performance estimates. Replace them with the selected vehicle specification and an agreed acceptance test.
Per-vehicle cost bands	Relative categories used in the selector; no representative quote set	Reviewed 2026-10-13	Partially known	These are qualitative screening labels, not a pricing survey or project quotations. Compare current supplier quotes with site-specific lifecycle costs.
AGV vs AMR behavioral distinction	Common operational shorthand; supplier labels and capabilities overlap	Reviewed 2026-10-13	Partially known	This page compares fixed-path guidance and stop-on-obstacle behavior with SLAM-based dynamic replanning as a typical distinction. Verify the route and obstacle behavior of the selected vehicle.
Reconfiguration effort ranking	Directional assessment of physical route edits versus digital map updates	Reviewed 2026-10-13	Partially known	No comparable cross-vendor benchmark was identified. Layout, fleet tools, validation work, and staffing can change the effort; confirm the expected scope with the supplier.
Safety framework (ISO 3691-4 · ISO 13849-1 · IEC 61496-3)	Primary international standards (type-C + functional safety + ESPE)	Reviewed 2026-10-13; edition status varies	Known	Determine applicable protective measures and required performance from the governing product standard and risk assessment. ISO 13849-1 does not prescribe a PLr for every application; a laser scanner is not universally mandated.
VDA 5050 fleet communication interface	VDA / VDMA open standard (JSON over MQTT)	v3.0.0, March 2026	Known	Standardizes order and status exchange between mobile robots and fleet control. Version 3.0 adds a zone concept for robots with higher autonomy; check both endpoints for compatible versions.
Wheel-odometry error model	Mobile-robotics literature (systematic vs non-systematic error)	2024 numerical simulation study; reviewed 2026-10-13	Partially known	The cited study evaluates calibration under slip in simulation; it does not establish a universal distance or heading drift rate. Measure the selected vehicle on representative floors.

VDA 5050VDA / VDMA · v3.0.0, March 2026
VDA 5050 v3.0 — Mobile robot communication interfaceChecked 2026-10-13
ISO 3691-4ISO · Current edition 2023
Industrial trucks — Safety requirements and verification — Part 4: Driverless industrial trucksChecked 2026-10-13
EN ISO 13849-1ISO · 2023 edition
ISO 13849-1:2023 — Safety-related parts of control systemsChecked 2026-10-13
IEC 61496-3IEC · 2025 edition
IEC 61496-3:2025 — Particular requirements for AOPDDR protective equipmentChecked 2026-10-13
ISO/DIS 3691-4ISO Online Browsing Platform · Draft; check status before specification freeze
ISO/DIS 3691-4 — Draft third edition and proposed technical revisionsChecked 2026-10-13
ROS 2 Nav2Open Robotics / ROS 2 · ROS 2 documentation
Navigation stack — AMCL localization, costmaps, replanningChecked 2026-10-13
Odometry errorMDPI Robotics, 13(1):7 · Robotics 2024, 13(1), 7; simulation study
Online odometry calibration in low-traction conditions (systematic vs non-systematic error)Checked 2026-10-13

Next steps

Run the selector

Enter your fleet constraints above to get a scored recommendation before talking to suppliers.

Plan a mapping pilot

For review-band results, agree pilot duration and acceptance criteria with the supplier; measure repeatability on representative routes and docking tasks.

Request an architecture review

For conflicting constraints, request a navigation architecture review to find a hybrid method set.

Request navigation architecture review

Related engineering resources

Continue with adjacent drivetrain checks, navigation evidence review, and direct RFQ actions.