-
Notifications
You must be signed in to change notification settings - Fork 62
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
Awaiting 'COMMANDING_WAIT' state. #251
Comments
hi @ZixuanLiu-Justin, thanks for providing these detailed reports. For some reason your robot disconnects immediately: [ros2_control_node-3] [INFO] [1740523033.929589624] [lbr_fri_ros2::AsyncClient]: LBR switched from 'MONITORING_WAIT' to 'MONITORING_READY'
[ros2_control_node-3] [INFO] [1740523034.002722950] [lbr_fri_ros2::AsyncClient]: LBR switched from 'MONITORING_READY' to 'IDLE' Have you managed to connect the robot before, e.g. running: The safety warnings are fine. I am assuming you installed this Java application: https://github.com/lbr-stack/fri/blob/fri-2.5/server_app/LBRServer.java @fredRocs could you please give me a helping hand here (I recall you used FRI |
Hi @mhubii, thank you for the information! I can confirm that I successfully connect to the robot by using:
and I can control the robot by using moveit via:
I tested in It currently should work fine for me for my need:) |
Okay very glad to hear, thank you very much for confirming! :) If you find some insights on why it didn't work, it would be very valuable for the community to share them. I do not have access to Sunrise Workbench with 2.5 and can thus not always verify the server side (robot side). |
Hi,
I'm trying to run the LBR Joint Position Command Controller (Hardware only) on the KUKA Med14. I've set the robot to automatic mode (AUT). From the output on the smartPad, it shows the connection actually established, but then it immediately closed itself.
below is the output from the terminal, it seems like the robot is never going to the expected state 'COMMANDING_WAIT'.
I'm using the ros2 humble with naive Ubuntu 22.04, the KUKA comes with fri version 2.5. Any ideas can potentially solve this?
BTW, I'm also attaching a photo showing a safety warning message here:
The text was updated successfully, but these errors were encountered: