Nvargus-daemon "Sensor could not be opened" (ImagerGUID 15) on multi-camera kill-and-restart after updating to ZED SDK 5.4 / JetPack 6.2 / L4T 36.5

Software ROS2
1

Hi all,

We’re hitting a camera launch failure after a recent software update and would appreciate any guidance.

Hardware

  • Jetson Orin NX

  • ZED 2i + ZED X Mini + two ZED One GS cameras

Software (recently updated)

  • JetPack 6.2

  • L4T R36.5.0

*** ZED SDK 5.4.0**

The problem
After that first successful multi-camera launch, if we kill the launch and start it again (without rebooting), nvargus-daemon fails to open one of the sensors. The sensor open fails with the following:
NvPclInitializeDrivers: error: Failed to init camera sub module v4l2_sensor_usb
NvPclStartPlatformDrivers: Failed to start module drivers
NvPclStateControllerOpen: Failed ImagerGUID 15. (error 0x2)
NvPclOpen: PCL Open Failed. Error: 0xf
SCF: Error BadParameter: Sensor could not be opened.
(in src/services/capture/CaptureServiceDeviceSensor.cpp, function getSourceFromGuid(), line 725)
SCF: Error BadParameter: (propagating from CaptureService.cpp, addSourceByGuid(), line 465)
SCF: Error BadParameter: (propagating from CameraDriver.cpp, addSourceByIndex(), line 384)
SCF: Error BadParameter: (propagating from CameraDriver.cpp, getSource(), line 556)

A full Jetson reboot clears it, the next launch works again. The failure only returns on the second (kill-and-restart) attempt. It is reproducible across two independent launch methods.

This same pipeline was running fine on ZED SDK 5.2 with L4T 36.4 / JetPack 6.1.

Any pointers, or confirmation of whether this is a known issue would be much appreciated.

Thanks!

2

Update:
The L4T 36.4 and JetPack 6.1 pipeline works well on SDK 5.4 as well.
But the newer L4T 36.5 gives us the same daemon error.

Any leads on this would be appreciated.
Thank you so much.

3

Hi @pratibhamadaan

Are you using ROS? Does the launch file exit with no errors?

You could try to run sudo service zed_x_daemon restart before re-launching the application.
With this command, if the cameras were not closed correctly, the driver is reset and all the connections restored.