-
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
Couldn't resolve requests in D435i #13596
Comments
Hi @yizhixia666 Does the error with the depth line still occur at 848x480 resolution if you set its FPS to the supported minimum of 6 instead of 60? |
Thanks for your reply! No matter what the resolution and the FPS is, the error is the same——"couldn't resolve requests". Now i can't find a correct way to run the code smoothly. |
What happens if you remove the word config from the brackets of the pipeline start line? The script should then ignore the config.enable_stream lines and apply the default stream configurations for depth and color that the camera is currently able to provide.
|
After removing the word"config", the script has no error! Nothing outputs in the terminal! |
The script code above can access the streams now, but cannot do anything useful with the streams. There is a test script at the link below that you can use to make the program produce a visible on-screen output. https://github.com/IntelRealSense/librealsense/blob/master/wrappers/python/readme.md#examples |
Please try next the test script below and remove config again from the pipeline start brackets. As the removal of 'config' from the brackets enables a script to work, this confirms that the problem is with the resolution / FPS defined in the Yes you can set custom resolution and FPS with config lines. The code that you used in those lines is correct, but for some reason the camera is not supporting that configuration for the depth stream. Does it make a difference if you unplug the micro-sized end of the USB cable from the side of the camera, turn the connector around the other way and re-insert it into the camera (USB-C cables are two-way insertion at the micro-sized end). |
Thanks for your suggestion! I just tried the method you mentioned and even restarted the system. But once config is added to pipeline.line(), an error will be reported. |
Please try inserting the block of Python code below at the line immediately before the pipeline start line to reset the camera with the
|
OK!I will get back for you in a few hours,thank you |
Hi! It seems to be a new error like this: for dev in devices: RuntimeError: xioctl(VIDIOC_S_EXT_CTRLS) failed Last Error: Invalid argument |
If programs run once the 'config' command is removed from the pipe start brackets then it suggests that your pyrealsense2 installation is okay and does not have an obvious fault. It is not clear though why it is having problems with config instructions or with hardware reset. Would it be possible for you to use the default stream configurations that are applied when config is not used? For a D435i that is 848x480 depth at 30 FPS and 1280x720 color at 30 FPS when on a USB 3 connection. |
Can I understand that if I don't set config.enable_stream() and directly use pipeline.start(), it corresponds to the default stream configurations? |
You are correct. If config instructions are not used then the default stream configurations are automatically used. |
OK! I will test it in Windows 11 to see what the reason is. Thank you very much! |
Hi! It is tested successfully in Win11. |
Thanks very much for the confirmation of success in your Windows test! |
In addition, I would like to ask whether the RGB image and depth map obtained by pyrealsense2 are aligned |
Hi! I just tried the default stream configuration, and the aligned_depth_frame returned by the method aligned_depth_frame = aligned_frames.get_depth_frame() is None. It seems that everything related to depth will report an error. Is this related to the ARM architecture I am using? |
RGB is not aligned with depth by default. There are rare occasions when alignment does not work on Jetson, though that is usually in ROS rather than the pyrealsense2 wrapper. If you test the SDK's example Python depth-color alignment script align_depth2color.py, is it able to provide an aligned image? |
Unfortunately, align-depth2color.py is stuck in an infinite loop because of aligned_depth_frame=None. Is it possible to solve this problem by upgrading the version of librealsense? |
The issues that you have been experiencing do not sound as though they are related to the librealsense version that you are using. Do you know what your camera firmware driver version is, please? If librealsense 2.50.0 is being used then the firmware version that should be used with it is 5.13.0.50. If you have access to the realsense-viewer tool then you can find the firmware version by clicking on the 'Info' option near the top of realsense-viewer's options side-panel. Another way is to use the command rs-enumerate-devices -s If you can use realsense-viewer then you could also try resetting your camera's calibration to its factory-new defaults using instructions at #10182 (comment) This factory reset also repairs any corruptions in a 'calibration table' stored inside the camera hardware, which can cause the camera to not work correctly if the table has become corrupted. |
Hi! Is there any other way to solve this problem? |
Assuming that the problem is not with the camera or the firmware driver since is works fine on Windows, sometimes when there is an apparently unsolvable problem it gets fixed if a complete wipe of the computer and reinstallation of everything (including Ubuntu) is performed. Doing this can suddenly fix a problem by removing hidden glitches in the operating system, kernel or the librealsense / pyrealsense2 installation that were causing the problem. |
Well, anyway, thank you very much for your advice. |
Hello, I just installed realsense-viewer version 2.55.1. Where does the stereo module display the depth map? |
When realsense-viewer is working correctly, the depth should be displayed in the center panel when Stereo Module is enabled. What method did you use to install realsense-viewer, please? Usually when librealsense is compiled from source code with CMake, it is installed by adding -DBUILD_EXAMPLES=True -DBUILD_GRAPHICAL_EXAMPLES=true to the CMake build instruction. I would not recommend building realsense-viewer separately using its GitHub source code page. https://github.com/IntelRealSense/librealsense/tree/master/tools/realsense-viewer |
I installed realsense-viewer through librealsense. If it is v2.55.1, I cannot view the depth image under “available streams”, only two infrared images. If it is v2.50.0, it will report the above error. But I used v2.50.0 before, and the function was normal. Is it related to the fact that I recently installed the opencv 4.5.5 with cuda? |
If you are using librealsense 2.50.0 then your camera firmware driver should ideally be version 5.13.0.50. Is that the firmware that you currently have installed in your camera, please? |
We established earlier that the camera and firmware driver works fine on your Windows 11 computer and it is Ubuntu that has the problem. Did you perform the wipe and complete reinstallation of your Ubuntu computer that I suggested earlier at #13596 (comment) please? |
We can't reinstall the system |
If the camera works on Windows and you can enable the depth stream in it, could you try resetting the camera to its factory-new settings using the instructions at #10182 (comment) please? As the adjustments made by the reset are saved to the camera hardware, you can take the reset camera back to your Ubuntu computer to test whether it has made a difference. |
Uh! I will try this method, thanks |
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 :)
Issue Description
<Describe your issue / question / feature request / etc..>
The realsense-viewer shows it is USB3.2, and it runs normally in it. “rs.stream.color” this line is normal, but “rs.stream.depth” is not normal. And I have tried many combinations of resolution and frame rate. Could you tell me how to work it out? Thank you very much!
The text was updated successfully, but these errors were encountered: