mirror of
https://github.com/orbbec/OrbbecSDK_ROS2.git
synced 2026-10-09 22:29:48 +08:00
deploy: da15b54f99
This commit is contained in:
@@ -18,6 +18,17 @@ Here is the device support list of main branch (v1.x) and v2-main branch (v2.x):
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td rowspan="2" style="text-align: center; font-weight: bold;">Gemini 340</td>
|
||||
<td>Gemini 345</td>
|
||||
<td>not supported</td>
|
||||
<td>recommended for new designs</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Gemini 345Lg</td>
|
||||
<td>not supported</td>
|
||||
<td>recommended for new designs</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td style="text-align: center; font-weight: bold;">Gemini 435Le</td>
|
||||
<td>Gemini 435Le</td>
|
||||
|
||||
@@ -85,7 +85,7 @@ The following are the launch parameters available:
|
||||
|
||||
* Enable the Depth auto exposure priority.
|
||||
* **`mean_intensity_set_point`**
|
||||
* Set the target mean intensity of the Depth image. For example: `mean_intensity_set_point:=100`.
|
||||
* Set the target average intensity of the depth image when auto-exposure is turned on. For example: `mean_intensity_set_point:=100`.
|
||||
> **Note:** This replaces the deprecated `depth_brightness`, which is still supported for backward compatibility.
|
||||
* **`enable_depth_scale`**
|
||||
* Whether to enable depth scaling after setting D2C. `true` means enabled, the default is `true`.
|
||||
@@ -102,8 +102,7 @@ The following are the launch parameters available:
|
||||
* **`ir_ae_max_exposure`**
|
||||
* Set the maximum exposure value for IR auto exposure.
|
||||
* **`ir_brightness`**
|
||||
* Set the IR brightness.
|
||||
|
||||
* Set the target average intensity of the ir image when auto-exposure is turned on.
|
||||
#### Laser / LDP
|
||||
* **`enable_laser`**
|
||||
* Enable the laser. The default value is `true`.
|
||||
@@ -156,10 +155,27 @@ The following are the launch parameters available:
|
||||
|
||||
#### Device-Specific
|
||||
* **`preset_resolution_config`**
|
||||
* Preset resolution configuration for the camera device. Format: "width,height,ir_decimation_factor,depth_decimation_factor". Example: "1280,720,4,4". Only supported on 435Le. Leave empty to disable.
|
||||
* Preset resolution configuration for the camera device. Format: "width,height,ir_decimation_factor,depth_decimation_factor". Example: "1280,720,4,4". Leave empty to disable.
|
||||
> Only supported 435Le.
|
||||
>
|
||||
* **`enable_gmsl_trigger`** / **`gmsl_trigger_fps`**
|
||||
* Enable the gmsl trigger out signal / set gmsl trigger fps. Used for [gmsl camera](../5_advanced_guide/multi_camera/gmsl_camera.md).
|
||||
|
||||
* Enable the gmsl trigger out signal / set gmsl trigger fps.
|
||||
> Only supports [gmsl camera](../5_advanced_guide/multi_camera/gmsl_camera.md).
|
||||
>
|
||||
* **`ae_mode`**
|
||||
* `colorbased`: Automatic exposure based on color flow. `depthbased`: Automatic exposure based on depth flow. **默认值:** `depthbased`
|
||||
> Only supports Gemini 305.
|
||||
>
|
||||
* **`enalbe_sports_mode`**
|
||||
* Whether to enable sports mode. **Default:** `false`
|
||||
> Only supports Gemini 305.
|
||||
>
|
||||
* **`depth_downscale`** / **`left_ir_downscale`** /**`right_ir_downscale`**
|
||||
* Set the downsampling multiple. You can use `ros2 run orbbec_camera list_camera_profile_mode_node` to view the settable resolution. **Default value:** `1`
|
||||
> Only supports Gemini 305.
|
||||
>
|
||||
* **`enable_ptp_config`**
|
||||
* Enable PTP time synchronization. Only for Gemini 335Le. Requires `enable_sync_host_time` to be `false`.
|
||||
|
||||
#### Disparity
|
||||
* **`disparity_to_depth_mode`**
|
||||
@@ -223,8 +239,6 @@ The following are the launch parameters available:
|
||||
|
||||
* Interval (in seconds) for synchronizing the camera time with the host system.
|
||||
> **Note**: This parameter only needs to be set when **`enable_sync_host_time = true`** and **`time_domain = device`**.
|
||||
* **`enable_ptp_config`**
|
||||
* Enable PTP time synchronization. Only for Gemini 335Le. Requires `enable_sync_host_time` to be `false`.
|
||||
* **`enable_frame_sync`**
|
||||
* Enable the frame synchronization.
|
||||
|
||||
|
||||
@@ -1,4 +1,4 @@
|
||||
# All available services for camera control
|
||||
# Available services
|
||||
|
||||
> **Note:** Services related to a specific stream (e.g., `/camera/set_color_*`) are only available if that stream is enabled in the launch file (e.g., `enable_color:=true`).
|
||||
|
||||
|
||||
+1
-2
@@ -1,7 +1,6 @@
|
||||
# Depth work mode switch
|
||||
|
||||
Orbbec SDK ROS 2 supports the depth work mode switch. The depth work mode switch is supported by Gemini 2, Gemini 2 L,
|
||||
and Femto and Femto Bolt cameras.
|
||||
Orbbec SDK ROS 2 supports the depth work mode switch. The depth work mode switch is supported by Gemini 2 and Gemini 2 L.
|
||||
|
||||
- Before starting the camera, depth work mode (depth_work_mode) can be configured for the corresponding xxx.launch.py
|
||||
file's support.
|
||||
|
||||
+1
-1
@@ -7,7 +7,7 @@
|
||||
| High Accuracy | - Depth of high confidence `<br>`- Barely noise depth values `<br>`- Lower fill rate | - Collision avoidance `<br>`- Object scanning |
|
||||
| High Density | - Higher fill rate `<br>`- More tiny objects `<br>`- May suffer from noise depth values | - Object recognition `<br>`- Pick & place `<br>`- Foreground & background animation |
|
||||
| Medium Density | - Balanced performance in fill rate and accuracy `<br>`- In comparison to Default: lower fill rate, better edge quality | - Generic and alternative to Default |
|
||||
| Custom | - User defined Preset `<br>`- Derived from Presets above, with customized modifications, e.g. a new configuration for the post-processing pipeline, modified mean intensity set point of depth AE function, etc. | - Better depth performance achieved using customized configurations in comparison to using predefined presets `<br>`- For well-established custom configurations |
|
||||
| Custom | - User defined Preset `<br>`- Derived from Presets above, with customized modifications `<br>`- e.g. a new configuration for the post-processing pipeline, etc. | - Better depth performance achieved using customized configurations in comparison to using predefined presets `<br>`- For well-established custom configurations |
|
||||
|
||||
Choose the appropriate preset name based on your specific use case and set it as the value for the `device_preset`
|
||||
parameter.
|
||||
|
||||
Reference in New Issue
Block a user