MiR1350 network requirements

MiR's network guide asks for at least -70 dBm from the best access point and -75 dBm from the second, 20 dB SNR, ping round trips of 200 ms at most, no more than 2% packet loss and full coverage along every robot path.

Ben RutterIndustrial network engineer

Updated Oct 5, 2026
Reviewed Oct 5, 2026
3 sources
Safety: educational only

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

Values

Parameter	Value	Condition
Minimum signal strength, best access point	-70 dBm¹	Measured from the robot's perspective while connected to the best access point
Minimum signal strength, second-best access point	-75 dBm¹	Measured from the robot's perspective for the second-best access point; section 4.2.3 repeats this as the backup access point requirement
Minimum signal strength, earlier fleet server guide	-75 dBm²	Single figure measured from the robot's perspective, in the 2021 MiR Fleet Server Solution guide
Minimum signal-to-noise ratio	20 dB¹	Measured from the robot's perspective. Table 2.1 prints the unit as dBm; SNR is a ratio, and the 2021 fleet server guide states 20 dB
Minimum data rate per robot	20 Mbps¹	Transfer rate to and from each robot
Minimum throughput per robot	3 Mbps¹	The network must let each robot send and receive at least 3 Mbps of data at a transfer rate of at least 20 Mbps
Robot to MiR Fleet traffic per robot	180 average, 220 peak kbit/s¹	Uplink 130 average (160 peak), downlink 50 average (60 peak). Robot to PC traffic is 520 kbit/s average and 3 Mbit/s peak
Minimum bandwidth per robot, earlier fleet server guide	1 Mb per robot²	2021 MiR Fleet Server Solution guide
Maximum latency, WLAN guideline	200 ms¹	Round-trip time, measured by pinging the robots
Maximum latency, robot to MiR Fleet	500 ms¹	Round-trip time. The same table gives 200 ms for robot to PC and 500 ms for MiR Fleet to PC
Maximum latency, earlier fleet server guide	150 ms²	2021 MiR Fleet Server Solution guide
Jitter limit	Not published by the vendor¹	Checked the network requirements chapter
Maximum packet loss	2 %¹
Channel utilization ceiling	60 %¹	MiR states that above 60% channel use the system is affected by latency and packet loss
Co-channel access points	2 access points per channel¹	Maximum number of access points heard per channel at -85 dBm
Maximum roam time	Not published by the vendor¹	The guide sets coverage overlap and controller requirements for roaming but gives no roam-time figure
Roaming infrastructure	WLAN controller required; access points share roaming information; load balancing disabled; airtime balancing disabled if possible¹	Full Wi-Fi coverage is required along all robot travel paths
Fast roaming	Network should support fast reauthentication to other access points¹	MiR names basic WPA2-PSK, or key caching options that keep stronger security, as ways to get fast reauthentication. The guide does not name 802.11r, 802.11k or 802.11v
Hidden SSIDs	Avoid¹	With a hidden SSID the robot must disconnect and actively scan to roam, which MiR says can take several seconds of complete loss of communication
Wireless standards	802.11a, 802.11b, 802.11g, 802.11n, 802.11ac¹	Software 3.x can restrict each robot to chosen channels in the 2.4 GHz or 5 GHz band
Supported bands	2.4 GHz and 5 GHz¹	The MiR1350 internal antennas support both bands. MiR states the MiR100, MiR200, MiR500 and MiR1000 internal antennas are designed for 2.4 GHz only
Channel width	20 MHz on 2.4 GHz; 20 or 40 MHz on 5 GHz¹	40 MHz on 5 GHz only where enough channels exist to keep co-channel cells apart; MiR says 80 MHz is often not required for its products
Wi-Fi security modes	WPA/WPA2 Personal; WPA/WPA2 Enterprise with PEAP or EAP-TLS¹	Enterprise requires the server to support TLS 1.2 or higher; robots will not connect with TLS 1.1 or older. EAP-TLS certificates in .pem, .pfx or .p12 format
IP addressing	IPv4 only; unique static IP or DHCP reservation per robot¹	MiR Fleet identifies robots by IP address. The robot's internal network makes 192.168.12.0/24 unusable on the site network
Fleet manager ports, software 3.x	Robot to MiR Fleet TCP 80 and 443; ROSbridge TCP 9090; MiR Fleet REST API TCP 8080; Modbus TCP 502¹	All ports are TCP and inbound, except the outbound MiR Remote support connection on TCP 80
Fleet manager port, MiR Fleet Enterprise	Robot to MiR Fleet TCP 5060¹	MiR Fleet Enterprise deployments
Fleet manager ports, fleet server solution	TCP 443 and 9090²	443 carries the MiR Fleet interface and REST traffic between MiR Fleet and robots; 9090 carries ROSbridge. Software below 2.10.0 uses 80 and 8080 instead of 443
Fleet server connection	Wired, in the same physical location as the robots¹	MiR states geographical distance causes delay between MiR Fleet and robots
Wi-Fi watchdog, software 2.x	Optional RSSI watchdog or ping watchdog that forces a reassociation (roam) when signal falls below a threshold or pings to a set address fail¹	MiR says to enable only one. A ping target behind the Fleet server tests the whole network path, and an unreachable target or an unobtainable threshold makes the robot drop its Wi-Fi connection repeatedly
Roam scanning, software 3.x	A background scan frequency setting replaces the watchdogs¹	Sets how aggressively the robot scans for an access point with a stronger signal
Loss-of-comms behavior	Not published by the vendor³	Checked the network guide and the MiR1350 User Guide 2.0

Top speed

1.2 m/s (MiR1350 maximum speed)³

Sources

MiR Network and Wi-Fi Guide v2.10. Read Oct 5, 2026.
MiR Fleet Server Solution Getting Started 1.6. Read Oct 5, 2026.
MiR1350 User Guide 2.0. Read Oct 5, 2026.

About this page

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

First published: Oct 5, 2026
Last updated: Oct 5, 2026

Change history (1)

Oct 5, 2026 First published

Cite this page

Plain

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

APA 7

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

BibTeX

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