Issues with multiple camera set up in Real Sense Viewer
Hi,
We are using a multiple cameras set-up for an interactive media installation. We currently have an asset of 4 Real Sense Cameras ( 3 x D455 and 1x D415 ) connected to MutecPower 30m USB 3.0 Active Cable extensions to a single PC (AMD Ryzen Threadripper 3960X 24-Core Processor 3.79 GHz and 2x Geforce RTX 2080Ti).
We have been testing the set up for quite long now (also on different PCs) and we bypassed any possible issue generated by our application by just checking the performance of the cameras using your Real Sense Viewer application. While most of the times the system is working, sometimes the cameras disconnect by themselves and disappear from the source list of the Real Sense Viewer application. We also experienced the following error message already reported by some other users:
Backend in rs2_get_option(options:000001A4BAAB31E0, option:Exposure):
hr returned: HResult 0x80004002: "No such interface supported"
Other issues that sometimes happen when all the camera modules are active in the viewport include framedrops of the stereo module and flickering of the RGB signal.
The firmware of the cameras are up to date and we are using the latest version of your SDK (SDK-WIN10-2.45.0.3212). Also all the USB extensions are powered.
Since we are evaluating if using these cameras for the next upcoming installs would be great if we can have some support on those issues before considering to use a different sensor.
Thank you & best regards
-
Hi Riccardo Torresi08 A good starting point would be a discussion in the link below that had a very similar scenario to yours. An exhibition company tested a multiple camera project in their home office and it worked fine, but when it was installed in an exhibition center in another country it had camera problems. They too were using 30 meter active repeater extender cables.
-
Hi Marty,
Thanks for pointing that thread, indeed a very similar case and lot of interesting information. But no solid solution unfortunately... We also experienced the USB 2.1 instead of 3.2 recognition but in our case an hardware reset and a restart of the application fixed the issue. After reading few other posts seems quite likely to be a powering problem of the devices over the cable extensions. We also noticed that the extensions always needed to be powered in order not to rely on the (instable?) power of the PC. When not powered the fps and quality of the signal is much worse. Do you think using a more robust camera like those industrial ones from FRAMOS or LIPS would be a more reliable choice?
https://www.framos.com/en/framos-depth-camera-d435e-starter-kit-22805
https://www.lips-hci.com/product-page/lipsedge-ae400-industrial-3d-camera
-
Intel does not comment on non-Intel depth camera products such as the models linked to above (support for them is the responsibility of their manufacturer).
My understanding of active repeater extension cables is that 20 meters should be considered as a maximum distance. The company Newnex offer a fiber optic solution for extending a 400 Series camera up to 100 meters.
https://www.newnex.com/realsense-3d-camera-connectivity.php
https://www.youtube.com/watch?v=GLQgR1jT04M
Newnex make the distinction of 20 meters without any additional power input on the active repeater section of their RealSense cable information page, which would seem to reflect the experience that you have had of unpowered versus powered.
A camera can also be extended up to 100 meters using an ethernet networking solution (as described in Intel's ethernet networking white-paper document linked to below), though the data transfer speeds of ethernet cables is slower than USB.
-
Well those seems to be essentially D435 cameras with ethernet cable in a housing, they are powered by your Inter Real Sense technology and using your SDK. But i understand is not your duty to comment on this. Thanks for the links, nothing new though. I guess we ll try some more cable extensions and see what performs better before passing to a more industrial option.
Please sign in to leave a comment.
Comments
4 comments