ROS2 start_svo_rec and stop_svo_rec service calls exit abruptly after trying to recover connection

Software ROS2
1

Hi @Myzhar, I have a setup where I stream from 3 ZED Xmini cameras and I launch 3 zed ros2 nodes on my host computer. I make the start and stop svo recording service calls multiple times using a bash script. I see that when the streaming gets interrupted and is restarted again, the ros2 node which made the service calls raises the error code CAMERA_NOT_INITIALIZED. It is never recovers from this state and in the end the process dies.

Here are the logs from the ros2 node.
59059530_rosnode_cam.log (49.5 KB)

2

Hi @abhishekpavani
it seems that you are starting and stopping the recording every 13/14 seconds.
This is not recommended behavior.
Do you really need to perform similar tasks?

3

Hi @Myzhar , I was running a bash script where I request to start the SVO service recording, wait for 12 seconds and then stop the service recording and wait for a period before calling the start SVO recording again. I would have to perform similar tasks where I create SVOs of varying lengths by calling the SVO start and SVO stop services. Is the issue here calling the SVO recordings in succession? I need to reliably call the services over extended periods without them running into the issues that I shared in the logs

4

Please try with longer waiting periods, for example, 30 seconds.

5

Hi @Myzhar , Are you suggesting that after I call the start SVO service recording, I wait for 30 seconds before I call the stop SVO service recording?
In my current scenario, I wait for 120 seconds after I call stop svo service before I call start again.

6

The SDK team is working on a fix to this problem

7

@abhishekpavani
Please remember to share with us the script that you are using to start/stop the recording.

Can you please specify what you mean by “streaming gets interrupted”?
Are you also using the Local Streaming?

8

Please remember to share with us the script that you are using to start/stop the recording

I have shared the scripts along with my setup description on support@stereolabs.com. Can you please acknowledge once you receive them.

Can you please specify what you mean by “streaming gets interrupted”?
Are you also using the Local Streaming?

I have also answered these in the email.

9

Hi @Myzhar ,

I tried another experiment to record the SVOs with the same duration(12 seconds) as before. This time I was able to record 25 SVOs before I ran into the CAMERA_NOT_INITIALIZED error. It is also seen that the last SVO file probably did not get the stop svo recording call and is 13.6Gb in size. All other svos are 30 MBs. I am sharing logs from all the camera rosnodes here along with the file sizes of the recorded SVOs. You can see that the GMSL rosnode logs have the CAMERA_NOT_INITIALIZED error, whereas the USB camera raises

[component_container_isolated-1][WARN] [1748474558.824097469] [zed_camera.base.rclcpp]: failed to send response to /zed_camera/base/start_svo_rec (timeout): client will not receive response, at ./src/rmw_response.cpp:154, at ./src/rcl/service.c:314

Just also wanted to bring to your attention that increasing the duration from 12 seconds to 30 seconds also caused the nodes to raise the same CAMERA_NOT_INITIALIZED error.

