Search the field guide, causes, requirements, and glossary

Requirements database

What each protocol and vehicle actually needs from the network, from first-party documents. Every value links to its source. "Not published by the vendor" is an answer, too.

AGILOX ONE network requirementsAGILOX runs without a fleet server, so its vehicles talk to each other over customer-provided Wi-Fi that the vendor says must reach every part of the operating area without fluctuation.deviceAGILOXOct 5, 2026
BALYO REACHY network requirementsBALYO asks for customer Wi-Fi on 802.11 a/b/g/n in the 2.4 or 5 GHz band, on channels it specifies, covering the whole robot working area, secured with TKIP or AES personal or EAP-MSCHAPv2 enterprise.deviceBALYOOct 5, 2026
Boston Dynamics Spot network requirementsSpot's public documents set no signal or latency target for the network; they state that Spot sits after 3 seconds without controller communication and turns off its motors after 8, and the 2025 instructions add a controller supervision window of 9 seconds by default.deviceBoston DynamicsOct 5, 2026
CIP Safety connection timingAt default settings a CIP Safety input connection faults when no valid packet arrives within 40 ms, four times its 10 ms RPI.protocolODVA (protocol); values as documented by Rockwell AutomationOct 5, 2026
EtherNet/IP standard I/O connection timeoutA Logix controller drops a standard EtherNet/IP I/O connection after RPI times a multiplier of at least 4, and never in less than 100 ms, while an OMRON NJ/NX controller defaults to 4 times the RPI with a floor of only 10 ms.protocolODVA (protocol); values as documented by Rockwell Automation and OMRONOct 5, 2026
MiR1350 network requirementsMiR'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.deviceMobile Industrial Robots (MiR)Oct 5, 2026
MiR600 network requirementsMiR 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.deviceMobile Industrial Robots (MiR)Oct 5, 2026
OMRON HD-1500 network requirementsOMRON's HD-1500 manual asks for at least -60 dBm, round trips of 10 ms or less, no more than two access points heard at -85 dBm, and 802.11 a/b/g, for a 1,500 kg AMR that tops out at 1.8 m/s.deviceOMRONOct 5, 2026
OMRON LD series network requirementsOMRON's AMR wireless guide asks for at least -60 dBm, round-trip latency of 10 ms recommended and 50 ms at most, and about 50 kbps per AMR, with constant coverage across the workspace.deviceOMRONOct 5, 2026
OMRON MD series network requirementsOMRON's MD-650 and MD-900 manual asks for at least -60 dBm, round trips of 10 ms or less, no more than two access points heard at -85 dBm, and 802.11 a/b/g, and says a lone AMR can run without Wi-Fi while a fleet cannot.deviceOMRONOct 5, 2026
OTTO 1500 network requirementsOTTO's public spec sheet gives the OTTO 1500 dual-band 802.11 a/b/g/n/ac Wi-Fi, while its signal, latency, security and port requirements sit in a vendor help center that needs a customer login.deviceOTTO by Rockwell AutomationOct 5, 2026
PROFINET IO update time and watchdogA PROFINET IO device declares a communication failure after its update time multiplied by the accepted update cycles without IO data, which defaults to 3, so 6 ms at a 2 ms update time.protocolPROFIBUS and PROFINET International (protocol); values as documented by PI and SiemensOct 5, 2026
PROFIsafe F-monitoring time (F_WD_Time)A PROFIsafe connection goes to a safe state when the next valid safety message does not arrive within F_WD_Time, a monitoring time in milliseconds that you set for each F-device.protocolPROFIBUS and PROFINET International (protocol); values as documented by SiemensOct 5, 2026