Closed akupferb closed 2 months ago
Hi @akupferb Did you install the librealsense SDK from source code using the libuvc backend or RSUSB backend methods? If you did then a characteristic of this install method is that it checks for changes less often than a package installation of the SDK or a non-RSUSB source code build that has had a patch applied to its kernel (a build type known as the V4L or native backend). Because libuvc / RSUSB versions of librealsense check for changes less often, an option change request may sometimes fail and have to be re-tried.
In this instance of the system the librealsense SDK has been installed via debian packages.
Have you tried commenting out depth_module.infra_profile $RESOLUTION
to test whether it is this change instruction or the infra ones that are timing-out?
It occurs inconsistently, sometimes on one of the 'set false' commands and sometimes on the resolution change. I just had a repeat occurrence of the error on the very first call.
Does stability improve if you add a sleep command before each instruction? For example, to wait for 1 second before initiating each command:
import time
time.sleep(1)
ros2 param set $CAMERA_NAME enable_infra1 false
time.sleep(1)
ros2 param set $CAMERA_NAME enable_infra2 false
time.sleep(1)
ros2 param set $CAMERA_NAME depth_module.infra_profile $RESOLUTION
time.sleep(1)
ros2 param set $CAMERA_NAME enable_infra1 true
time.sleep(1)
ros2 param set $CAMERA_NAME enable_infra2 true
Hi @akupferb Do you require further assistance with this case, please? Thanks!
Case closed due to no further comments received.
Issue Description
While in a Docker container, and running the following ROS2 commands from a command line script:
I occasionally get the error response to one of the
param set
commands (not necessarily the first command, sometimes a couple work and then I get the error):[camera.camera.rclcpp]: failed to send response to /camera/camera/set_parameters (timeout): client will not receive response, at ./src/rmw_response.cpp:154, at ./src/rcl/service.c:314
Why is this error sometimes occurring during runtime, especially when previous calls to the
set_parameters
service viaparam set
have worked?