You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While controlling our H2017 with the doosan-robot package, we've been noticing that often the robot will move in an uneven manner, with alternating sections of fast and slow motion as seen in this video, of the robot moving from one setpoint to another using the dsr_moveit launch file. Is this a known issue, or is there a known fix for a mistake we might be making?
Additionally, we're hoping to control our arm using moveit servo. Our current setup sees the servo node publish commands as trajectory_msgs/JointTrajectory, which we then send to the FollowJointTrajectory Action server as an action goal. Although the commands are published at a rate of 100hz, the motion by the arm is piecewise as seen in this video. Our initial guess is that this occurs because each movement command blocking and must complete before the next command begins; is this intuition correct?
The text was updated successfully, but these errors were encountered:
Regarding the first question, we are aware of the issue internally and it is scheduled to be addressed with an improved motion servoj in the upcoming 2.12 version update.
As for the second question about the servo, it pertains to the moveit_servo functionality. Since our provided package does not utilize the moveit_servo feature, it may be challenging to resolve everything with the improved servoj motion.
Hello,
While controlling our H2017 with the doosan-robot package, we've been noticing that often the robot will move in an uneven manner, with alternating sections of fast and slow motion as seen in this video, of the robot moving from one setpoint to another using the dsr_moveit launch file. Is this a known issue, or is there a known fix for a mistake we might be making?
Additionally, we're hoping to control our arm using moveit servo. Our current setup sees the servo node publish commands as trajectory_msgs/JointTrajectory, which we then send to the FollowJointTrajectory Action server as an action goal. Although the commands are published at a rate of 100hz, the motion by the arm is piecewise as seen in this video. Our initial guess is that this occurs because each movement command blocking and must complete before the next command begins; is this intuition correct?
The text was updated successfully, but these errors were encountered: