Unreliability in Zed Live installation

Software
,
1

Hello community!

In my software team we develop a lighting design tool that embeds in architecture and it employs Zed cameras for tracking and experiential illumination.

We sometimes run into issues that we do not know how to address. We use the tracking data via USB, and mostly, the diagnostic tools and the Jsons it provides points to the USB 3.0 having a lacking bandwidth, or just swapping USB port altogether. Weirdly, sometimes on the same port we had errors, later it works. On other errors that might not be critical, like specific resolutions unavailable, we can’t get it to work. The diagnostic tools seems to give an OK or an Error diagnostic based on conditions we can’t seem to understand, but it seems concordant with our software, i.e: On diagnostics OK our integration works, on diagnostic Error it does not.

We are open to ideas like using USB 3.0 PCIe expansion cards, but for us it is critical to have a reliable installation and maintainability, since as we mentioned, we embed them in architecture. We have already tried one recommended USB 3.0 PCIe hub, and it worked first try, but this is in our offices, in a server where the Zed already worked on a USB backport, and we need it to be reliably working for demos and future installations.

Our software environment consists of:

  • Windows 11 (mostly IoT enterprise versions)
  • Zed SDK 5.0.0
  • Cuda 12.8.1_572

We are eager to hear from you, your recommendations are most welcome,
Tomas

2

Hi @Tomas-Skandal
Welcome to the Stereolabs community.

This is normally a clue of bad USB 3 signal. Are you using cable extenders of USB 3 Hubs?

Is this a multi-camera setup? How many cameras are you using with the same Hub?

We recommend you do not use more than 2 cameras on the same USB 3 channel.
This means not only that you should not connect more than a camera to a single USB 3 Hub, but also that you must check that the USB 3 ports of your PC do not share the same channel (internal USB 3 Hub).

3

Hello, this was our setup:

  • Using the 10m cable sold by stereo labs for this camera with both extra power inputs connected to power. Also tried with short (1.5m) USB-C 3.2 cable.

  • Single camera. No USB extenders or hubs.

  • No more USB connections on those backports.

Tell us what you think!

4

Please run ZED Diagnostic and send me the report file that you can save at the end of the tests.

5

New users cannot upload, unfortunately :worried:

6 
"Camera Test": {
    "InternalDevicesCount (GMSL)": 0,
    "InternalDevicesCount (USB)": 1,
    "ZEDCount": 0,
    "ZEDs": [
    ],
    "error": [
        "<b>Camera not detected</b> <br/> Make sure the camera is plugged in or try another USB 3.0 port."
    ]
},

this is in the json, but so is:

{
“USBMode”: 3,
“USB_path”: “/22/1/1”,
“bDescriptorType”: 1,
“bDeviceProtocol”: 1,
“bLength”: 18,
“bMaxPacketSize0”: 9,
“bNumConfigurations”: 1,
“bcdDevice”: “1.0”,
“bcdUSB”: “3.0”,
“bcdUSBClass”: 239,
“bcdUSBSubClass”: 2,
“busNumber”: 1,
“device”: “ZED2i”,
“iManufacturer”: 1,
“iProduct”: 2,
“iSerial”: 4,
“idProduct”: “0xf880”,
“idVendor”: “0x2b03”
},

7

We link against the zedCamera.dll in SDK 5.0.0, but we have observed that the .dlls changed from SDK 5.0.1 onwards so we tried to stick to it. Is it possible that the issues arise because of this? Or is it purely a hardware thing…

8

Please copy and paste the full content of the report.

We recommend using the latest ZED SDK v5.0.6 and to not mix DLL versions.

9

Yeah, but the dlls changed so much, we basically need to redo our implementation then? Also we need to rebundle it since you do not provide static libs. The zedCamera.dll that we used for implementation does not have a 1-1 in the new ones. What would you recommend to reach a similar state like the one we had with 5.0.0 in 5.0.6?

10

What do you mean? Can you add details to your affirmation?