-
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
Color Stream: No Frames Received #8711
Comments
Hi @MichaelD92 Would it be possible to update your RealSense SDK version to the current 2.43.0 version using the automated Windows installer file from the Assets file list at the link below to see whether the problem still occurs, please? https://github.com/IntelRealSense/librealsense/releases/tag/v2.43.0 In regard to the metadata problem: you should still be able to view the RGB stream if support for Frame Metadata has not been enabled. The message Per-frame metadata is not enabled at the OS level should disappear if you enable metadata in the RealSense Viewer. If metadata is not enabled, you may see the message box below when you launch the Viewer. Clicking the Enable button on that message box adds metadata support. If the message cannot be made to appear, it may be triggered by unplugging the camera from the USB port and plugging it into a different USB port if you have an additional one available. May I also ask whether you have enabled the Motion Module at any time during a Viewer session when Depth and RGB have also been enabled? Some RealSense users experience No Frames Received on the RGB stream if they have enabled Depth, RGB and Motion Module during the same Viewer session. It does not matter which order the three stream types are activated in, because enabling the Motion Module is always the trigger for the issue. Once the No Frames Received problem with the RGB stream has been first triggered, it may persist after the Viewer has been closed and re-launched, even if the Motion Module is not enabled in the subsequent sessions. It can be corrected by a reboot of the computer. It is worth mentioning that I have not been able to replicate this issue with Motion Module activation when using SDK 2.43.0. |
I have now updated the firmware. Unfortunately, it still does not work. Somehow the message box does not appear even after several tries. I have plugged the camera into several USB ports and started the computer several times. I have also not activated the motion module. |
I have just tried the camera on another PC. The box appeared there and I was able to click enable. However, the RGB stream does not work there either. |
Please check that the RGB camera is able to function by using the Camera app in Windows, as described in the instructions below. STEP ONE STEP TWO If the display is empty then left-click on the Change Camera option to switch to the RealSense camera. If you get a pop-up warning saying that the camera could not be started but you can see the RGB video image behind the box, just ignore it and click Close to continue. Do you see a normal video image like the one below when following this procedure? |
Hi @MichaelD92 Do you require further assistance with this case, please? Thanks! |
Thank you very much for the update. Can you confirm please that you can receive no picture in the Camera app even if you toggle the Change Camera option repeatedly by left-clicking on it? |
I would expect to see the CreateDeviceSource error on Windows if permission for the camera to be accessed by applications was set to Off in the camera section of the Windows privacy settings. Instructions in the link below describe how to check this. The access should be set to On. |
If you have not enabled the Motion Module and triggered the RGB No Frames Received problem mentioned earlier in this case then you could try the standalone version of the Viewer - Intel.Realsense.Viewer.exe - that can be downloaded from the same Assets list that the SDK installer file is downloaded from. This version of the Viewer does not contain computer processor minimum requirements that the Viewer bundled in the SDK has. Once Intel.RealSense.Viewer.exe is downloaded to the Downloads folder of your computer after left-clicking on the link in the Assets list then it can be launched from that folder with a double-leftclick (do not use the Viewer shortcut icon on the Windows desktop). |
When I got the camera, I already switched on the motion module once. But since then some time has passed and in the meantime I have uninstalled and reinstalled the SDK several times and also restarted the computer several times. I have now also downloaded the stand alone version of the viewer and uninstalled the SDK. Unfortunately, my problem has not been solved. |
As the camera is identified by the Viewer as D435i, this suggests that the camera firmware is correctly detecting the presence of the RGB sensor hardware, otherwise the firmware would likely identify the camera model as D430i (i,e no RGB). I note that you have uninstalled and reinstalled several times. Does that mean that you have already tried the recent 2.44.0 SDK please? https://github.com/IntelRealSense/librealsense/releases/tag/v2.44.0 |
Does your computer have an AMD processor? The 400 Series cameras should work with any Intel or Arm processor. As far as I am aware, there is not the same guarantee for AMD-based computers though and though the cameras can work with AMD processors, I can experience more Viewer log warnings on my AMD-based laptop than I do with my Intel-based laptop. |
I use an Intel I7-9700 and an Nvidia Quadro P1000 as a graphics card. The PC also has 16 GB RAM. |
Let's next try reinstalling the camera's drivers in the Windows Device Manager (which are separate from the SDK). STEP 1 STEP 2 STEP 3 Does performing this process make any difference to your ability to stream RGB, please? |
In your Cameras section of the Device Manager, could you right-click on Xi Imager and select the menu option Disable device to test whether ths device is preventing the RealSense RGB from operating? Or unplug it if it is a USB device. If disabling it does not make a difference then you can re-enable it by right-clicking on Xi Imager again and selecting Enable device. |
What does the log show if you launch the Viewer with no cameras attached and then plug in the Xi Imager? |
I tested the Viewer with an old RealSense F200 camera that is not supported by RealSense SDK 2.0. Like your Xi Imager, the F200 also generated a Found 1 RealSense devices message in the log, even though the Viewer cannot generate options in the side-panel for that camera model. So if this log message is generated even for unsupported cameras, it may epxlain why your Xi Imager causes this message when inserted with no other cameras attached. So to confirm: even when the Xi Imager camera is unplugged, you cannot get RGB when the D435i is plugged in? |
I went through the case from the beginning and do not see a mention of trying a different resolution. Can the camera stream if RGB is set to resolution 640x480 ? |
No, I have now tried different settings with the resolution and the frame rate and no stream comes up with any of them. |
I do not think that we have tried a reset of the Viewer settings yet (which is different from a reset of the camera). A reset of the Viewer configuration can be performed with the instructions in the link below. https://support.intelrealsense.com/hc/en-us/community/posts/360052013914/comments/1500000416522 |
I have reset the Viewer settings, unfortunately there is still no RGB stream. |
A camera can be reset to its factory-new default configuration using a tool called CustomRW that is packaged with the RealSense Dynamic Calibration tool. 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 Windows Command Prompt to launch CustomRW in Gold Reset mode: Intel.Realsense.CustomRW.exe -g |
Has your D435i's RGB ever functioned since you purchased the camera, or did it work for a time and then just stop working one day? |
The RGB camera worked at the beginning and at some point it no longer delivered a stream. |
I recall that you tried the camera on another computer and it did not work. Is the other computer the same manufacturer / model as the computer that the RGB has not been functioning on? |
The other computer I tried the RGB camera on is the same model, but it doesn't have an Nvidia graphics card. The RGB camera does not work on the other computer either. |
Let's test the RGB with an example program to confirm if RGB is inaccessible in the examples too. On the Windows desktop, right-click on the launch shortcut for the RealSense Viewer and select the Open file location menu option. This will open the SDK Tools folder where the SDK's pre-built launchable example programs are stored. Locate a file called rs-capture.exe and double-leftclick on it to launch the program. With a D435i camera model, the rs-capture program generates a multi-panel view of the depth, RGB and IMU streams when the camera is working correctly, like this: |
Thank you very much. At this point I will seek advice from Intel about your case. |
Hi @MichaelD92 Could you send me your email address to my email above please so that we can assist you. Thanks! |
Thanks very much for sending your email address @MichaelD92 - I have passed it to the appropriate RealSense team member. |
Case closed due to resolution reached with customer. |
Have you solved the problem? I meet the problem too. |
Hi @calmelo Please start a new case for your issue by visiting the front page of this support forum at the link below and clicking the green New Issue button. Include a link to this case here in your message so that we can refer to it. Thanks! |
I have the problem that the RGB camera does not receive frames. When I display the frame metadata, the error "Per-frame metadata is not enabled at the OS level! Please follow the installation guide for the details" is displayed and the logged issues can be seen in the picture.
The text was updated successfully, but these errors were encountered: