I can't get my ZED mini camera to work

Software
1

Hi guys. I am trying to get my ZED mini camera to work. It came with my open arm 2.0 robot kit I bought from WowRobo. I have a mac mini, a Raspberry pi 5 and a old linux pc I’ve tried it on with no luck, i don’t have cuda hardware (although I downloaded that new code for cuda to work on the mac mini i just cant get the camera to register).

Raspberry pi:

What we tested:

  • Connected the ZED Mini through the USB hub and also moved/reconnected the USB hardware.
  • Inspected the USB topology on both the Mac and Raspberry Pi.
  • macOS I/O Registry detects a Stereolabs device named ZED-M Hid Device.
  • The detected HID connection reports only 12 Mbps, which appears to be the camera’s USB 2 control/sensor interface.
  • macOS AVFoundation reports no ZED video device or video formats.
  • Because no video interface is enumerated, there is no device available for a bounded AVFoundation capture test.
  • On the Raspberry Pi, the ZED similarly appears only as its HID interface.
  • No /dev/video* UVC side-by-side ZED video node is created.
  • The Pi’s USB topology showed the connected hub operating at 480 Mbps, while the available 5000 Mbps SuperSpeed buses were empty.
  • The Render Studio ZED image endpoint consequently returns HTTP 503 / camera not detected.
  • The two separate Arducam wrist cameras work correctly through the same camera system and return live 960×600 JPEG frames. This confirms that the Pi camera publisher, Mac proxy, network connection, and Render Studio camera wall are functioning.
  • We updated the Pi publisher to automatically discover a ZED UVC side-by-side video node if one appears. It continues to report the ZED as unavailable because no video node exists.
  • We also updated the wrist-camera discovery after moving USB connections, confirming that USB topology changes are detected correctly.
  • We investigated Mac CUDA compatibility software, but it did not change the result. The immediate failure appears to occur before CUDA or the ZED SDK is involved because the operating system never exposes the camera’s USB video interface.
  • We did not install the official ZED SDK on the Raspberry Pi because Stereolabs documents its ARM/CUDA SDK for NVIDIA Jetson hardware. Our intended Pi fallback was standard UVC side-by-side color video. Depth and tracking would run on a supported NVIDIA/Jetson host.

Current observed state

The computer can see the ZED Mini’s Stereolabs HID/control input, so the camera is not completely absent. However, it cannot see any camera/video input. There is no UVC video interface, no AVFoundation camera, no /dev/video device, and therefore no image stream.

The strongest indication is that only the 12 Mbps HID interface is connected while the required SuperSpeed video interface is missing. I have plugged it into the blue port both ways and even bought a cable that matches specs, no luck.

Mac Mini

What we tested:

  • Connected the ZED Mini through the USB hub and also moved/reconnected the USB hardware.
  • Inspected the USB topology on both the Mac and Raspberry Pi.
  • macOS I/O Registry detects a Stereolabs device named ZED-M Hid Device.
  • The detected HID connection reports only 12 Mbps, which appears to be the camera’s USB 2 control/sensor interface.
  • macOS AVFoundation reports no ZED video device or video formats.
  • Because no video interface is enumerated, there is no device available for a bounded AVFoundation capture test.
  • On the Raspberry Pi, the ZED similarly appears only as its HID interface.
  • No /dev/video* UVC side-by-side ZED video node is created.
  • The Pi’s USB topology showed the connected hub operating at 480 Mbps, while the available 5000 Mbps SuperSpeed buses were empty.
  • The Render Studio ZED image endpoint consequently returns HTTP 503 / camera not detected.
  • The two separate Arducam wrist cameras work correctly through the same camera system and return live 960×600 JPEG frames. This confirms that the Pi camera publisher, Mac proxy, network connection, and Render Studio camera wall are functioning.
  • We updated the Pi publisher to automatically discover a ZED UVC side-by-side video node if one appears. It continues to report the ZED as unavailable because no video node exists.
  • We also updated the wrist-camera discovery after moving USB connections, confirming that USB topology changes are detected correctly.
  • We investigated Mac CUDA compatibility software, but it did not change the result. The immediate failure appears to occur before CUDA or the ZED SDK is involved because the operating system never exposes the camera’s USB video interface.
  • We did not install the official ZED SDK on the Raspberry Pi because Stereolabs documents its ARM/CUDA SDK for NVIDIA Jetson hardware. Our intended Pi fallback was standard UVC side-by-side color video. Depth and tracking would run on a supported NVIDIA/Jetson host.

Current observed state

The computer can see the ZED Mini’s Stereolabs HID/control input, so the camera is not completely absent. However, it cannot see any camera/video input. There is no UVC video interface, no AVFoundation camera, no /dev/video device, and therefore no image stream.

The strongest indication is that only the 12 Mbps HID interface is connected while the required SuperSpeed video interface is missing.

Could you please advise whether this points to:

  1. A USB cable that carries control but not SuperSpeed video.
  2. An incompatible USB-C adapter or hub.
  3. A camera firmware or USB-interface problem.
  4. A required macOS driver or permission step.
  5. A hardware fault in the ZED Mini or its cable.

We would also appreciate the recommended method for confirming that both the HID interface and SuperSpeed stereo-video interface are enumerating correctly on macOS.

These were the cables I bought to test, as mine didn’t come with a cable that I saw