-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DOCS-1825: Document teleop page as how-to #3675
base: main
Are you sure you want to change the base?
Changes from all commits
bc8ed87
499a0f8
4de897a
754f3c6
8c90e8d
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
@@ -0,0 +1,112 @@ | ||||||
--- | ||||||
title: "Configure a teleop workspace" | ||||||
linkTitle: "Configure a teleop workspace" | ||||||
weight: 10 | ||||||
type: "docs" | ||||||
description: "Create and configure a teleop workspace with widgets." | ||||||
images: ["/how-tos/teleop/full-workspace.png"] | ||||||
icon: true | ||||||
tags: ["teleop", "configuration"] | ||||||
languages: [] | ||||||
viamresources: ["sensor", "camera", "movement sensor"] | ||||||
platformarea: ["viz", "data"] | ||||||
level: "Intermediate" | ||||||
date: "2024-11-13" | ||||||
# updated: "2024-08-26" # When the tutorial was last entirely checked | ||||||
cost: "0" | ||||||
--- | ||||||
|
||||||
You can use teleop to create a custom workspace where you can visualize and aggregate data from a machine. | ||||||
You can currently visualize data from a camera, a sensor, or a movement sensor. | ||||||
|
||||||
{{% alert title="In this page" color="info" %}} | ||||||
|
||||||
- [Configure a workspace](#configure-a-workspace) | ||||||
|
||||||
{{% /alert %}} | ||||||
|
||||||
## Prerequisites | ||||||
|
||||||
{{% expand "A configured machine with teleoperable components" %}} | ||||||
|
||||||
Make sure your machine has at least one of the following: | ||||||
|
||||||
- A [camera](/components/camera/) | ||||||
- A [movement sensor](/components/movement-sensor/) | ||||||
- A [sensor](/components/sensor/) | ||||||
|
||||||
See [configure a machine](/how-tos/configure/) for more information. | ||||||
|
||||||
{{% /expand%}} | ||||||
|
||||||
## Configure a workspace | ||||||
|
||||||
{{< table >}} | ||||||
{{% tablestep %}} | ||||||
**1. Create a workspace in the Viam app** | ||||||
|
||||||
Log in to the [Viam app](https://app.viam.com/). | ||||||
|
||||||
Navigate to the **FLEET** page's **TELEOP** tab. | ||||||
Create a workspace by clicking **+ Create workspace**. | ||||||
Give it a name. | ||||||
|
||||||
{{<imgproc src="/how-tos/teleop/blank-workspace.png" resize="800x" style="width: 500px" class="fill aligncenter imgzoom" declaredimensions=true alt="Blank teleop page.">}} | ||||||
|
||||||
{{% /tablestep %}} | ||||||
{{% tablestep %}} | ||||||
**2. Add widgets** | ||||||
|
||||||
Click **Add widget** and select the appropriate widget for your machine. | ||||||
Repeat as many times as necessary. | ||||||
|
||||||
- If you have a camera, select **Camera stream**, which allows you to view a camera stream. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think these should be needed. The UI should be self explanatory from here, shouldn't it? If it isn't this is a place where we should work with Product to improve the UI instead. See notes below There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you mean to suggest removing all of these bullets? Just want to be sure. I agree the UI should be self explanatory There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes |
||||||
Enter the name of your camera. | ||||||
|
||||||
- If you have a movement sensor, select a **GPS map**, which displays the location of a machine on a map. | ||||||
Enter the name of your movement sensor. | ||||||
Toggle **Historic positions** to on to see how position has changed over time. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. did you test this? Does this create a heatmap or how is this visualized? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||||||
|
||||||
- If you have a sensor, select **Stat** to view a single sensor value. | ||||||
Enter the name of the sensor for **Sensor name** and enter the key for the value in **Path**, for example `time_unix`. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think for these it would be good to add a tip for people trying to figure out how to get the path (go to machine's test panel and check the returned json object. should probably also include what to do if it's inside another object) However, this should ideally be a tooltip in the app. Please file the appropriate ticket with a suggestion for copy. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They are going to make it selectable from a dropdown so I think it's not worth filing that as it would quickly be deprecated, does that make sense? @npentrel There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. sounds good |
||||||
Optionally, add **Units** and give the stat a **Widget title**. | ||||||
|
||||||
Then, add that same sensor as a time series graph. | ||||||
Click **Add widget** again and select **Time series**, which allows you to graph sensor values over time. | ||||||
Enter the name of the sensor for **Sensor name**. | ||||||
Give the graph a line title and enter the key for the sensor value in **Path**, for example `time_unix`. | ||||||
Add more lines if your sensor measures multiple values. | ||||||
|
||||||
Now your workspace setup is complete: | ||||||
|
||||||
{{<imgproc src="/how-tos/teleop/configured-workspace.png" resize="700x" style="width: 500px" class="fill aligncenter" declaredimensions=true alt="Teleop workspace with values configured for each of the four widgets.">}} | ||||||
|
||||||
{{% /tablestep %}} | ||||||
{{% tablestep %}} | ||||||
**3. Select a machine** | ||||||
|
||||||
Now, select a machine with which to make your teleop workspace come to life. | ||||||
Select **Monitor** in the top right corner to leave editing mode. | ||||||
Click **Select machine** and select your configured machine. | ||||||
|
||||||
Your dashboard now shows the configured widgets for the data from your machine: | ||||||
|
||||||
{{<imgproc src="/how-tos/teleop/full-workspace.png" resize="900x" style="width: 500px" class="fill aligncenter" declaredimensions=true alt="Teleop workspace with values configured for each of the four widgets on monitor mode.">}} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
You can go back to **Edit** mode and drag and drop the widgets' panes around to edit their appearance. | ||||||
For example: | ||||||
|
||||||
{{<imgproc src="/how-tos/teleop/four-panes.png" resize="900x" style="width: 500px" class="fill aligncenter" declaredimensions=true alt="Teleop workspace with values configured for each of the four widgets on monitor mode with four panes.">}} | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
||||||
{{% /tablestep %}} | ||||||
{{< /table >}} | ||||||
|
||||||
## Next steps | ||||||
|
||||||
Follow more of our how-to guides to do more with the Viam platform: | ||||||
|
||||||
{{< cards >}} | ||||||
{{% card link="/how-tos/detect-people/" %}} | ||||||
{{% card link="/how-tos/drive-rover/" %}} | ||||||
{{% card link="/how-tos/train-deploy-ml/" %}} | ||||||
{{< /cards >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
figure this covers device requirements and viam app requirements? lmk and I can add more but this isn't a super basic thing to do with viam so I figured a tiny bit of cross-linking was ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, I like it