-
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
SR300 is only working on alternate runs #840
Comments
Hi @syedharoonalam |
@dorodnic Here is the dmesg logs after librealsense crashes:
And here is the log after successfully running librealsense:
I can see after the crash, dmesg shows few lines in the end as: uvcvideo: Non-zero status (-71) in video completion handler. Do you think this should be the problem, and any suggestions to fix this error? Also, can you please let me know me where should I find librealsense logs file ? I am not able to get logs from the command you mentioned. |
@syedharoonalam I replied to your info on the JetsonHack site. How did you ever get the Depth image to stop flickering and the IR data to appear on the TX2? The INZI problem is something no one seems to be able to solve! |
@lesreaper you need to apply a patch for INZI support and rebuild the UVC module. Please follow: https://github.com/syedharoonalam/buildJetsonTX2Kernel |
This is awesome @syedharoonalam ! Great work. Very clear instructions, and only one thing that got glossed over a little in the instructions. When you said "follow the patch by realsense", which patch are you referring to for the TX2? |
@syedharoonalam Thanks for the help, I got it all working to some extent. You and I seem to be running into a lot of the same issues. The USB3 connection b/w the Realsense and Jetson fails a lot. Were you ever able to get your problem here to work with the Jetson? |
@icarpis I'm having the same problem with the SR300, it only works every other time. The problem can easily be replicated using the realsense-viewer program, when enabling/disabling the depth/color stream it will show a white screen with "No Frames Received!" text every other time. After a while a notification will come up saying "Frames didn't arrive within 5 seconds". This can be solved in code by simply restarting the pipeline using stop() and start(). However, there is a problem when the two streams become "unsynchronized" such that the depth stream receives no frames while the color stream works like it should, and vice versa. When this happens you have to restart only one of the streams to get them "synchronized" again.
Is there some better way to solve this? |
I just got a D435 and I have the same problem. This seems to be an issue in librealsense and not hardware related. I'm running Ubuntu 16.04 with kernel 4.13 and librealsense 2.9.0. |
[Realsense Customer Engineering Team Comment]
|
[Realsense Customer Engineering Team Comment] Still need any help? |
Thanks, @RealSense-Customer-Engineering. I will check out the latest L4T and get back if found any issues. Thanks! |
[Realsense Customer Engineering Team Comment] |
On Realsense sdk2 2.8.1, SR300 only works on alternate runs. First time camera extracts data, but second time application exits with error:
rs_error was raised when calling rs2_pipeline_wait_for_frames(pipe:0x437740): Frame didn't arrived within 5000
OR
RealSense error calling rs2_pipeline_wait_for_frames(pipe:0x766ad0): Frame didn't arrived within 5000
The error is same in sdk's all examples (C and C++). I made sure that pipe.stop() in C++, and code in //Stop the pipeline streaming //Release resources in C gets called.
Please advise.
The text was updated successfully, but these errors were encountered: