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

Throwing an error of "rs2::invalid_value_error" when using D455 #13634

Open
AMLIFY opened this issue Dec 27, 2024 · 5 comments
Open

Throwing an error of "rs2::invalid_value_error" when using D455 #13634

AMLIFY opened this issue Dec 27, 2024 · 5 comments

Comments

@AMLIFY
Copy link

AMLIFY commented Dec 27, 2024

  • Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

  • All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)


Required Info
Camera Model D435i/D455
Firmware Version (Open RealSense Viewer --> Click info)
Operating System & Version Ubuntu 22
Kernel Version (Linux Only) Linux 5.15.148-tegra
Platform NVIDIA Jetson Orin NX Engineering Reference Developer Kit
SDK Version 2.55.1
Language {C++}
Segment {SLAM }

Issue Description

Recently I'm depolying ORB_SLAM3 on the Jetson developer kit, and I tested the codes seperately with Intel RealSense D435i and D455(with their specific intrinsics). The program ran succesfully with D435i. However, it faced some errors when using D455.:

terminate called after throwing an instance of 'rs2::invalid_value_error'
  what():  get_xu(ctrl=1) failed! Last Error: Resource temporarily unavailable

And I found that the error would appear when running the codes below:
get_sensor_option(sensor);
and:
rs2_intrinsics intrinsics_cam = cam_stream.as<rs2::video_stream_profile>().get_intrinsics();
I'm wondering why the same API can't work with D455, and I didn't find similar problem in the previous issues. Thanks in advance!

@MartyG-RealSense
Copy link
Collaborator

Hi @AMLIFY Do you have access to the RealSense Viewer tool, please? If you do then please try using the instructions at #10182 (comment) to reset the camera's calibration to its factory-new settings to see whether it resolves your problem.

@AMLIFY
Copy link
Author

AMLIFY commented Dec 31, 2024

Hi @AMLIFY Do you have access to the RealSense Viewer tool, please? If you do then please try using the instructions at #10182 (comment) to reset the camera's calibration to its factory-new settings to see whether it resolves your problem.

Thanks for your resolution. I've got the RealSense Viewer tool, and I'll try to recalibrate it. I'll update soon.

@AMLIFY
Copy link
Author

AMLIFY commented Dec 31, 2024

Hi @AMLIFY Do you have access to the RealSense Viewer tool, please? If you do then please try using the instructions at #10182 (comment) to reset the camera's calibration to its factory-new settings to see whether it resolves your problem.

Hello, I tried the resolution you mentioned, and the same error appeared

@AMLIFY
Copy link
Author

AMLIFY commented Dec 31, 2024

Hi, my colleague used another D455 to run the same code, and it went well without throwing the error I mentioned. Both of our devices are brand new, so is it the problem of my specific device?

@MartyG-RealSense
Copy link
Collaborator

Does it make a difference if you unplug the micro-sized end of the USB cable from the base of your D455, turn the connector around the other way and re-insert it? Sometimes the camera will work better when the micro-sized connector is inserted in one particular orientation of the two insertion directions available.

Do you have access to your colleague's D455? If so, have you tried swapping their USB cables to test whether the problem is with your camera's USB cable?

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