Skip to content

Commit 99cd792

Browse files
committed
update headings for consistency and standardize references
1 parent a650d88 commit 99cd792

1 file changed

Lines changed: 20 additions & 14 deletions

File tree

docs/integrations/software/olo-robotics.mdx

Lines changed: 20 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: OLO Robotics Integration with Leo Rover | Cloud ROS Bridge
2+
title: OLO Robotics Integration with Leo Rover | Cloud ROS 2 Bridge
33
sidebar_label: OLO Robotics
44
keywords:
55
- olo robotics
66
- olo
77
- docker
8-
- ros 2
8+
- ROS 2
99
- cloud
1010
- teleoperation
1111
- leo
@@ -22,10 +22,12 @@ image: /img/robots/leo/integrations/olo-robotics/leo_olo_dashboard.webp
2222

2323
[OLO Robotics](https://olo-robotics.com/) is a browser-based robotics platform
2424
that brings simulation, visualization, teleoperation, and development into one
25-
placewith native ROS 2 access, JavaScript and Python SDKs, and AI-assisted
25+
place - with native ROS 2 access, JavaScript and Python SDKs, and AI-assisted
2626
coding. The goal is to spend less time wiring together separate tools and more
2727
time working with your robot.
2828

29+
## What to expect?
30+
2931
This guide shows how to connect a Leo Rover to OLO by installing the **OLO
3032
appliance** on the Leo Rover. The appliance runs in Docker, links the robot to
3133
the [OLO dashboard](https://app.olo-robotics.com/), and bridges your ROS 2 stack
@@ -37,8 +39,8 @@ from anywhere. No changes to Leo Rover hardware are required.
3739
loading="eager"
3840
src="/img/robots/leo/integrations/olo-robotics/leo_olo_dashboard.webp"
3941
alt="Leo Rover in the OLO platform visualizer"
40-
width="2000"
41-
height="1300"
42+
width="2533"
43+
height="1484"
4244
/>
4345

4446
## Prerequisites
@@ -66,15 +68,19 @@ You also need a free [OLO account](https://app.olo-robotics.com/register).
6668

6769
:::note
6870

69-
This guide assumes your Leo Rover is running **LeoOS 1.9** or newer.
71+
This guide assumes your Leo Rover is running **LeoOS 2.0.0** or newer with ROS 2 Jazzy.
7072

7173
:::
7274

7375
## Software integration
7476

77+
:::info
78+
7579
All steps below are performed on the Leo Rover over SSH unless noted otherwise.
7680

77-
### Install Docker on the Leo Rover
81+
:::
82+
83+
### Installing Docker on the Leo Rover
7884

7985
Install Docker Engine by following the
8086
[official Docker installation guide for Ubuntu](https://docs.docker.com/engine/install/ubuntu/).
@@ -87,7 +93,7 @@ sudo usermod -aG docker $USER
8793
newgrp docker
8894
```
8995

90-
### Generate a device API key
96+
### Generating a device API key
9197

9298
Open the [OLO dashboard](https://app.olo-robotics.com/), sign in, and click
9399
**Register Appliance**. In the dialog, name the robot `Leo Rover` and continue.
@@ -101,7 +107,7 @@ mkdir -p ~/olo-appliance
101107
echo "OLO_APL_DEVICE_API_KEY=apl_<your-device-api-key>" > ~/olo-appliance/.env
102108
```
103109

104-
### Create Docker Compose
110+
### Creating Docker Compose
105111

106112
Create a Docker Compose file:
107113

@@ -125,7 +131,7 @@ volumes:
125131
EOF
126132
```
127133

128-
### Start the appliance
134+
### Starting the appliance
129135

130136
Pull the image and start the appliance. The first run downloads the Docker
131137
image, which may take a few minutes:
@@ -135,12 +141,12 @@ cd ~/olo-appliance
135141
docker compose up -d
136142
```
137143

138-
### Verify the installation
144+
### Verifying the installation
139145

140146
After the image is pulled and the container starts, the appliance should appear
141147
on your [OLO dashboard](https://app.olo-robotics.com/).
142148

143-
You can also verify the container is running:
149+
You can also verify that the container is running:
144150

145151
```bash
146152
docker compose ps
@@ -155,7 +161,7 @@ docker compose logs -f olo-appliance
155161
You should see the appliance connect to the OLO backend and discover the Leo
156162
Rover's ROS 2 topics.
157163

158-
### Update the appliance
164+
### Updating the appliance
159165

160166
When a new appliance image is available, pull the latest image and recreate the
161167
container:
@@ -172,7 +178,7 @@ Optional cleanup of old unused images:
172178
docker image prune -f
173179
```
174180

175-
### Uninstall
181+
### Uninstalling the appliance
176182

177183
To remove the OLO appliance, stop and remove the Compose resources:
178184

0 commit comments

Comments
 (0)