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
I find that both the /vel_based_pos_traj_controller and the /pos_based_traj_controller produce erratic motions for the UR3. The velocity-based controller is highly unstable and takes off immediately (video) while the position-based controller oscillates with large magnitude about the setpoint (video). The PID gains on the velocity-based controller are ridiculously high (Kp=50) but even if I turn them down to Kp=0.01, Kd=0.001, the robot is unstable. I'm not sure how to go about tuning the position-based controller because ros_control does not expose PID gains for it.
I launch with roslaunch ur_modern_driver ur3_ros_control.launch robot_ip:=192.168.1.102
No other ROS nodes were running and no commands were sent. I added the appropriate controller to ur3_moveit_config/config/controllers.yaml like this:
The velocity controller video looks like you may be hitting #206 more than an oscillation going unstable. Could you try with the fix proposed in #213 and see if that solves the problem for you?
Regarding the position controller, no PID gains are exposed because there's no PID controller involved at all. I'm truly baffled that you are experiencing that oscillatory behavior. Are you absolutely sure its the pos_based_pos_traj_controller you are running?
I find that both the
/vel_based_pos_traj_controller
and the/pos_based_traj_controller
produce erratic motions for the UR3. The velocity-based controller is highly unstable and takes off immediately (video) while the position-based controller oscillates with large magnitude about the setpoint (video). The PID gains on the velocity-based controller are ridiculously high (Kp=50) but even if I turn them down to Kp=0.01, Kd=0.001, the robot is unstable. I'm not sure how to go about tuning the position-based controller because ros_control does not expose PID gains for it.I launch with
roslaunch ur_modern_driver ur3_ros_control.launch robot_ip:=192.168.1.102
No other ROS nodes were running and no commands were sent. I added the appropriate controller to
ur3_moveit_config/config/controllers.yaml
like this:My UR3 software is version 3.5.0.1.10584, ur_modern_driver commit c4b2c73, universal_robot commit f528e20 (a.k.a. the most recent).
The default
roslaunch ur_modern_driver ur3_bringup_joint_limited.launch
works great.The text was updated successfully, but these errors were encountered: