Separate power, connection, software and behavior problems before changing settings. The goal is to identify the smallest failing step and preserve useful evidence.
If the controller will not connect
Check that it is in pairing mode rather than merely powered on. Follow the official sequence for that model. Note whether it was previously connected to another device and what the pairing command reports. Avoid changing Wi-Fi settings to solve a controller problem unless the documentation specifically connects those two issues.
If the laptop cannot find the robot
Confirm that you are following the laptop-tool guide and that your host has the relevant Bluetooth access. Distinguish “no robot found” from “robot found but operation refused” and from “network feature unavailable.” Each message points to a different stage. Capture the exact error rather than describing every failure as “it does not work.”
If a behavior looks wrong
Stop the experiment and compare against the last known-good setup. Record the policy, software version, starting pose and floor conditions. Ask whether the problem is repeatable. A changed behavior after an experiment may be a policy issue; a connection failure before any movement is a different problem. Do not treat repeated resets as a substitute for identifying the cause.
Make a useful support report
Include a short title describing the failing action, the environment and version, steps to reproduce, expected behavior and actual behavior. Remove credentials, private network details and unrelated personal information from logs. Link to the official issue tracker or community through the repository. For order, delivery or hardware concerns, use the seller’s support route rather than assuming a software issue tracker can access your purchase.
Go to the source
Reviewed September 7, 2026. Prices, availability and software can change.