diff --git a/docs/conf.py b/docs/conf.py
index 6927898d..cc28e247 100644
--- a/docs/conf.py
+++ b/docs/conf.py
@@ -1,27 +1,200 @@
# Configuration file for the Sphinx documentation builder.
#
-# For the full list of built-in configuration values, see the documentation:
+# This file only contains a selection of the most common options. For a full
+# list see the documentation:
# https://www.sphinx-doc.org/en/master/usage/configuration.html
+# -- Path setup --------------------------------------------------------------
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#
+# import os
+# import sys
+# sys.path.insert(0, os.path.abspath('.'))
+
+import os
+import shutil
+import sphinx
+
+import recommonmark
+from recommonmark.transform import AutoStructify
+
+# import sphinx_book_theme
+# import sphinx_rtd_theme
+# import furo
+
+
+#choice theme default
+# html_theme = 'sphinx_book_theme'
+html_theme = 'sphinx_rtd_theme'
+# html_theme = "furo"
+
# -- Project information -----------------------------------------------------
-# https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
project = 'OrbbecSDK V2 ROS2 Wrapper'
-copyright = '2025, ORBBEC yalian'
-author = 'ORBBEC yalian'
+# project = """
+# OrbbecSDK ROS2 documentation
+# """
+copyright = '2025, ORBBEC INC. www.orbbec.com.'
+author = 'ORBBEC INC. www.orbbec.com.'
+
# -- General configuration ---------------------------------------------------
-# https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration
+# The master toctree document.
+master_doc = 'index'
-extensions = []
+# Add any Sphinx extension module names here, as strings. They can be
+# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom
+# ones.
+extensions = ['recommonmark',
+ 'sphinx_markdown_tables',
+ 'sphinx.ext.autosectionlabel',
+
+# 'myst_parser',
+]
+
+# The suffix(es) of source filenames.
+# You can specify multiple suffix as a list of string:
+source_suffix = ['.rst', 'rest', '.md', '.MD']
+
+
+# Add any paths that contain templates here, relative to this directory.
templates_path = ['_templates']
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#
+# This is also used if you do content translation via gettext catalogs.
+# Usually you set "language" from the command line for these cases.
+# language = 'zh_CN'
+language = 'en'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+# This pattern also affects html_static_path and html_extra_path.
exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
-
# -- Options for HTML output -------------------------------------------------
-# https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output
-html_theme = 'alabaster'
-html_static_path = ['_static']
+# html_logo = "source/_static/orbbec_logo2.png"
+# html_favicon = "source/_static/orbbec_logo2.png"
+
+#html_logo = "source/_static/orbbec-light_no_colour.svg"
+html_favicon = "source/_static/orbbec_footerlogo_3d_world.svg"
+# html_logo = "source/_static/orbbec_footerlogo_3d_world.svg"
+# html_favicon = "source/_static/orbbec_footerlogo_3d_world.svg"
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['source/_static','source/images']
+
+html_extra_path = ['source/images']
+
+html_theme_options = {
+ # 'analytics_id': 'G-EVD5Z6G6NH',
+ 'collapse_navigation': False,
+ # 启用导航栏的“粘性”头部，这样导航栏会固定在页面顶部
+ 'sticky_navigation': True,
+ # 配置导航栏的深度，-1 表示显示所有层级的标题
+ 'navigation_depth': 5,
+ # 'show_navbar_depth': 4,
+ # 导航栏显示+号
+ 'collapse_navigation': False,
+
+ # 'analytics_anonymize_ip': False,
+ # 'logo_only': False,
+ # 'display_version': True,
+ # 'prev_next_buttons_location': 'bottom',
+ # 'style_external_links': False,
+ # 'vcs_pageview_mode': '',
+ # 'style_nav_header_background': 'white',
+ # # Toc options
+ # 'collapse_navigation': True,
+ # 'sticky_navigation': True,
+ # 'navigation_depth': 5,
+ # 'includehidden': True,
+ # 'titles_only': False
+}
+
+
+
+
+
+
+# # 添加自定义的 JavaScript 文件
+# html_js_files = ["theme.js"]
+
+
+# #不需要添加_static目录，加了会不起作用
+html_css_files = ["custom.css"]
+
+# 与文档无关的其他资源的路径，由于无需构建此文件夹的文件，会自动忽略
+# 默认情况下，此路径下的文件会输出到生成的html的根目录
+# html_extra_path = ["_extra"]
+
+# 在页面底部显示上一次更新于某某时间
+html_last_updated_fmt = "%Y-%m-%d %H:%M:%S"
+
+# 以下为 sphinx_book_theme 的主题配置/定制（sphinx_book_theme）
+# html_theme_options = {
+# # ----------------主题内容中导航栏的功能按钮配置--------
+# # 添加存储库链接
+# "repository_url": "https://github.com/Eugene-Forest/NoteBook",
+# # 添加按钮以链接到存储库
+# "use_repository_button": True,
+# # 要添加按钮以打开有关当前页面的问题
+# "use_issues_button": True,
+# # 添加一个按钮来建议编辑
+# "use_edit_page_button": True,
+# # 默认情况下，编辑按钮将指向master分支，但如果您想更改此设置，请使用以下配置
+# "repository_branch": "main",
+# # 默认情况下，编辑按钮将指向存储库的根目录；而我们 sphinx项目的 doc文件其实是在 source 文件夹下的，包括 conf.py 和 index(.rst) 主目录
+# "path_to_docs": "source",
+# # 您可以添加 use_download_button 按钮，允许用户以多种格式下载当前查看的页面
+# "use_download_button": True,
+
+# # --------------------------右侧辅助栏配置---------
+# # 重命名右侧边栏页内目录名，标题的默认值为Contents。
+# "toc_title": "页内目录",
+# # 通常，右侧边栏页内目录中仅显示页面的第 2 级标题，只有当它们是活动部分的一部分时（在屏幕上滚动时），才会显示更深的级别。可以使用以下配置显示更深的级别，指示应显示多少级别
+# "show_toc_level": 2,
+
+# # --------------------------左侧边栏配置--------------
+# # logo 配置
+# "logo_only": True,
+# # 控制左侧边栏列表的深度展开,默认值为1，它仅显示文档的顶级部分
+# "show_navbar_depth": 1,
+# # 自定义侧边栏页脚,默认为 Theme by the Executable Book Project
+# # "extra_navbar": "
Your HTML
",
+# "home_page_in_toc": True,
+# # ------------------------- 单页模式 -----------------
+# # 如果您的文档只有一个页面，并且您不需要左侧导航栏，那么您可以 使用以下配置将其配置sphinx-book-theme 为以单页模式运行
+# # "single_page": True,
+# }
+
+# 是否显示页面下方的由sphinx创建, 默认为True
+html_show_sphinx = False
+
+# Function to copy video files to output directory
+def setup(app):
+ app.connect('build-finished', copy_videos)
+
+def copy_videos(app, exception):
+ if exception is None: # Only copy if build succeeded
+ src_dir = os.path.join(app.srcdir, '_static/videos')
+ dest_dir = os.path.join(app.outdir, '_static/videos')
+ if os.path.exists(src_dir):
+ shutil.copytree(src_dir, dest_dir)
+
+# 20201030
+def setup(app):
+ app.add_config_value('recommonmark_config', {
+ 'url_resolver': lambda url: github_doc_root + url,
+ 'auto_toc_tree_section': 'Contents',
+ }, True)
+ app.add_transform(AutoStructify)
diff --git a/docs/index.rst b/docs/index.rst
index 7a050be4..e58482a8 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -12,6 +12,12 @@ documentation for details.
.. toctree::
- :maxdepth: 2
- :caption: Contents:
+ :maxdepth: 3
+ :numbered:
+ source/1_overview/overview.rst
+ source/2_installation/installation.rst
+ source/3_quickstarts/quickstarts.rst
+ source/4_application_guide/application_guide.rst
+ source/5_advanced_guide/advanced_guide.rst
+ source/6_FAQ/FAQ.rst
diff --git a/docs/requirements.txt b/docs/requirements.txt
new file mode 100755
index 00000000..ea30deb3
--- /dev/null
+++ b/docs/requirements.txt
@@ -0,0 +1,20 @@
+# markdown suport
+recommonmark
+# markdown table suport
+sphinx-markdown-tables
+
+# theme default rtd
+
+# crate-docs-theme
+sphinx-rtd-theme
+
+doc8
+docutils
+pip
+sphinx
+sphinx-copybutton
+sphinx-lint
+sphinx-multiversion
+sphinx-rtd-theme
+sphinx-tabs
+sphinxcontrib-mermaid
\ No newline at end of file
diff --git a/docs/source/1_overview/introduction.md b/docs/source/1_overview/introduction.md
index d4061ecd..378fe943 100644
--- a/docs/source/1_overview/introduction.md
+++ b/docs/source/1_overview/introduction.md
@@ -8,59 +8,30 @@ If you are a user in China, it is recommended to use [gitee Repo](https://gitee.
## Support Hardware Products
-This document is based on the v2-main branch code, which is a Python Wrapper built on Orbbec SDK v2. It supports the following devices.
-If your device is included in this supported list, we recommend using the v2-main branch. If not, you can use the main branch instead.
+The following devices are supported by the OrbbecSDK ROS2 Wrapper v2-main branch. More devices support will be added in the near future. If you can not find your device in the table below, try the [main](https://github.com/orbbec/OrbbecSDK_ROS2) branch.
-| **Products List** | **Minimal Firmware Version** |
-|-------------------|------------------------------|
-| Gemini 435Le | 1.2.04 |
-| Gemini 335Le | 1.5.31 |
-| Gemini 330 | 1.2.20 |
-| Gemini 330L | 1.2.20 |
-| Gemini 335 | 1.2.20 |
-| Gemini 335L | 1.2.20 |
-| Gemini 336 | 1.2.20 |
-| Gemini 336L | 1.2.20 |
-| Gemini 335Lg | 1.3.46 |
-| Femto Bolt | 1.1.2 |
-| Femto Mega | 1.3.0 |
-| Femto Mega I | 2.0.4 |
-| Astra 2 | 2.8.20 |
-| Gemini 2 L | 1.4.53 |
-| Gemini 2 | 1.4.92 |
-| Gemini 215 | 1.0.9 |
-| Gemini 210 | 1.0.9 |
+For optimal performance, we strongly recommend updating to the latest firmware version. This ensures that you benefit from the most recent enhancements and bug fixes.
-the main branch supports the following devices:
-
-
-| **Products List** | **Minimal Firmware Version** |
-|-------------------|-----------------------------|
-| Gemini 330 | 1.2.20 |
-| Gemini 330L | 1.2.20 |
-| Gemini 335 | 1.2.20 |
-| Gemini 335L | 1.2.20 |
-| Gemini 336 | 1.2.20 |
-| Gemini 336L | 1.2.20 |
-| Femto Bolt | 1.0.6 |
-| Femto Mega | 1.1.7 |
-| Femto Mega I | 2.0.2 |
-| Gemini 2 XL | Obox: V1.2.5 VL:1.4.54 |
-| Astra 2 | 2.8.20 |
-| Gemini 2 L | 1.4.32 |
-| Gemini 2 | 1.4.60 |
-| Astra+ | 1.0.19 |
-| Femto | 1.6.7 |
-| Femto W | 1.1.8 |
-| DaBai | 2436 |
-| DaBai DCW | 2460 |
-| DaBai DW | 2606 |
-| Astra Mini Pro | 1007 |
-| Gemini E | 3460 |
-| Gemini E Lite | 3606 |
-| Gemini | 3018 |
-| Astra Mini S Pro | 1005 |
+| Product List | Minimal Firmware Version | **Launch File** |
+| :------------- | :----------------------- | :-------------------------- |
+| Gemini 435Le | 1.2.04 | gemini435_le.launch.py |
+| Gemini 335 | 1.2.20 | gemini_330_series.launch.py |
+| Gemini 336 | 1.2.20 | gemini_330_series.launch.py |
+| Gemini 335L | 1.2.20 | gemini_330_series.launch.py |
+| Gemini 336L | 1.2.20 | gemini_330_series.launch.py |
+| Gemini 335Lg | 1.3.46 | gemini_330_series.launch.py |
+| Gemini 335Le | 1.5.31 | gemini_330_series.launch.py |
+| Gemini 330 | 1.2.20 | gemini_330_series.launch.py |
+| Gemini 330L | 1.2.20 | gemini_330_series.launch.py |
+| Gemini 2 | 1.4.92 | gemini2.launch.py |
+| Gemini 2 L | 1.4.53 | gemini2L.launch.py |
+| Femto Bolt | 1.1.2 | femto_bolt.launch.py |
+| Femto Mega | 1.3.0 | femto_mega.launch.py |
+| Astra 2 | 2.8.20 | astra2.launch.py |
+| Astra Mini Pro | 2.0.01 | astra.launch.py |
+All launch files are essentially similar, with the primary difference being the default values of the parameters set
+for different models within the same series. Differences in USB standards, such as USB 2.0 versus USB 3.0, may require adjustments to these parameters. If you encounter a startup failure, please carefully review the specification manual. Pay special attention to the resolution settings in the launch file, as well as other parameters, to ensure compatibility and optimal performance.
## Support Platforms
diff --git a/docs/source/1_overview/overview.rst b/docs/source/1_overview/overview.rst
new file mode 100644
index 00000000..a79b9f4c
--- /dev/null
+++ b/docs/source/1_overview/overview.rst
@@ -0,0 +1,11 @@
+Overview
+======================================================
+
+This chapter provides an overview of the Orbbec SDK, including supported products, main features, and architecture.
+
+.. toctree::
+ :maxdepth: 2
+
+ introduction.md
+ orbbecsdk_overview.md
+
diff --git a/docs/source/2_installation/build_the_package.md b/docs/source/2_installation/build_the_package.md
index 4dacc472..02368207 100644
--- a/docs/source/2_installation/build_the_package.md
+++ b/docs/source/2_installation/build_the_package.md
@@ -1,7 +1,5 @@
### 2.2. Build from Source
-If no wheel package is available, or if you want to build with the latest source code, follow these steps:
-
#### 2.2.1. Environment
Install ROS 2 according to the official guide:
@@ -49,4 +47,3 @@ cd ~/ros2_ws
colcon build --event-handlers console_direct+ --cmake-args -DCMAKE_BUILD_TYPE=Release
```
-
diff --git a/docs/source/2_installation/installation.rst b/docs/source/2_installation/installation.rst
new file mode 100644
index 00000000..a603dbd1
--- /dev/null
+++ b/docs/source/2_installation/installation.rst
@@ -0,0 +1,11 @@
+Installation
+======================================================
+
+This chapter explains how to install the Orbbec ROS2 Python SDK, including building from source, installing dependencies, and using registration scripts.
+
+.. toctree::
+ :maxdepth: 2
+
+ build_the_package.md
+ registration_script.md
+
diff --git a/docs/source/3_quickstarts/quickstart.md b/docs/source/3_quickstarts/quickstart.md
new file mode 100644
index 00000000..62b000a7
--- /dev/null
+++ b/docs/source/3_quickstarts/quickstart.md
@@ -0,0 +1,92 @@
+## QuickStarts
+
+### 3.1. Introduction
+
+This section provides a quick start to using the Orbbec ROS 2 wrapper.
+You will learn how to:
+
+* Launch a camera node.
+* Visualize depth/color streams in **RViz2**.
+* Interact with topics and services using **ROS 2 CLI tools**.
+
+---
+
+### 3.2. Build your First Camera Application
+
+#### Step 1: Source ROS 2 and Workspace
+
+Make sure ROS 2 and your workspace environment are sourced:
+
+```bash
+source /opt/ros/$ROS_DISTRO/setup.bash
+source ~/ros2_ws/install/setup.bash
+```
+
+#### Step 2: Launch the Camera Node
+
+- On terminal 1
+
+```bash
+. ./install/setup.bash
+ros2 run orbbec_camera list_devices_node #Check if the camera is connected
+ros2 launch orbbec_camera gemini_330_series.launch.py # Or other launch file, see below table
+```
+
+If you have multiple cameras connected, you can specify the **serial number**:
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py serial_number:=
+```
+
+#### Step 3: Visualize in RViz2
+
+Launch RViz2 and load the default config:
+
+- On terminal 2
+
+```bash
+rviz2
+```
+
+* Add an **Image** display, set topic to `/camera/color/image_raw`.
+* Add another **Image** display for `/camera/depth/image_raw`.
+* Optionally, add a **PointCloud2** display for `/camera/depth/points`.
+
+You should now see the color stream, depth stream, and 3D point cloud in RViz2.
+
+---
+
+### 3.3. Sample Features
+
+After the node is running, try some ROS 2 CLI commands:
+
+#### 3.3.1. List available topics / services/ parameters
+
+```bash
+ros2 topic list
+ros2 service list
+ros2 param list
+```
+
+#### 3.3.2. Echo a topic
+
+View depth camera data:
+
+```bash
+ros2 topic echo /camera/depth/camera_info
+```
+
+#### 3.3.3. Call a service
+
+For example, get device Information:
+
+```bash
+ros2 service call /camera/get_device_info orbbec_camera_msgs/srv/GetDeviceInfo '{}'
+```
+
+#### 3.3.4. Record with rosbag2
+
+```bash
+ros2 bag record /camera/color/image_raw /camera/depth/image_raw
+```
+
diff --git a/docs/source/3_quickstarts/quickstarts.rst b/docs/source/3_quickstarts/quickstarts.rst
new file mode 100644
index 00000000..d245876e
--- /dev/null
+++ b/docs/source/3_quickstarts/quickstarts.rst
@@ -0,0 +1,10 @@
+Quickstarts
+======================================================
+
+This chapter provides quick start guides for the SDK, allowing users to run basic example programs quickly.
+
+.. toctree::
+ :maxdepth: 2
+
+ quickstart.md
+
diff --git a/docs/source/4_application_guide/application_guide.rst b/docs/source/4_application_guide/application_guide.rst
new file mode 100644
index 00000000..ca9ddb30
--- /dev/null
+++ b/docs/source/4_application_guide/application_guide.rst
@@ -0,0 +1,12 @@
+Application Guide
+======================================================
+
+This chapter introduces application development with the SDK, including launch parameter configuration, ROS2 services, and topics usage.
+
+.. toctree::
+ :maxdepth: 2
+
+ launch_parameters.md
+ services.md
+ topics.md
+
diff --git a/docs/source/4_application_guide/launch_parameters.md b/docs/source/4_application_guide/launch_parameters.md
new file mode 100644
index 00000000..a37114e0
--- /dev/null
+++ b/docs/source/4_application_guide/launch_parameters.md
@@ -0,0 +1,262 @@
+# Launch parameters
+
+> If you are not sure how to set the parameters, you can connect the orbbec camera and open the [OrbbecViewer](https://github.com/orbbec/OrbbecSDK/releases).
+
+The following are the launch parameters available:
+
+### Core & Stream Configuration
+
+* **`camera_name`**
+ * Start the node namespace.
+
+* **`depth_registration`**
+ * Enable alignment of the depth frame to the color frame. This field is required when the `enable_colored_point_cloud` is set to `true`.
+
+* **`serial_number`**
+ * The serial number of the camera. This is required when multiple cameras are used.
+
+* **`usb_port`**
+ * The USB port of the camera. This is required when multiple cameras are used.
+
+* **`device_num`**
+ * The number of devices. This must be filled in if multiple cameras are required.
+
+* **`[color|depth|left_ir|right_ir|ir]_[width|height|fps|format]`**
+ * The resolution and frame rate of the sensor stream.
+
+* **`[color|depth|left_ir|right_ir|ir]_rotation`**
+ * Set stream image rotation.
+ * The possible values are `0`, `90`, `180`, `270`.
+
+* **`[color|depth|left_ir|right_ir|ir]_flip`**
+ * Enable the stream image flip.
+
+* **`[color|depth|left_ir|right_ir|ir]_mirror`**
+ * Enable the stream image mirror.
+
+* **`enable_point_cloud`**
+ * Enable the point cloud.
+
+* **`enable_colored_point_cloud`**
+ * Enable the RGB point cloud.
+
+* **`cloud_frame_id`**
+ * Modify the `frame_id` name within the ros message.
+
+* **`ordered_pc`**
+ * Enable filtering of invalid point clouds.
+
+* **`align_mode`**
+ * The alignment mode to be used. Options are `HW` for hardware alignment and `SW` for software alignment.
+
+* **`align_target_stream`**
+ * Set align target stream mode.
+ * The possible values are `COLOR`, `DEPTH`.
+ * `COLOR`: Align depth to color.
+ * `DEPTH`: Align color to depth.
+
+* **`point_cloud_qos`, `[stream]_qos`, `[stream]_camera_info_qos`**
+ * ROS 2 Message Quality of Service (QoS) settings. The possible values are `SYSTEM_DEFAULT`, `DEFAULT`, `PARAMETER_EVENTS`, `SERVICES_DEFAULT`, `PARAMETERS`, `SENSOR_DATA` and are case-insensitive. These correspond to `rmw_qos_profile_system_default`, `rmw_qos_profile_default`, `rmw_qos_profile_parameter_events`, `rmw_qos_profile_services_default`, `rmw_qos_profile_parameters`, and `SENSOR_DATA`, respectively.
+
+### Sensor Controls
+
+#### Color Stream
+* **`enable_color_auto_exposure`**
+ * Enable the Color auto exposure.
+* **`enable_color_auto_exposure_priority`**
+ * Enable the Color auto exposure priority.
+* **`color_exposure`**
+ * Set the Color exposure.
+* **`color_gain`**
+ * Set the Color gain.
+* **`enable_color_auto_white_balance`**
+ * Enable the Color auto white balance.
+* **`color_white_balance`**
+ * Set the Color white balance.
+* **`color_ae_max_exposure`**
+ * Set the maximum exposure value for Color auto exposure.
+* **`color_brightness`**, **`color_sharpness`**, **`color_gamma`**, **`color_saturation`**, **`color_contrast`**, **`color_hue`**
+ * Set the Color brightness, sharpness, gamma, saturation, contrast, and hue.
+* **`enable_color_backlight_compensation`**
+ * Enable the Color backlight compensation.
+* **`color_powerline_freq`**
+ * Set the power line freq. The possible values are `disable`, `50hz`, `60hz`, `auto`.
+* **`enable_color_decimation_filter`** / **`color_decimation_filter_scale`**
+ * Enable the Color decimation filter and set its scale.
+* **`color_ae_roi_[left|right|top|bottom]`**
+ * Set Color auto exposure ROI.
+
+#### Depth Stream
+* **`enable_depth_auto_exposure_priority`**
+ * 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`.
+ > **Note:** This replaces the deprecated `depth_brightness`, which is still supported for backward compatibility.
+* **`enable_depth_scale`**
+ * Enable the depth scale.
+* **`depth_precision`**
+ * The depth precision should be in the format `1mm`. The default value is `1mm`.
+* **`depth_ae_roi_[left|right|top|bottom]`**
+ * Set Depth auto exposure ROI.
+
+#### IR Stream
+* **`enable_ir_auto_exposure`**
+ * Enable the IR auto exposure.
+* **`ir_exposure`** / **`ir_gain`**
+ * Set the IR exposure and gain.
+* **`ir_ae_max_exposure`**
+ * Set the maximum exposure value for IR auto exposure.
+* **`ir_brightness`**
+ * Set the IR brightness.
+
+#### Laser / LDP
+* **`enable_laser`**
+ * Enable the laser. The default value is `true`.
+* **`laser_energy_level`**
+ * Set the laser energy level.
+* **`enable_ldp`** / **`ldp_power_level`**
+ * Enable the LDP and set its power level.
+
+### Device, Sync & Advanced Features
+
+#### Multi-Camera Synchronization
+* **`sync_mode`**
+ * Set sync mode. The default value is `standalone`.
+* **`depth_delay_us`** / **`color_delay_us`**
+ * The delay time (microseconds) of the depth/color image capture after receiving the capture command or trigger signal.
+* **`trigger2image_delay_us`**
+ * The delay time (microseconds) of the image capture after receiving the capture command or trigger signal. Us
+* **`trigger_out_delay_us`**
+ * The delay time (microseconds) of the trigger signal output after receiving the capture command or trigger signal.
+* **`trigger_out_enabled`**
+ * Enable the trigger out signal.
+* **`software_trigger_enabled`** / **`software_trigger_period`**
+ * Enable the software trigger out signal / set the software trigger period in ms.
+* **`frames_per_trigger`**
+ * The frame number of each stream after each trigger in triggering mode.
+
+> Used for [multi camera synced](../5_advanced_guide/multi_camera_synced.md).
+
+#### Network Cameras
+* **`enumerate_net_device`**
+ * Enable automatically enumerate network devices. Used for [net camera](../orbbec_camera/examples/net_camera/README.MD).
+* **`net_device_ip`** / **`net_device_port`**
+ * Set net device's IP address and port (Usually `8090`). Used for [net camera](../orbbec_camera/examples/net_camera/README.MD).
+
+#### Device-Specific
+* **`device_preset`**
+ * The default value is `Default`. Only the G330 series is supported. For more information, refer to the [G330 documentation](https://www.orbbec.com/docs/g330-use-depth-presets/). The value should be one of the preset names listed [in the table](./predefined_presets.md).
+* **`enable_gmsl_trigger`** / **`gmsl_trigger_fps`**
+ * Enable the gmsl trigger out signal / set gmsl trigger fps. Used for [gmsl camera](../orbbec_camera/examples/gmsl_camera/README.MD).
+
+#### Disparity
+* **`disparity_to_depth_mode`**
+ * `HW`: use hardware disparity to depth conversion. `SW`: use software disparity to depth conversion.
+* **`disparity_range_mode`**, **`disparity_search_offset`**, **`disparity_offset_config`**
+ * Parameters for disparity search offset. Used for [disparity search offset](../orbbec_camera/examples/disparity_search_offset/README.MD).
+
+#### Interleave AE Mode
+* **`interleave_ae_mode`**
+ * Set `laser` or `hdr` interleave.
+* **`interleave_frame_enable`**, **`interleave_skip_enable`**, **`interleave_skip_index`**
+ * Parameters to control interleave frame mode.
+* **`[hdr|laser]_index[0|1]_[...]`**
+ * In interleave frame mode, set the 0th and 1st frame parameters of hdr or laser interleaving frames.
+* *All interleave parameters are used for [interleave ae mode](../orbbec_camera/examples/interleave_ae_mode/README.MD).*
+
+### Basic & General Parameters
+
+#### Firmware & Backend
+* **`upgrade_firmware`**
+ * The input parameter is the firmware path.
+* **`preset_firmware_path`**
+ * The input parameter is the preset firmware path. If multiple paths are input, each path needs to be separated by `,` and a maximum of 3 firmware paths can be input.
+* **`uvc_backend`**
+ * Optional values: `v4l2`, `libuvc`.
+* **`connection_delay`**
+ * The delay time in milliseconds for reopening the device. Some devices, such as Astra mini, require a longer time to initialize and reopening the device immediately can cause firmware crashes when hot plugging.
+* **`retry_on_usb3_detection_failure`**
+ * If the camera is connected to a USB 2.0 port and is not detected, the system will attempt to reset the camera up to three times. It is recommended to set this parameter to `false` when using a USB 2.0 connection to avoid unnecessary resets.
+
+#### TF, Extrinsics & Calibration
+* **`publish_tf`** / **`tf_publish_rate`**
+ * Enable the TF publish and set its publication rate.
+* **`enable_publish_extrinsic`**
+ * Enable the extrinsics publish.
+* **`ir_info_url`** / **`color_info_url`**
+ * Set URL of the IR/color camera info.
+* **`enable_color_undistortion`**
+ * Enable the Color undistortion.
+
+#### Time Synchronization
+* **`enable_sync_host_time`**
+ * Enable synchronization of the host time with the camera time. The default value is `true`. If using global time, set to `false`.
+* **`time_domain`**
+ * Select timestamp type: `device`, `global`, and `system`.
+* **`time_sync_period`**
+ * 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.
+
+#### Logging & Diagnostics
+* **`log_level`**
+ * SDK log level. Default is `info`. Optional values: `debug`, `info`, `warn`, `error`, `fatal`.
+* **`diagnostic_period`**
+ * Diagnostic period in seconds.
+* **`enable_heartbeat`**
+ * Enable the heartbeat function. Default is `false`. If `true`, the camera node will send heartbeat signals to the firmware.
+
+#### Miscellaneous
+* **`config_file_path`**
+ * The path to the YAML configuration file. Default is `""`. If not specified, default parameters from the launch file will be used.
+* **`frame_aggregate_mode`**
+ * Set frame aggregate output mode. Optional values: `full_frame`, `color_frame`, `ANY`, `disable`.
+* **`enable_d2c_viewer`**
+ * Publishes the D2C overlay image (for testing only).
+
+### IMU
+
+* **`enable_accel`** / **`enable_gyro`**
+ * Enable the Accelerometer/gyroscope and output its info topic data.
+* **`enable_sync_output_accel_gyro`**
+ * Enable the sync `accel_gyro`, and output IMU topic real-time data.
+* **`accel_rate`** / **`gyro_rate`**
+ * The frequency of the accelerometer/gyroscope. Values range from `1.5625hz` to `32khz`.
+* **`accel_range`** / **`gyro_range`**
+ * The range of the accelerometer (`2g`, `4g`, `8g`, `16g`) and gyroscope (`16dps` to `2000dps`).
+* **`enable_accel_data_correction`** / **`enable_gyro_data_correction`**
+ * Enable data correction for the accelerometer/gyroscope.
+* **`linear_accel_cov`** / **`angular_vel_cov`**
+ * Covariance of the linear acceleration and angular velocity.
+
+### Depth Filters
+
+* **`enable_decimation_filter`**
+ * Enable the Depth decimation filter. Set with `decimation_filter_scale`.
+* **`enable_hdr_merge`**
+ * Enable the Depth hdr merge filter. Set with `hdr_merge_exposure_1`, etc.
+* **`enable_sequence_id_filter`**
+ * Enable the Depth sequence id filter. Set with `sequence_id_filter_id`.
+* **`enable_threshold_filter`**
+ * Enable the Depth threshold filter. Set with `threshold_filter_max`, `threshold_filter_min`.
+* **`enable_hardware_noise_removal_filter`**
+ * Enable the Depth hardware noise removal filter.
+* **`enable_noise_removal_filter`**
+ * Enable the Depth software noise removal filter. Set with `noise_removal_filter_min_diff`, etc.
+* **`enable_spatial_filter`**
+ * Enable the Depth spatial filter. Set with `spatial_filter_alpha`, etc.
+* **`enable_temporal_filter`**
+ * Enable the Depth temporal filter. Set with `temporal_filter_diff_threshold`, etc.
+* **`enable_hole_filling_filter`**
+ * Enable the Depth hole filling filter. Set with `hole_filling_filter_mode`.
+* **`enable_spatial_fast_filter`**
+ * Enable the Depth spatial fast filter. Set with `spatial_fast_filter_radius`.
+* **`enable_spatial_moderate_filter`**
+ * Enable the Depth spatial moderate filter. Set with `spatial_moderate_filter_diff_threshold`, etc.
+
+---
+
+> **_IMPORTANT_**: Please carefully read the instructions regarding software filtering settings at [this link](https://www.orbbec.com/docs/g330-use-depth-post-processing-blocks/). If you are uncertain, do not modify these settings.
diff --git a/docs/source/4_application_guide/services.md b/docs/source/4_application_guide/services.md
new file mode 100644
index 00000000..a2cc7f34
--- /dev/null
+++ b/docs/source/4_application_guide/services.md
@@ -0,0 +1,209 @@
+# All available services for camera control
+
+> **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`).
+
+### Stream Control
+
+#### Color Stream
+* `/camera/toggle_color`
+ ```bash
+ ros2 service call /camera/toggle_color std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/get_color_exposure` & `/camera/get_color_gain`
+ ```bash
+ ros2 service call /camera/get_color_exposure orbbec_camera_msgs/srv/GetInt32 '{}'
+ ros2 service call /camera/get_color_gain orbbec_camera_msgs/srv/GetInt32 '{}'
+ ```
+* `/camera/set_color_auto_exposure`
+ ```bash
+ ros2 service call /camera/set_color_auto_exposure std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/set_color_exposure` & `/camera/set_color_gain`
+ ```bash
+ ros2 service call /camera/set_color_exposure orbbec_camera_msgs/srv/SetInt32 '{data: 1}'
+ ros2 service call /camera/set_color_gain orbbec_camera_msgs/srv/SetInt32 '{data: 64}'
+ ```
+* `/camera/set_color_mirror`, `/camera/set_color_flip`, `/camera/set_color_rotation`
+ ```bash
+ ros2 service call /camera/set_color_mirror std_srvs/srv/SetBool '{data: true}'
+ ros2 service call /camera/set_color_flip std_srvs/srv/SetBool '{data: true}'
+ ros2 service call /camera/set_color_rotation orbbec_camera_msgs/srv/SetInt32 '{data: 180}'
+ ```
+* `/camera/set_color_ae_roi`
+ ```bash
+ # data_param: [Left, Right, Top, Bottom]
+ ros2 service call /camera/set_color_ae_roi orbbec_camera_msgs/srv/SetArrays '{data_param: [0,1279,0,719]}'
+ ```
+
+#### Depth Stream
+* `/camera/toggle_depth`
+ ```bash
+ ros2 service call /camera/toggle_depth std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/get_depth_exposure` & `/camera/get_depth_gain`
+ ```bash
+ ros2 service call /camera/get_depth_exposure orbbec_camera_msgs/srv/GetInt32 '{}'
+ ros2 service call /camera/get_depth_gain orbbec_camera_msgs/srv/GetInt32 '{}'
+ ```
+* `/camera/set_depth_auto_exposure`
+ ```bash
+ ros2 service call /camera/set_depth_auto_exposure std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/set_depth_exposure` & `/camera/set_depth_gain`
+ ```bash
+ ros2 service call /camera/set_depth_exposure orbbec_camera_msgs/srv/SetInt32 '{data: 3000}'
+ ros2 service call /camera/set_depth_gain orbbec_camera_msgs/srv/SetInt32 '{data: 64}'
+ ```
+* `/camera/set_depth_mirror`, `/camera/set_depth_flip`, `/camera/set_depth_rotation`
+ ```bash
+ ros2 service call /camera/set_depth_mirror std_srvs/srv/SetBool '{data: true}'
+ ros2 service call /camera/set_depth_flip std_srvs/srv/SetBool '{data: true}'
+ ros2 service call /camera/set_depth_rotation orbbec_camera_msgs/srv/SetInt32 '{data: 180}'
+ ```
+* `/camera/set_depth_ae_roi`
+ ```bash
+ # data_param: [Left, Right, Top, Bottom]
+ ros2 service call /camera/set_depth_ae_roi orbbec_camera_msgs/srv/SetArrays '{data_param: [0,847,0,479]}'
+ ```
+
+#### IR Stream
+* `/camera/toggle_ir`
+
+ ```bash
+ ros2 service call /camera/toggle_ir std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/get_ir_exposure` & `/camera/get_ir_gain`
+ ```bash
+ ros2 service call /camera/get_ir_exposure orbbec_camera_msgs/srv/GetInt32 '{}'
+ ros2 service call /camera/get_ir_gain orbbec_camera_msgs/srv/GetInt32 '{}'
+ ```
+* `/camera/set_ir_auto_exposure`
+ ```bash
+ ros2 service call /camera/set_ir_auto_exposure std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/set_ir_exposure` & `/camera/set_ir_gain`
+ ```bash
+ ros2 service call /camera/set_ir_exposure orbbec_camera_msgs/srv/SetInt32 '{data: 3000}'
+ ros2 service call /camera/set_ir_gain orbbec_camera_msgs/srv/SetInt32 '{data: 64}'
+ ```
+* `/camera/switch_ir`
+ ```bash
+ ros2 service call /camera/switch_ir orbbec_camera_msgs/srv/SetString '{data: left}'
+ ```
+
+#### All Streams
+* `/camera/get_streams_enable` & `/camera/set_streams_enable`
+ ```bash
+ ros2 service call /camera/get_streams_enable orbbec_camera_msgs/srv/GetBool '{}'
+ ros2 service call /camera/set_streams_enable std_srvs/srv/SetBool '{data: false}'
+ ```
+
+### Sensor & Emitter Control
+
+* `/camera/set_auto_white_balance` & `/camera/get_auto_white_balance`
+ ```bash
+ ros2 service call /camera/set_auto_white_balance std_srvs/srv/SetBool '{data: true}'
+ ros2 service call /camera/get_auto_white_balance orbbec_camera_msgs/srv/GetInt32 '{}'
+ ```
+* `/camera/set_white_balance` & `/camera/get_white_balance`
+ ```bash
+ ros2 service call /camera/set_white_balance orbbec_camera_msgs/srv/SetInt32 '{data: 2800}'
+ ros2 service call /camera/get_white_balance orbbec_camera_msgs/srv/GetInt32 '{}'
+ ```
+* `/camera/set_laser_enable`
+ ```bash
+ ros2 service call /camera/set_laser_enable std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/set_ldp_enable` & `/camera/get_ldp_status`
+ ```bash
+ ros2 service call /camera/set_ldp_enable std_srvs/srv/SetBool '{data: true}'
+ ros2 service call /camera/get_ldp_status orbbec_camera_msgs/srv/GetBool '{}'
+ ```
+* `/camera/set_fan_work_mode`
+ ```bash
+ ros2 service call /camera/set_fan_work_mode orbbec_camera_msgs/srv/SetInt32 '{data: 0}'
+ ```
+* `/camera/set_floor_enable`
+ ```bash
+ ros2 service call /camera/set_floor_enable std_srvs/srv/SetBool '{data: true}'
+ ```
+
+### Device Information & Management
+
+* `/camera/get_device_info`
+ ```bash
+ ros2 service call /camera/get_device_info orbbec_camera_msgs/srv/GetDeviceInfo
+ ```
+* `/camera/get_sdk_version`
+ ```bash
+ ros2 service call /camera/get_sdk_version orbbec_camera_msgs/srv/GetString
+ ```
+* `/camera/reboot_device`
+ ```bash
+ ros2 service call /camera/reboot_device std_srvs/srv/Empty '{}'
+ ```
+
+### Synchronization & Triggering
+
+* `/camera/send_software_trigger`
+ ```bash
+ ros2 service call /camera/send_software_trigger std_srvs/srv/SetBool '{data: true}'
+ ```* `/camera/set_reset_timestamp`
+ ```bash
+ # Only available when time_domain param is set to device
+ ros2 service call /camera/set_reset_timestamp std_srvs/srv/SetBool '{data: true}'
+ ```
+* `/camera/set_sync_interleaverlaser`
+ ```bash
+ # Only available if interleave_ae_mode is 'laser' and interleave_frame_enable is true
+ ros2 service call /camera/set_sync_interleaverlaser orbbec_camera_msgs/srv/SetInt32 '{data: 0}'
+ ```
+
+### Depth Filter Configuration
+
+* `/camera/set_filter`
+ ```bash
+ # Set DecimationFilter
+ ros2 service call /camera/set_filter orbbec_camera_msgs/srv/SetFilter '{filter_name: DecimationFilter, filter_enable: false, filter_param: [5]}'
+ # Set SpatialAdvancedFilter
+ ros2 service call /camera/set_filter orbbec_camera_msgs/srv/SetFilter '{filter_name: SpatialAdvancedFilter, filter_enable: true, filter_param: [0.5,160,1,8]}'
+ ```
+
+### Data Capture & Calibration Management
+
+* `/camera/save_images`
+ ```bash
+ ros2 service call /camera/save_images std_srvs/srv/Empty '{}'
+ ```
+* `/camera/save_point_cloud`
+ ```bash
+ ros2 service call /camera/save_point_cloud std_srvs/srv/Empty '{}'
+ ```
+
+> **Note**: The following services are currently supported only on the 435Le module. Each service can store only one set of data or string at a time.
+
+* `/camera/write_customer_data` & `/camera/read_customer_data`
+ ```bash
+ ros2 service call /camera/write_customer_data orbbec_camera_msgs/srv/SetString '{data: "string"}'
+ ros2 service call /camera/read_customer_data orbbec_camera_msgs/srv/GetString '{}'
+ ```
+* `/camera/set_user_calib_params` & `/camera/get_user_calib_params`
+ ```bash
+ ros2 service call /camera/set_user_calib_params orbbec_camera_msgs/srv/SetUserCalibParams \
+ '{k: [614.9613647460938, 0.0, 634.91552734375,
+ 0.0, 614.65771484375, 391.407470703125,
+ 0.0, 0.0, 1.0],
+ d: [-0.03131488710641861,
+ 0.032955970615148544,
+ 9.096559369936585e-05,
+ -0.0003368517500348389,
+ -0.01115430984646082,
+ 0.0, 0.0, 0.0],
+ rotation: [0.9999880790710449, 0.0003024190664291382, -0.004874417092651129,
+ -0.0002965621242765337, 0.9999992251396179, 0.001202247804030776,
+ 0.004874777048826218, -0.0012007878394797444, 0.9999874234199524],
+ translation: [-0.023897956848144532,
+ -9.439220279455185e-05,
+ -6.804073229432106e-06]}'
+ ros2 service call /camera/get_user_calib_params orbbec_camera_msgs/srv/GetUserCalibParams '{}'
+ ```
diff --git a/docs/source/4_application_guide/topics.md b/docs/source/4_application_guide/topics.md
new file mode 100644
index 00000000..b9fbd3d9
--- /dev/null
+++ b/docs/source/4_application_guide/topics.md
@@ -0,0 +1,67 @@
+# Available Topics
+
+Topics are organized by stream and function. By default, all topics are published under the `/camera` namespace, which can be changed with the `camera_name` launch parameter.
+
+> **Note:** Topics for a specific stream (e.g., `/camera/color/...`) are only published if their corresponding launch parameter (e.g., `enable_color`) is set to `true`.
+
+### Image Streams
+
+These topics provide the raw image data and corresponding calibration information for each enabled camera stream. The pattern is consistent for `color`, `depth`, `ir`, `left_ir`, and `right_ir` streams.
+
+* `/camera/color/image_raw`
+ * Raw image data from the color stream.
+* `/camera/color/camera_info`
+ * Camera calibration data and metadata for the color stream.
+* `/camera/color/metadata`
+ * Low-level metadata from the color stream firmware.
+
+* `/camera/depth/image_raw`
+ * Raw image data from the depth stream.
+* `/camera/depth/camera_info`
+ * Camera calibration data and metadata for the depth stream.
+* `/camera/depth/metadata`
+ * Low-level metadata from the depth stream firmware.
+
+* `/camera/ir/image_raw`
+ * Raw image data from the infrared (IR) stream.
+* `/camera/ir/camera_info`
+ * Camera calibration data and metadata for the IR stream.
+* `/camera/ir/metadata`
+ * Low-level metadata from the IR stream firmware.
+
+### Point Cloud Topics
+
+* `/camera/depth/points`
+ * Point cloud data generated from the depth stream.
+ * **Condition:** Published only when `enable_point_cloud` is `true`.
+
+* `/camera/depth_registered/points`
+ * Colored point cloud data, where the depth points are registered to the color image frame.
+ * **Condition:** Published only when `enable_colored_point_cloud` is `true`.
+
+### IMU Topics
+
+The Inertial Measurement Unit (IMU) topics provide accelerometer and gyroscope data. Their behavior depends on the synchronization setting.
+
+* `/camera/accel/sample`
+ * Individual accelerometer data stream.
+ * **Condition:** Published when `enable_accel` is `true` AND `enable_sync_output_accel_gyro` is `false`.
+
+* `/camera/gyro/sample`
+ * Individual gyroscope data stream.
+ * **Condition:** Published when `enable_gyro` is `true` AND `enable_sync_output_accel_gyro` is `false`.
+
+* `/camera/gyro_accel/sample`
+ * Synchronized data stream containing both accelerometer and gyroscope data in a single message.
+ * **Condition:** Published when `enable_sync_output_accel_gyro` is `true`.
+
+### Device Status & Diagnostics
+
+* `/camera/device_status`
+ * Reports the current status of the camera device.
+
+* `/camera/depth_filter_status`
+ * Reports the status of the depth sensor's post-processing filters.
+
+* `/diagnostics`
+ * Publishes diagnostic information about the camera node. Currently, this includes the device temperature.
diff --git a/docs/source/5_advanced_guide/advanced_guide.rst b/docs/source/5_advanced_guide/advanced_guide.rst
new file mode 100644
index 00000000..1555edf2
--- /dev/null
+++ b/docs/source/5_advanced_guide/advanced_guide.rst
@@ -0,0 +1,26 @@
+Advanced Guide
+======================================================
+
+This chapter covers advanced features of the SDK, including multi-camera synchronization, depth-color alignment, performance tuning, and more.
+
+.. toctree::
+ :maxdepth: 2
+
+ align_depth_color.md
+ benchmark.md
+ building_a_Debian_Package.md
+ configuration_of_depth_NFOV_and_WFOV_modes.md
+ depth_work_mode_switch.md
+ disparity_search_offset.md
+ efficient_intra_process_communication.md
+ fastdds_tuning.md
+ gmsl_camera.md
+ interleave_ae_mode.md
+ lower_cpu_usage.md
+ multi_camera.md
+ multi_camera_synced.md
+ multi_camera_synced_verification_tool.md
+ net_camera.md
+ point_cloud.md
+ predefined_presets.md
+
diff --git a/docs/source/5_advanced_guide/align_depth_color.md b/docs/source/5_advanced_guide/align_depth_color.md
new file mode 100644
index 00000000..673458f1
--- /dev/null
+++ b/docs/source/5_advanced_guide/align_depth_color.md
@@ -0,0 +1,39 @@
+## Aligning Depth to Color in ROS 2
+
+This section explains how to align depth images with color images to create an overlay image using ROS 2. This is particularly useful for applications requiring synchronized visual information from different sensor modalities.
+
+### Commands to Align and View Depth and Color Images
+
+1. **Basic Depth to Color Alignment:**
+
+ To simply align the depth image to the color image, use the following command:
+
+ ```bash
+ ros2 launch orbbec_camera gemini_330_series.launch.py depth_registration:=true
+ ```
+
+ This command activates the depth registration feature without opening a viewer.
+2. **Viewing Depth to Color Overlay:**
+
+ If you wish to view the depth to color overlay, you need to enable the viewer by using the command below:
+
+ ```bash
+ ros2 launch orbbec_camera gemini_330_series.launch.py depth_registration:=true enable_d2c_viewer:=true
+ ```
+
+ This launches the camera node with depth to color registration and opens a viewer to display the overlay image.
+
+### Selecting Topics in RViz2
+
+To visualize the aligned images in RViz2:
+
+1. Launch RViz2 after running one of the above commands.
+2. Select the topic for the depth to color overlay image. An example topic selection is shown here:
+
+ 
+
+### Example of Depth to Color Overlay
+
+After selecting the appropriate topic in RViz2, you will be able to see the depth to color overlay image. Here's what it might look like:
+
+
diff --git a/docs/source/5_advanced_guide/benchmark.md b/docs/source/5_advanced_guide/benchmark.md
new file mode 100644
index 00000000..419c69c6
--- /dev/null
+++ b/docs/source/5_advanced_guide/benchmark.md
@@ -0,0 +1,51 @@
+# Ob_benchmark tool
+
+> The goal of this tool is to benchmark the performance of various OrbbecSDK_ROS2 camera configurations. The benchmark results depend on the camera and settings used.(Currently only works with ROS2 Humble)
+
+## Usage Instructions
+
+### Tool Configuration ([start_benchmark_params.json](../../config/tools/startbenchmark/start_benchmark_params.json))
+
+```json
+{
+ "start_benchmark_params": {
+ "camera_name": [
+ "camera_01",
+ "camera_02",
+ "camera_03",
+ "camera_04"
+ ],
+ "process_name": "component_conta",
+ "switch_cycle": 300,
+ "test_cycle": 1,
+ "skip_number": 30
+ }
+}
+
+```
+
+* `camera_name`: Names of the cameras to be configured. Example: `"camera_01"`, `"camera_02"`, etc.
+* `process_name`: The name of the process to be monitored. For example, `"component_conta"` will monitor the data of the container process.
+* `switch_cycle`: The cycle time for switching configurations, in seconds. For example, setting it to `300` means the configuration will switch every 300 seconds.
+* `test_cycle`: The testing cycle, in seconds. For example, setting it to `1` means the tool will collect data for the monitored process every 1 second.
+* `skip_number`: The number of data points to skip. For example, setting it to `30` means that the first 30 data points will be ignored.
+
+### Camera configuration (launch files)
+
+In the launch folder, there are multiple\.launch.py files (`ob_benchmark_0.launch.py`, `ob_benchmark_1.launch.py`, ..., `ob_benchmark_19.launch.py`). Each file corresponds to a different camera configuration.
+
+### Running the ob_benchmark tool
+
+To run the tool, use the following commands:
+
+```bash
+source install/setup.bash
+ros2 run orbbec_camera ob_benchmark_node
+```
+
+### Output Data Files
+
+The output data files will be stored in the ob_benchmark folder with filenames like `0.csv`, `1.csv`, ..., 19.csv. For example:
+
+* `0.csv` contains data from the `ob_benchmark_0.launch.py` configuration.
+* `1.csv` contains data from the `ob_benchmark_1.launch.py` configuration.
diff --git a/docs/source/5_advanced_guide/building_a_Debian_Package.md b/docs/source/5_advanced_guide/building_a_Debian_Package.md
new file mode 100644
index 00000000..7441bfca
--- /dev/null
+++ b/docs/source/5_advanced_guide/building_a_Debian_Package.md
@@ -0,0 +1,45 @@
+# Building a Debian Package
+
+## Preparing the Environment
+
+Before starting, install the required tools:
+
+```bash
+sudo apt install debhelper fakeroot python3-bloom
+```
+
+## Configuring ROS Dependencies
+
+Add the following YAML file to your system at `/etc/ros/rosdep/sources.list.d/00-orbbec.yaml`. Make sure to
+replace `focal` with the codename of your Ubuntu version and `humble` with your ROS2 distribution name:
+
+```yaml
+orbbec_camera_msgs:
+ ubuntu:
+ focal: [ ros-humble-orbbec-camera-msgs ]
+```
+
+Next, create a new file `/etc/ros/rosdep/sources.list.d/50-orbbec.list` and add this line to specify the path to the
+YAML file:
+
+```bash
+yaml file:///etc/ros/rosdep/sources.list.d/00-orbbec.yaml
+```
+
+Update the rosdep database to reflect these changes:
+
+```bash
+rosdep update
+```
+
+## Building the Package
+
+Navigate to your workspace and build the project:
+
+```bash
+cd ~/ros2_ws/
+colcon build --event-handlers console_direct+ --cmake-args -DCMAKE_BUILD_TYPE=Release
+. install/setup.bash
+cd src/OrbbecSDK_ROS2/
+bash .make_deb.sh
+```
diff --git a/docs/source/5_advanced_guide/configuration_of_depth_NFOV_and_WFOV_modes.md b/docs/source/5_advanced_guide/configuration_of_depth_NFOV_and_WFOV_modes.md
new file mode 100644
index 00000000..ad4312c3
--- /dev/null
+++ b/docs/source/5_advanced_guide/configuration_of_depth_NFOV_and_WFOV_modes.md
@@ -0,0 +1,13 @@
+# Configuration of depth NFOV and WFOV modes
+
+For the Femto Mega and Femto Bolt devices, the NFOV and WFOV modes are implemented by configuring the resolution of
+Depth and IR in the launch file.
+In launch file, depth_width, depth_height, ir_width, ir_height represents the resolution of the depth and the resolution of
+the IR.
+The frame fps and resolution of IR must be consistent with the depth. The correspondence between different modes and
+resolutions is as follows:
+
+- NFOV unbinned: 640 x 576.
+- NFOV binned: 320 x 288.
+- WFOV unbinned: 1024 x 1024.
+- WFOV binned: 512 x 512.
diff --git a/docs/source/5_advanced_guide/depth_work_mode_switch.md b/docs/source/5_advanced_guide/depth_work_mode_switch.md
new file mode 100644
index 00000000..bdd82bb8
--- /dev/null
+++ b/docs/source/5_advanced_guide/depth_work_mode_switch.md
@@ -0,0 +1,32 @@
+# 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.
+
+- Before starting the camera, depth work mode (depth_work_mode) can be configured for the corresponding xxx.launch.py
+ file's support.
+- The depth work mode switch is supported by Gemini 2, Gemini 2 L, and Gemini 2 XL cameras.
+- The default depth work mode configuration of xxx.launch.py is the camera's default configuration. If you need to
+ modify it, you can switch to the corresponding mode as needed.
+- The specific camera depth work mode support types can be found in the comments of the depth mode.
+
+```python
+# Depth work mode support is as follows:
+# Unbinned Dense Default
+# Unbinned Sparse Default
+# Binned Sparse Default
+# Obstacle Avoidance
+DeclareLaunchArgument('depth_work_mode', default_value='')
+```
+
+- View depth work modes:
+
+```bash
+ros2 run orbbec_camera list_depth_work_mode_node
+```
+
+* Example:
+
+```bash
+ros2 launch orbbec_camera gemini2L.launch.py depth_work_mode:="Unbinned Dense Default"
+```
diff --git a/docs/source/5_advanced_guide/disparity_search_offset.md b/docs/source/5_advanced_guide/disparity_search_offset.md
new file mode 100644
index 00000000..3790c078
--- /dev/null
+++ b/docs/source/5_advanced_guide/disparity_search_offset.md
@@ -0,0 +1,47 @@
+# Disparity_search_offset
+
+> This section describes how to use the disparity_search_offset function in the Gemini330 series cameras (minimum camera firmware version [1.4.60](https://www.orbbec.com/docs/g330-firmware-release/)).Disparity_search_offset is effective only for1280×720, 1280×800 and 640×400 resolutions of depth stream.
+
+## Function Introduction
+
+The definition of disparity search range: For any pixel *(u_l, v)* in the left image, by default, the corresponding disparity search range in the right image is *[ (u_l - 255, v)*, *(u_l, v) ]*, where the disparity search length is 256 and the maximum integer disparity is 255. If the starting point of the search is adjusted to *[ (u_l - 255 - offset, v)*, *(u_l - offset, v) ]*, the offset is defined as the disparity shift. Therefore, our disparity search range configuration includes both the disparity search length and the search position offset (which can also be referred to as the disparity shift).
+
+
+
+## Parameter Introduction
+
+The disparity_search_offset related parameters are set in [gemini_330_series.launch.py](../../launch/gemini_330_series.launch.py)
+
+* `disparity_range_mode` : Disparity search length,can only be set to 64, 128 and 256.
+
+* `disparity_search_offset` : Disparity search offset value,Disparity search offset value, can be set from 0 to 127.
+
+* `disparity_offset_config` : Disparity search offset interleave frames.
+
+* `offset_index0` : Frame 0 disparity search offset value.
+
+* `offset_index1` : Frame 1 disparity search offset value.
+
+| disparity range mode | disparity search offset | Minimum depth of inclined wall (mm) |
+| :------------------: | :---------------------: | :---------------------------------: |
+| 64 | 85 | Gemini 335L 388-406 |
+| 64 | 127 | Gemini 335L 302-317 |
+
+| disparity range mode | disparity search offset | Minimum depth of inclined wall (mm) |
+| :------------------: | :---------------------: | :---------------------------------------------: |
+| 128 | 0 | Gemini 335 233-249 Gemini 335L 453-475 |
+| 128 | 45 | Gemini 335 172-184 Gemini 335L 334-349 |
+| 128 | 127 | Gemini 335 117-125 Gemini 335L 226-236 |
+
+| disparity range mode | disparity search offset | Minimum depth of inclined wall (mm) |
+| :------------------: | :---------------------: | :---------------------------------: |
+| 256 | 85 | Gemini 335L 169-178 |
+| 256 | 127 | Gemini 335L 151-158 |
+
+## Run the launch
+
+Setting the disparity_search_offset parameter,`colcon build` again and run launch
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py
+```
diff --git a/docs/source/5_advanced_guide/efficient_intra_process_communication.md b/docs/source/5_advanced_guide/efficient_intra_process_communication.md
new file mode 100644
index 00000000..c2b11638
--- /dev/null
+++ b/docs/source/5_advanced_guide/efficient_intra_process_communication.md
@@ -0,0 +1,35 @@
+# Efficient intra-process communication:
+
+Our ROS2 Wrapper node supports zero-copy communications if loaded in the same process as a subscriber node. This can reduce copy times on image/pointcloud topics, especially with big frame resolutions and high FPS.
+
+You will need to launch a component container and launch our node as a component together with other component nodes. Further details on "Composing multiple nodes in a single process" can be found [here](https://docs.ros.org/en/rolling/Tutorials/Composition.html).
+
+Further details on efficient intra-process communication can be found [here](https://docs.ros.org/en/humble/Tutorials/Intra-Process-Communication.html#efficient-intra-process-communication).
+
+## Example
+
+### Manually loading multiple components into the same process
+
+* Start the component:
+
+ ```bash
+ ros2 run rclcpp_components component_container
+ ```
+* Add the wrapper:
+
+ ```bash
+ ros2 component load /ComponentManager orbbec_camera orbbec_camera::OBCameraNodeDriver -e use_intra_process_comms:=true
+ ```
+
+ Load other component nodes (consumers of the wrapper topics) in the same way.
+
+### Using a launch file
+
+```bash
+ros2 launch orbbec_camera gemini_intra_process_demo_launch.py
+```
+
+### Limitations
+
+* Node components are currently not supported on RCLPY
+* Compressed images using `image_transport` will be disabled as this isn't supported with intra-process communication
diff --git a/docs/source/5_advanced_guide/fastdds_tuning.md b/docs/source/5_advanced_guide/fastdds_tuning.md
new file mode 100644
index 00000000..03f94d85
--- /dev/null
+++ b/docs/source/5_advanced_guide/fastdds_tuning.md
@@ -0,0 +1,154 @@
+# Fast DDS Optimization for Orbbec Camera with ROS2
+
+When operating with the default configuration, Fast DDS exhibits suboptimal transmission efficiency, resulting in
+significant image transmission delays when used with the Orbbec camera in ROS2. This document provides guidance on
+optimizing Fast DDS to enhance image transfer efficiency.
+
+## Adjusting System Parameters
+
+### IP Fragmentation Time
+
+- **Path**: `/proc/sys/net/ipv4/ipfrag_time` (default: 30 seconds)
+- **Purpose**: Defines the duration that IP fragments are kept in memory.
+- **Adjustment**: Decrease this value to reduce the time window where no fragments are received, which can help reduce
+ delays. Consider the specific needs of your environment as this setting affects all incoming fragments.
+
+ **Example**: Set to 3 seconds.
+
+ ```bash
+ sudo sysctl net.ipv4.ipfrag_time=3
+ ```
+
+### IP Fragmentation Memory Threshold
+
+- **Path**: `/proc/sys/net/ipv4/ipfrag_high_thresh` (default: 262144 bytes)
+- **Purpose**: Sets the maximum memory used to reassemble IP fragments.
+- **Adjustment**: Increase this value to allow more memory for fragment reassembly, which can improve handling of larger
+ data packets.
+
+ **Example**: Increase to 128 MB.
+
+ ```bash
+ sudo sysctl net.ipv4.ipfrag_high_thresh=134217728
+ ```
+
+### Maximum Buffer Sizes
+
+- **Purpose**: Configures the maximum buffer sizes for receiving and sending data, which is critical for high-throughput
+ data transmission.
+- **Adjustment**: Set the maximum buffer sizes for both receiving and sending operations.
+
+ **Commands**:
+
+ ```bash
+ sudo sysctl -w net.core.rmem_max=2147483647
+ sudo sysctl -w net.core.rmem_default=2147483647
+ sudo sysctl -w net.core.wmem_max=2147483647
+ sudo sysctl -w net.core.wmem_default=2147483647
+ ```
+
+Alternatively, make these settings permanent by adding them to the `/etc/sysctl.d/10-fastrtps-max.conf` file.
+
+```bash
+sudo gedit /etc/sysctl.d/10-fastrtps-max.conf
+```
+
+add blow lines to the file:
+
+```bash
+net.core.rmem_max=2147483647
+net.core.rmem_default=2147483647
+net.core.wmem_max=2147483647
+net.core.wmem_default=2147483647
+```
+
+then save and exit the file. run `sudo sysctl -p` to apply the changes.
+
+For detailed guidance, refer
+to [ROS 2 DDS Tuning Documentation](https://docs.ros.org/en/foxy/How-To-Guides/DDS-tuning.html).
+
+## Fast DDS Configuration
+
+Below is an example of a Fast DDS configuration file optimized for ROS2 usage with the Orbbec camera. This configuration
+enhances the overall data transmission by adjusting buffer sizes and transport settings.
+
+### Configuration File: `shm_fastdds.xml`
+
+Place this file in the `$HOME` directory.
+
+```xml
+
+
+
+
+ UDP_transport
+ UDPv4
+ 10
+ 65000
+ 1048576
+ 1048576
+
+
+
+
+ profile_for_ros2_context
+
+ UDP_transport
+
+ false
+ 1048576
+ 1048576
+
+
+
+
+ 127.0.0.1
+
+
+
+
+
+
+
+
+
+ ASYNCHRONOUS
+
+
+
+ 0
+ 1000000
+
+
+
+ PREALLOCATED_WITH_REALLOC
+
+
+
+
+ AUTOMATIC
+
+
+
+ 0
+ 1000000
+
+
+
+ PREALLOCATED_WITH_REALLOC
+
+
+```
+
+### Environment Variables
+
+Set the following environment variables to use the custom Fast DDS profile:
+
+```bash
+export RMW_IMPLEMENTATION=rmw_fastrtps_cpp
+export FASTRTPS_DEFAULT_PROFILES_FILE=$HOME/shm_fastdds.xml
+export RMW_FASTRTPS_USE_QOS_FROM_XML=1
+```
+
+This configuration aims to optimize the data flow and reduce transmission delays, improving the responsiveness and
+reliability of the Orbbec camera system in a ROS2 environment.
diff --git a/docs/source/5_advanced_guide/gmsl_camera.md b/docs/source/5_advanced_guide/gmsl_camera.md
new file mode 100644
index 00000000..b979d560
--- /dev/null
+++ b/docs/source/5_advanced_guide/gmsl_camera.md
@@ -0,0 +1,50 @@
+# GMSL_camera
+
+> This section describes how to use GMSL camera in OrbbecSDK_ROS2.Currently, only Gemini 335Lg GMSL devices are supported, and other GMSL devices will be supported in the near future.
+
+## Single GMSL camera
+
+The usage of GMSL camera in OrbbecSDK_ROS2 is the same as that of Gemini 330 series camera via USB.
+
+```bash
+ros2 launch orbbec_camera gemini_330_gmsl.launch.py
+```
+
+## Multi GMSL camera
+
+To get the `usb_port` of the GMSL camera, plug in the camera and run the following command in the terminal:
+
+```bash
+ros2 run orbbec_camera list_devices_node
+```
+
+For example, the obtained gmsl camera `usb_port`: `gmsl2-1`
+
+Go to the [multi_gmsl_camera.launch.py](./multi_gmsl_camera.launch.py) file and change the `usb_port`.
+
+```bash
+ros2 launch orbbec_camera multi_gmsl_camera.launch.py
+```
+
+> Note: By default, multi_gmsl_camera.launch.py only starts color and left_ir. If you want to start other sensors, please go to [camera_secondary_params.yaml](../../config/camera_secondary_params.yaml) to modify them.
+
+## Multi GMSL camera synced
+
+First, please see how to use [multi_camera_synced](../multi_camera_synced/README.MD).
+
+In addition, GMSL multi-camera synced does not require Multi-Camera Sync Hub Pro, so there is no need to set the `primary` mode. Each GMSL camera is `secondary`.
+
+### Additional Parameter Settings
+
+* `gmsl_trigger_fps` : set hardware soc trigger source frame rate.
+* `enable_gmsl_trigger` : enable hardware soc trigger.
+
+### Run the launch
+
+Please refer to the configuration in [multi_gmsl_camera_synced.launch.py.](multi_gmsl_camera_synced.launch.py)
+
+```bash
+ros2 launch orbbec_camera multi_gmsl_camera_synced.launch.py
+```
+
+> Note: By default, multi_gmsl_camera_synced.launch.py only starts color and left_ir. If you want to start other sensors, please go to [camera_secondary_params.yaml](../../config/camera_secondary_params.yaml) and [camera_params.yaml](../../config/camera_params.yaml) to modify them.
diff --git a/docs/source/5_advanced_guide/interleave_ae_mode.md b/docs/source/5_advanced_guide/interleave_ae_mode.md
new file mode 100644
index 00000000..46a8cc04
--- /dev/null
+++ b/docs/source/5_advanced_guide/interleave_ae_mode.md
@@ -0,0 +1,81 @@
+# Using interleave_ae with Gemini330 series cameras
+
+> This section describes how to use interleave_ae in Gemini 330 series cameras (minimum camera firmware version [1.4.00](https://www.orbbec.com/docs/g330-firmware-release/))
+
+## Parameter Introduction
+
+The interleave_ae related parameters are set in [gemini_330_series.launch.py](../../launch/gemini_330_series.launch.py)
+
+* `interleave_ae_mode` : Set laser or hdr interleave.
+
+* `interleave_frame_enable` : enable interleave frame mode.
+
+* `interleave_skip_enable` : enable skip frame mode.
+
+* `interleave_skip_index` : Set 0 for skip pattern ir, set 1 for skip flood ir.
+
+### interleave hdr
+
+When the `interleave_ae_mode` parameter is set to `hdr` and `interleave_frame_enable `is set to `true`, interleave hdr will be enabled
+
+* `hdr_index1_laser_control` : Frame 1 laser switch settings.
+
+* `hdr_index1_depth_exposure` : Frame 1 depth exposure value setting, not in AE mode.
+
+* `hdr_index1_depth_gain` : Frame 1 depth gain value setting, not in AE mode.
+
+* `hdr_index1_ir_brightness` : Frame 1 ir gain value setting.
+
+* `hdr_index1_ir_ae_max_exposure` : Frame 1 ir maximum exposure value setting in AE (auto exposure).
+
+* `hdr_index0_laser_control`: Frame 0 laser switch settings.
+
+* `hdr_index0_depth_exposure`: Frame 0 depth exposure value setting, not in AE mode.
+
+* `hdr_index0_depth_gain` : Frame 0 depth gain value setting, not in AE mode.
+
+* `hdr_index0_ir_brightness` : Frame 0 ir gain value setting.
+
+* `hdr_index0_ir_ae_max_exposure` : Frame 0 ir maximum exposure value setting in AE (auto exposure).
+
+### interleave laser
+
+When the `interleave_ae_mode` parameter is set to `laser` and `interleave_frame_enable `is set to `true`, interleave laser will be enabled
+
+* `laser_index1_laser_control` : Frame 1 laser switch settings.
+
+* `laser_index1_depth_exposure` : Frame 1 depth exposure value setting, not in AE mode.
+
+* `laser_index1_depth_gain` : Frame 1 depth gain value setting, not in AE mode.
+
+* `laser_index1_ir_brightness` : Frame 1 ir gain value setting.
+
+* `laser_index1_ir_ae_max_exposure` : Frame 1 ir maximum exposure value setting in AE (auto exposure).
+
+* `laser_index0_laser_control` : Frame 0 laser switch settings.
+
+* `laser_index0_depth_exposure` : Frame 0 depth exposure value setting, not in AE mode.
+
+* `laser_index0_depth_gain` : Frame 0 depth gain value setting, not in AE mode.
+
+* `laser_index0_ir_brightness` : Frame 0 ir gain value setting.
+
+* `laser_index0_ir_ae_max_exposure` : Frame 0 ir maximum exposure value setting in AE (auto exposure).
+
+## Run the launch
+
+Setting the interleave_ae parameter,`colcon build` again and run launch
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py
+```
+
+#### Example Visualization
+
+
+
+
+
+## Multi_camera_synced + Interleave_ae
+
+Please refer to [multi_camera_synced](../multi_camera_synced/README.MD) and [Parameter Introduction](#parameter-introduction)
diff --git a/docs/source/5_advanced_guide/lower_cpu_usage.md b/docs/source/5_advanced_guide/lower_cpu_usage.md
new file mode 100644
index 00000000..9ef453ac
--- /dev/null
+++ b/docs/source/5_advanced_guide/lower_cpu_usage.md
@@ -0,0 +1,86 @@
+## Reducing CPU Usage with Orbbec ROS Package
+
+This document outlines strategies for minimizing CPU usage in the **OrbbecSDK_ROS2 v2** environment when using **Gemini 330 series cameras**. The firmware version must be **no lower than 1.4.10**, and `device` should be set to **Default**.
+
+### Recommended Settings for Lower CPU Usage
+
+To achieve the lowest possible CPU usage in OrbbecSDK_ROS2, it is recommended to configure the following parameters.
+
+| Parameter | Recommendation | Note |
+| :--------------: | :------------------------------------: | :--------------------------------------------: |
+| `uvc_backend` | `v4l2` | Lower CPU usage compared to `libuvc` |
+| `color_format` | `RGB` | Lower CPU usage than `MJPG` |
+| `filter` | Only `hardware_noise_removal_filter` | Other filters significantly increase CPU usage |
+
+### Launch Files Used for Testing
+
+* `gemini_330_series_lower_cpu_usage.launch.py`
+* `multi_camera_lower_cpu_usage.launch.py`
+
+### Test environment
+
+#### Hardware Configuration
+
+* **CPU**: Intel i7-8700 @ 3.20GHz
+* **Memory**: 24 GB
+* **Storage**: Micron 2200S NVMe 256GB
+* **GPU**: NVIDIA GeForce GTX 1660Ti
+* **OS**: Ubuntu22.04
+
+#### ROS Configuration
+
+* **ROS Version**: ROS2 Humble
+* **SDK Version**: OrbbecSDK_ROS2 v2.2.1
+
+#### Camera Setup
+
+* Devices: 2x Gemini 335, 1x Gemini 336, 1x Gemini 336L
+* Firmware Version: 1.4.10
+
+### Test Setup
+
+* **Stream Settings:**
+ * Depth / IR Left / IR Right: 848×480 @ 30fps
+ * Color: 848×480 @ 30fps
+
+Note: The following CPU usage data focuses on `uvc_backend`, `color_format` and various filter combinations.
+
+### Test Results
+
+#### `uvc_backend` Comparison (RGB format)
+
+| libuvc CPU Usage | v4l2 CPU Usage | Absolute Change |
+| :--------------: | :------------: | :-------------: |
+| 182.8% | 118.8% | -64.0% |
+
+The CPU usage can be significantly reduced with v4l2 backend. In our implementation, v4l2 works without requiring any patches to the Linux kernel, allowing users to easily switch between v4l2 and libuvc and maintaining full compatibility with standard Linux distributions.
+
+#### `color_format` Comparison (MJPG vs RGB)
+
+| Backend | MJPG CPU Usage | RGB CPU Usage | Absolute Change |
+| :-----: | :------------: | :-----------: | :-------------: |
+| libuvc | 347.7% | 182.8% | -164.9% |
+| v4l2 | 170.0% | 118.8% | -51.2% |
+
+The CPU usage can be reduced if the RGB format is selected instead of MJPG, since the decoding of MJPG image will consume the host CPU resource.
+
+#### Filter Configuration Impact
+
+| Filters Applied | libuvc CPU Usage | CPU Usage Increase | v4l2 CPU Usage | CPU Usage Increase |
+| ----------------------------------------------------- | ---------------- | ------------------ | -------------- | ------------------ |
+| No Filter (benchmark) | 182.8% | 0.0%(benchmark) | 118.8% | 0.0%(benchmark) |
+| `(software)noise_removal_filter` | 218.0% | +35.2% | 128.5% | +9.7% |
+| `(software)noise_removal_filter + spatial_filter` | 469.6% | +286.8% | 336.7% | +217.9% |
+| `hardware_noise_removal_filter` | 186.3% | +3.5% | 115.4% | -3.4% |
+| `hardware_noise_removal_filter + spatial_filter` | 251.3% | +68.5% | 152.5% | +33.7% |
+
+Based on the test results, using only the `hardware_noise_removal_filter` results in a negligible change in CPU usage for both `libuvc` (+3.5%) and `v4l2` (-3.4%) compared to the no-filter benchmark, as this filter runs internally on the camera hardware. In contrast, other filters execute on the host system. Adding the `spatial_filter` to the hardware filter leads to a moderate increase in CPU usage, while applying the software-based `noise_removal_filter` —either alone or combined with `spatial_filter` —significantly increases CPU load. To maintain low CPU usage, it is recommended to avoid software-based filters and rely solely on the `hardware_noise_removal_filter`.
+
+### Further Optimizationa
+
+| Parameter | Recommendation | Note |
+| :----------------------------: | :----------------------------------------------: | :---------------------------------------------: |
+| `depth_registration` | `false` or `true` with `align_mode=HW` | Software alignment consumes more CPU |
+| `enable_point_cloud` | `false` | Disabling point cloud reduces CPU usage |
+| `enable_colored_point_cloud` | `false` | Disabling colored point cloud reduces CPU usage |
+
diff --git a/docs/source/5_advanced_guide/multi_camera.md b/docs/source/5_advanced_guide/multi_camera.md
new file mode 100644
index 00000000..a6d514fd
--- /dev/null
+++ b/docs/source/5_advanced_guide/multi_camera.md
@@ -0,0 +1,91 @@
+# Multi-Camera
+
+- To get the `usb_port` of the camera, plug in the camera and run the following command in the terminal:
+
+```bash
+ros2 run orbbec_camera list_devices_node
+```
+
+- Set the `device_num` parameter to the number of cameras you have.
+- Go to the `OrbbecSDK_ROS2/launch/multi_xxx.launch.py` file and change the `usb_port`.
+- Don't forget to put the `include` tag inside the `group` tag.
+ Otherwise, the parameter values of different cameras may become contaminated.
+
+```python
+from launch import LaunchDescription
+from launch.actions import DeclareLaunchArgument, IncludeLaunchDescription, GroupAction, ExecuteProcess
+from launch.launch_description_sources import PythonLaunchDescriptionSource
+from launch_ros.actions import Node
+from ament_index_python.packages import get_package_share_directory
+import os
+
+
+def generate_launch_description():
+ # Include launch files
+ package_dir = get_package_share_directory('orbbec_camera')
+ launch_file_dir = os.path.join(package_dir, 'launch')
+ launch1_include = IncludeLaunchDescription(
+ PythonLaunchDescriptionSource(
+ os.path.join(launch_file_dir, 'gemini2L.launch.py')
+ ),
+ launch_arguments={
+ 'camera_name': 'camera_01',
+ 'usb_port': '6-2.4.4.2', # replace your usb port here
+ 'device_num': '2'
+ }.items()
+ )
+
+ launch2_include = IncludeLaunchDescription(
+ PythonLaunchDescriptionSource(
+ os.path.join(launch_file_dir, 'gemini2L.launch.py')
+ ),
+ launch_arguments={
+ 'camera_name': 'camera_02',
+ 'usb_port': '6-2.4.1', # replace your usb port here
+ 'device_num': '2'
+ }.items()
+ )
+
+ # If you need more cameras, just add more launch_include here, and change the usb_port and device_num
+
+ # Launch description
+ ld = LaunchDescription([
+ GroupAction([launch1_include]),
+ GroupAction([launch2_include]),
+ ])
+
+ return ld
+
+```
+
+- To launch the cameras, run the following command:
+
+```bash
+ros2 launch orbbec_camera multi_camera.launch.py
+```
+
+## No Data Stream from Multiple Cameras
+
+**Insufficient Power Supply**:
+
+- Ensure that each camera is connected to a separate hub.
+- Use a powered hub to provide sufficient power to each camera.
+
+**High Resolution**:
+
+- Try lowering the resolution to resolve data stream issues.
+
+**Increase usbfs_memory_mb Value**:
+
+- Increase the `usbfs_memory_mb` value to 128MB (this is a reference value and can be adjusted based on your system’s needs)
+ by running the following command:
+
+```bash
+ echo 128 | sudo tee /sys/module/usbcore/parameters/usbfs_memory_mb
+```
+
+- To make this change permanent, check [this link](https://github.com/OpenKinect/libfreenect2/issues/807).
+
+## Image topic frame rate too low from Multiple Cameras
+
+Refer to the [Fast DDS Configuration](./docs/fastdds_tuning.md) file.
diff --git a/docs/source/5_advanced_guide/multi_camera_synced.md b/docs/source/5_advanced_guide/multi_camera_synced.md
new file mode 100644
index 00000000..572fe3b6
--- /dev/null
+++ b/docs/source/5_advanced_guide/multi_camera_synced.md
@@ -0,0 +1,55 @@
+# Multi_camera synced Instructions
+
+> The purpose of this document is to explain how to use multi-camera synced with OrbbecSDK_ROS2
+
+## Setup instructions
+
+* Please read the Multi-Camera Synchronization Setup Guide:[Multi-Camera Synchronization Setup](https://www.orbbec.com/docs/set-up-cameras-for-external-synchronization_v1-2/)
+* Make sure the camera is correctly connected to the multi-camera synchronizer.
+
+
+
+### Checking camera port with OrbbecSDK_ROS2
+
+```bash
+ros2 run orbbec_camera list_devices_node
+```
+
+### OrbbecSDK_ROS2 multi-camera synced configuration
+
+Open multi_camera_synced.launch.py, and configure the camera settings as shown below:
+
+
+
+1. `gemini_330_series.launch.py` is the launch file for starting the camera.
+
+2. Set `camera_name` to `G330_0`. For example, the published color image topic will be `/G330_0/color/image_raw`.
+
+3. Set `usb_port` to `2-2`, indicating that the camera device on port `2-2` is being used. This value can be found in the output of the `ros2 run orbbec_camera list_devices_node` command.
+
+4. Set `device_num` to `2`, meaning two cameras will be used.
+
+5. Set `sync_mode` to `primary` to indicate that the `2-7` camera device is in primary mode. The multi-camera sync mode options can be found in the figure below.
+
+6. Parameters from the `config_file_path` can override the parameters set in `gemini_330_series.launch.py` (optional).
+
+7. For slave cameras, set `trigger_out_enabled` to false.
+
+| **Pattern Nam**e | **Setting effect description** |
+| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| free_run | -Support different frame rate settings The -8-pin synchronization interface does not support external output of synchronization-related signals |
+| standalone(default) | ● Same as Primary by default ● Built-in RGBD frame synchronization ● 8-pin synchronous interface does not output signals to the outside by default |
+| primary | ● Set as primary camera ● 8-pin synchronous interface output signal to external device |
+| secondary | ● Set as secondary (passive synchronization; When there is a hardware continuous trigger signal input from the outside and the continuous trigger signal matches the currently set frame rate, the image is collected according to the external trigger signal; When there is no external trigger signal, the flow is stopped) ● 8-pin synchronous interface output signal to external device |
+| secondary_synced | ● Set to secondary synchronization (passive synchronization; When there is a hardware continuous trigger signal input from the outside and the continuous trigger signal matches the currently set frame rate, the image is collected according to the external trigger signal; When there is no external trigger signal, the image is collected according to the internal trigger signal at the set frame rate) ● 8-pin synchronous interface output signal to external device |
+| hardware_triggering | ● Set as hardware trigger (passive trigger; When there is a hardware trigger signal input from the outside and the trigger signal time interval is not less than the current upper limit, the image is collected according to the external trigger signal; When there is no external trigger signal, the image is not collected) ● 8-pin synchronous interface output signal to external device |
+| software_triggering | ● Set as software trigger (passive trigger; When there is a trigger command input from the host computer and the trigger command time interval is not less than the current upper limit, the image is collected according to the trigger command; When there is no trigger command, the image is not collected) ● 8-pin synchronous interface output signal to external device |
+
+* The master camera should be launched last.
+* Ideally, there should be a 2-second delay between starting each camera.
+
+### Run the following command to start the multi-camera synced
+
+```bash
+ros2 launch orbbec_camera multi_camera_synced.launch.py
+```
diff --git a/docs/source/5_advanced_guide/multi_camera_synced_verification_tool.md b/docs/source/5_advanced_guide/multi_camera_synced_verification_tool.md
new file mode 100644
index 00000000..7523d9e8
--- /dev/null
+++ b/docs/source/5_advanced_guide/multi_camera_synced_verification_tool.md
@@ -0,0 +1,159 @@
+# Multi_camera_synced_verification_tool
+
+> This article will introduce how to verify the synchronization accuracy of multi-camera synchronization.
+>
+> First, please see how to use [multi_camera_synced](../multi_camera_synced/README.MD).
+
+## Directory Structure
+
+```plaintext
+.
+├── multicamera_sync/
+│ ├── output/
+│ ├──20250218102900/
+│ ├──DevicesInfo.txt
+│ ├──StreamProfileInfo.txt
+│ ├── Python/
+│ ├──Config.ini
+├── gemini_330_series_synced_verify.launch.py
+├── multi_camera_synced_verify.launch.py
+```
+
+### multicamera_sync
+
+* `gemini_330_series_synced_verify.launch.py` : Single camera runs launch, which provides the camera running node for multi_camera_synced_verify.launch.py.
+* `multi_camera_synced_verify.launch.py` : Multi camer synced + launch of save_rgbir tool.
+
+#### output
+
+> The `ouput` folder is the folder where the camera pictures are output
+
+In the output example provided
+
+* `20250218102900` : Represents the camera image information collected at 10:29:00 on February 18, 2025.
+* `TotalModeFrames` : Camera image information storage directory.
+* `results-2025-02-25_163648` : The result after analyzing and matching the image information of TotalModeFrames.
+* `DevicesInfo.txt` : Camera equipment basic information (need to be modified).
+* `StreamProfileInfo.txt` : Camera video stream information (no need to modify).
+
+#### Python
+
+* `Config.ini` : Configuration file for Python analysis script (need to be modified).
+
+## Preparation for operation
+
+### save_rgbir node
+
+Edit multi_camera_synced_verify.launch.py and fill in the activated camera device,we can find that save_rgbir is started at the end.
+
+> IMPORTANT
+>
+> If you are using ROS 2 Foxy, you need to launch the save_rgbir node first.
+
+```python
+# Launch description
+ ld = LaunchDescription(
+ [
+ shared_orbbec_container,
+ TimerAction(period=0.0, actions=[GroupAction([launch2_include])]),
+ TimerAction(period=2.0, actions=[GroupAction([launch1_include])]),
+ # The primary camera should be launched at last
+ TimerAction(period=6.0, actions=[GroupAction([save_rgbir])]),
+ # save_rgbir is synced verification tool
+ ]
+ )
+
+ return ld
+```
+
+save_rgbir is a tool for saving images. The configuration file of this tool is in [multi_save_rgbir_params.json](../../config/tools/multisavergbir/multi_save_rgbir_params.json).
+
+```json
+{
+ "save_rgbir_params": {
+ "time_domain": "global",
+ "usb_ports": [
+ "2-1",
+ "2-3"
+ ],
+ "camera_name": [
+ "camera_01",
+ "camera_02"
+ ]
+ }
+}
+```
+
+* `time_domain` : Timestamp Type
+* `usb_ports` : "primary", "secondary 1", "secondary 2", "secondary 3", fill in as many usb_ports as there are cameras
+* `camera_name` : The name of the camera setting, for example: camera_01
+
+### DevicesInfo.txt
+
+Edit DevicesInfo.txt. Only the `primarySerialNumber`, `index` and `serialNumber` parameters need to be changed. Other parameters do not need to be changed.Refer to the example of [20250218102900](./multicamera_sync/output/20250218102900).
+
+* `primarySerialNumber` : The SN serial number of the primary camera
+* `index` : Camera index
+* `serialNumber` : The SN serial number of the camera
+
+### Config.ini
+
+Edit Config.ini.Modify `frameRate` and `tspRangeThreshold`.
+
+## Run this example
+
+### Run launch and save camera pictures
+
+* First terminal
+
+```bash
+ros2 launch orbbec_camera multi_camera_synced_verify.launch.py
+```
+
+* Second terminal
+
+```bash
+ros2 service call /save_rgbir/start_capture orbbec_camera_msgs/srv/SetInt32 '{data: 100}'
+```
+
+When the terminal displays "over", the image is saved.A new multicamera_sync folder will be generated under the workspace.
+
+### Camera pictures naming format
+
+Take [color_SNCP1E5420006D_Index0_g1739874543227_f0_s1739874543327_e50_d16_.jpg](./multicamera_sync/output/20250218102900/TotalModeFrames/SNCP1E5420006D_Index0/color_SNCP1E5420006D_Index0_g1739874543227_f0_s1739874543327_e50_d16_.jpg) as an example
+
+* `color` : This image is a snapshot of the color stream.
+* `SNCP1E5420006D` : The camera's SN serial number is CP1E5420006D.
+* `Index0` : Camera 0 (usually referred to primary camera).
+* `g1739874543227` : “g” represents the global timestamp, which means the global timestamp of this frame is 1739874543227.
+* `f0` : The 0th picture of the color stream acquisition of this camera.
+* `s1739874543327` : "s" represents the timestamp of the current system, which means the current system timestamp of this frame is 1739874543327.
+* `e50` : The exposure of this frame is 50.
+* `d16` : The gain of this frame is 16.
+
+### Analyzing camera image data
+
+You need to copy the modified [Python folder](./multicamera_sync/Python) to the new multi_camera_synced subdirectory, and copy the modified [DevicesInfo.txt ](./multicamera_sync/output/20250218102900/DevicesInfo.txt)and [StreamProfileInfo.txt](./multicamera_sync/output/20250218102900/StreamProfileInfo.txt) to the same level directory as the TotalModeFrames folder.
+
+* Finally everything is ready, run the python script
+
+```bash
+cd multicamera_sync/Python
+python3 SyncFramesMain.py
+```
+
+After the operation is successful, you can view the synchronization effect in the `results folder`
+
+## Files that need to be changed
+
+### Analysis tools
+
+* [multi_save_rgbir_params.json](../../config/tools/multisavergbir/multi_save_rgbir_params.json)
+* [DevicesInfo.txt ](./multicamera_sync/output/20250218102900/DevicesInfo.txt)
+* [Config.ini](./multicamera_sync/Python/Config.ini)
+
+### Camera Configuration
+
+[camera_params.yaml](../../config/camera_params.yaml)(Camera startup parameter settings)
+
+[multi_camera_synced_verify.launch.py](./multi_camera_synced_verify.launch.py)
diff --git a/docs/source/5_advanced_guide/net_camera.md b/docs/source/5_advanced_guide/net_camera.md
new file mode 100644
index 00000000..476581f9
--- /dev/null
+++ b/docs/source/5_advanced_guide/net_camera.md
@@ -0,0 +1,69 @@
+# Net_camera
+
+> This section describes how to use Net camera in OrbbecSDK_ROS2.Currently, only Femto_Mega, Gemini 335Le and Gemini 435Le devices are supported, and other Net devices will be supported in the near future.
+
+## Femto Mega & Gemini 435Le
+
+### Parameter Introduction
+
+Network device settings: `enumerate_net_device` is set to true, which will automatically enumerate network devices.
+
+If you do not want to automatically enumerate network devices,you can set `enumerate_net_device` to false, `net_device_ip` to the device's IP address, and `net_device_port` to the default value of 8090.
+
+* `enumerate_net_device` : Enable automatically enumerate network devices.
+* `net_device_ip` : Setting net device's IP address.
+* `net_device_port` : Setting net device's port.Usually, you can set it to 8090.
+
+### Single Net camera
+
+> If you need to run Gemini 435Le, you only need to replace [femto_mega.launch.py ](../../launch/femto_mega.launch.py)in the run command with [gemini435_le.launch.py](../../launch/gemini435_le.launch.py)
+
+For [femto_mega.launch.py](../../launch/femto_mega.launch.py) as an example:
+
+#### automatically enumerate network devices:
+
+```bash
+ros2 launch orbbec_camera femto_mega.launch.py enumerate_net_device:=true
+```
+
+#### Specify IP address to start the device:
+
+Note: `net_device_ip` needs to be changed to the IP address of the device, here it is 192.168.1.10
+
+```bash
+ros2 launch orbbec_camera femto_mega.launch.py enumerate_net_device:=false net_device_ip:=192.168.1.10 net_device_port:=8090
+```
+
+## Gemini 335Le
+
+Network device settings: `enumerate_net_device` must be set to true, set `net_device_ip` to the IP address of the device, and set `net_device_port` to the default value of 8090.
+
+* `enumerate_net_device` : Enable automatically enumerate network devices.
+* `net_device_ip` : Setting net device's IP address.
+* `net_device_port` : Setting net device's port.Usually, you can set it to 8090.
+
+### Single Net camera
+
+For [gemini_330_series.launch.py](../../launch/gemini_330_series.launch.py) as an example:
+
+- **automatically enumerate network devices:**
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py enumerate_net_device:=true
+```
+
+- **Specify IP address to start the device:**
+
+Note: `net_device_ip` needs to be changed to the IP address of the device, here it is 192.168.1.10
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py enumerate_net_device:=true net_device_ip:=192.168.1.10 net_device_port:=8090
+```
+
+## Multi Net camera
+
+For [multi_net_camera.launch.py](./multi_net_camera.launch.py) as an example:
+
+```bash
+ros2 launch orbbec_camera multi_net_camera.launch.py
+```
diff --git a/docs/source/5_advanced_guide/point_cloud.md b/docs/source/5_advanced_guide/point_cloud.md
new file mode 100644
index 00000000..0197ba9e
--- /dev/null
+++ b/docs/source/5_advanced_guide/point_cloud.md
@@ -0,0 +1,53 @@
+## Enabling and Visualizing Point Cloud in ROS 2
+
+This section demonstrates how to enable point cloud data output from the camera node and visualize it using RViz2, similarly to the initial camera node setup discussed in the [Starting Camera Node](../start_camera_node/start_camera_node.MD) document.
+
+### Enabling Depth Point Cloud
+
+#### Command to Enable Depth Point Cloud
+
+To activate the point cloud data stream for depth information, use the following command:
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py enable_point_cloud:=true
+```
+
+#### Visualizing Depth Point Cloud in RViz2
+
+After running the above command, perform the following steps to visualize the depth point cloud:
+
+1. Open RViz2.
+2. Add a `PointCloud2` display.
+3. Select the `/camera/depth/points` topic for visualization.
+4. Set the fixed frame to `camera_link` to properly align the data.
+
+- **Example Visualization**
+
+Here is what the depth point cloud might look like in RViz2:
+
+
+
+### Enabling Colored Point Cloud
+
+#### Command to Enable Colored Point Cloud
+
+To enable the colored point cloud feature, enter the following command:
+
+```bash
+ros2 launch orbbec_camera gemini_330_series.launch.py enable_colored_point_cloud:=true
+```
+
+#### Visualizing Colored Point Cloud in RViz2
+
+To visualize the colored point cloud data:
+
+1. Launch RViz2 following the command execution.
+2. Add a `PointCloud2` display panel.
+3. Choose the `/camera/depth_registered/points` topic from the list.
+4. Ensure the fixed frame is set to `camera_link`.
+
+- **Example Visualization**
+
+The result of the colored point cloud in RViz2 should look similar to this:
+
+
diff --git a/docs/source/5_advanced_guide/predefined_presets.md b/docs/source/5_advanced_guide/predefined_presets.md
new file mode 100644
index 00000000..ba40063c
--- /dev/null
+++ b/docs/source/5_advanced_guide/predefined_presets.md
@@ -0,0 +1,15 @@
+# Predefined presets
+
+| Preset | Features | Recommended use cases |
+| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Default | - Best visual perception``- Overall good performance in accuracy, fill rate, tiny objects, etc. | - Generic ` `- Robotics |
+| Hand | - Clear hand and finger edges | - Gesture recognition |
+| High Accuracy | - Depth of high confidence ` `- Barely noise depth values ` `- Lower fill rate | - Collision avoidance ` `- Object scanning |
+| High Density | - Higher fill rate ` `- More tiny objects ` `- May suffer from noise depth values | - Object recognition ` `- Pick & place ` `- Foreground & background animation |
+| Medium Density | - Balanced performance in fill rate and accuracy ` `- In comparison to Default: lower fill rate, better edge quality | - Generic and alternative to Default |
+| Custom | - User defined Preset ` `- 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 ` `- 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.
+
+
diff --git a/docs/source/6_FAQ/FAQ.md b/docs/source/6_FAQ/FAQ.md
new file mode 100644
index 00000000..a5a02a96
--- /dev/null
+++ b/docs/source/6_FAQ/FAQ.md
@@ -0,0 +1,36 @@
+# Frequently Asked Questions
+
+### Unexpected Crash
+
+If the camera node crashes unexpectedly, it will generate a crash log in the current running directory: `Log/camera_crash_stack_trace_xx.log`. Please send this log to the support team or submit it to a GitHub issue for further assistance.
+
+### No Data Stream from Multiple Cameras
+
+**Insufficient Power Supply**:
+
+- Ensure that each camera is connected to a separate hub.
+- Use a powered hub to provide sufficient power to each camera.
+
+**High Resolution**:
+
+- Try lowering the resolution to resolve data stream issues.
+
+**Increase usbfs_memory_mb Value**:
+
+- Increase the `usbfs_memory_mb` value to 128MB (this is a reference value and can be adjusted based on your system’s needs) by running the following command:
+
+```
+ echo 128 | sudo tee /sys/module/usbcore/parameters/usbfs_memory_mb
+```
+
+- To make this change permanent, check [this link](https://github.com/OpenKinect/libfreenect2/issues/807).
+
+### Additional Troubleshooting
+
+- If you encounter other issues, set the `log_level` parameter to `debug`. This will generate an SDK log file in the running directory: `Log/OrbbecSDK.log.txt`. Please provide this file to the support team for further assistance.
+- If firmware logs are required, set `enable_heartbeat` to `true` to activate this feature.
+
+### Why Are There So Many Launch Files?
+
+- Different cameras have varying default resolutions and image formats.
+- To simplify usage, each camera has its own launch file.
\ No newline at end of file
diff --git a/docs/source/6_FAQ/FAQ.rst b/docs/source/6_FAQ/FAQ.rst
new file mode 100644
index 00000000..e4ad428f
--- /dev/null
+++ b/docs/source/6_FAQ/FAQ.rst
@@ -0,0 +1,10 @@
+FAQ
+======================================================
+
+This chapter collects frequently asked questions and answers related to the SDK usage.
+
+.. toctree::
+ :maxdepth: 2
+
+ FAQ.md
+
diff --git a/docs/source/LICENSE.txt b/docs/source/LICENSE.txt
new file mode 100755
index 00000000..b86a0979
--- /dev/null
+++ b/docs/source/LICENSE.txt
@@ -0,0 +1,1115 @@
+## License for this repository
+
+This repository is licensed under the MIT license.
+
+```
+Copyright (c) 2023 OrbbecDeveloper
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+## License for the Orbbec SDK library
+
+The Orbbec SDK library binary files are provided at the "lib" directory of this
+repository. The license for the Orbbec SDK library is provided below:
+
+```
+Copyright (c) 2023 OrbbecDeveloper
+
+Scope of License: This license grants, free of charge, to any person obtaining a
+copy of this repository or substantial portions of this repository, the right to
+use the files in this repository for ultilizing products from Orbbec Inc.You may
+apply this repository for personal, academic, and commercial use. The above copyright
+notice and this permission notice shall be included in all copies or substantial
+portions of the repository.
+
+Prohibited Actions: You are prohibited from modifying, decompiling, or reverse
+engineering any part of this library. You cannot use this library for products
+other than those of Orbbec.
+
+Reservation of Rights: The author reserves the right to modify this license at
+any time without prior notice. The author reserves all rights to this library.
+
+Disclaimer: This library is provided "as is," and the author assumes no responsibility
+for any direct, indirect, incidental, special, or consequential damages resulting
+from the use of this library.
+
+License Updates: If the author releases a new version of the license, you agree
+to comply with the new version after receiving notice.
+```
+
+## License for the third party libraries dependencies of Orbbec SDK library
+
+The Orbbec SDK library uses third party libraries that may have their own licenses.
+
+### Third party libraries under the MIT license
+
+1. spdlog
+
+ * By: Gabi Melman
+ * Version: v1.11.0
+ * Repository: https://github.com/gabime/spdlog
+
+2. dylib
+
+ * By: Martin Olivier
+ * Version: v2.2.1
+ * Repository: https://github.com/martin-olivier/dylib
+
+3. cmrc
+
+ * By: vectorofbool@gmail.com
+ * Version: v2.0.1
+ * Repository: https://github.com/vector-of-bool/cmrc
+
+4. jsoncpp
+
+ * By: chenguopingdota@163.com
+ * Version: v1.9.5
+ * Repository: https://github.com/open-source-parsers/jsoncpp
+
+Terms of the MIT License:
+
+```
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
+### Third party libraries under the BSD license
+
+1. libuvc
+
+ * By: libuvc organization
+ * Version: v0.0.7
+ * Repository: https://github.com/libuvc/libuvc
+
+2. libjpeg-turbo
+
+ * By: libjpeg-turbo organization (libjpeg-turbo.org)
+ * Version: v2.0.90
+ * Repository: https://github.com/libjpeg-turbo/libjpeg-turbo
+
+Terms of the BSD License:
+
+```
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice, this
+ list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+ this list of conditions and the following disclaimer in the documentation
+ and/or other materials provided with the distribution.
+
+3. Neither the name of the copyright holder nor the names of its
+ contributors may be used to endorse or promote products derived from
+ this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
+DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
+FOR ANY DIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
+LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
+ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+```
+
+### Third party libraries under the Apache license
+
+1. OpenCV
+
+ * By: OpenCV Organization (opencv.org)
+ * Version: v3.4.16
+ * Repository: https://github.com/opencv/opencv
+
+Terms of the Apache License:
+
+```
+
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+```
+
+### Third party libraries under the LGPL license
+
+1. libusb
+
+ * By: libusb organization (libusb.info)
+ * Version: v1.0.26
+ * Repository: https://github.com/libusb/libusb
+
+2. live555
+
+ * By: http://www.live555.com/
+ * Version: v2019.08.13
+ * Repository: https://github.com/rgl/live555
+
+Terms of the LGPL license:
+
+```
+GNU LESSER GENERAL PUBLIC LICENSE
+ Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL. It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+ Preamble
+
+ The licenses for most software are designed to take away your
+freedom to share and change it. By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+ This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it. You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+ When we speak of free software, we are referring to freedom of use,
+not price. Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+ To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights. These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+ For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you. You must make sure that they, too, receive or can get the source
+code. If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it. And you must show them these terms so they know their rights.
+
+ We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+ To protect each distributor, we want to make it very clear that
+there is no warranty for the free library. Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+ Finally, software patents pose a constant threat to the existence of
+any free program. We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder. Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+ Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License. This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License. We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+ When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library. The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom. The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+ We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License. It also provides other free software developers Less
+of an advantage over competing non-free programs. These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries. However, the Lesser license provides advantages in certain
+special circumstances.
+
+ For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard. To achieve this, non-free programs must be
+allowed to use the library. A more frequent case is that a free
+library does the same job as widely used non-free libraries. In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+ In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software. For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+ Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+ The precise terms and conditions for copying, distribution and
+modification follow. Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library". The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+ GNU LESSER GENERAL PUBLIC LICENSE
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+ 1. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+ A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+ The "Library", below, refers to any such software library or work
+which has been distributed under these terms. A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language. (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+ "Source code" for a work means the preferred form of the work for
+making modifications to it. For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+ Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope. The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it). Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+ 1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+ You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+ 2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+ a) The modified work must itself be a software library.
+
+ b) You must cause the files modified to carry prominent notices
+ stating that you changed the files and the date of any change.
+
+ c) You must cause the whole of the work to be licensed at no
+ charge to all third parties under the terms of this License.
+
+ d) If a facility in the modified Library refers to a function or a
+ table of data to be supplied by an application program that uses
+ the facility, other than as an argument passed when the facility
+ is invoked, then you must make a good faith effort to ensure that,
+ in the event an application does not supply such function or
+ table, the facility still operates, and performs whatever part of
+ its purpose remains meaningful.
+
+ (For example, a function in a library to compute square roots has
+ a purpose that is entirely well-defined independent of the
+ application. Therefore, Subsection 2d requires that any
+ application-supplied function or table used by this function must
+ be optional: if the application does not supply it, the square
+ root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole. If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works. But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+ 3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library. To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License. (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.) Do not make any other change in
+these notices.
+
+ Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+ This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+ 4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+ If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+ 5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library". Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+ However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library". The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+ When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library. The
+threshold for this to be true is not precisely defined by law.
+
+ If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work. (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+ Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+ 6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+ You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License. You must supply a copy of this License. If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License. Also, you must do one
+of these things:
+
+ a) Accompany the work with the complete corresponding
+ machine-readable source code for the Library including whatever
+ changes were used in the work (which must be distributed under
+ Sections 1 and 2 above); and, if the work is an executable linked
+ with the Library, with the complete machine-readable "work that
+ uses the Library", as object code and/or source code, so that the
+ user can modify the Library and then relink to produce a modified
+ executable containing the modified Library. (It is understood
+ that the user who changes the contents of definitions files in the
+ Library will not necessarily be able to recompile the application
+ to use the modified definitions.)
+
+ b) Use a suitable shared library mechanism for linking with the
+ Library. A suitable mechanism is one that (1) uses at run time a
+ copy of the library already present on the user's computer system,
+ rather than copying library functions into the executable, and (2)
+ will operate properly with a modified version of the library, if
+ the user installs one, as long as the modified version is
+ interface-compatible with the version that the work was made with.
+
+ c) Accompany the work with a written offer, valid for at
+ least three years, to give the same user the materials
+ specified in Subsection 6a, above, for a charge no more
+ than the cost of performing this distribution.
+
+ d) If distribution of the work is made by offering access to copy
+ from a designated place, offer equivalent access to copy the above
+ specified materials from the same place.
+
+ e) Verify that the user has already received a copy of these
+ materials or that you have already sent this user a copy.
+
+ For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it. However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+ It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system. Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+ 7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+ a) Accompany the combined library with a copy of the same work
+ based on the Library, uncombined with any other library
+ facilities. This must be distributed under the terms of the
+ Sections above.
+
+ b) Give prominent notice with the combined library of the fact
+ that part of it is a work based on the Library, and explaining
+ where to find the accompanying uncombined form of the same work.
+
+ 8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License. Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License. However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+ 9. You are not required to accept this License, since you have not
+signed it. However, nothing else grants you permission to modify or
+distribute the Library or its derivative works. These actions are
+prohibited by law if you do not accept this License. Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+ 10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions. You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+ 11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License. If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all. For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices. Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+ 12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded. In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+ 13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number. If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation. If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+ 14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission. For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this. Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+ NO WARRANTY
+
+ 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+ 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+ END OF TERMS AND CONDITIONS
+
+ How to Apply These Terms to Your New Libraries
+
+ If you develop a new library, and you want it to be of the greatest
+possible use to the public, we recommend making it free software that
+everyone can redistribute and change. You can do so by permitting
+redistribution under these terms (or, alternatively, under the terms of the
+ordinary General Public License).
+
+ To apply these terms, attach the following notices to the library. It is
+safest to attach them to the start of each source file to most effectively
+convey the exclusion of warranty; and each file should have at least the
+"copyright" line and a pointer to where the full notice is found.
+
+ 和
也自动拉伸 */
+th,
+td {
+ width: auto;
+}
+
+ul {
+ width: 100%;
+ /* 列表宽度占满整个容器 */
+ }
+
+
+/* 修改 Sphinx Theme 项目标题的字体大小 Book和rtd 均OK */
+.wy-side-nav-search>a {
+ font-size: 16px;
+ /* 你可以根据需要调整这个值 */
+}
+
+/* 修改项目标题的字体大小 Book和rtd 均OK*/
+.wy-side-nav-search>div.version {
+ font-size: 16px;
+ /* 你可以根据需要调整这个值 */
+}
+
+
+.sidebar-logo {
+ width: 500px;
+ /* 或者使用百分比 */
+ height: auto;
+ max-width: 90%;
+ max-height: 90%;
+}
+
+
+.sidebar-content {
+ line-height: 1.0;
+ /* 行间距是字体大小的1.5倍 */
+}
+
+.sidebar {
+ padding: 20px;
+ /* 内边距 */
+ margin-bottom: 20px;
+ /* 外边距 */
+}
+
+.sidebar-text {
+ font-size: 30px;
+}
+/* 修改侧边栏的背景颜色 */
+.wy-nav-side {
+ background-color: #cecece !important;
+}
+
+/* 针对导航栏链接的选择器 */
+.wy-nav-side a {
+ color: #000000;
+ /* 修改为您需要的颜色 */
+}
+
+/* 如果需要，您可以添加 hover 和 active 状态的样式 */
+.wy-nav-side a:hover {
+ color: #fffcfc;
+}
+
+.wy-nav-side .current>a {
+ color: #108bf0 !important;
+ font-weight: bold !important;
+ /* 设置为粗体 */
+ /* 当前活动项的颜色 */
+}
+
+/* 提示：不同版本的 Sphinx 主题生成的 HTML 结构可能有所不同，请根据实际情况调整选择器 */
+h1.wy-banner-title {
+ color: #0267da !important;
+ /* 将此处的颜色替换为您希望的颜色 */
+}
+
+/* 如果也需要修改小标题 */
+h2.wy-banner-subtitle {
+ color: #7b7b7b !important;
+ /* 替换为希望的颜色 */
+}
+
+.wy-side-nav-search>a {
+ color: #ffffff !important;
+ /* 将 #your-color 替换为你想要颜色的十六进制代码 */
+}
+
+
+/* 调整最大宽度 OK */
+.wy-nav-content {
+ max-width: 960px;
+
+}
+
+
+/* 可选：调整侧边栏宽度 */
+/* .wy-side-scroll {
+ width: 300px;
+
+} */
\ No newline at end of file
diff --git a/docs/source/_static/custom.js b/docs/source/_static/custom.js
new file mode 100755
index 00000000..f405b0d4
--- /dev/null
+++ b/docs/source/_static/custom.js
@@ -0,0 +1,34 @@
+// custom.js 可以禁止自动折叠，但不能跳转
+// document.addEventListener('DOMContentLoaded', function () {
+// // 展开所有侧边栏目录项
+// var toctreeItems = document.querySelectorAll('.toctree-l1');
+// toctreeItems.forEach(function (item) {
+// item.classList.add('current');
+// });
+
+// // 监听点击事件，确保点击标题时不会折叠其他标题，并且能够跳转到相应的文档部分
+// document.querySelectorAll('.toctree-l1 a').forEach(function (link) {
+// link.addEventListener('click', function (event) {
+// // 阻止默认的折叠行为
+// event.preventDefault();
+// // 展开点击的标题
+// var parentLi = this.closest('li');
+// parentLi.classList.add('current');
+// // 移除其他同级目录项的 'current' 类
+// parentLi.parentElement.children.forEach(function (sibling) {
+// if (sibling !== parentLi) {
+// sibling.classList.remove('current');
+// }
+// });
+// // 跳转到相应的文档部分
+// var target = this.getAttribute('href');
+// if (target.startsWith('#')) {
+// document.querySelector(target).scrollIntoView();
+// } else {
+// // 如果链接不是锚点，则在新窗口或当前窗口打开链接
+// window.open(target, '_blank');
+// }
+// });
+// });
+// });
+
diff --git a/docs/source/_static/orbbec-light_no_colour.svg b/docs/source/_static/orbbec-light_no_colour.svg
new file mode 100755
index 00000000..a3b6a754
--- /dev/null
+++ b/docs/source/_static/orbbec-light_no_colour.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/source/_static/orbbec_footerlogo_3d_world.svg b/docs/source/_static/orbbec_footerlogo_3d_world.svg
new file mode 100755
index 00000000..7f702a6d
--- /dev/null
+++ b/docs/source/_static/orbbec_footerlogo_3d_world.svg
@@ -0,0 +1 @@
+
\ No newline at end of file
diff --git a/docs/source/_static/orbbec_logo.png b/docs/source/_static/orbbec_logo.png
new file mode 100755
index 00000000..7a60b4c3
Binary files /dev/null and b/docs/source/_static/orbbec_logo.png differ
diff --git a/docs/source/_static/orbbec_logo2.png b/docs/source/_static/orbbec_logo2.png
new file mode 100755
index 00000000..3cd81012
Binary files /dev/null and b/docs/source/_static/orbbec_logo2.png differ
diff --git a/docs/source/_static/orbbec_logo4.png b/docs/source/_static/orbbec_logo4.png
new file mode 100755
index 00000000..92f681ca
Binary files /dev/null and b/docs/source/_static/orbbec_logo4.png differ
diff --git a/docs/source/_static/orbbec_only_english_logo.svg b/docs/source/_static/orbbec_only_english_logo.svg
new file mode 100755
index 00000000..775cbc0b
--- /dev/null
+++ b/docs/source/_static/orbbec_only_english_logo.svg
@@ -0,0 +1,53 @@
+
diff --git a/docs/source/_static/theme.js b/docs/source/_static/theme.js
new file mode 100755
index 00000000..966d5ee6
--- /dev/null
+++ b/docs/source/_static/theme.js
@@ -0,0 +1,212 @@
+// 创建一个自执行的函数，用于封装模块定义和执行逻辑
+!function (n) {
+ // 定义模块存储对象和模块导出相关函数
+ var e = {};
+ function t(i) {
+ // 模块缓存逻辑，避免重复执行
+ if (e[i]) return e[i].exports;
+ var o = e[i] = { i: i, l: !1, exports: {} };
+ // 执行模块定义函数并缓存结果
+ return n[i].call(o.exports, o, o.exports, t),
+ o.l = !0,
+ o.exports
+ }
+ // 初始化模块系统，定义模块数组、缓存对象、导出函数等
+ t.m = n,
+ t.c = e,
+ t.d = function (n, e, i) {
+ t.o(n, e) || Object.defineProperty(n, e, { enumerable: !0, get: i })
+ },
+ t.r = function (n) {
+ "undefined" != typeof Symbol && Symbol.toStringTag && Object.defineProperty(n, Symbol.toStringTag, { value: "Module" }),
+ Object.defineProperty(n, "__esModule", { value: !0 })
+ },
+ t.t = function (n, e) {
+ if (1 & e && (n = t(n)), 8 & e) return n;
+ if (4 & e && "object" == typeof n && n && n.__esModule) return n;
+ var i = Object.create(null);
+ if (t.r(i), Object.defineProperty(i, "default", { enumerable: !0, value: n }),
+ 2 & e && "string" != typeof n) for (var o in n)
+ t.d(i, o, function (e) { return n[e] }.bind(null, o));
+ return i
+ },
+ t.n = function (n) {
+ var e = n && n.__esModule ? function () { return n.default } : function () { return n };
+ return t.d(e, "a", e), e
+ },
+ t.o = function (n, e) { return Object.prototype.hasOwnProperty.call(n, e) },
+ t.p = "",
+ // 执行入口模块
+ t(t.s = 0)
+}([
+ // 定义模块数组，每个模块是一个函数
+ function (n, e, t) {
+ // 执行依赖模块并导出结果
+ t(1),
+ n.exports = t(3)
+ },
+ function (n, e, t) {
+ // 根据环境获取jQuery对象
+ (function () {
+ var e = "undefined" != typeof window ? window.jQuery : t(2);
+ // 定义并导出ThemeNav对象
+ n.exports.ThemeNav = {
+ navBar: null,
+ win: null,
+ winScroll: !1,
+ winResize: !1,
+ linkScroll: !1,
+ winPosition: 0,
+ winHeight: null,
+ docHeight: null,
+ isRunning: !1,
+ // 启用导航栏功能
+ enable: function (n) {
+ var t = this;
+ void 0 === n && (n = !0),
+ t.isRunning || (t.isRunning = !0,
+ e((function (e) {
+ t.init(e),
+ t.reset(),
+ t.win.on("hashchange", t.reset),
+ n && t.win.on("scroll", (function () {
+ t.linkScroll || t.winScroll || (t.winScroll = !0,
+ requestAnimationFrame((function () {
+ t.onScroll()
+ })))
+ })),
+ t.win.on("resize", (function () {
+ t.winResize || (t.winResize = !0,
+ requestAnimationFrame((function () {
+ t.onResize()
+ })))
+ })),
+ t.onResize()
+ })))
+ },
+ // 启用粘性导航栏
+ enableSticky: function () {
+ this.enable(!0)
+ },
+ // 初始化导航栏
+ init: function (n) {
+ n(document);
+ var e = this;
+ this.navBar = n("div.wy-side-scroll:first"),
+ this.win = n(window),
+ n(document).on("click", "[data-toggle='wy-nav-top']", (function () {
+ n("[data-toggle='wy-nav-shift']").toggleClass("shift"),
+ n("[data-toggle='rst-versions']").toggleClass("shift")
+ })).on("click", ".wy-menu-vertical .current ul li a", (function () {
+ var t = n(this);
+ n("[data-toggle='wy-nav-shift']").removeClass("shift"),
+ n("[data-toggle='rst-versions']").toggleClass("shift"),
+ e.toggleCurrent(t),
+ e.hashChange()
+ })).on("click", "[data-toggle='rst-current-version']", (function () {
+ n("[data-toggle='rst-versions']").toggleClass("shift-up")
+ })),
+ n("table.docutils:not(.field-list,.footnote,.citation)").wrap(""),
+ n("table.docutils.footnote").wrap(""),
+ n("table.docutils.citation").wrap(""),
+ n(".wy-menu-vertical ul").not(".simple").siblings("a").each((function () {
+ var t = n(this);
+ expand = n(''),
+ expand.on("click", (function (n) {
+ return e.toggleCurrent(t),
+ n.stopPropagation(),
+ !1
+ })),
+ t.prepend(expand)
+ }))
+ },
+ // 重置导航栏状态
+ reset: function () {
+ var n = encodeURI(window.location.hash) || "#";
+ try {
+ var e = $(".wy-menu-vertical"),
+ t = e.find('[href="' + n + '"]');
+ if (0 === t.length) {
+ var i = $('.document [id="' + n.substring(1) + '"]').closest("div.section");
+ 0 === (t = e.find('[href="#' + i.attr("id") + '"]')).length && (t = e.find('[href="#"]'))
+ }
+ if (t.length > 0) {
+ $(".wy-menu-vertical .current").removeClass("current").attr("aria-expanded", "false"),
+ t.addClass("current").attr("aria-expanded", "true"),
+ t.closest("li.toctree-l1").parent().addClass("current").attr("aria-expanded", "true");
+ for (let n = 1; n <= 10; n++)
+ t.closest("li.toctree-l" + n).addClass("current").attr("aria-expanded", "true");
+ t[0].scrollIntoView()
+ }
+ } catch (n) {
+ console.log("Error expanding nav for anchor", n)
+ }
+ },
+ // 滚动事件处理
+ onScroll: function () {
+ this.winScroll = !1;
+ var n = this.win.scrollTop(),
+ e = n + this.winHeight,
+ t = this.navBar.scrollTop() + (n - this.winPosition);
+ n < 0 || e > this.docHeight || (this.navBar.scrollTop(t),
+ this.winPosition = n)
+ },
+ // 窗口大小变化事件处理
+ onResize: function () {
+ this.winResize = !1,
+ this.winHeight = this.win.height(),
+ this.docHeight = $(document).height()
+ },
+ // hash变化事件处理
+ hashChange: function () {
+ this.linkScroll = !0,
+ this.win.one("hashchange", (function () {
+ this.linkScroll = !1
+ }))
+ },
+ // 切换当前导航项
+ toggleCurrent: function (n) {
+ var e = n.closest("li");
+ // 20201030 a
+ e.siblings("li.current").removeClass("current").attr("aria-expanded", "false"),
+ e.siblings().find("li.current").removeClass("current").attr("aria-expanded", "false");
+ var t = e.find("> ul li");
+ t.length && (t.removeClass("current").attr("aria-expanded", "false"),
+ e.toggleClass("current").attr("aria-expanded", (function (n, e) {
+ return "true" == e ? "false" : "true"
+ })))
+ }
+ },
+ "undefined" != typeof window && (window.SphinxRtdTheme = {
+ Navigation: n.exports.ThemeNav,
+ StickyNav: n.exports.ThemeNav
+ }),
+ // 实现跨浏览器的requestAnimationFrame和cancelAnimationFrame方法
+ function () {
+ for (var n = 0, e = ["ms", "moz", "webkit", "o"], t = 0; t < e.length && !window.requestAnimationFrame; ++t)
+ window.requestAnimationFrame = window[e[t] + "RequestAnimationFrame"],
+ window.cancelAnimationFrame = window[e[t] + "CancelAnimationFrame"] || window[e[t] + "CancelRequestAnimationFrame"];
+ window.requestAnimationFrame || (window.requestAnimationFrame = function (e, t) {
+ var i = (new Date).getTime(),
+ o = Math.max(0, 16 - (i - n)),
+ r = window.setTimeout((function () {
+ e(i + o)
+ }), o);
+ return n = i + o,
+ r
+ }),
+ window.cancelAnimationFrame || (window.cancelAnimationFrame = function (n) {
+ clearTimeout(n)
+ })
+ }()
+ }).call(window)
+ },
+ function (n, e) {
+ // 导出jQuery对象
+ n.exports = jQuery
+ },
+ function (n, e, t) {
+ // 未定义的模块体
+ }
+]);
+
diff --git a/docs/source/_templates/disable-layout.html b/docs/source/_templates/disable-layout.html
new file mode 100755
index 00000000..1ff02ee7
--- /dev/null
+++ b/docs/source/_templates/disable-layout.html
@@ -0,0 +1,292 @@
+{# TEMPLATE VAR SETTINGS #}
+{%- set url_root = pathto('', 1) %}
+{%- if url_root == '#' %}{% set url_root = '' %}{% endif %}
+{%- if not embedded and docstitle %}
+{%- set titlesuffix = " — "|safe + docstitle|e %}
+{%- else %}
+{%- set titlesuffix = "" %}
+{%- endif %}
+{%- set lang_attr = 'en' if language == None else (language | replace('_', '-')) %}
+{%- set sphinx_writer = 'writer-html5' if html5_doctype else 'writer-html4' -%}
+
+{# Build sphinx_version_info tuple from sphinx_version string in pure Jinja #}
+{%- set (_ver_major, _ver_minor) = (sphinx_version.split('.') | list)[:2] | map('int') -%}
+{%- set sphinx_version_info = (_ver_major, _ver_minor, -1) -%}
+
+
+= (7, 2) %} data-content_root="{{
+content_root }}"{% endif %}>
+
+
+
+ {{- metatags }}
+
+ {%- block htmltitle %}
+ {{ title|striptags|e }}{{ titlesuffix }}
+ {%- endblock -%}
+
+ {#- CSS #}
+ {%- if sphinx_version_info
+ < (4, 0) -%}
+
+ {%- endif %}
+ {%- for css_file in css_files %}
+ {%- if css_file|attr("filename") %}
+ {{ css_tag(css_file) }}
+ {%- else %}
+
+ {%- endif %}
+ {%- endfor %}
+
+ {# "extra_css_files" is a theme option and it's always a string #}
+ {%- for css_file in extra_css_files %}
+
+ {%- endfor -%}
+
+ {#- FAVICON
+ favicon_url is the only context var necessary since Sphinx 4.
+ In Sphinx
+ <4, we use favicon but need to prepend path info. #} {%- set _favicon_url=favicon_url | default(pathto('_static/' +
+ (favicon or "" ), 1)) %} {%- if favicon_url or favicon %}
+ {%- endif %}
+
+ {#- CANONICAL URL (deprecated) #}
+ {%- if theme_canonical_url and not pageurl %}
+
+ {%- endif -%}
+
+ {#- CANONICAL URL #}
+ {%- if pageurl %}
+
+ {%- endif -%}
+
+ {#- JAVASCRIPTS #}
+ {%- block scripts %}
+
+ {%- if not embedded %}
+ {# XXX Sphinx 1.8.0 made this an external js-file, quick fix until we refactor the template to inherert more blocks
+ directly from sphinx #}
+ {%- if sphinx_version_info >= (1, 8) -%}
+ {%- if sphinx_version_info < (4, 0) -%}
+ {%- endif -%}
+ {%- for scriptfile in script_files %}
+ {{ js_tag(scriptfile) }}
+ {%- endfor %}
+ {%- else %}
+
+ {%- for scriptfile in script_files %}
+
+ {%- endfor %}
+ {%- endif %}
+
+
+ {#- OPENSEARCH #}
+ {%- if use_opensearch %}
+
+ {%- endif %}
+ {%- endif %}
+ {%- endblock %}
+
+ {%- block linktags %}
+ {%- if hasdoc('about') %}
+
+ {%- endif %}
+ {%- if hasdoc('genindex') %}
+
+ {%- endif %}
+ {%- if hasdoc('search') %}
+
+ {%- endif %}
+ {%- if hasdoc('copyright') %}
+
+ {%- endif %}
+ {%- if next %}
+
+ {%- endif %}
+ {%- if prev %}
+
+ {%- endif %}
+ {%- endblock %}
+ {%- block extrahead %} {% endblock %}
+
+
+
+
+ {%- block extrabody %} {% endblock %}
+
+ {#- SIDE NAV, TOGGLES ON MOBILE #}
+
+
+
+
+ {#- MOBILE NAV, TRIGGLES SIDE NAV ON TOGGLE #}
+ {#- Translators: This is an ARIA section label for the navigation menu that is visible when viewing the page
+ on mobile devices -#}
+
+
+
+ {% endblock %}
+
+
+
+
\ No newline at end of file
diff --git a/docs/source/image/align_depth_color/image3.png b/docs/source/image/align_depth_color/image3.png
new file mode 100644
index 00000000..58322895
Binary files /dev/null and b/docs/source/image/align_depth_color/image3.png differ
diff --git a/docs/source/image/align_depth_color/image4.jpg b/docs/source/image/align_depth_color/image4.jpg
new file mode 100644
index 00000000..b204c845
Binary files /dev/null and b/docs/source/image/align_depth_color/image4.jpg differ
diff --git a/docs/source/image/disparity_search_offset/search_offset0.png b/docs/source/image/disparity_search_offset/search_offset0.png
new file mode 100644
index 00000000..27237215
Binary files /dev/null and b/docs/source/image/disparity_search_offset/search_offset0.png differ
diff --git a/docs/source/image/interleave_ae_mode/interleave_ae0.jpeg b/docs/source/image/interleave_ae_mode/interleave_ae0.jpeg
new file mode 100644
index 00000000..7655e93f
Binary files /dev/null and b/docs/source/image/interleave_ae_mode/interleave_ae0.jpeg differ
diff --git a/docs/source/image/interleave_ae_mode/interleave_ae1.jpeg b/docs/source/image/interleave_ae_mode/interleave_ae1.jpeg
new file mode 100644
index 00000000..ac4a770d
Binary files /dev/null and b/docs/source/image/interleave_ae_mode/interleave_ae1.jpeg differ
diff --git a/docs/source/image/multi_camera_synced/multi_camera_synced1.png b/docs/source/image/multi_camera_synced/multi_camera_synced1.png
new file mode 100644
index 00000000..87f2cbd5
Binary files /dev/null and b/docs/source/image/multi_camera_synced/multi_camera_synced1.png differ
diff --git a/docs/source/image/multi_camera_synced/multi_camera_synced2.png b/docs/source/image/multi_camera_synced/multi_camera_synced2.png
new file mode 100644
index 00000000..9c883b87
Binary files /dev/null and b/docs/source/image/multi_camera_synced/multi_camera_synced2.png differ
diff --git a/docs/source/image/point_cloud/image5.jpg b/docs/source/image/point_cloud/image5.jpg
new file mode 100644
index 00000000..03b65e9b
Binary files /dev/null and b/docs/source/image/point_cloud/image5.jpg differ
diff --git a/docs/source/image/point_cloud/image6.jpg b/docs/source/image/point_cloud/image6.jpg
new file mode 100644
index 00000000..29b1aad8
Binary files /dev/null and b/docs/source/image/point_cloud/image6.jpg differ
diff --git a/docs/source/license.md b/docs/source/license.md
new file mode 100755
index 00000000..30afe30a
--- /dev/null
+++ b/docs/source/license.md
@@ -0,0 +1,14 @@
+## License
+
+Copyright 2024 Orbbec INC.
+
+Licensed under the Apache License, Version 2.0 (the "License"); you may not use this project except in compliance with
+the License. You may obtain a copy of the License at
+
+[http://www.apache.org/licenses/LICENSE-2.0](http://www.apache.org/licenses/LICENSE-2.0)
+
+Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "
+AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific
+language governing permissions and limitations under the License.
+
+Other names and brands may be claimed as the property of others.