Robots that have been offline for an extended period of time and that do not have a connection to the RoboKind management server may struggle to re-connect to WiFi or when attempting to run a network test.
If your robot is not in use and remains powered off or stored for an extended period, it can lead to potential issues when powering it back on. This can be due to outdated settings or configurations that need to be updated.
- Robot software may be outdated
- If the robot software is not up to date, it may cause connectivity issues and prevent the robot from functioning properly. It is important to regularly check for software updates and install them to ensure optimal performance.
- Learn more about Robot software versions >
- The firewall is blocking ports used to allow the robot to connect to our servers, or the robot is otherwise disconnected from the Internet
- Firewalls and network settings can sometimes block the necessary ports and prevent the robot from establishing a connection with our servers. Additionally, if the robot is not connected to the internet, it will not be able to perform certain functions or receive updates.
Possible symptoms:
- When running a network test, a FAIL error occurs on Server #3: During a network test, if there is a failure error specifically on Server #3, it indicates a connectivity issue between the robot and our servers. This can be caused by firewall restrictions or a disconnected internet connection.
- Robot may fail to fully boot up within 5 minutes, and stay on the RoboKind page: If the robot fails to fully boot up within the expected time frame of 5 minutes and remains stuck on the RoboKind page, it could be a result of outdated software or connectivity problems preventing it from completing the boot process.
- Attempts to connect the robot to a new Wi-Fi router fails: When trying to connect the robot to a new Wi-Fi router, if the connection fails, it suggests that there might be an issue with the robot's network settings or firewall restrictions. These issues need to be addressed to establish a successful connection.
Troubleshooting Steps
-
If possible, connect the robot to an Ethernet network, reset the robot (button on back) and then use Utilities - Update Software after rebooting. After the robot is updated to the current software version, it will be able to connect to WiFi.
- (IT department assistance recommended) Save the attached autorun-r25 file to a cleanly formatted USB drive. Insert into the back of the fully booted robot and listen for “Success. Please update your robot now.”
-
-
If after inserting the drive you do not hear anything from the robot, possible causes include:
-
The attached script might be saved with a .txt extension or otherwise, the file name should be exactly “autorun-r25”.
-
The USB drive in question may not be compatible or formatted differently; please test with a different drive or see Troubleshooting - USB Flash Drive
-
The volume on the robot is set too low, try using the volume up on the back of the robot to check the volume.
-
-
-
A robot can be temporarily connected to a WiFi hotspot/tethered device (thus allowing a temporary connection to our management server). After rebooting the robot, repeat the network test. Utilities - Network - Test Network
Learn More: Establishing a WiFi connection for your robot
Advanced Troubleshooting:
(IT department request) An organizations network firewall is temporarily enabled to allow the robot to contact our management server at cypress.robokind.us (72.249.182.162) over UDP port 1194, after which a robot will download the update from our server upon being rebooted.