Closed xarthurx closed 5 years ago
The driver will assume that motion commands take a certain amount of time. By changing the speed slider value, you change that time, but unilaterally: MoveIt doesn't get notified, nor do the controllers.
This is the likely cause of the "desync" that you observed.
Is this a bug in the driver?
No. At the moment this is expected behaviour.
You could see whether configuring the same velocity and acceleration scaling in your MoveIt plan request improves the situation, but especially the acceleration scaling will not be trivial to get just right.
I'm going to close this as I'm going to assume that we've sufficiently dealt with the issue you report and that it's not something we can change in the driver for now.
Feel free to keep commenting on the issue of course.
this should be documented in the README
Using MoveIt to compute trajectory and execute.
If I set the speed to
100%
, no problem. (set on the panel with the slider) If I set the speed ton < 100%
, robot will not stop at the target location, but continues to move and slowly stop little by little.Ubuntu 18.04 ur_modern_driver compiled from catkin (It also affect ubuntu 16.04 on another machine)
command executed from websocket through
rosbridge
.Is this a bug in the driver?