RealSense D435 No Frames Received in Stereo Module Depth Stream。
Hello,I using my RealSense D435 camera.But "No Frames Received!" message in the Depth Stream of the Stereo Module in the Intel RealSense Viewer.The RGB streams is fine
PC:NUC8i5BEK (Memo:16G ,SSD:512G)
OS:Windows 10 pro Version 20H2 (OS Build 19042.1055)
I have tried:
1,Different USB port (same PC ,USB port is USB3.1Gen2).
2,Used both RealSense Viewer and (2.41, 2.45)
3,Upgraded firmware to 5.12.13.50 and 5.12.14.50 .
4,Restore Factory to camera.
Please refer to the log
C:\Program Files (x86)\Intel RealSense SDK 2.0\tools>rs-capture.exe
RealSense error calling rs2_pipeline_wait_for_frames(pipe:0000017190494A80):
Frame didn't arrive within 15000
C:\Program Files (x86)\Intel RealSense SDK 2.0\tools>rs-hello-realsense.exe
RealSense error calling rs2_pipeline_wait_for_frames(pipe:000001B69B33F830):
Frame didn't arrive within 15000
Intel Real SenseViewer
22:52:08 [Info] - librealsense version: 2.45.0
22:52:08 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\rs.cpp:2610 - Framebuffer size changed to 1920 x 1017
22:52:08 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\rs.cpp:2610 - Window size changed to 1920 x 1017
22:52:08 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\rs.cpp:2610 - Scale Factor is now 1
22:52:08 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\context.cpp:382 - Found 1 RealSense devices (mask 0xfe)
22:52:09 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\common\post-processing-filter.h:52 - Starting Face Detection : OpenVINO
22:52:09 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\tools\realsense-viewer\openvino-face-detection.cpp:109 - Loading CPU extensions...
22:52:09 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\wrappers\openvino\rs-vino\object-detection.cpp:74 - Loading object detection model from: face-detection-adas-0001.xml
22:52:09 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\wrappers\openvino\rs-vino\age-gender-detection.cpp:68 - Loading age/gender model from: age-gender-recognition-retail-0013.xml
22:52:09 [Info] - Intel RealSense D435 was selected as a default device
22:52:10 [Info] - No online SW / FW updates available
22:52:10 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\src\types.h:1104 - Depth stream start failure
22:52:10 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\common\notifications.cpp:514 - Depth stream start failure
22:52:15 [Info] - Starting streaming of Color...
22:52:15 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\sensor.cpp:1416 - Request: RGB8 Color,
Resolved to: YUYV Color,
22:52:18 [Info] - Starting streaming of Depth...
22:52:18 [Info] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\sensor.cpp:1416 - Request: Z16 Depth,
Resolved to: Z16 Depth,
22:52:33 [Info] - Stopping streaming
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:34 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\src\proc\synthetic-stream.cpp:48 - Exception was thrown during user processing callback: Out of frame resources!
22:52:35 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\src\types.h:1104 - Depth stream start failure
22:52:35 [Error] C:\jenkins_sys_rsbuild\workspace\LRS_windows_compile_pipeline\common\notifications.cpp:514 - Depth stream start failure
22:52:37 [Info] - Stopping streaming
22:52:38 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\src\frame-archive.h:215 - The user was holding on to 1 frames after stream 0x000001E004086D40 stopped
22:52:38 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\src\frame-archive.h:215 - The user was holding on to 1 frames after stream 0x000001E004086D40 stopped
22:52:38 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\src\frame-archive.h:215 - The user was holding on to 1 frames after stream 0x000001E004086D40 stopped
22:52:38 [Info] c:\jenkins_sys_rsbuild\workspace\lrs_windows_compile_pipeline\src\frame-archive.h:215 - The user was holding on to 1 frames after stream 0x000001E004086D40 stopped
Could you tell me good idea?
Thank you.
-
Hi Eniuyu As a starting point in investigating your case, could you set the depth resolution in the RealSense Viewer to 480x270 please and only enable the depth stream. This will test whether your problem is occurring because your computer's USB system is being over-burderned for some reason. Does using this resolution make a positive difference?
-
When you are using the RealSense Viewer or the rs-capture example program, do you have any other RealSense programs running at the same time?
For example, if rs-capture was started first then RealSense Viewer would be unable to access the depth stream. And if the Viewer was launched first then rs-capture would be unable to access the depth stream. This is because the first program that accesses a stream 'claims' it so that it cannot be used by another process until the program that is currently using the depth stream disables the stream and releases its claim on it.
The rules that govern stream access are described in the Multi Streaming Model documentation linked to below.
-
Which method did you use to install RealSense SDK version 2.45.0 on Windows 10 on your computer, please? Was it with the Intel.RealSense.SDK-WIN10-2.45.0.3212.exe automated installer file in the Assets file list of the SDK 'Releases' page?
https://github.com/IntelRealSense/librealsense/releases
-
I am sure using Intel.RealSense.SDK-WIN10-2.45.0.3212.exe package in stall to my PC.
-
Thanks very much for the confirmation of the reset method that you used. The other method, activated through the CustomRW tool that is packaged with the RealSense Dynamic Calibration tool, is called the Gold Reset. The Windows version of the tool can be downloaded from the link below and installed.
https://downloadcenter.intel.com/download/29618/Intel-RealSense-D400-Series-Dynamic-Calibration-Tool
After installation is complete, you can input the command below into the Command Prompt to launch CustomRW and activate the Gold Reset:
Intel.Realsense.CustomRW.exe -g
-
HI,MartyG.Thank you prompt reply. It was executed according to your method .
------------------------------------------------------------------
C:\Program Files\Intel\CalibrationToolAPI\2.11.0.0\bin\Intel.Realsense.CustomRW.exe -g
CustomRW for Intel RealSense D400, Version: 2.11.0.0Device PID: ----
Device name: Intel RealSense D435
Serial number: 045---------
Firmware version: 05.12.13.50Calibration on device successfully reset to default gold factory settings.
C:\Program Files\Intel\CalibrationToolAPI\2.11.0.0\bin>Intel.Realsense.DynamicCalibrator.exe -sn 045---------C:\Program Files\Intel\CalibrationToolAPI\2.11.0.0\bin>Intel.Realsense.DynamicCalibratorCLI.exe
Result folder: C:\Users\intel\AppData\Local/Intel//DC//DyCalibResult/045---------/DC8
Serial Number: 045---------
Device Name: Intel RealSense D435
Device PID: 0--7
FW version: 05.12.13.50Calibration Type: Targeted
Laser Power: On
Auto Exposure: On
AE SetPoint: Auto
Target images: 15
Target and device orientation aligned: No
Skip rgb calibration: No
Initializing GL ...
display size: 1920,1080 with aspect ratio 1.77778
window size: 1440,810 with aspect ratio 1.77778
Launching graphical view ...
Streamming Resolution: 1280x720 at 30(fps)
disable AUTO_EXPOSURE_PRIORITY to ensure frame sync between rgb and depth/left/right sensorsError (9998): Unknown
C:\Program Files\Intel\CalibrationToolAPI\2.11.0.0\bin>
------------------------------------------------------------------
But,It doesn't help.
-
Thanks again for checking whether a Gold Reset would work. Next, let's focus on the error that is generated repeatedly in your kindly provided log when starting the depth stream.
Exception was thrown during user processing callback: Out of frame resources!
This could be related to the computer being unable to keep up with processing the incoming flow of images and the 'frame queue' becomes jammed full, resulting in the exception message. A way to resolve that could be to reduce frame rate and resolution, but you have already tried that.
Are you using the official 1 meter USB cable supplied with the computer or a cable of your own choice, please?
-
Sorry, I meant supplied with the camera. But you understand what I meant. :)
Can you run the rs-hello-realsense example program please? This is a plain-text printout of the depth measurement without any graphics. So this test will help to determine whether it is a graphics-related issue.
rs-hello-realsense can be launched from the Windows Command Prompt interface. Instructions on how to navigate to the Tools folder that contains the program from within the Command Prompt text interface are provided in the link below.
https://github.com/IntelRealSense/librealsense/issues/9115#issuecomment-849861189
-
Yes, I understand you mean, so I edit my comment. :)
I executed the commands you said, but did not get a good result.
-------------------------------------------------------------
Microsoft Windows [Version 10.0.19042.1055]
(c) Microsoft Corporation. All rights reserved.C:\Windows\system32>cd C:\Program Files (x86)\Intel RealSense SDK 2.0\tools
C:\Program Files (x86)\Intel RealSense SDK 2.0\tools>rs-hello-realsense.exe
RealSense error calling rs2_pipeline_wait_for_frames(pipe:0000024C42BCC710):
Frame didn't arrive within 15000C:\Program Files (x86)\Intel RealSense SDK 2.0\tools>
-------------------------------------------------------------
-
If the camera was stored in a cool dry place and then did not work from the first time that you took it out of the box again, there is the possibility that something on your computer's configuration might have changed during the period when the camera was not in use. For example, there have been past cases of RealSense cameras stopping working suddenly one day because of a Windows update that has been automatically installed.
Do you have any other computers at your office that you can try the camera on?
-
I carried out further extensive research into your issue. The number of remaining possible solutions to try is reducing.
Can you confirm whether the problem still occurs after resetting the camera by going to the More option near the top of the RealSense Viewer's options side-panel and selecting the Hardware Reset option from its drop-down menu.
-
My research of Windows version 20H indicated that numerous RealSense users have been able to use their camera with that Windows version, so Windows may not be an important factor in this case.
Can you confirm that there is nothing that you can think of about your computer's configuration that may have changed in the April to June period when the camera was not being used.
If your camera can be accessed by programs (even if the depth stream does not start) then this suggests that the Windows privacy settings are okay. For the sake of eliminating the possibility though, could you use the instructions in the link below to check in the privacy settings that permissions for both the access to camera hardware and access to applications are set to On
https://github.com/IntelRealSense/librealsense/issues/3381#issuecomment-503424789
-
At this point I will escalate your case to a team member of this Intel RealSense Customer Support forum to decide the next course of action.
**********
Hi @... In this particular case, the D435 camera of Eniuyu is experiencing Depth Stream Start Failure (manifesting as a No Frames Received message) after having been stored unused in a dry cool area for the period April-June 2021. The camera previously worked before this storage period.
As well as the depth stream not functioning, the Infrared stream is also producing No Frames Received. The RGB stream works though.
A range of possible solutions have been tested during this case but it has not resulted in the issue being corrected.
-
Hi Jesus Garcia , please tell me, what information do you need?
Please sign in to leave a comment.
Comments
34 comments