"control_transfer returned error" occurring at high frequency with multiple cameras #1843
Comments
|
@victorll998 Do you mean that two D455 cameras connected to one USB hub? |
|
I also have done the same tests when I connect each d455 to thunderbolt3. The warnings are relieved compared to use the USB hub but still are coming at a disturbingly high rate. |
|
@victorll998 Do you mean you still get frequent "control_transfer returned error" if you connect each D455 to host USB port directly? Do you still get such issue if you reduce RGB resolution to 848x480? |
|
Hi All, we get the same message a few dozen times from each camera node after start-up, on industrial computers with 2, 3 or 4 D435 cameras each, all attached to host USB ports. Resolutions used for both color and depth are 848x480. Some of the output from lspci:
|
|
@RealSenseSupport When I connect each D455 to the host USB port (thunderbolt3) I still get frequent "control_transfer returned error". I have the same issue even though I reduce RGB resolution to 848x480. I also found this issue could be related to auto-exposure because I can see the frequent "control_transfer returned error" when I change the ambient light. To rule out possibilities of camera hiccup, could you take a look and see if you can reproduce the same error? |
|
@victorll998 So you will get "control_transfer returned error" when connect two D455 to the host. But no such issue if connect one D455, right? How did you install librealsense and ROS wrapper? By apt-get install or build from source? |
|
@victorll998 Could you please update so that we can provide further support on this? Thanks! |
|
@victorll998 Do you still have issue? Looking forward to your update. Thanks! |
|
@victorll998 Could you please update? Please note that the issue will be closed if we don't hear from you for another 7 days. Thanks! |
|
@victorll998 Sorry we don't hear from you for weeks. This issue will be closed. Please feel free to create another one if you still have any issues or questions. Thanks! |
Hi everyone,
I have encountered similar cases related #1162 but with multiple cameras (two d455 and one t265) in my system.
I have two d455 and t265 running on Intel NUC (i7). I tested with the cables inbox and a powered USB hub. When only one d455 and t265 connected, the control_transfer returned error has refrained after a few seconds when nodes initialize. But when I tried to connect two d455 and t265, one of the d455 would retain the control transfer error at a high frequency while the other d455 is fine.
The errors come at an average rate of 3 sec, which I think it is not normal. Does anyone have an idea about it?
camera 1 continue to give me the error
camera 2 is fine
The text was updated successfully, but these errors were encountered: