Skip to main content

Quickstart

Get your first robot connected to Roboticks and see data flowing.

Step 1: Create a Project

  1. Log in to the Roboticks Dashboard
  2. Navigate to SettingsProjects
  3. Click Create Project
  4. Give it a name (e.g., “My Robots”)

Step 2: Register a Device

  1. Go to FleetAdd Device
  2. Enter a name for your device (e.g., “warehouse-robot-01”)
  3. Select the device type
  4. Click Register
  5. Download the device capsule - you’ll need this for the next step
The capsule contains credentials that let your device connect securely to Roboticks.

Step 3: Install Device Manager

On your robot/device, install the Device Manager:
# Download
curl -L -o roboticks-manager.tar.gz \
  "https://releases.roboticks.io/manager/latest/roboticks-manager-$(uname -m).tar.gz"

# Extract
sudo tar -xzf roboticks-manager.tar.gz -C /opt/

# Apply your capsule
sudo tar -xzf device-capsule.tar.gz -C /opt/roboticks-manager/

# Start
sudo /opt/roboticks-manager/install.sh
sudo systemctl start roboticks-manager

Step 4: Verify Connection

Within 30 seconds, your device should appear online:
  1. Go to Fleet in the dashboard
  2. Your device status should show Online
  3. You’ll see heartbeat timestamps updating
Success! Your device is now connected to Roboticks.

Step 5: Start Your First Session

Now let’s run a session to see logs and data:
  1. Click on your device in Fleet
  2. Click Start Session
  3. Select a composition (or use the default HelloWorld)
  4. Click Start

Step 6: View Logs

While the session is running:
  1. Go to Sessions in the dashboard
  2. Click on your active session
  3. Watch logs stream in real-time

What You Should See

  • Device status: Online in Fleet
  • Session status transitions: Starting → Running → Completed
  • Logs streaming in near real-time
  • Artifacts available after session ends

Troubleshooting

  • Check network connectivity: curl -I https://api.roboticks.io
  • Verify capsule was extracted correctly
  • Check service is running: sudo systemctl status roboticks-manager
  • Wait a few seconds for the first batch
  • Verify the session is in “Running” state
  • Check device logs: sudo journalctl -u roboticks-manager -f

Next Steps