-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
realsense-ros does not work on a Xavier (2.2.10) #1018
Comments
Finally I have downgraded realsense some versions until I have find a stable version which works. The final setup is this:
|
I met the similar case. |
@furushchev I face the similar problem when use two or more cameras. It always show device or resource busy even when the cpu usage is below 30%. Did you able to resolve this problem? |
@szx0112 Hi, I ended up removing librealsense installed via |
@furushchev Thanks for the quick reply. My librealsense is also build from source with the same sdk and ros version as @mcalafat-earthrover mentioned. On realsense-viewer, it can stream at most 2 cameras with full resolution (color+depth). However when use realsense ros, it always show Did you just follow the JetsonHack for the sdk installation? Patch kernel? The usb-hub if used is powered (my usb hub is not powered but I don't think it is a major issue)? Sorry for many questions. |
@szx0112 I followed the script found at https://github.com/jetsonhacks/buildLibrealsense2Xavier but modified to support later L4T. |
Great. I am on L4T 32.3.1 (Jetpack 4.3) without kernel patch (as jetsonhack mentioned). I guess it is still needed for ROS? I will try to re-install it with your version. Thank you for the help @furushchev ! |
Can we close this ticket if there is no other question? |
I think we should keep the issue open for now. If indeed building from source, as @furushchev suggests, fixes the issue then something needs to be fixed the the apt-get version. I am currently looking into issues relating several devices. |
@doronhi @RealSenseCustomerSupport I cannot check by myself since I have a few test configuration. Let's wait reports from other users who use multiple devices simultaneously with apt-get configuration. |
Just add a quick comment here. Finally I end up with the configuration suggested by @furushchev with the downgraded librealsense (build from source). I am now able to run two d435i cameras with full resolution (1280x720) and high frame rate (15HZ) with both color and depth_aligned frames enabled on ROS. If we want to add more cameras, we have to either reduce the resolution or drop the frame rate (actually the frame rate will drop by itself somehow). I guess the bottleneck is caused by the usb power supply on xavier. It seems that at most 4.5W can be supplied in total by the two usb ports. However, according to the realsense multi-camera sync whitepaper, each realsense camera may consume more than 2W power (with full resolution). |
@szx0112 Interesting... FYI, I actually use a PCIe-USB card to support multiple camera devices on Xavier since all USB ports on Xavier developer kit share bandwidth of USB3.0. |
@furushchev Thanks for sharing this link, we might start to take a look at those PCIe cards. BTW, just curious how many cameras have you tested (with PCIe) on Xavier? Our ideal case is to make 4 or 5 D435i works at full resolutions and frame rate (~30HZ). |
Please let us know if there is any further help needed in regard to the original topic. There's no activity for 30+ days. |
Hi!
I have installed librealsense 2.30.0 on my Jetson Xavier with help of this guide Jetson Installation.
Then I installed realsense-ros 2.2.10 compatible with the librealsense version installed before.
I also updated the firmware of my D435 depth camera up to date (it is 5.12.01).
My problem is the next: when I try to launch the rs-camera.launch in order to start receiving some visual data, I get this output:
In addition, I have tried the camera on my laptop (with librealsense 2.31.0 on it) and it is correctly working and displaying images.
Thank you very much!
The text was updated successfully, but these errors were encountered: