Planning Robot Behavior for the Moment Every Internet Connection Is Gone Robot connectivity loss needs a defined behavior on the robot, because detection is slow and one-sided. The robot sees an internet connection drop locally. A fleet manager on MQTT with a 60-second keepalive waits through 90 seconds of silence before marking the robot gone. More internet connections make a … Read More

Why Robot Software Built for One Network Struggles Across Cellular Robot software over cellular breaks three assumptions from the lab at once. Multicast discovery stops at the first router. Carrier-grade NAT lets a robot open connections out but blocks every connection in. And a change of network gives the robot a new IP address, which resets every open TCP session … Read More

Private 5G and Wi-Fi for Warehouse Robots, Combined Instead of Chosen Private 5G and Wi-Fi for warehouse robots work best combined, not chosen. An autonomous mobile robot (AMR) crosses dozens of Wi-Fi access points per shift. Without 802.11r, each handover can mean a full 802.1X re-authentication lasting hundreds of milliseconds. The delay is long enough to miss heartbeats and show … Read More

A Buyer’s Checklist for Networking Software on Robots Networking software for robots has to be measured on the robot, with the robot’s real workload running. The software shares the onboard computer with perception, planning and logging. Five measurements decide whether a package fits. The five are CPU and memory under load, behavior when an internet connection breaks, routing control, management … Read More

Why Robot Fleet Connectivity Matters as Much as Autonomy Robot fleet connectivity decides whether data leaving a robot arrives on time. Every change of network path costs measurable time. A Wi-Fi re-authentication on an 802.1X network can take hundreds of milliseconds. A TCP upload can sit idle for seconds after the internet connection returns. An MQTT broker with a 60-second … Read More