After updating my ZED SDK to v5.0.5 and the driver to 1.3.1 on my Jetson Orin (JetPack 6.2.1), my capture card duo has started behaving abnormally. The camera was working fine on the previous setup, but since the update, I’m unable to start the camera stream—it keeps giving an “error opening camera: camera stream failed to start” message when running the ros2 wrapper . Additionally, the capture card’s indicator light remains on and the card itself overheats, even after unplugging the power source. Running ZED Diagnostics doesn’t help, as the camera is not detected at all. I even tried reverting to my previous Jetson device and SDK, but the issue persists: the capture card’s link light stays on and it overheats, and the camera is still not recognized. This problem only began after the SDK and driver update. Any help or suggestions would be greatly appreciated.
everything was working smoothly but when i installed the new zed sdk 5.0.5 with the latest driver 1.3.1 the issue started popping on the jetpack 6.2.1 and im using jetson orin nano super …
below is the link to the setup ive been using for a while now … pictures
the previous zed-sdk was 5.0.3 and driver was 1.3.0 , tested it in a new device with all the latest sdk and drivers and it was able to detect the camera but failed after a while in ros wrapper so i connected back it to the old jetson with sdk 5.0.3 and driver 1.3.0 and since then issue has been persistent
Can you confirm your capture card is properly power up ? Do you have a multimeter to do so ?
Can you confirm your gmsl cable is properly connected at both ends ?
Can you test to plug your cameras on each cable (0,1,2,3) if you still encounter the issue ?
Are you able to restore the camera behavior by using the driver 1.3.0 ?
From your dmesg it appears the driver is working properly but your camera is not detected, this usually indicates a faulty power on the capture card or a disconnected/faulty gmsl cable.
yes the capture card is powered properly …the gmsl cables are fine as i have shared the picture of the setup as well … in fact i changed the cables to make sure if that was the cables that were causing that but they werent
i tried reverting back but the issue still persists and even after removing the power the capture card light still glows . and im using ZED LINK DUO.
Does restarting the drivers: sudo systemctl restart zed_x_daemon.service blinks the LED ?
Did you try every gmsl cable ?
Can you share a new dmesg with the capture card powered on since you plugged/unplugged the mipi csi ?
i do have another capture card and that is already in use…and also i tried it on the same jetson and its working fine … i guess its an issue with the sofytware of the capture card …
If this is working with another capture card the drivers/SDK are working properly - There isn’t a specific software being uploaded to the capture card.
If you have connected the ribbon cables while the capture card or the board was powered on, this can be potentially dangerous and may have damaged the port.
