Setting Dynamic reconfig parameters does not return. #3162
Comments
|
If I kill the launch and re-run I always get Only when I reboot, I can re-run the launch file up until the Setting Dynamic reconfig parameters point. |
|
Hi @axkoenig Please try installing dynamic_reconfigure for Noetic manually using the command below to see whether it makes a difference to your launch.
|
|
Hey, thanks for the quick response! I entered your command, and got |
|
You are very welcome. :) I note that your camera firmware driver version is 5.12.6.0. This firmware is designed for the very old librealsense SDK version 2.36.0. For librealsense version 2.50,0, firmware version 5.13.0.50 should be installed in your camera. Please try updating your firmware version. |
|
Ok thanks for the pointer. Do I need to install librealsense from source to get And I get Sorry, I'm a realsense newbie ;) |
|
It's no trouble at all. Everyone was new once. :) The command I do not know what other tools might be omitted by this install method. You could check in the Ubuntu folder usr/local/bin whether rs-fw-update has been installed there. |
|
I've done the firmware upgrade after installing librealsense from source, but the issue still persists, unfortunately. I do get pretty pictures from the camera in RealSenseViewer though. |
|
Ok now I installed the newest version of the Firmware via the RealSenseViewer, and now I am getting slightly more - does this output help? |
|
5.16.0.1 should not be used with SDK 2.50.0 and wrapper 2.3.2, though there are sometimes cases where it does work even though it shouldn't. Does it make a difference if you add initial_reset:=true to your roslaunch instruction to reset the camera at launch. |
|
Ok I am back on the version you recommended. No, unfortunately it makes no difference. Could the |
|
The message If the same problem with getting stuck on dynamic reconfigure also occurs with your D435 then it is likely to be a software issue rather than a camera hardware one. Let's try a different launch method - an RGBD launch instead of rs_camera. First, you will need to install support for an RGBD launch on Noetic using the command below.
Then launch using the rs_rgbd.launch file.
|
|
Hey so I tried this on three different Cameras D455, D435 and D435i and I have the same problem with all of them. My colleagues have the same setup (same kernel, same ros versions, same librealsense version) and it works for them without a problem, so it isn't a problem of the camera. Another intriguing thing is that once I kill the roslaunch that seems stuck, the camera won't ever re-connect - it only shows One more intriguing thing is that if I just unplug the USB cable while it's stuck on |
|
The log warnings Exception: usb device disconnected and failed to open usb interface indicate that the launch is aware that the camera has been disconnected and therefore cannot be accessed. If your colleagues used the exact same installation procedure that you did and with the same configuration, are they also using the exact same model of computer that you are? |
|
For RGBD I have exactly the same problem, unfortunately... |
|
My colleagues have different models and different hardware specifications On 12. Jul 2024, at 12:38, MartyG-RealSense ***@***.***> wrote:
The log warnings Exception: usb device disconnected and failed to open usb interface indicate that the launch is aware that the camera has been disconnected and therefore cannot be accessed.
If your colleagues used the exact same installation procedure that you did and with the same configuration, are they also using the exact same model of computer that you are?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
What could be interpreted from this is that if you all followed the same installation procedure and have the same software and the same versions but it works on their computers but not yours, there could be a conflict with your model of computer specifically. When you built librealsense from source, did you build it with CMake? If you did, then did you include the flag -DFORCE_RSUSB_BACKEND=TRUE in the CMake build instruction? An RSUSB = true source code build of librealsense - described at IntelRealSense/librealsense#9931 (comment) - is not dependent on Linux versions or kernel versions and does not need to have a kernel patch applied to it, so it is very good in situations where the computer hardware is exotic (not typical of a shop-bought PC) or when librealsense may be conflicting with the kernel. |
|
Hi @axkoenig Do you require further assistance with this case, please? Thanks! |
|
Hi, For the librealsense installation I initially followed these docs. I just added realsense-viewer
18/07 19:16:14,431 INFO [140389761197952] (context.cpp:116) ... 5-2-3
18/07 19:16:14,431 INFO [140389761197952] (context.cpp:128) Found 1 RealSense devices (0xff requested & 0xff from device-mask in settings)and it finds the realsense as shown in the command line. But then in the Realsenseviewer the device is not displayed. When I reboot the machine it works (a single time) but when I disconnect the camera and re-connect I have the same problem... Maybe this rings a bell? |
|
Thanks very much for the additional information. How does the camera behave in the Viewer if you launch it in sudo admin permissions mode with sudo realsense-viewer |
System
Issue Description
Hi,
I am connecting my Realsense D455 to an USB 3.2 port. I installed the ROS wrapper via
sudo apt-get install ros-noetic-realsense2-camera. Unfortunatelyroslaunch realsense2_camera rs_camera.launchhangs at the point where it's "Setting Dynamic reconfig parameters". I waited for at least half an hour and nothing is happening. From other posts I see the next print on my screen should beDone Setting Dynamic reconfig parameters., so I assume it has something to do with those.Also the
(Confidence, 0) sensor isn't supported by current device! -- Skipping...seems intriguing, could this be the issue?I also tried the D435 and have the same issue.
Could you please help me out?
The text was updated successfully, but these errors were encountered: