You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/mobility/base-rc/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,10 @@ aliases:
12
12
# SME: Eric
13
13
---
14
14
15
-
The Base Remote Control service implements an [input controller](/components/input-controller/) as a remote control for a [base](/components/base/).
15
+
The base remote control service implements an [input controller](/components/input-controller/) as a remote control for a [base](/components/base/).
16
16
This uses the [`input` api](/components/input-controller/#api) to make it easy to add remote drive controls for your rover or other mobile robot with a controller like a gamepad.
17
17
18
-
Add the Base Remote Control service after configuring your robot with a base and input controller to control the linear and angular velocity of the base with the controller's button or joystick controls.
18
+
Add the base remote control service after configuring your robot with a base and input controller to control the linear and angular velocity of the base with the controller's button or joystick controls.
19
19
20
20
Control mode is determined by the configuration attribute `"mode"`, for which there are five options:
21
21
@@ -39,7 +39,7 @@ You can monitor the input from these controls in the **Control** tab of the [Via
39
39
40
40
## Configuration
41
41
42
-
You must configure a [base](/components/base/) with a [movement sensor](/components/movement-sensor/) as part of your robot to be able to use a Base Remote Control service.
42
+
You must configure a [base](/components/base/) with a [movement sensor](/components/movement-sensor/) as part of your robot to be able to use a base remote control service.
43
43
44
44
{{< tabs >}}
45
45
{{% tab name="Config Builder" %}}
@@ -103,7 +103,7 @@ The base remote control service supports the following methods:
103
103
104
104
{{% alert title="Tip" color="tip" %}}
105
105
106
-
The following code examples assume that you have a robot configured with a [base](/components/base/) named `"my_base"`, [input controller](/components/input-controller/) named `"my_controller"`, and Base Remote Control service named `"my_base_rc_service"`.
106
+
The following code examples assume that you have a robot configured with a [base](/components/base/) named `"my_base"`, [input controller](/components/input-controller/) named `"my_controller"`, and base remote control service named `"my_base_rc_service"`.
107
107
Make sure to add the required code to connect to your robot and import any required packages at the top of your code file.
108
108
Go to your robot's **Code sample** tab on the [Viam app](https://app.viam.com) for boilerplate code to connect to your robot.
Copy file name to clipboardExpand all lines: docs/mobility/navigation/_index.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ aliases:
13
13
# SMEs: Raymond
14
14
---
15
15
16
-
The Navigation service is the stateful definition of Viam's [motion service](/mobility/motion/).
16
+
The navigation service is the stateful definition of Viam's [motion service](/mobility/motion/).
17
17
It uses GPS to autonomously navigate a rover [base](/components/base/) to user defined endpoints called waypoints.
18
18
Configure your base with a navigation service, add waypoints, and set the mode of the service to [**Waypoint**](#setmode) to move your rover along a defined path at your desired motion configuration.
19
19
@@ -29,7 +29,7 @@ Configure your base with a navigation service, add waypoints, and set the mode o
29
29
30
30
## Requirements
31
31
32
-
You must configure a [base](/components/base/) with [movement sensors](/components/movement-sensor/) as part of your robot to configure a Navigation service.
32
+
You must configure a [base](/components/base/) with [movement sensors](/components/movement-sensor/) as part of your robot to configure a navigation service.
33
33
34
34
To use the navigation service, configure a stack of movement sensors that implement the following methods in their {{< glossary_tooltip term_id="model" text="models'" >}} implementations of the [movement sensor API](/components/movement-sensor/#api):
35
35
@@ -55,7 +55,7 @@ Click the **Services** subtab, then click **Create service** in the lower-left c
55
55
Select the type `Navigation`.
56
56
Enter a name for your service, then click **Create**.
57
57
58
-

58
+

59
59
60
60
{{% /tab %}}
61
61
{{% tab name="JSON Template" %}}
@@ -148,7 +148,7 @@ The following attributes are available for `Navigation` services:
148
148
<!-- prettier-ignore -->
149
149
| Name | Type | Inclusion | Description |
150
150
| ---- | ---- | --------- | ----------- |
151
-
|`store`| obj |**Required**| The type and configuration of data storage to use. Either type `"memory"`, where no additional configuration is needed and the waypoints are stored in local memory while the Navigation process is running, or `"mongodb"`, where data persists at the specified [MongoDB URI](https://www.mongodb.com/docs/manual/reference/connection-string) of your MongoDB deployment. <br> Default: `"memory"`|
151
+
|`store`| obj |**Required**| The type and configuration of data storage to use. Either type `"memory"`, where no additional configuration is needed and the waypoints are stored in local memory while the navigation process is running, or `"mongodb"`, where data persists at the specified [MongoDB URI](https://www.mongodb.com/docs/manual/reference/connection-string) of your MongoDB deployment. <br> Default: `"memory"`|
152
152
|`base`| string |**Required**| The `name` you have configured for the [base](/components/base/) you are operating with this service. |
153
153
|`movement_sensor`| string |**Required**| The `name` of the [movement sensor](/components/movement-sensor/) you have configured for the base you are operating with this service. |
154
154
|`motion_service`| string | Optional | The `name` of the [motion service](/mobility/motion/) you have configured for the base you are operating with this service. If you have not added a motion service to your robot, the default motion service will be used. Reference this default service in your code with the name `"builtin"`. |
@@ -753,7 +753,7 @@ After configuring the navigation service for your robot, navigate to the **Contr
753
753
754
754
Here, you can toggle the mode of the service between **Manual** and **Waypoint** to start and stop navigation, add waypoints and obstacles, and view the position of your rover base on a map:
755
755
756
-

756
+

0 commit comments