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
Provide a description of the purpose of the module and any relevant information.
3
+
Use [Orbbec cameras](https://www.orbbec.com/products/) compatible with [v2 of the Orbbec SDK](https://github.com/orbbec/pyorbbecsdk/tree/v2-main?tab=readme-ov-file#hardware-products-supported-by-python-sdk).
4
+
This module provides access to the color and depth sensors.
4
5
5
6
## Model viam-labs:camera:orbbec
6
7
7
-
Provide a description of the model and any relevant information.
8
+
Use [Orbbec cameras](https://www.orbbec.com/products/) compatible with [v2 of the Orbbec SDK](https://github.com/orbbec/pyorbbecsdk/tree/v2-main?tab=readme-ov-file#hardware-products-supported-by-python-sdk).
8
9
9
10
### Configuration
10
11
The following attribute template can be used to configure this model:
11
12
12
13
```json
13
14
{
14
-
"attribute_1": <float>,
15
-
"attribute_2": <string>
15
+
"sensors": ["color", "depth"]
16
16
}
17
17
```
18
18
@@ -22,29 +22,31 @@ The following attributes are available for this model:
|`attribute_1`| float | Required | Description of attribute 1 |
26
-
|`attribute_2`| string | Optional | Description of attribute 2 |
25
+
|`sensors`| array | Optional | An array that contains the strings `color` and/or `depth`, defaults to include both. The sensor that comes first in the array is designated the "main sensor" and will be the image that gets returned by `get_image` calls and what will appear in the Control tab on the [Viam app](https://app.viam.com). When both sensors are requested, `get_point_cloud` will be available for use, and `get_images` will return both the color and depth outputs. Additionally, color and depth outputs returned together will always be aligned, have the same height and width, and have the same timestamp. See [Viam's documentation on the Camera API](https://docs.viam.com/components/camera/#api) for more details. |
27
26
28
27
#### Example Configuration
29
28
30
29
```json
31
30
{
32
-
"attribute_1": 1.0,
33
-
"attribute_2": "foo"
31
+
"sensors": ["color"]
34
32
}
35
33
```
36
34
37
-
### DoCommand
35
+
##Troubleshooting
38
36
39
-
If your model implements DoCommand, provide an example payload of each command that is supported and the arguments that can be used. If your model does not implement DoCommand, remove this section.
37
+
**Unable to connect to camera**
40
38
41
-
#### Example DoCommand
39
+
The `first_run.sh` script included in this module should automatically install the `udev` rules for connecting to the camera on Linux devices.
40
+
If there is an issue, try copying `99-obsensor-libusb.rules` in the `scripts/` directory of this repo to `/etc/udev/rules.d/` on the Viam machine and calling the following command on the system:
42
41
43
-
```json
44
-
{
45
-
"command_name": {
46
-
"arg1": "foo",
47
-
"arg2": 1
48
-
}
49
-
}
50
42
```
43
+
sudo udevadm control --reload-rules && sudo udevadm trigger
44
+
```
45
+
46
+
## Development
47
+
48
+
This module depends on the [v2-main branch of the pyorbbecsdk](https://github.com/orbbec/pyorbbecsdk/tree/v2-main) as a git submodule. So use the `--recursive` flag when cloning this repo or `git submodule update --init --recursive` if you've already cloned it.
49
+
50
+
To build this module on the target device (aarch64 or amd64 Linux machines), run `make archive.tar.gz`.
51
+
52
+
To build this module on another platform for a target device, use a tool like [canon](https://github.com/viamrobotics/canon) to run the Make command in the appropriate Docker container: `canon make archive.tar.gz`
0 commit comments