A gamepad is the direct play interface. The documentation distinguishes robotctl, which runs on the robot, from duckctl, which communicates from a laptop. Choose the guide for the device you are actually using.
Start with the physical controller
A controller being switched on does not necessarily mean it is in pairing mode. The official pairing guide explains the different button sequences for supported examples. Read that sequence before repeatedly restarting the robot. Once paired, a controller connection and a movement command are still separate things: establish the connection first, then confirm the expected control mapping.
Know where a command runs
When a tutorial shows a command, first locate the machine where it should run. The onboard command-line tool belongs on the robot. The laptop tool belongs on the laptop. Confusing those contexts can produce errors even when the spelling is correct. Label your notes with “laptop” or “robot” so you do not have to reconstruct the context next time.
Bluetooth and Wi-Fi answer different questions
The laptop tool provides a Bluetooth path that can be useful before a robot is on a Wi-Fi network. A browser-based console may have additional network prerequisites. A visible Bluetooth device is not proof that every network-dependent feature is ready. Check the connection needed by the particular function you want instead of treating “connected” as one universal state.
A better pairing troubleshooting sequence
Confirm the controller model and its pairing indicator. Check the current official instructions. Record what the robot reports and whether the controller was previously paired elsewhere. If the first connection still fails, consult the troubleshooting section of the pairing guide before changing unrelated network settings. For an issue report, include the controller model, software version and the smallest sequence that reproduces the problem.
Go to the source
Reviewed September 7, 2026. Prices, availability and software can change.