Skip to main content

Your First Session

Once your device is connected, you can start a session to run software and collect data. This guide walks you through your first session.

Prerequisites

  • Device Manager installed and connected (Installation Guide)
  • Device visible in the Fleet dashboard

Starting a Session

From the Dashboard

  1. Navigate to Fleet in the left sidebar
  2. Click on your device
  3. Click Start Session
  4. Select a composition and mode (or use the default)
  5. Click Start Start Session Button

What Happens During a Session

When you start a session:
1. START command sent to device

2. Device Manager loads composition

3. Software modules start running

4. Logs stream to cloud in real-time

5. Data is collected and uploaded

Session Lifecycle

StateDescription
StartingDevice is loading the composition
RunningModules are executing, logs streaming
StoppingGraceful shutdown in progress
StoppedSession complete, data available

Viewing Logs

While your session is running:
  1. Go to Sessions in the dashboard
  2. Click on your active session
  3. View real-time logs in the Logs tab
Logs are streamed in real-time and stored for later analysis.

Collecting Artifacts

Sessions can produce artifacts like:
  • Log files
  • Rosbag recordings (for ROS2)
  • Data exports
  • Screenshots or recordings
View artifacts in the Artifacts tab of your session.

Stopping a Session

  1. Navigate to your session
  2. Click Stop Session
  3. Wait for graceful shutdown

Example: HelloWorld Session

Let’s run the built-in HelloWorld example:

1. Start the Session

roboticks session start \
  --device my-device \
  --composition HelloWorldComposition \
  --mode prod

2. Watch the Logs

In the dashboard, you’ll see logs like:
[INFO] HelloWorldTask starting...
[INFO] Publishing: Hello from Roboticks! (count: 1)
[INFO] Publishing: Hello from Roboticks! (count: 2)
...

3. Stop When Done

roboticks session stop --device my-device

4. Review the Session

Go to Sessions in the dashboard to see:
  • Session duration
  • Log history
  • Any artifacts produced

Troubleshooting

  • Check the device is online in Fleet
  • Verify the composition exists on the device
  • Check device logs: sudo journalctl -u roboticks-manager -f
  • Wait a few seconds for logs to stream
  • Check the session is in “Running” state
  • Verify network connectivity from the device
  • Check the composition configuration is valid
  • Look at device logs for error messages
  • Ensure required dependencies are installed on the device

Next Steps