Search the field guide, causes, requirements, and glossary

MiR600 network requirements

MiR applies the same network guide to the MiR600 as to its other robots, at least -70 dBm from the best access point and -75 dBm from the second, 200 ms round trips, 2% packet loss, for a 600 kg AMR that runs at 2 m/s.

Vendor or body
Mobile Industrial Robots (MiR)
Model or version
MiR600 with MiR Fleet; MiR Network and Wi-Fi Guide v2.10 (12/2024)
Last verified
Oct 5, 2026
Sourced values
16
Top speed
2.0 m/s

Values

ParameterValueCondition
Minimum signal strength, best access point-70 dBm1Measured from the robot's perspective
Minimum signal strength, second-best access point-75 dBm1Measured from the robot's perspective
Minimum signal-to-noise ratio20 dB1Table 2.1 prints the unit as dBm; SNR is a ratio
Maximum latency, WLAN guideline200 ms1Round-trip time, measured by pinging the robots; robot to MiR Fleet is 500 ms round trip
Maximum packet loss2 %1
Minimum throughput per robot3 Mbps1At a transfer rate of at least 20 Mbps
Channel utilization ceiling60 %1Above this MiR says latency and packet loss affect the system
Supported bands2.4 GHz and 5 GHz1MiR states the internal antennas of the MiR250, MiR600 and MiR1350 support both bands
Wireless standards802.11a, 802.11b, 802.11g, 802.11n, 802.11ac1Software 3.x can restrict each robot to chosen channels
Roaming infrastructureWLAN controller required; access points share roaming information; load balancing disabled; airtime balancing disabled if possible1Full Wi-Fi coverage along all robot travel paths
Fast roamingNetwork should support fast reauthentication to other access points1MiR names basic WPA2-PSK, or key caching that keeps stronger security; the guide does not name 802.11r, 802.11k or 802.11v; hidden SSIDs force a disconnect and active scan that can take several seconds
Maximum roam timeNot published by the vendor1The guide sets coverage overlap and controller requirements but gives no roam-time figure
Wi-Fi security modesWPA/WPA2 Personal; WPA/WPA2 Enterprise with PEAP or EAP-TLS1Enterprise requires TLS 1.2 or higher on the server
Fleet manager ports, software 3.xRobot to MiR Fleet TCP 80 and 443; ROSbridge TCP 9090; MiR Fleet REST API TCP 8080; Modbus TCP 5021All TCP and inbound, except the outbound remote support connection on TCP 80; MiR Fleet Enterprise uses TCP 5060 from robot to fleet
Wi-Fi watchdog, software 2.xOptional RSSI watchdog or ping watchdog that forces a reassociation when signal falls below a threshold or pings fail1Software 3.x replaces the watchdogs with a background scan frequency setting
Loss-of-comms behaviorNot published by the vendor1Checked the network guide

Top speed

2.0 m/s2

Sources

  1. MiR Network and Wi-Fi Guide v2.10. Read Oct 5, 2026.
  2. Top speed

About this page

Built from 2 sources: 2 vendor documents. Researched and drafted with AI assistance, then reviewed and approved by Ben Rutter on . How pages are made

First published
Last updated
Change history (1)
  • First published
Cite this page

Plain

Ben Rutter. "MiR600 network requirements." OT Wireless, published October 5, 2026. https://otwireless.com/requirements/mir-mir600/

APA 7

Rutter, B. (2026, October 5). MiR600 network requirements. OT Wireless. https://otwireless.com/requirements/mir-mir600/

BibTeX

@misc{rutter2026mirmir600,
  author = {Rutter, Ben},
  title = {{MiR600 network requirements}},
  year = {2026},
  howpublished = {\url{https://otwireless.com/requirements/mir-mir600/}},
  organization = {OT Wireless},
}