fails to build from sources #3139
Labels
Comments
|
Hi @alonsnir The 4.51.1 wrapper installation is requiring the development branch of librealsense (2.56) rather than the latest master branch. https://github.com/IntelRealSense/librealsense/tree/development If you do not wish to build the develoment branch of librealsense then a workaround is to try building an earlier version of the ROS wrapper for 2.55 from source using the git checkout command below. Alternatively, you can use the latest realsense2_camera released (4.55.1) from ROS apts so that you don't need to colcon the source code.
Another approach to the issue is to edit the CMakeLists.txt file of the ROS wrapper in the way described at #3131 (comment) |
|
I did as suggested: and managed to build. This doesn't work: I'm facing a new issue however, it refuses to set desired resolution and setting camera and depth profiles to default: Attempts to run with launch file and configure the profile there ended with same result. I'm attaching the launch and the log with debug level on. |
|
It appears from the log that depth and RGB are being set to the camera's ROS wrapper defaults (848x480 depth at 30 FPS and 640x480 RGB at 30 FPS). Did you want to set different resolutions to these, please? You can set custom resolutions for the launch by adding profile commands to the rs_launch.py launch instruction. For example:
|
|
@MartyG-RealSense Thanks for the prompt reply. Changed as suggested and it took the settings but now fails with hardware error: |
|
Does it make a difference if you add initial_reset:=true to the launch instruction to reset the camera hardware at launch? |
|
Sorry, my mistake, I was running it with x30. Restarted with x15 and it worked. |
|
You are very welcome. I'm pleased to hear that you succeeded! |
|
Hi @MartyG-RealSense tested launch file: camera-settings.json: realsense: |
|
I note that your listed firmware version in the log is 5.15.0.2. The firmware that should be used with librealsense 2.55.1 is 5.16.0.1. Please update your camera's firmware. |
|
upgraded |
|
Have you tried adding initial_reset:=true to reset the camera at launch, please? Have you also tried not importing the json file? |
|
after reset and without the json |
|
Have you checked whether the streams are being published correctly in RViz despite the Hardware Notification warning messages? Does it make a difference if you unplug the micro-sized end of the USB cable from the side of the camera, turn the connector around the other way and re-insert it (USB-C cables are two-way insertion at the micro-sized end). |
|
@MartyG-RealSense could it be installation instructions here are outdated? It refers to v2.53.1 as latest Intel® RealSense™ SDK 2.0 and that version doesn't support kernels 6.*, |
color stream been published but not the depth |
|
@MartyG-RealSense |
|
Having the infrared streams disabled will not affect depth accuracy. The IR emitter of the camera that aids depth analysis is a separate component from the two IR sensors and can function when the IR streams are disabled. |
|
@MartyG-RealSense note it's on another system i build kernel 6.5 Ubuntu 22.04.4 |
|
On some computers the camera may not be detected after a restart of the computer (not a shutdown). A solution for this can be to shut the computer down completely and then boot the computer by pressing the power button. |
|
same error after complete shutdown and start |
|
On this other system you may need to repeat the git clone installation procedure that you described earlier at #3139 (comment) instead of using apt install, bearing in mind the problems with using librealsense 2.55.1 with the master branch of the SDK. |
|
Hi @MartyG-RealSense, I'm closing this one, as with your help, I have managed to build from sources and run on Ubuntu 22.04 kernel 5.5 (with infra disabled). |
|
Thanks very much @alonsnir for the update! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
failed to build
I have opted to build the SDK as here
The text was updated successfully, but these errors were encountered: