Replies: 3 comments 1 reply
-
The delay is caused by the network communication. There are ways to reduce it through configurations of the dds stack. |
Beta Was this translation helpful? Give feedback.
-
Are you using the Create3 actions? Have you characterized the /cmd_vel topic delay? (It appears to be always sub-second unless the Create3 is having one of its 10 second overload crisies) |
Beta Was this translation helpful? Give feedback.
-
"The delay is caused by the network communication." "Are you using the Create3 actions?" "It appears to be always sub-second" |
Beta Was this translation helpful? Give feedback.
-
How are you connecting to your Create 3?
Wi-Fi (ROS 2)
Computer(s) Model(s) and Operating System(s)
Asus Vivobook - Ubuntu 22.04
Which version of ROS 2 is installed on your computer?
Humble
Which firmware version is installed on your robot?
H.2.5
Which RMW is your robot running?
CycloneDDS
Does your robot have an assigned namespace? If so, please share.
No
Is the robot connected to a network? If so, what is the network type?
Normal WiFi in my office
Are there multiple Create 3 robots connected to your network?
No
Is multicast enabled?
No
What is the Adapter Board's USB/BLE Toggle currently switched to?
None
Describe your question.
I work with irobot create3 and I noticed that there is a delay between sending a massage and performing an action. I tried to estimate it and the delay is usually less than 2.5 seconds (which is still long) but it can be as much as 8 seconds.
In my work, I try to use the robot to avoid obstacles as close as possible with Model Predictive Control, but it is very difficult to model the delay without being able to predict it.
Beta Was this translation helpful? Give feedback.
All reactions