Begin with the official instructions for your delivered robot and software version. Get a known built-in behavior working before changing policies or development settings.
Before the robot arrives
Read the official operating documentation and identify which guide covers your controller. Try the simulator if you want to become familiar with the idea of commanded movement. Make a short list of what you will need to verify on arrival: supplied items, charging instructions, software information and the first control procedure. Avoid purchasing speculative extras before checking the included contents.
Make the first session small
Use a clear, level area away from edges and fragile objects, following the manufacturer’s operating guidance. Check the physical condition of the robot and supplied components before use. The first goal is a calm, repeatable demonstration of normal operation, not a collection of tricks. Change one setting at a time so you can tell what caused an unexpected result.
Record a known-good state
Note the software version, the control method and what worked. A short baseline note is valuable later when you install an update or try a different policy. If something goes wrong, return to that comparison: did the connection change, the software change or the physical conditions change? Separating those possibilities makes troubleshooting less frustrating.
Choose your next session
If driving is the enjoyable part, explore the behavior guide and document one move. If understanding the system interests you, read the GitHub navigation guide. If you want to teach a behavior, follow the reinforcement-learning path and check its compute prerequisites. None of these requires changing everything at once. End a session with one question for the next one and a note of what you actually observed.
Go to the source
Reviewed September 7, 2026. Prices, availability and software can change.