Skip to content

Networking Academy

How a mobile robot
stays connected.

From the Wi-Fi device on the robot to access points, the site network and the control systems — and what really changes when a robot roams.

PUBLIC CONCEPTSafe architectural / educational information.

01 · Basics

Robot → Wi-Fi → AP → network → control.

Start simple. Each term has a Simple and a Technical explanation.

ROBOTACCESS POINTNETWORKSERVER / CONTROLWi-FiEthernet
  • IP address

    The robot's address on the network, so messages can find it.

  • MAC address

    A unique hardware ID built into each network device.

  • SSID

    The name of the Wi-Fi network.

  • BSSID

    The ID of the specific access point the robot is connected to.

  • Subnet

    A group of addresses that can talk directly to each other.

  • Gateway

    The door from the robot's network to other networks.

  • DNS

    Turns names into IP addresses.

  • RSSI

    How strongly the robot currently receives a wireless signal.

  • Channel

    The radio 'lane' a Wi-Fi network uses.

  • Access point

    A box on the ceiling that connects Wi-Fi devices to the wired network.

  • Wireless client

    The Wi-Fi device on the robot.

  • Bridge

    Connects Wi-Fi on one side to a wired cable on the other.

  • Roaming

    Switching from one access point to a better one while moving.

  • Packet loss

    Messages that never arrive.

  • Latency

    How long a message takes to arrive.

02 · Roaming

Watch a robot change access points.

As the robot drives, AP-A weakens and AP-B strengthens. The client doesn't jump instantly — it evaluates candidates, then reassociates.

AP-AAP-BAP-C

RSSI along the aisle (dBm)

Dashed red: example roaming threshold (-70 dBm). Real thresholds are site-specific.

STATE
ASSOCIATED
SSID
WAREHOUSE-ROBOTS (example)
BSSID
xx:xx:xx:00:00:0A
CHANNEL
36
RSSI
-60 dBm
NETWORK
CONNECTED

03 · RSSI lab

Powered is not the same as reachable.

Move the robot away from the AP and switch conditions. Watch signal, latency, loss and application connectivity on one timeline.

RSSI

-62 dBm

LATENCY

8 ms

PACKET LOSS

0%

APPLICATION

REACHABLE

Timeline (most recent on the right)

AP association
RSSI
Latency
Packet loss
Roaming
Application

ROBOT POWER: ON — yet with weak signal, interference or loss, higher-level software can still see the robot as unavailable. Powered ≠ reachable.

04 · Layers

Roaming versus API.

Beginners often mix these up. The network layer changes; the application session runs above it.

Network layer

AP-AAP-Bswitch / networkROBOT

WLAN CLIENT → AP-A

Application layer

Fleet control
Middleware / broker
Robot software

SESSION: CONTINUOUS (messages flow over IP)

Wi-Fi roaming does not mean an API is roaming. The wireless connection changes its AP association. The application protocol keeps communicating over the IP network as long as connectivity remains intact.

  1. APPLICATIONFleet / orchestration / APIs
  2. MIDDLEWARERobot communication services
  3. NETWORKIP · TCP · MQTT where applicable
  4. WIRELESSWLAN · AP · roaming
  5. ROBOT CONTROLRobot software · controllers
  6. HARDWAREDrivers · motors · sensors

05 · Moxa / WLAN client

Explore the robot's Wi-Fi device.

Rotate the device, open its components, then walk through the concepts its configuration covers — classified as concept, vendor-verified, site-specific or authorized-only.

GENERIC DEVICE · NOT A REAL ADMIN UI — configuration screens differ by AWK family and firmware. Lock down your exact model and firmware, then use Moxa's model-specific manual. No production settings are shown.

Component

Radio

PUBLIC CONCEPT
What it is
The Wi-Fi radio that talks to access points.
What it does
Connects to the strongest suitable AP.
Input
RF from antennas
Output
Frames to/from the device
Communicates with
AntennasDevice CPU
VENDOR VERIFIEDSupported by official manufacturer documentation (linked).

Moxa's AWK families are industrial WLAN devices that can act as access point, bridge or client, depending on model and configuration.

On a mobile robot the device usually runs as a client, bridging Wi-Fi to the robot's onboard Ethernet.

Official Moxa documentation

What to look at

  • Exact model and hardware revision
  • Firmware version
  • Operating mode

06 · Certificates

Identity before communication.

Certificate → device identity → authentication → secure communication. Switch states to see how a powered robot can still be unable to communicate.

  1. OK

    Certificate

  2. OK

    Device identity

  3. OK

    Authentication

  4. OK

    Secure communication

POWER

ON

WI-FI

ASSOCIATED

SESSION

SECURE SESSION ESTABLISHED

Identity proven; communication proceeds. Not every “dead” robot is a certificate problem — always isolate layer by layer.

07 · Firmware

A controlled update, step by step.

The lifecycle of a firmware update — simulated, with the parts that must stay inside the authorized procedure clearly marked.

  1. 01

    Authorized workstation

  2. 02

    Validated firmware package

  3. 03

    Network connection

  4. 04

    Device

  5. 05

    Validation

  6. 06

    Installation

  7. 07

    Reboot / reinitialisation

  8. 08

    Version verification

Concept
Prerequisites
Validation
Authorized procedure
Post-change verification
Rollback / escalation

WARNING — the exact procedure depends on the hardware model and approved vendor documentation. Never load arbitrary firmware onto production equipment.