[ZED-X][Warning] Failed to connect to zed_x_daemon

Hi,
I got [ZED-X][Warning] Failed to connect to zed_x_daemon. when running ROS1 zedx driver.
I tried to restart the zed_x_daemon and to check the status:

zed_x_daemon.service - ZED-X Daemon service
     Loaded: loaded (/etc/systemd/system/zed_x_daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-06-11 10:51:58 BST; 2min 32s ago
   Main PID: 12724 (ZEDX_Daemon)
      Tasks: 5 (limit: 18143)
     Memory: 2.9M
     CGroup: /system.slice/zed_x_daemon.service
             └─12724 /usr/sbin/ZEDX_Daemon

Jun 11 10:51:58 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:51:58 2024" ]  ** Start ZED-X Daemon
Jun 11 10:51:58 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: Tegra release :  9
Jun 11 10:51:58 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:51:58 2024" ]  ** Searching for Preload file  "/etc/systemd/system/zed_x_daemon.preload"  :  false
Jun 11 10:51:58 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:51:58 2024" ]   Process  "rmmod sl_zedx" outputs  "rmmod: ERROR: Module sl_zedx is not currently loaded\n"
Jun 11 10:51:58 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:51:58 2024" ]   Process  "rmmod sl_max96712" outputs  "rmmod: ERROR: Module sl_max96712 is not currently loaded\n"
Jun 11 10:51:59 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: ** ZED-X Driver loaded
Jun 11 10:51:59 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:51:59 2024" ]  ** Searching for Postload file  "/etc/systemd/system/zed_x_daemon.postload"  :  false
Jun 11 10:51:59 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:51:59 2024" ]  ** Created Endpoint  "tcp://127.0.0.1:20026"
Jun 11 10:52:01 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:52:01 2024" ]  >> Port  0  Opening for ModeliD  8
Jun 11 10:52:03 GTW-ONX-E1XEQYWE ZEDX_Daemon[12724]: [ "Tue Jun 11 10:52:03 2024" ]  >> Port  0  Running for ModeliD  8

How to solve it? Thank you.

Hi @yyyxs1125
please run the command sudo ZED_Diagnostic --dmesg and send me the dmesg.log report file that it generates.

dmesg_4.log (63.1 KB)

The report is good.
Can you open the camera with ZED_Explorer and ZED_Depth_Viewer?

Hi,
ZED_Explorer and ZED_Depth_Viewe work well, but still gets error from ros driver

sudo service zed_x_daemon restart
sudo service nvargus-daemon restart
sudo systemctl restart zed_x_daemon

# Change directory to catkin workspace
cd ~/catkin_ws

# Source the setup bash
source ~/catkin_ws/devel/setup.bash

# Launch the ZED wrapper
time roslaunch zed_wrapper zedx.launch

[ INFO] [1718108455.678195800]: +++ ZED Node started +++
[ INFO] [1718108455.678519974]: Published static transform 'zedx_imu_link' -> 'zedx_left_camera_frame'
(Argus) Error EndOfFile: Unexpected error in reading socket (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 277)
(Argus) Error EndOfFile: Receive worker failure, notifying 1 waiting threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 350)
(Argus) Error InvalidState: Argus client is exiting with 1 outstanding client threads (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 366)
(Argus) Error EndOfFile: Receiving thread terminated with error (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadWrapper(), line 379)
(Argus) Error EndOfFile: Client thread received an error from socket (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 145)
(Argus) Error EndOfFile:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 96)
(Argus) Error InvalidState:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 96)
(Argus) Error InvalidState:  (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
^C[zedx/zed_node-2] killing on exit
[zedx/zedx_state_publisher-1] killing on exit
ZED 41307849 closed.

You cannot launch this script as it is.
When you restart the daemons you must wait for a few seconds to let the driver correctly restart.

Thanks, and how can I check the drive started properly?

Here are the status feedback:

sudo service nvargus-daemon status
● nvargus-daemon.service - Argus daemon
     Loaded: loaded (/etc/systemd/system/nvargus-daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-06-11 13:34:49 BST; 54s ago
   Main PID: 74715 (nvargus-daemon)
      Tasks: 2 (limit: 18143)
     Memory: 151.7M
     CGroup: /system.slice/nvargus-daemon.service
             └─74715 /usr/sbin/nvargus-daemon

Jun 11 13:34:59 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:34:59 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:34:59 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:34:59 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:35:01 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:35:01 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:35:01 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:35:01 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:35:01 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
Jun 11 13:35:01 GTW-ONX-E1XEQYWE nvargus-daemon[74715]: Wrong frequency range!
sudo service zed_x_daemon status
● zed_x_daemon.service - ZED-X Daemon service
     Loaded: loaded (/etc/systemd/system/zed_x_daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-06-11 13:34:06 BST; 1min 17s ago
   Main PID: 73732 (ZEDX_Daemon)
      Tasks: 5 (limit: 18143)
     Memory: 1.0M
     CGroup: /system.slice/zed_x_daemon.service
             └─73732 /usr/sbin/ZEDX_Daemon

Jun 11 13:34:06 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:06 2024" ]   Process  "rmmod sl_zedx" outputs  "rmmod: ERROR: Module sl_zedx is not currently loaded\n"
Jun 11 13:34:08 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: ** ZED-X Driver loaded
Jun 11 13:34:08 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:08 2024" ]  ** Searching for Postload file  "/etc/systemd/system/zed_x_daemon.postload"  :  false
Jun 11 13:34:08 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:08 2024" ]  ** Created Endpoint  "tcp://127.0.0.1:20026"
Jun 11 13:34:09 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:09 2024" ]  >> Port  0  Opening for ModeliD  8
Jun 11 13:34:11 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:11 2024" ]  >> Port  0  Running for ModeliD  8
Jun 11 13:34:49 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:49 2024" ]  ** Restart Argus Daemon
Jun 11 13:34:51 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:51 2024" ]  >> Port  0  Opening for ModeliD  8
Jun 11 13:34:54 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:54 2024" ]  >> Port  0  Running for ModeliD  8
Jun 11 13:35:04 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:35:04 2024" ]  >> Port  0  Closing for ModeliD  8

sudo systemctl status zed_x_daemon
● zed_x_daemon.service - ZED-X Daemon service
     Loaded: loaded (/etc/systemd/system/zed_x_daemon.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-06-11 13:34:06 BST; 3min 26s ago
   Main PID: 73732 (ZEDX_Daemon)
      Tasks: 5 (limit: 18143)
     Memory: 1.0M
     CGroup: /system.slice/zed_x_daemon.service
             └─73732 /usr/sbin/ZEDX_Daemon

Jun 11 13:34:06 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:06 2024" ]   Process  "rmmod sl_zedx" outputs  "rmmod: ERROR: Module sl_zedx is not currently loaded\n"
Jun 11 13:34:08 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: ** ZED-X Driver loaded
Jun 11 13:34:08 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:08 2024" ]  ** Searching for Postload file  "/etc/systemd/system/zed_x_daemon.postload"  :  false
Jun 11 13:34:08 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:08 2024" ]  ** Created Endpoint  "tcp://127.0.0.1:20026"
Jun 11 13:34:09 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:09 2024" ]  >> Port  0  Opening for ModeliD  8
Jun 11 13:34:11 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:11 2024" ]  >> Port  0  Running for ModeliD  8
Jun 11 13:34:49 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:49 2024" ]  ** Restart Argus Daemon
Jun 11 13:34:51 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:51 2024" ]  >> Port  0  Opening for ModeliD  8
Jun 11 13:34:54 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:34:54 2024" ]  >> Port  0  Running for ModeliD  8
Jun 11 13:35:04 GTW-ONX-E1XEQYWE ZEDX_Daemon[73732]: [ "Tue Jun 11 13:35:04 2024" ]  >> Port  0  Closing for ModeliD  8

What is the grab frequency setting that you are using?
Can you send the zedx.yaml file?

common.yaml (9.8 KB)
zedx.yaml (480 Bytes)

I noticed that you disabled Positional Tracking, but you did not disable depth_stabilization.
In this case the Positional Tracking will be activated because it’s required.