-rw-r--r-- 1 ubuntu ubuntu    82616047 May 28 18:07 left_1.svo2
-rw-r--r-- 1 ubuntu ubuntu    90303472 May 28 18:10 left_2.svo2
-rw-r--r-- 1 ubuntu ubuntu    86670196 May 28 18:14 left_3.svo2
-rw-r--r-- 1 ubuntu ubuntu    79820959 May 28 18:17 left_4.svo2
-rw-r--r-- 1 ubuntu ubuntu    90491761 May 28 18:20 left_5.svo2
-rw-r--r-- 1 ubuntu ubuntu    95425022 May 28 18:37 right_10.svo2
-rw-r--r-- 1 ubuntu ubuntu    94273681 May 28 18:40 right_11.svo2
-rw-r--r-- 1 ubuntu ubuntu    86779537 May 28 18:43 right_12.svo2
-rw-r--r-- 1 ubuntu ubuntu    95248602 May 28 18:46 right_13.svo2
-rw-r--r-- 1 ubuntu ubuntu    88313983 May 28 18:50 right_14.svo2
-rw-r--r-- 1 ubuntu ubuntu    78209166 May 28 18:53 right_15.svo2
-rw-r--r-- 1 ubuntu ubuntu    82486430 May 28 18:56 right_16.svo2
-rw-r--r-- 1 ubuntu ubuntu    89703686 May 28 18:59 right_17.svo2
-rw-r--r-- 1 ubuntu ubuntu    95531904 May 28 19:03 right_18.svo2
-rw-r--r-- 1 ubuntu ubuntu    92943708 May 28 19:06 right_19.svo2
-rw-r--r-- 1 ubuntu ubuntu    78057019 May 28 18:07 right_1.svo2
-rw-r--r-- 1 ubuntu ubuntu    87938329 May 28 19:09 right_20.svo2
-rw-r--r-- 1 ubuntu ubuntu    88785982 May 28 19:12 right_21.svo2
-rw-r--r-- 1 ubuntu ubuntu    86166925 May 28 19:16 right_22.svo2
-rw-r--r-- 1 ubuntu ubuntu    92360625 May 28 19:19 right_23.svo2
-rw-r--r-- 1 ubuntu ubuntu    88854814 May 28 19:22 right_24.svo2
-rw-r--r-- 1 ubuntu ubuntu           0 May 28 19:25 right_25.svo2
-rw-r--r-- 1 ubuntu ubuntu    88371894 May 28 18:11 right_2.svo2
-rw-r--r-- 1 ubuntu ubuntu    88663459 May 28 18:14 right_3.svo2
-rw-r--r-- 1 ubuntu ubuntu    86876725 May 28 18:17 right_4.svo2
-rw-r--r-- 1 ubuntu ubuntu    81081208 May 28 18:20 right_5.svo2
-rw-r--r-- 1 ubuntu ubuntu    88829682 May 28 18:24 right_6.svo2
-rw-r--r-- 1 ubuntu ubuntu    83682886 May 28 18:27 right_7.svo2
-rw-r--r-- 1 ubuntu ubuntu    89298246 May 28 18:30 right_8.svo2
-rw-r--r-- 1 ubuntu ubuntu    88574291 May 28 18:33 right_9.svo2
-rw-r--r-- 1 ubuntu ubuntu    34659670 May 28 18:37 base_10.svo2
-rw-r--r-- 1 ubuntu ubuntu    34717371 May 28 18:40 base_11.svo2
-rw-r--r-- 1 ubuntu ubuntu    37284268 May 28 18:43 base_12.svo2
-rw-r--r-- 1 ubuntu ubuntu    37419475 May 28 18:46 base_13.svo2
-rw-r--r-- 1 ubuntu ubuntu    37559813 May 28 18:50 base_14.svo2
-rw-r--r-- 1 ubuntu ubuntu    37564834 May 28 18:53 base_15.svo2
-rw-r--r-- 1 ubuntu ubuntu    37508270 May 28 18:56 base_16.svo2
-rw-r--r-- 1 ubuntu ubuntu    40159324 May 28 18:59 base_17.svo2
-rw-r--r-- 1 ubuntu ubuntu    40044263 May 28 19:03 base_18.svo2
-rw-r--r-- 1 ubuntu ubuntu    37378565 May 28 19:06 base_19.svo2
-rw-r--r-- 1 ubuntu ubuntu    37228513 May 28 18:07 base_1.svo2
-rw-r--r-- 1 ubuntu ubuntu    37519656 May 28 19:09 base_20.svo2
-rw-r--r-- 1 ubuntu ubuntu    37317557 May 28 19:13 base_21.svo2
-rw-r--r-- 1 ubuntu ubuntu    37611580 May 28 19:16 base_22.svo2
-rw-r--r-- 1 ubuntu ubuntu    34729828 May 28 19:19 base_23.svo2
-rw-r--r-- 1 ubuntu ubuntu 13698531328 May 28 20:48 base_24.svo2
-rw-r--r-- 1 ubuntu ubuntu    34628620 May 28 18:11 base_2.svo2
-rw-r--r-- 1 ubuntu ubuntu    35301806 May 28 18:14 base_3.svo2
-rw-r--r-- 1 ubuntu ubuntu    37321590 May 28 18:17 base_4.svo2
-rw-r--r-- 1 ubuntu ubuntu    34506992 May 28 18:20 base_5.svo2
-rw-r--r-- 1 ubuntu ubuntu    37429461 May 28 18:24 base_6.svo2
-rw-r--r-- 1 ubuntu ubuntu    37523268 May 28 18:27 base_7.svo2
-rw-r--r-- 1 ubuntu ubuntu    40188192 May 28 18:30 base_8.svo2
-rw-r--r-- 1 ubuntu ubuntu    34742378 May 28 18:33 base_9.svo2
-rw-r--r-- 1 ubuntu ubuntu    82399280 May 28 18:07 center_1.svo2
-rw-r--r-- 1 ubuntu ubuntu    92751144 May 28 18:11 center_2.svo2
-rw-r--r-- 1 ubuntu ubuntu    88674161 May 28 18:14 center_3.svo2
-rw-r--r-- 1 ubuntu ubuntu    87882775 May 28 18:17 center_4.svo2
-rw-r--r-- 1 ubuntu ubuntu    84357165 May 28 18:20 center_5.svo2

32929916_rosnode_cam.log (67.7 KB)
54832066_rosnode_cam.log (48.7 KB)
59059530_rosnode_cam.log (401.1 KB)
59819861_rosnode_cam.log (69.7 KB)

10

Thank you for the additional information, they are very useful.

11

Hi @abhishekpavani
Is this problem related to this?

If they are related, can you provide the following information:

  • initialization parameters of the sender
  • console log of the sender, especially when the camera_not_initialized appeared

We tried to stop the sender several times and then restarted it. When the sender is stopped (or the camera is unplugged), it is expected to get the CAMERA_NOT_INITIALIZED error on the receiver side. But when we restarted the sender, the receiver automatically recovered and run again

13

Hi @Myzhar , Those are two separate issues and unrelated. This thread is specifically about being able to start and stop svo calls reliably.

CAM_NOT_INITIALIZED error pops up even when the streaming sender is running. I sent an email to support@stereolabs.com with the scripts we used to start and stop the SVO recordings on May 28 2025. Could you please confirm if you received them?

14

Hi @abhishekpavani
I cannot find your message to support@stereolabs.com sent on May 28.
Please send it again.

15

Hi @Myzhar , I sent the email again. Can you please check and confirm that you received it?

16

No, I confirm that I’ve not received it again.

17

Here are the scripts that we use to start and stop the svo recordings.

We run the streaming_sender.py python script (each camera is a separate process) on the jetson side and then launch the zed ros nodes using the zed_camera.launch.py. We then run each of the bash scripts shared in the link above to start and stop the svo recordings.

Setup: 4 cameras in total. 3 GMSL ZED XMini cameras (2 cameras connected to the same 4 wire port on capture card and 1 connected to the second 4 wire port) and one of them is a USB camera (ZED2i).

18

Thank you.
We’ll get back to you as soon as possible.