sensors:rgbdcamera

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
sensors:rgbdcamera [2025/08/28 11:31] – clohrsensors:rgbdcamera [2026/10/22 20:39] (current) – external edit 127.0.0.1
Line 35: Line 35:
  
  
-++++ These instructions have not been successfully tested yet|+==== These instructions have not been successfully tested yet ====
 Bon, vous avez besoin d'abord d'un contrôlleur USB 3.0 sinon la Kinect est même pas détectée ! Bon, vous avez besoin d'abord d'un contrôlleur USB 3.0 sinon la Kinect est même pas détectée !
 Ensuite vérifier que vous avez un noyau linux >3.16 minimum car les versions les plus anciennes ont un bug. Ensuite vérifier que vous avez un noyau linux >3.16 minimum car les versions les plus anciennes ont un bug.
Line 48: Line 48:
 # echo 0 > /sys/module/i915/parameters/enable_cmd_parser # echo 0 > /sys/module/i915/parameters/enable_cmd_parser
  
-++++ 
  
 ===== Kinect Skeletal tracking ===== ===== Kinect Skeletal tracking =====
Line 83: Line 82:
  
     - The "native" backend is a Linux kernel driver. It is therefore very dependent on the kernel to run (the latest one (I wrote this in Sept. 2025) is for Linux 6.8.0, the one for legacy Realsense devices is for Linux 4.4)     - The "native" backend is a Linux kernel driver. It is therefore very dependent on the kernel to run (the latest one (I wrote this in Sept. 2025) is for Linux 6.8.0, the one for legacy Realsense devices is for Linux 4.4)
-    - The "libuvc" backend uses the standard uvc+hit kernel drivers and do the job in userland via the standard libuvc library. It is probably less efficient (latency), but it is much more flexible and mostly independent of Linux kernel version.+    - The "libuvc" backend uses the standard uvc+hid kernel drivers and does the job in userland via the standard libuvc library. It is possibly less efficient (latency), but it is much more flexible and mostly independent of Linux kernel version.
  
 So, the idea is to compile librealsense v2.50.0 with the libuvc backend. The following is freely adapted from libuvc_installation.sh (https://github.com/IntelRealSense/librealsense/blob/master/scripts/libuvc_installation.sh#L35-L39) So, the idea is to compile librealsense v2.50.0 with the libuvc backend. The following is freely adapted from libuvc_installation.sh (https://github.com/IntelRealSense/librealsense/blob/master/scripts/libuvc_installation.sh#L35-L39)
Line 89: Line 88:
   * Compile & Install   * Compile & Install
  
-      wget https://github.com/IntelRealSense/librealsense/archive/refs/tags/v2.54.2.tar.gz +      wget https://github.com/IntelRealSense/librealsense/archive/refs/tags/v2.50.0.tar.gz 
-      tar xvf v2.54.2.tar.gz+      tar xvf v2.50.0.tar.gz
       cd ./librealsense-2.50.0       cd ./librealsense-2.50.0
        
Line 96: Line 95:
       sudo udevadm control --reload-rules && sudo udevadm trigger        sudo udevadm control --reload-rules && sudo udevadm trigger 
        
 +      sudo apt-get install -y git cmake libssl-dev freeglut3-dev libusb-1.0-0-dev pkg-config libgtk-3-dev
       mkdir build && cd build       mkdir build && cd build
       cmake ../ -DFORCE_LIBUVC=true -DCMAKE_BUILD_TYPE=release       cmake ../ -DFORCE_LIBUVC=true -DCMAKE_BUILD_TYPE=release
Line 102: Line 102:
  
  
-   * Test+  * Test
  
       rs-enumerate-devices        rs-enumerate-devices 
       realsense-viewer       realsense-viewer
  
- +  * Tips: In case compilation fails on some non-essential SDK functionnalities, try to add one or several of the following compilation options on the cmake command line: `-DCHECK_FOR_UPDATES=OFF` `-DBUILD_EXAMPLES=OFF` `-DBUILD_TOOLS=OFF`
- +
- +
  • sensors/rgbdcamera.1756380717.txt.gz
  • Last modified: 2025/08/28 11:31
  • by clohr