-
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
How to connect two D415 devices? #2754
Comments
Hi @HungLearner |
Let me try again~ |
I have a similar problem with a pair of D435s. I have not tried v2.16.5, but I have tried adding a separate PCIe USB port and using a powered AmazonBasics hub (as described in the multi-cam whitepaper). More details here: https://forums.intel.com/s/question/0D50P0000490Z6WSAU/frame-errors-when-recording-from-multiple-cameras-on-a-single-computer |
I just want to clarify that the reason for adding the PCIe USB card was to test the sort of bandwidth hypothesis that @dorodnic mentioned (i.e., to provide a second USB hub, since Windows Device Manager indicated that all native USB ports used the same hub). I initially thought that this had mitigated or solved the problem, but it seems to be happening more frequently now. It is also my impression -- based on the multi-camera whitepaper -- that bandwidth should not be an issue for just 2 cameras. It's also worth mentioning that the cameras do sometimes disconnect, or they fail to be detected, so I have not ruled power out as a factor. In both cases, the issues are not especially consistent, and are therefore challenging to debug. |
Note: Another user reported the same problem on my Intel Community post (https://forums.intel.com/s/question/0D50P0000490Z6WSAU/frame-errors-when-recording-from-multiple-cameras-on-a-single-computer), and noted a possible connection to camera metadata. Edit: I confirmed this. Disabling metadata seemed to mitigate or eliminate the issues on my system. I was even able to stream from 3 cameras for a few minutes without issues. Details in my community post. |
[Realsense Customer Engineering Team Comment] I use the realsense-viewer based on 2.17.0 to run RGB (RGB8 format) + Depth steams at 1280x720/30FPS with two D415 cameras more than 5 minutes on Win10 RS3. My setup as follows: By the way, how did you verify if the metadata is enabled? |
Thanks @RealSense-Customer-Engineering .
Thanks again. |
I confirmed that the issue occurs with Realsense Viewer 2.17.0. |
Hello, i have a new question about sdk. |
[Realsense Customer Engineering Team Comment] Which C# sample app did you use? Did you also enable Metadata? |
@RealSense-Customer-Engineering I am not sure exactly what is meant by "dump to a log file" in usbview. There were two menu options that this could refer to, and neither seemed to be documented very well. I just exported to text and XML, and that is what I am attaching. The attachment is the export when two cameras were plugged directly into the computer ports and caused a "No frames found" error. For anyone else trying to do this, I followed the instructions here to get "usbview": https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/usbview |
[Realsense Customer Engineering Team Comment] From your USBview file, one of D435 USB devices is not enumerated normally. As you can see below, some info is missing. Did you have the chance to try another PC or different OS like Ubuntu to see if the same issue "No Frames Received!" there during two D435 streams with metadata? Device Power State: PowerDeviceD0 |
@RealSense-Customer-Engineering Regarding trying another PC or OS: Are you suggesting that this would help to debug the problem? |
Another observation: I just looked inside a short bag file that I recorded yesterday, right after metadata was enabled. Only one camera. There was no frame error while recording, but there are multiple frame drops in the file. There is one gap that is 0.4s long. Should I expect to see dropped frames frequently? Even for one camera in a standard configuration on a standard computer? Is the "No frames received" error just an indication that dropped frames have passed a threshold? |
This problem might be related to another problem that we are now experiencing. I've provided detailed information about that problem here: #2216 (comment). That problem occurs in Realsense Viewer, but not when .bag files are recorded via a Python script (even with metadata enabled). Preliminary tests seem to indicate that the same might be true of the "No frames received" error described here. This suggests that the problem is with Realsense Viewer, and not the SDK, the drivers, the OS, or the hardware. Edit: I let a Python script record from 2 cameras for 21 minutes, resulting in a pair of bag files that were about 86 GB each. I did the same using Realsense Viewer and the files were about 16 GB and 32GB. The video feeds were choppy and one of the color streams showed the "No frames received", starting between minutes 4 and 5. |
Please try the latest firmware and librealsense. Not observe this issue. I will close this. If the issue is still there, you can create another ticket for track. |
Can you please explain the context of "Not observe this issue"? Are you referring to the "No frames" error? What kind of system was tested? Was metadata enabled? What version of firmware / software was tested? Which camera model? I still consider this to be an issue. I will try the latest firmware and software as soon as possible, and report back here. |
hi all, I'm new to realsense. May I ask how to enable two devices at the same time in C#? As I understand, I have to create two pipelines. But what is the correct grammer to do it? |
Do I need to enable a device using the serial number? |
| Camera Model | D400 |
| Firmware Version | 05.10.06.00 |
| Operating System & Version | Win (10) |
| Platform | PC |
| SDK Version | 2.16.1 |
| Language | C# |
Issue Description
I need to connect two depth camera devices on the same computer.
Sometimes, the other one camera frames cannot receive.
Is it possible USB power not enough?
The text was updated successfully, but these errors were encountered: