Quickstart
Install Sentinel, start the runtime, and drive your robot in a first teleoperation session.
This page takes a supported robot from nothing installed to a first teleoperation session. Each step links to the full page for that topic.
Before you start
You'll need:
- A supported robot connected to an Ubuntu 22.04 or 24.04 computer
- A Meta Quest 3 or 3S with the latest software update
- A Sentinel account with access to the dashboard
Connecting your own ROS 2 stack? Complete the ROS 2 integration checklist before you create the Sentinel configuration in step 2.
Install Sentinel
On the computer connected to your robot:
curl -fsSL https://sentinel.avearobotics.com/install.sh | bash
sentinel doctorThe installer sets up the Sentinel daemon and CLI. doctor verifies Docker and GPU prerequisites. See Install Sentinel for requirements per platform.
Create the robot and its configuration
Create the robot in the dashboard and generate its license key. Then set up the robot's configuration — hardware interfaces, cameras, controls, and limits. See Configure your robot for templates and the file's structure.
Enroll the robot
sentinel enrollEnter the license key at the prompt. Enrollment happens once — the key is exchanged for a device identity the daemon keeps.
Start Sentinel
sentinel startThe daemon pulls the runtime image for your platform and brings the stack up. Check progress with:
sentinel statusConfirm the robot is online
Put on the headset, open the browser app, and go to app.avearobotics.com, follow the onscreen prompts to sign in, and confirm the robot appears in the robot list. If it does not appear within a minute, see Robot does not appear.
Run a first session
Select the robot, confirm every camera view is live, and clear the workspace. Then, with the default controller bindings:
- Press A to arm the robot, then press A again to move it to its start pose.
- Hold the grip button to drive. Releasing it stops teleoperation.
- Press B to disarm when you are done.
See Teleoperation for the full session flow and safety notes.
Keep a physical emergency stop within reach whenever the robot can move. Do not rely on the headset or network as the only emergency-stop path.