TL;DR

Navigation deviations are usually caused by a dirty LIDAR sensor, a damaged floor fiducial marker, or a stale map that does not match the current warehouse layout. Clean the LIDAR and verify map version first.

What you might see

robot stopping unexpectedly in the middle of an aisle
robot reporting localization failure on the fleet management screen
robot taking incorrect aisle or not finding target location
robot drifting off its expected path and triggering a safety stop

Likely causes

Tap to mark as ruled out

Dirty or obscured LIDAR sensor window reducing scan range and causing localization failure
Damaged or covered floor fiducial markers that the robot uses for precise localization
Warehouse layout change (moved shelving, new obstruction) not reflected in the current robot map
Wheel odometry error from a worn drive wheel or accumulated floor contamination reducing traction

Required tools

Fleet management console access
Lint-free cloth for LIDAR cleaning
Replacement fiducial tape (retroreflective, correct specification)

Safety first

When moving an AMR in manual mode in a live warehouse, clear the path and notify area personnel. AMRs in manual mode may not stop automatically for people.
Do not attempt to physically move or push a robot that has stopped in an aisle without first placing it in manual mode from the fleet console.

Procedure

7 steps · ~45 min

1
Check the fleet management console for the specific localization error code reported by the robot.[1]
2
Drive the robot to a clear area using manual mode from the fleet console. Check the LIDAR live scan view; it should show walls and racking as clean lines. Blurry or short-range scan indicates a dirty sensor.
Warning: When operating a robot in manual mode in a live warehouse environment, alert floor personnel and ensure the path is clear. AMRs in manual mode do not follow normal traffic rules.
3
Clean the LIDAR sensor window with a dry lint-free cloth. Do not use solvent-based cleaners.
4
Inspect the floor fiducial markers in the area where failures occur. Tape must be fully adhered, not torn or peeled. Replace any damaged markers with the correct retroreflective tape.
5
Confirm the robot is running the correct current map version from the fleet console. If a layout change has been made, update and push the revised map.
6
Inspect the drive wheels for uneven wear or debris stuck in the wheel tread. Replace worn wheels per the OEM wear limit.
7
Return the robot to auto mode and run a supervised test mission through the affected area to confirm navigation is restored.

Sources

Locus Robotics Locus Origin AGV / AMR (Mobile Robots) general technical documentation, Locus Robotics
AMR navigation system maintenance, LIDAR sensor cleaning and map management, general material handling references (general)

More guides for Locus Robotics Locus Origin

How to diagnose battery charging failure and short run time on a Locus Robotics Locus Origin AMR

Short run time or incomplete charge is almost always a dirty dock contact or a battery cell that has lost capacity. Clean the charging contacts first; if health flags persist, escalate to the OEM for battery replacement.

~30 min6 steps

How to reduce obstacle detection false stops on a Locus Robotics Locus Origin AMR

Repeated false stops in the same location usually mean a dirty safety scanner or a highly reflective surface (shrink wrap, chrome rack label) creating a phantom return. Clean the scanner and identify nearby reflectors.