-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't execute "ros2 run realsense2_camera realsense2_camera_node" #3158
Comments
Hi @drinkBr That rgb_camera.power_line_frequency message can usually be ignored. The power_line_frequency parameter is usually configured in situations where you have fluorescent lights on the ceiling that are interfering with the image (because they flicker at frequencies that are hard to see with the human eye) and you need to change its value to reduce the interference. Do you experience the same problems if you launch with ros2 launch instead of ros2 run, please?
|
I executed
|
xioctl(UVCIOC_CTRL_QUERY) errors are typically related to a conflict between librealsense and the Linux kernel. Such conflicts may be avoided if librealsense is built from source code with CMake with the flag -DFORCE_RSUSB_BACKEND=TRUE included in the CMake build instruction. Which method did you use to install librealsense on your Pi, please? |
I understand how to avoid the error, but I don't know exactly what actions to take. Since I am a beginner with Ubuntu, I would appreciate a simplified explanation.
The specific steps are as follows. I have also included the URL I referenced.
-install librealsense2-
-LibUVC-backend installation-
Reference Thanks. |
To build librealsense from source code in RSUSB = true mode, you need additional flags included in your CMake build command. At the moment you are using this:
This command will not build librealsense in RSUSB mode though. To do so, please try the build command below.
This command comes from my RSUSB installation guide at IntelRealSense/librealsense#9931 (comment) I note that after performing the CMake build, you then used the libuvc backend script. But the CMake build process will have already installed librealsense, so doing a libuvc backend build afterwards means that you could have two separate installations of librealsense on the same computer that could potentially conflict with each other. |
I am currently working on this, so I will report back once it's finished. I have a separate question. I want to obtain RGB and depth images from Realsense based on key inputs. However, I read on another page that images are obtained from the topic, which made me wonder. Since it is not possible to perform key input and image subscription at the same time, I think this might be difficult. Is there any solution to this? I would like to hear your opinion. |
Some RealSense Python users write a script that subscribes to ROS topics and has the script use those as the camera data. The link below has an example of doing so. https://stackoverflow.com/questions/62938146/getting-realsense-depth-frame-in-ros The RealSense ROS wrapper also provides some example ROS2 'node scripts' in Python language. https://github.com/IntelRealSense/realsense-ros/tree/ros2-master/realsense2_camera/scripts |
I tested two methods for this.
After executing this, I immediately ran realsense-viewer and was able to confirm both RGB and Depth images. Then, when I ran
When I checked realsense-viewer, I could no longer get the Depth image, and the following error occurred.
Second,
As before, when I ran realsense-viewer, I was able to confirm both RGB and Depth images. However, when I tried executing ros2 run realsense2_camera realsense2_camera_node, the same error appeared without success. After that, I checked realsense-viewer again, and I could no longer get the Depth image, and the same error as before was displayed. Are the commands I entered correct? I would like to hear your opinion. |
The commands that you entered are correct. If your librealsense version is 2.55.1 though then the firmware version installed in your camera should be the current latest 5.16.0.1 version instead of the 5.13.0.55 currently installed. |
Hi @drinkBr Do you require further assistance with this case, please? Thanks! |
Sorry for the late reply.
I don't have a Raspberry Pi at hand right now, so I can't verify this. I will send another message later this week. |
You're very welcome. I look forward to your next update. Good luck! |
I have verified this, and when I checked with
Thanks. |
Do you have access to any other computers other than your Pi that you could attempt a firmware update on? |
Yes, I have a Windows PC. |
The firmware driver is stored inside the camera hardware and not on the computer. So if you are able to install the RealSense Viewer tool on your Windows computer and update the firmware in it then the updated firmware will be carried back to the Pi inside the camera. You can download and run the Viewer on its own on Windows using the Intel.RealSense.Viewer.exe file in the Assets file list at the link below. https://github.com/IntelRealSense/librealsense/releases/tag/v2.55.1 |
Issue Description
I encountered the following error when executing
ros2 run realsense2_camera realsense2_camera_node
.I believe that it is necessary to set the value of rgb_camera.power_line_frequency, but I would like to hear your opinion.
Also, after this error was displayed, I executed realsense-viewer, and when I turned on the Stereo Module, the following error appeared. I confirmed that the same error message appeared when executing
ros2 run realsense2_camera realsense2_camera_node
, so I believe they are related. I would like to hear your opinion.The text was updated successfully, but these errors were encountered: