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

Unexpected Connection Break Without Warning and Emergency Stop #116

Open
anubhav-dogra opened this issue Mar 22, 2024 · 2 comments
Open

Comments

@anubhav-dogra
Copy link

Hi @costashatz
Have you ever found this issue ?

I am using this library from quite a while now, and while running experiments, I do find that robot just stops working after a sometime (may be an hour or so). There is no error on the smartpad or on the ROS machine. I have noticed that the Application status just turns off !
Here is the screenshot of the SmartPad.
image

After this, robot stays at whatever controller it was booted on. For example it stays in Torque mode (stiffness Zero) or PositionController with stiffness X. Next step for me it just to press the emergency stop!

Later on, If I close FRI application and rerun it again, I got his error:
image

I can only make it work if I restart robot controller.

Any comments please ?

@matthias-mayr
Copy link
Contributor

I missed that issue apparently

I am using this library from quite a while now, and while running experiments, I do find that robot just stops working after a sometime (may be an hour or so). There is no error on the smartpad or on the ROS machine. I have noticed that the Application status just turns off !

I have no memories of this pattern. I had disconnects into the past until I pushed some changes to the driver. Then it was working fine for me with a preempt_rt kernel. iirc, I used 500 Hz most of the time.

What is important to fully reset the program though is to untick the current program in the list of applications and then select it again. This is a bit finicky since the checkbox is not that easy to hit on the smartpad. But this is the procedure I always went through.

@anubhav-dogra
Copy link
Author

Hi @matthias-mayr
Thanks for your response. What I am noticing is I think beyond this library. Because in my case, Kuka becomes unresponsive (even from the smartpad) after like 45 mins or so.
I have contacted KUKA support, and waiting for their response.

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

2 participants