Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

timeout detected: BaseCyclicClient::RefreshFeedback #248

Open
MiguelGarciaUVa opened this issue Oct 30, 2024 · 4 comments
Open

timeout detected: BaseCyclicClient::RefreshFeedback #248

MiguelGarciaUVa opened this issue Oct 30, 2024 · 4 comments

Comments

@MiguelGarciaUVa
Copy link

MiguelGarciaUVa commented Oct 30, 2024

Hi,

I'm encountering an issue where the execution of my node stops intermittently due to an error. Here’s the message I receive:

[ros2_control_node-1] terminate called after throwing an instance of 'std::runtime_error'
[ros2_control_node-1] what(): timeout detected: BaseCyclicClient::RefreshFeedback
[ros2_control_node-1]
[ERROR] [ros2_control_node-1]: process has died [pid 2240, exit code -6, cmd '/opt/ros/humble/lib/controller_manager/ros2_control_node --ros-args --params-file /tmp/launch_params_k4apqsns --params-file /opt/ros/humble/share/kinova_gen3_7dof_robotiq_2f_85_moveit_config/config/ros2_controllers.yaml'].

Another error I have is this one:

[ros2_control_node-1] [ERROR] [1730297841.669743775] [KortexMultiInterfaceHardware]: Runtime error: timeout detected: BaseCyclicClient::Refresh
[ros2_control_node-1]
[ros2_control_node-1] [ERROR] [1730297842.610749945] [KortexMultiInterfaceHardware]: Future error: std::future_error: Future already retrieved

The last error occurs more frequently when I use the camera with the command ros2 launch kinova_vision kinova_vision.launch.py.
Does anyone have insights into what could be causing this timeout error?

Thanks!

@Melih199
Copy link

I am facing with the same issue. Did you find any solution for it? @MiguelGarciaUVa

Thanks!

@MiguelGarciaUVa
Copy link
Author

No, I didn´t find a solution but I think it depends on the computational load of the computer. It happens more when I have the computer close to its maximum performance.
I have the arm on a mobile platform and the control is on a NUC. I bought a better NUC but it still happens..

@aalmrad
Copy link
Collaborator

aalmrad commented Feb 11, 2025

Hello,

We have noticed this problem on our side when running computationally intensive applications and we are working towards finding a solution.

Best,
Abed

@martinleroux
Copy link
Collaborator

To add on @aalmrad 's comment, we did indeed stumble unto the same symptoms on our side. As @MiguelGarciaUVa has highlighted, we have also noticed it seems to be related to the computational load on the PC. Running the code on a better PC did improve things a lot, but I understand this is not necessarily a viable solution for everyone. Our next best recommendation is to use the RT patch for Linux on your PC to stabilize the real-time connection.

We are still looking for better solutions that could solve the issue entirely. If we end up finding anything, we'll make sure to update this issue. Although I admittedly can't promise we will find a universal solution since the occurrence is linked to things happening on the PC outside of the driver itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants