-
Notifications
You must be signed in to change notification settings - Fork 4.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
Nano Orin #13114
Comments
Hi @djaniel There is a known issue for some RealSense users when starting three streams (RGB, depth, IMU) in the RealSense Viewer tool. The problem, which typically manifests as No Frames Received on one of the streams, does not have a fix. It is therefore recommendable to only enable two streams at a time if you experience this problem and need to use the IMU (depth + IMU, or RGB + IMU). Or only use the IMU on its own. The trigger is the enabling of the Motion Module when using three streams, so changing the order that the streams are enabled in does not make a difference. The problem also occurs in program scripts, but can be avoided if creating two separate pipelines (Python) or using callbacks (C++). |
Hi @djaniel Do you require further assistance with this case, please? Thanks! |
I have also run into this problem with my Jetson Orin Nano running Jetpack 6.0. @MartyG-RealSense do you know if this is a librealsense issue or a Jetpack 6.0 issue? In either case, while there may not be a fix at the moment, is a fix in the pipeline or planned for the future? |
Hi @nlitz88 The RealSense Viewer 'enabling three streams' issue with the Motion Module is not related to JetPack 6. I will raise the question of a fix with my Intel RealSense colleagues. It is possible to display depth, RGB and IMU streams in the rs-capture pre-made example program as it is not affected by the issue. If you installed librealsense with the examples included then you should be able to find a pre-built executable version of rs-capture in the usr/local/bin folder of Linux. As mentioned above, when writing your own program script you can workaround the issue to avoid problems occurring by creating two separate pipelines in Python or using callbacks in C++. |
Thanks for getting back @MartyG-RealSense Maybe this deserves its own issue in realsense-ros, but I am wondering if this has anything to do with a similar issue realsense ros has when attempting to launch the realsense camera node with the gyroscope and accelerometer enabled. When I run the following launch command:
I get a very similar output compared to the output Alexander is getting in his post: IntelRealSense/realsense-ros#3162 (comment) My output is as follows:
And so on. Only when I omit both the Just for some context, I have:
Is it possible this is the same underlying problem? |
Quick update: I just downgraded the D435i's firmware to version 5.13.0.50 per NVIDIA's Isaac ROS RealSense setup guide (mainly because that is my target application). NOW, when I run
I only get a few of those "control_transfer returned error" messages, but ultimately I'm getting messages published to both Soooo...maybe downgrading the firmware solved the problem for this scenario? Sorry if this isn't relevant here, just wanted to reported what I found! |
Hi @nlitz88 Do you require further assistance with this case, please? Thanks! |
I believe my problem is solved for now--thank you for steering me in the right direction @MartyG-RealSense ! |
You are very welcome, @nlitz88 - I'm pleased that you had a successful outcome. Thanks very much for the update! |
Case closed due to solution achieved and no further comments received. |
Thank you for your interest. After your reply, I abandoned the idea of launching all streams. I am more cautious, now. |
You are very welcome. Thanks very much for the update! |
Hello
I am having some difficulties when setting up librealsense and camera D435i on a Jetson Nano Orin. Here is my setup:
Issue Description
I recently reinstalled everything on the Jetson Nano Orin (Fresh start, Ubuntu 22, jetson pack 6.0). I installed from source
librealsense
and testedrealsense-viewer
. The only camera that worked with no particular changes to the CMake configuration was D435. Unfortunately , the D435i was listed when typinglsusb
but not shown when launchingrs-enumerate-devices
.I changed the
RSUSB_BACKEND
flag to true, and thers-enumerate-devices
started recognizing the D435i camera. Unfortunately the connection is not reliable,realsense-viewer
crashes when starting all three streams (RGB, depth, IMU). A lot of error messages appear on the console ofrealsense-viewer
. Here is an screenshot:Do you have any suggestions?
The text was updated successfully, but these errors were encountered: