Skip to content

SOP · Troubleshooting · Networking · Moxa

Robot powered but offline

Isolate why a physically ON robot is unavailable to fleet/orchestration software — layer by layer.

Purpose

Find the failing layer when a robot is powered but not reachable or not reporting state.

Prerequisites

  • Access to fleet/orchestration status view
  • Network team contact
  • Robot identity (name/ID) — not its address

Safety considerations

  • Follow your site's lockout / isolation and robot-zone entry rules before approaching equipment.
  • Only trained, authorized personnel perform service actions. This page is concept training.

Normal behavior

A healthy robot is powered, associated to an AP, reachable on the network, its services running and its state visible upstream.

Conceptual operation

  • Power → network link → WLAN association → IP reachability → application service → middleware → robot software → controller.
  • Each layer depends on the one below it; test from the bottom up or from the top down, but one layer at a time.

Inspection points

  • Power and status indicators
  • WLAN client link/association state
  • Robot software status screen (if available)

Diagnostics

  • Is the WLAN client associated (which AP/BSSID, RSSI)?
  • Is the robot reachable from the network side?
  • Is the robot service running?
  • Is the middleware/broker connection established?
  • Are certificate/authentication errors logged?

Common symptoms

  • Robot shows OFFLINE upstream but lights are on
  • Tasks not accepted
  • State timestamps stop updating

Recovery decision tree

  1. 1. Is the robot powered and booted?

    YES → Check the network link and WLAN association.

    NO → Follow the power / charging SOP.

  2. 2. Is the WLAN client associated with good signal?

    YES → Test IP reachability.

    NO → Follow WLAN client diagnostics / RSSI SOP.

  3. 3. Is the robot reachable on the network?

    YES → Check application service and middleware connection.

    NO → Escalate to network team with AP/BSSID and time.

  4. 4. Is the middleware/broker session connected?

    YES → Check robot software errors and controller state.

    NO → Check service status and certificate/authentication.

Authorized procedure

INTERNAL / AUTHORIZED ONLY

Commands, addresses, service restart steps and credentials — available only in the model-specific, authorized SOP for your site. Not published on this website.

Verification

  • Robot state visible and updating upstream
  • A test task is accepted and completes

Escalation

Escalate with: robot ID, time window, associated AP, observed layer results. Never share credentials in tickets.

References