Skip to content

Troubleshooting Lab

Something
is wrong.

Learn troubleshooting as layers, not random resets. Observe, isolate, test, identify the layer, recover, verify and document.

PUBLIC CONCEPTSafe architectural / educational information.

The lab

Where is the failure?

Choose a scenario. Inspect layers to collect evidence, then mark the failing layer.

  1. OBSERVE
  2. ISOLATE
  3. TEST
  4. IDENTIFY LAYER
  5. RECOVER
  6. VERIFY
  7. DOCUMENT

VIRTUAL ROBOT · DEAD / OFFLINE

Lights on, but fleet control shows OFFLINE.

Inspect layers to gather evidence. When you know where the failure is, mark it.

CHECKS: 0 · OPEN

  • Power

  • Network link

  • WLAN

  • IP connectivity

  • Application service

  • Middleware

  • Certificate / auth

  • Robot controller

  • Driver

  • Motor

  • Sensor

  • Safety state

The method

Ask the questions in order.

  1. 01Physical robot powered?
  2. 02Can network connectivity be established?
  3. 03Is the wireless / network layer healthy?
  4. 04Is the relevant application / service reachable?
  5. 05Is middleware communicating?
  6. 06Does robot software report an error?
  7. 07Does the controller / drive report an error?
  8. 08Do sensors agree with physical reality?

HTM and VTM errors

Twelve recurring robot errors.

Pick an error and press play: a short animated explainer shows what happens, what to check, how authorized staff fix it and when to escalate. Turn on sound for narration.

Operators only look and report. Approaching, moving, restarting or releasing a robot needs your site safety and authorization procedure first. This guide is concept training — confirm every step against your approved SOP.

The recovery ladder

  1. 01

    Init

    Try Init from the fleet console when appropriate.

  2. 02

    Error-specific check

    Follow the checks for that error below.

  3. 03

    Clear and confirm

    Clear the error, confirm the robot is online, then verify recovery.

  4. 04

    Escalate

    Report what you saw, not what you assume.

ERROR 01

Positioning / localization

The robot cannot confirm where it is — sometimes between several floor barcodes.

DOCUMENTEDSITE PRACTICE

Operator: look and report

  • Note exactly where it stopped. Do not approach.
  • Check nothing is covering the barcodes nearby.
  • Report it. Try Init from the fleet console if your site allows it.

Authorized staff only

  • Place the robot exactly on a safe, suitable barcode.
  • Clear the error, confirm the robot is online, then Init.
  • Correct its location in the system if needed (site practice).

Stop and escalate when: The robot is not exactly on a barcode and you cannot tell whether moving it is safe, or Init fails twice.

Before restarting the robot-interface service, check whether the robot is paused: a restart while paused can lose the robot's load information.

Other recurring issues — no complete recovery found, escalate

  • Network disconnections, stale status, frozen station screens

    Note which screens and robots show old status.

  • Auto-charging failures, low battery

    Check the charger is up and in automatic mode.

  • Firmware command rejects

    No recovery found — escalate.

  • Conveyor / station hand-off problems, missed pickup points

    Record the order and tote affected so inventory can be checked.

  • Slow movement, repeated manual interventions

    Note how often, where, and which error came first.

Recoverable by authorized staff Always escalate

DOCUMENTED
Behaviour described in vendor documentation. Still confirm it is your current approved SOP.
SITE PRACTICE
Reported by sites, not verified in vendor documentation. Confirm with your SOP before using.
GENERAL GUIDANCE
General explanation or safe default.