Skip to content
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

Depth Quality Tool Crashing #10584

Closed
Cpeck71 opened this issue Jun 10, 2022 · 9 comments
Closed

Depth Quality Tool Crashing #10584

Cpeck71 opened this issue Jun 10, 2022 · 9 comments

Comments

@Cpeck71
Copy link

Cpeck71 commented Jun 10, 2022

Required Info
Camera Model L515
Firmware Version 01.05.08.01
Operating System & Version Linux Ubuntu 18.04
Kernel Version (Linux Only) 4.9.253-tegra
Platform NVIDIA Jetson Nano
SDK Version 2.50.0
Language ~
Segment Depth Tool

Issue Description

Howdy Realsense Team,

I'm trying to open the Depth Quality tool, however my computer (Jetson Nano, 4 GB RAM) crashes when it's loading. It doesn't get beyond opening the window for the tool, so I don't ever see any warnings etc. I suspect it might be a RAM issue or other hardware problem but I figured I'd reach out to see if there was a way to diagnose the problem. Looking at previous cases, i saw #4948 but I'm not sure I'm having the same version issue.

Thanks!

@MartyG-RealSense
Copy link
Collaborator

Hi @Cpeck71 4 GB should be a sufficient amount of memory. Is the RealSense Viewer able to open successfully on your Nano, since the Viewer has a similar architecture to the Depth Quality Tool.

@Cpeck71
Copy link
Author

Cpeck71 commented Jun 10, 2022

Hi Marty,

Yes, the viewer works perfectly fine

@MartyG-RealSense
Copy link
Collaborator

If a camera can work normally on the Viewer then it usually works on the Depth Quality Tool as well.

Please try unplugging the micro-sized end of the USB cable from the base of the L515 camera, turning it around the opposite way and re-inserting it (USB-C cables are two-way insertion at the micro-sized end). If it does not resolve the problem with launching the DQT then change the connector back to its previous orientation.

@MartyG-RealSense
Copy link
Collaborator

Hi @Cpeck71 Do you require further assistance with this case, please? Thanks!

@Cpeck71
Copy link
Author

Cpeck71 commented Jun 17, 2022

Hi Marty, I'm sorry I've been busy with another task recently and haven't been able to attend to the depth quality in the past week. I should have time next week to pick it back up, can I keep the issue open in the meantime or should I close it and re-open when I have progress? Whatevers best for y'all.

Thanks!

@MartyG-RealSense
Copy link
Collaborator

If you will likely be picking it up again next week then it's fine to keep it open. You are welcome to close it yourself later if you find that it is going to be longer before you return to it. Good luck!

@Cpeck71
Copy link
Author

Cpeck71 commented Jun 23, 2022

Hi @MartyG-RealSense I'm back! So i just flipped the usb cable but my computer still crashed. (i put it back the other way too)

@Cpeck71
Copy link
Author

Cpeck71 commented Jun 23, 2022

So I think i figured it out (thanks to your flipping the usb comment). I realized that my setup currently has the usb cable it came with plugged into a usb hub, which itself is connected to a usb extension cord, which may have been causing the issue. I plugged the device directly into the computer and it didnt crash!

Thanks for the help

@Cpeck71 Cpeck71 closed this as completed Jun 23, 2022
@MartyG-RealSense
Copy link
Collaborator

That's excellent news that you achieved a positive outcome. Thanks very much for the update :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants