ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question
0

Waiting for dof_fit/follow_joint_trajectory to come up; Action client not connected: dof_fit/follow_joint_trajectory

asked 2021-09-30 17:52:58 -0500

Arnolvalencia1 gravatar image

updated 2021-10-04 14:37:33 -0500

hi, when i try to connect moveit to my gazebo simulation i get the following error:

[ WARN] [1633040618.377249905]: Waiting for dof_fit/follow_joint_trajectory to come up
[ERROR] [1633040624.377429395]: Action client not connected: dof_fit/follow_joint_trajectory
[ERROR] [1633040629.027678746]: Unable to connect to move_group action server 'move_group' within allotted time (30s)

i am using noetic ros, ubuntu 18.04, gazebo and moveit.

Mi archivo controllers.yaml luce del siguiente modo:

joint_state_controller:
type: joint_state_controller/JointStateController
  publish_rate: 50
controller_list:
  - name: dof_fit
    action_ns: follow_joint_trajectory
    type: FollowJointTrajectory
    default: true
    joints:
      - Joint_1
      - Joint_2
      - ...
  - name: hand_controller
    action_ns: follow_joint_trajectory
    type: FollowJointTrajectory
    default: true
    parallel: true
    joints:
      - Gripper_Idol_Gear_Joint
      - Gripper_Servo_Gear_Joint

my kimo_control.yaml file:

dof_fit:
    # Publish all joint states -----------------------------------
    joint_state_controller:
      type: joint_state_controller/JointStateController
      publish_rate: 50

    # Position Controllers ---------------------------------------
    Joint_1_position_controller:
      type: effort_controllers/JointPositionController
      joint: Joint_1
      pid: {p: 60.0, i: 40.0, d: 0.0}
    Joint_2_position_controller:
      type: effort_controllers/JointPositionController
      joint: Joint_2
      pid: {p: 80.0, i: 60.0, d: 0.0}
    Joint_3_position_controller:
  #..........

a part of the error:

[ INFO] [1633040607.368356602]: About to load: pilz_industrial_motion_planner::PlanningContextLoaderPTP
[ INFO] [1633040607.369259001]: Registered Algorithm [PTP]
[ INFO] [1633040607.369275481]: Using planning interface 'Pilz Industrial Motion Planner'
[ WARN] [1633040612.377062495]: Waiting for dof_fit/follow_joint_trajectory to come up
[ WARN] [1633040618.377249905]: Waiting for dof_fit/follow_joint_trajectory to come up
[ERROR] [1633040624.377429395]: Action client not connected: dof_fit/follow_joint_trajectory
[ERROR] [1633040629.027678746]: Unable to connect to move_group action server 'move_group' within allotted time (30s)
[ INFO] [1633040629.028283349]: Constructing new MoveGroup connection for group 'arm' in namespace ''
[ WARN] [1633040629.392726935]: Waiting for hand_controller/follow_joint_trajectory to come up
[ WARN] [1633040635.392889117]: Waiting for hand_controller/follow_joint_trajectory to come up
[ERROR] [1633040641.393057390]: Action client not connected: hand_controller/follow_joint_trajectory
[ INFO] [1633040641.403387237]: Returned 0 controllers in list
[ INFO] [1633040641.412451398]: Trajectory execution is managing controllers
[ INFO] [1633040641.412487078]: MoveGroup debug mode is ON

This error happens when I try to connect my gazebo simulation with moveit_rviz.launch and start to do movement planning.

Is the choice of controllers in controllers.yaml correct?

action_ns: follow_joint_trajectory
    type: FollowJointTrajectory

What controllers should I choose to control a joint: type: effort_controllers / JointPositionController?

rosnode list:

/arm_controller_spawner
/dof_fit/controller_spawner
/gazebo
/gazebo_gui
/move_group
/robot_state_publisher
/rosout
/rviz_iudc_desktop_pc_18608_6360793226529266128

rostopic list:

/attached_collision_object
/clock
/collision_object
/dof_fit/Gripper_Idol_Gear_Joint_position_controller/command
/dof_fit/Gripper_Idol_Gear_Joint_position_controller/pid/parameter_descriptions
/dof_fit/Gripper_Idol_Gear_Joint_position_controller/pid/parameter_updates
/dof_fit/Gripper_Idol_Gear_Joint_position_controller/state
/dof_fit/Gripper_Servo_Gear_Joint_position_controller/command
/dof_fit/Gripper_Servo_Gear_Joint_position_controller/pid/parameter_descriptions
/dof_fit/Gripper_Servo_Gear_Joint_position_controller/pid/parameter_updates
/dof_fit/Gripper_Servo_Gear_Joint_position_controller/state
/dof_fit/Joint_1_position_controller/command
/dof_fit/Joint_1_position_controller/pid/parameter_descriptions
/dof_fit/Joint_1_position_controller/pid/parameter_updates
/dof_fit/Joint_1_position_controller/state
/dof_fit/Joint_2_position_controller/command
/dof_fit/Joint_2_position_controller/pid/parameter_descriptions
/dof_fit/Joint_2_position_controller/pid/parameter_updates
/dof_fit/Joint_2_position_controller/state
/dof_fit/Joint_3_position_controller/command
/dof_fit/Joint_3_position_controller/pid/parameter_descriptions
/dof_fit/Joint_3_position_controller/pid/parameter_updates
/dof_fit/Joint_3_position_controller/state
/dof_fit/Joint_4_position_controller/command
/dof_fit/Joint_4_position_controller/pid/parameter_descriptions
/dof_fit/Joint_4_position_controller/pid/parameter_updates
/dof_fit/Joint_4_position_controller/state
/dof_fit/Joint_5_position_controller/command
/dof_fit/Joint_5_position_controller/pid/parameter_descriptions
/dof_fit/Joint_5_position_controller/pid/parameter_updates
/dof_fit/Joint_5_position_controller/state
/dof_fit/Joint_6_position_controller/command
/dof_fit/Joint_6_position_controller/pid/parameter_descriptions
/dof_fit/Joint_6_position_controller/pid/parameter_updates
/dof_fit/Joint_6_position_controller/state
/dof_fit/joint_states
/execute_trajectory/cancel
/execute_trajectory/feedback
/execute_trajectory/goal
/execute_trajectory/result
/execute_trajectory/status
/gazebo/link_states
/gazebo/model_states
/gazebo/parameter_descriptions
/gazebo/parameter_updates
/gazebo/performance_metrics
/gazebo/set_link_state
/gazebo/set_model_state
/head_mount_kinect/depth_registered/points
/joint_states
/move_group/cancel
/move_group/display_contacts
/move_group/display_cost_sources
/move_group/display_grasp_markers
/move_group ...
(more)
edit retag flag offensive close merge delete

Comments

Please edit your description to show us the output of rosnode list and rostopic list. You edit using the "edit" button at the end of your description.

Mike Scheutzow gravatar image Mike Scheutzow  ( 2021-10-04 11:29:14 -0500 )edit

arm_controller appears when a rosnode list is written but when it performs rostopic list the services are not connecting

Arnolvalencia1 gravatar image Arnolvalencia1  ( 2021-10-04 14:43:39 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
1

answered 2021-10-03 11:05:59 -0500

Mike Scheutzow gravatar image

Do you have any topic name that ends with .../follow_joint_trajectory/goal? If not, you have not started the Action Server.

Did you use the same controller name in gazebo config and in MoveIt config? See 2nd answer to #q296694.

edit flag offensive delete link more

Comments

the solution was to follow the steps described in the second answer and add to my gazebo simulation the controller like this:

<node name="controller_spawner" pkg="controller_manager" type="spawner" respawn="false"
        output="screen" ns="/dof_fit" args="joint_state_controller
                                            arm_controller
                                            Joint_1_position_controller
                                            Joint_2_position_controller
                                            ......"/>
Arnolvalencia1 gravatar image Arnolvalencia1  ( 2021-10-04 23:24:40 -0500 )edit

Glad you figured it out - I've never found good docs for this ros_control stuff.

Mike Scheutzow gravatar image Mike Scheutzow  ( 2021-10-05 07:48:06 -0500 )edit

I found an interesting template that solves many ros_control problems, I will work on it, I share the link:

https://github.com/PickNikRobotics/ros_control_boilerplate

Arnolvalencia1 gravatar image Arnolvalencia1  ( 2021-10-05 09:30:19 -0500 )edit

Thanks for the link. I'll take a look at it.

Mike Scheutzow gravatar image Mike Scheutzow  ( 2021-10-06 05:58:29 -0500 )edit

Question Tools

2 followers

Stats

Asked: 2021-09-30 17:52:58 -0500

Seen: 1,590 times

Last updated: Oct 04 '21