D455 camera - not functioning
Hello,
I am trying to use the D455 camera in my application. The camera was functioning properly for initial 2 days. After that for some reason, I am not able to get the stream from the device. It is constantly throwing a error saying that "Resource temporarily unavailable".
I have tried,
a) Reconnecting the device
b) Made sure no application is using the camera in background.
c) On both Windows-10 and Ubuntu-18.04, still the issue persists.
But the camera is getting detected in rs-enumerate-devices.
Since it was working initially, I am suspecting it to be a hardware issue. Can anyone help me to solve this?
I am using only the recommended configurations(
Camera : D455
Firmware version : 5.12.7.100
Realsense SDK : 2.38.1
The error log, when I started realsense viewer.
$ realsense-viewer
23/10 12:18:59,168 ERROR [140566390667008] (types.h:313) xioctl(VIDIOC_S_CTRL) failed Last Error: Invalid argument
23/10 12:18:59,168 WARNING [140566390667008] (sensor.cpp:632) Exception was thrown when inspecting Raw RGB Camera property Controls exposure time of color camera. Setting any value will disable auto exposure
23/10 12:18:59,176 ERROR [140566390667008] (types.h:313) xioctl(VIDIOC_S_CTRL) failed Last Error: Invalid argument
23/10 12:18:59,176 WARNING [140566390667008] (sensor.cpp:632) Exception was thrown when inspecting Raw RGB Camera property Controls white balance of color image. Setting any value will disable auto white balance
23/10 12:19:04,466 WARNING [140566476357056] (backend-v4l2.cpp:1267) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
When I turn on depth stream,
23/10 12:19:04,466 WARNING [140566476357056] (backend-v4l2.cpp:1267) Pixel format 36315752-1a66-a242-9065-d01814a likely requires patch for fourcc code RW16!
23/10 12:20:13,314 WARNING [140566209713920] (backend-v4l2.cpp:1032) Frames didn't arrived within 5 seconds
23/10 12:20:18,317 WARNING [140566209713920] (backend-v4l2.cpp:1032) Frames didn't arrived within 5 seconds
23/10 12:20:20,764 ERROR [140566276855552] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: get_xu(ctrl=1) failed! Last Error: Device or resource busy
23/10 12:20:21,765 ERROR [140566276855552] (types.h:313) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
23/10 12:20:21,765 ERROR [140566276855552] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
23/10 12:20:22,766 ERROR [140566276855552] (types.h:313) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
23/10 12:20:22,766 ERROR [140566276855552] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
23/10 12:20:23,322 WARNING [140566209713920] (backend-v4l2.cpp:1032) Frames didn't arrived within 5 seconds
23/10 12:20:23,767 ERROR [140566276855552] (types.h:313) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
23/10 12:20:23,767 ERROR [140566276855552] (global_timestamp_reader.cpp:239) Error during time_diff_keeper polling: set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
23/10 12:20:24,767 ERROR [140566276855552] (types.h:313) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: Device or resource busy
-
Hi Karthikeyan A There is a currently a D455 case on the RealSense GitHub forum with the same errors that you are experiencing.
https://github.com/IntelRealSense/librealsense/issues/7617#issuecomment-714999812
Given that more than one person is having this issue, I will consult with Intel and update you when I have information. Thank you very much for your patience.
-
Hi MartyG, Do you have an update? Kindly let me know if the product needs to be replaced for Hardware issue.
-
Hi Karthikeyan A I am just starting some testing to try to replicate your problem with my own D455. I will update you again soon. Thanks very much for your patience.
-
Hi Karthikeyan A I ran thorough tests but was unable to replicate the Exception was thrown when inspecting Raw RGB Camera errors that you experienced.
I was able to generate Error during time_diff_keeper polling though if I started a depth stream and then pulled the USB cable out without stopping the stream first. This could indicate that your errors are related to uncontrolled camera disconnections occurring.
Are there any possibilities during your use of the camera when the USB cable might be pulled or jostled out of the USB port (such being mounted on as a mobile robot)?
-
No MartyG, I have not mounted the device on any mobile robot. I am just evaluating the camera in office environment, the camera was stationary. So for the error you generated by pulling the USB cable out without stopping the stream. How did you solve this? If you could tell me the solution for that error, I will try the same in my side though the cause might be different.
-
I performed further testing in Windows and found that if the camera was pulled out during streaming when using the standalone Intel.RealSense.Viewer.exe version of the Viewer (not the one installed by the SDK installer) then the Error during time_diff_keeper polling error almost never occurred despite many repeats of the pull-out test.
You can test with the standalone Viewer in Windows by downloading it from the 'Assets' list at the bottom of each SDK version's details on the SDK Releases page.
https://github.com/IntelRealSense/librealsense/releases
This Viewer should be launched from the location that you download it to, not with the launcher icon on the Windows desktop.
-
Hi MartyG, I have tried the option using the standalone viewer as you suggested. The camera is still not functioning. Attaching the log and screenshot of the errors.
11:45:12 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\types.h:313 - hr returned: HResult 0x800703e3: "The I/O operation has been aborted because of either a thread exit or an application request."11:45:14 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\global_timestamp_reader.cpp:239 - Error during time_diff_keeper polling:hr returned: HResult 0x8007001f: "A device attached to the system is not functioning."
-
We have not yet tested whether the USB cable has developed a problem. As the problems occur on both Windows and Ubuntu and we have already tried updating the firmware, the other component that both computers have in common (other than the camera hardware itself) is the cable. A faulty cable may allow the camera to be detected by Windows Device Manager or rs-enumerate-devices but not be able to cope once data starts getting continuously passed through it when streaming starts.
Speaking of the Windows Device Manager, could you access it please and look for the RealSense drivers. There should be two of them for a 400 Series camera, Depth and RGB. They may be under the 'Cameras' or 'Imaging Devices' section.
-
MartyG: I am using the standard cable that comes along with the product only. Even I have tried with a different cable. As you can see below, device is being listed.
-
Thank you very much for checking the drivers. Next, could you try performing a calibration of the camera on Windows by downloading and installing the Dynamic Calibrator software in the link below, please?
https://downloadcenter.intel.com/download/29618/Intel-RealSense-D400-Series-Dynamic-Calibration-Tool
-
I installed the Dynamic calibrator in both my ubuntu PC 18.04 and windows 10 ,the application gets hanged, once I click the start calibration button and the application is not streaming the frames on this device D455.To debug, I have a D415 camera working in good condition. With this dynamic calibration tool, I tested D415, it got streaming the frames with no issues.
-
Installing the Dynamic Calibrator software will also have installed a program called CustomRW. Please input the instruction below into the Windows Command Prompt or your Linux terminal to perform a Gold Reset of the camera to its factory-new configuration:
Intel.RealSense.CustomRW -g
-
I reviewed your case again from the beginning to try to get new insights. The summary of the situation seems to be:
- The D455 worked fine, until it suddenly didn't work.
- It is detectable by programs such as rs-enumerate-devices and CustomRW.
- The problems occur on both Windows and Ubuntu
- You tried changing the USB cable (putting the D415 cable on the D455?).
- D415 works fine, which would seem to rule out a problem with the USB ports. Presumably the D415 is also running the same 5.12.8.200 firmware version as the D455?
My next question would be: does the D415 still work if the D455's USB cable is used on it?
-
Could you try your D455 with the rs-capture sample program please? This should display depth, RGB and IMU stream panels in a single window. You can find a pre-made version of this program in Windows that you can launch with a double-leftclick by right-clicking on the RealSense Viewer shortcut icon on the desktop and selecting Open file location from the drop-down menu to open the Tools folder that contains the pre-made executable versions of sample programs.
-
$ rs-capture
11/11 11:01:45,434 ERROR [139716578858752] (global_timestamp_reader.cpp:208) Error during time_diff_keeper polling: get_xu(ctrl=1) failed! Last Error: Success
RealSense error calling rs2_pipeline_wait_for_frames(pipe:0x561c4eb3bab0):
Frame didn't arrive within 15000I have tested almost all the applications Marty. All the applications involving streaming getting hanged. -
Do you experience different results if you update SDK 2.38.1 to 2.39.0 please? You can test this quickly on Windows by using the installer file in the Assets file list.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.39.0
-
As per your earlier comment (https://support.intelrealsense.com/hc/en-us/community/posts/360052144833/comments/360013488754), I have tried the standalone viewer from v2.39.0 and seen the issue was there.
-
I ran some further tests. On one of my Windows laptops I was able to generate the Exception was thrown when inspecting raw RGB Camera property error when launching the Viewer without a camera plugged in. This message did not occur on my other Windows laptop though.
This supports the assertion mentioned earlier in this discussion that on some computers with an attached or built-in non RealSense camera such as a USB or laptop screen webcam, this error may ocur without having any relation to a RealSense camera that is being used on the affected computer.
On the affected computer, inserting a D455 camera then caused a pop-up error box with the message Invalid value in rs2_get_option ... option: Emitter On Off): hwon command failed (response -21= No data to return). Performing a hardware reset of the camera caused the same errior pop-up to occur each time. This occurred when installing the full SDK of both 2.38.1 and 2.39.0.
I went to the Cameras section of the Windows device manager and disabled the built-in UVC webcam of the laptop and launched the Viewer again.
The Exception was thrown when inspecting raw RGB Camera property error and the Invalid value in rs2_get_option error no longer occurred, verifying that the errors were caused by a non-RealSense camera on the system being detected. They returned when the built-in webcam was re-enabled in the device manager.
On your Windows computer, can you open the Cameras section of the device manager whilst the D455 is unplugged and confirm that there is not any cameras listed there, please?
-
Hi Karthikeyan A,After a lapse of two years, I encountered a situation similar to yours in the process of using sr300. That is, the device manager shows the sr300 device, but it cannot be used normally. I have tried many ways to solve the problem, including the way in your communication with Mr. MartyG above, but I can't solve the problem successfully. So I took an unexplainable method, which is to uninstall the sr300 universal bus in the device manager and the two related devices in the camera. Then re-install automatically by scanning and detecting the hardware function. Successfully solved my problem. Hope this can help you too.
Please sign in to leave a comment.
Comments
29 comments