Dock Action Server Succeeds But Sometimes Does Not Send Completion To Client #503
Replies: 2 comments 2 replies
-
It is possible you are running into a bug we have fixed with H.2.4, which is about to be released; please give it a try and let us know. It is also possible that there's something else going on. |
Beta Was this translation helpful? Give feedback.
2 replies
-
Wali has faithfully responded properly with dock goal result since updating to H.2.4 - 6 dock goal requests in 24 hours of testing. Closing this issue:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you connecting to your Create 3?
Wi-Fi (ROS 2)
Computer(s) Model(s) and Operating System(s)
Ubuntu 22.04 in Docker over Raspberry Pi 5 PiOS Bookworm
Which version of ROS 2 is installed on your computer?
Humble
Which firmware version is installed on your robot?
H.2.3
Which RMW is your robot running?
FastRTPS
Does your robot have an assigned namespace? If so, please share.
No response
Is the robot connected to a network? If so, what is the network type?
Yes: 2.4GHz Home WiFi
Are there multiple Create 3 robots connected to your network?
No
Is multicast enabled?
Yes
What is the Adapter Board's USB/BLE Toggle currently switched to?
Bluetooth (default)
Describe your question.
Dock Action Server Succeeds But Fails To Send Completion To Client
My ROS 2 Humble wali_node.py is successfully controlling my Create3:
But recently the Dock action server has been successfully docking the Create3, but failing to send the completion to the client. (Can't say if it is every time or just the last two times, but rotate_angle has never missed a result message):
Adding log from Create3:
ActionServerSuccessDidNotSendCompletion.txt
I posted a design question for this issue on robotics.stackexchange.com
Beta Was this translation helpful? Give feedback.
All reactions