Hi,
Thank you so much for sharing. I tried it on my Jetson device, and it is working as expected. To keep the testing criteria similar and maximize the chance of reproducing the bug, can you please try it with the Aruco example, or run the
ros2 service call /zed/zed_node/set_pose zed_msgs/srv/SetPose '{pos: [0.0, 0.0, 0.0], orient: [0.0, 0.0, 0.0]}'
requester: making request: zed_msgs.srv.SetPose_Request(pos=array([0., 0., 0.], dtype=float32), orient=array([0., 0., 0.], dtype=float32))
Command repeatedly for multiple runs?
I have found 2 instances where people faced similar bugs like here. It is not helpful to solve the bug, but it points out that maybe it has something to do with how the ROS2 app interacts with the SDK. I’m not sure, I’m just sharing some guesses.
I will share the stacktrace in the next few minutes
thanks!