Revision history [back]

Looking at the github repository you linked, it appears you have a workspace within a workspace. While that can technically work, I'd not advise it. Move all dirs in industrial_core_ws/src to where v068_description is. Also move v068_description/moveit_config to where v068_description is.

Looking at the github repository repo you linked, it appears you have a workspace within a workspace. While that can technically work, I'd not advise it. Move all dirs I'd create a new workspace, and clone the ros-i pkgs in the industrial_core_ws/srcsrc to where dir, place your v068_description is. Also move in v068_description/moveit_configsrc as well. Move moveit_config to where v068_descriptionsrc is..

Looking at the github repo you linked, it appears you have a workspace within a workspace. While that can technically work, I'd not advise it. I'd create it.

Suggested layout for a new workspace, workspace:

/path/to/catkin_ws
  src
    industrial_robot_client
      industrial_core
      ..
    v068_description
      URDF
      ..
    moveit_config
      ..

Now, in a fresh terminal (make sure you have not sourced setup.bash of your old workspace), build the new workspace.

If successful, source /path/to/catkin_ws/devel/setup.bash.

If I source the setup.bash then I can use rosrun and clone the ros-i execute the joint_trajectory_action and industrial_robot_simulator files solo without any errors, but I cannot source the setup.bash and re-execute the moveit_planning_execution.launch.

This should be sorted after you source the new workspace: all your pkgs now live in the src dir, place your v068_description a single workspace.

The second:

[FATAL] [1443558286.149773220]: Parameter '~moveit_controller_manager' not specified. This is needed to identify the plugin to use for interacting with controllers. No paths can be executed.

I believe this could be due to the setup of your MoveIt configuration package. In particular the files in src as well. Move moveit_config to src.

Looking at the github repo you linked, it appears you have a workspace within a workspace. While that can technically work, I'd not advise it.

Suggested layout for a new workspace:

/path/to/catkin_ws
  src
    industrial_robot_client
      industrial_core
      ..
    v068_description
      URDF
      ..
    moveit_config
      ..

Now, in a fresh terminal (make sure you have not not sourced setup.bash of your old workspace), build the new workspace.

If successful, source /path/to/catkin_ws/devel/setup.bash.

If I source the setup.bash then I can use rosrun and execute the joint_trajectory_action and industrial_robot_simulator files solo without any errors, but I cannot source the setup.bash and re-execute the moveit_planning_execution.launch.

This should be sorted after you source the new workspace: all your pkgs now live in a single workspace.

The second:

[FATAL] [1443558286.149773220]: Parameter '~moveit_controller_manager' not specified. This is needed to identify the plugin to use for interacting with controllers. No paths can be executed.

I believe this could be due to the setup of your MoveIt configuration package. In particular the files in config and the denso_vs068A2-AV6-NNN-AA_moveit_controller_manager.launch.xml file. The Create a MoveIt Package for an Industrial Robot tutorial should show you how to set it up.

General comment: it is not recommended to merge your MoveIt configuration with your description package. Also, you might be interested in the wiki/denso packages. They don't use the industrial_robot_client infrastructure, but are more tailored towards using ROS with Denso robots.

Looking at the github repo you linked, it appears you have a workspace within a workspace. While that can technically work, I'd not advise it.

Suggested layout for a new workspace:

/path/to/catkin_ws
  src
    industrial_core
      industrial_robot_client
      industrial_core
      ..
      industrial_robot_simulator
      --
    v068_description
      URDF
      ..
    moveit_config
      ..

Now, in a fresh terminal (make sure you have not sourced setup.bash of your old workspace), build the new workspace.

If successful, source /path/to/catkin_ws/devel/setup.bash.

If I source the setup.bash then I can use rosrun and execute the joint_trajectory_action and industrial_robot_simulator files solo without any errors, but I cannot source the setup.bash and re-execute the moveit_planning_execution.launch.

This should be sorted after you source the new workspace: all your pkgs now live in a single workspace.

The second:

[FATAL] [1443558286.149773220]: Parameter '~moveit_controller_manager' not specified. This is needed to identify the plugin to use for interacting with controllers. No paths can be executed.

I believe this could be due to the setup of your MoveIt configuration package. In particular the files in config and the denso_vs068A2-AV6-NNN-AA_moveit_controller_manager.launch.xml file. The Create a MoveIt Package for an Industrial Robot tutorial should show you how to set it up.

General comment: it is not recommended to merge your MoveIt configuration with your description package. Also, you might be interested in the wiki/denso packages. They don't use the industrial_robot_client infrastructure, but are more tailored towards using ROS with Denso robots.

Looking at the github repo you linked, it appears you have a workspace within a workspace. While that can technically work, I'd not advise it.

Suggested layout for a new workspace:

/path/to/catkin_ws
  src
    industrial_core
      industrial_robot_client
      ..
      industrial_robot_simulator
      --
..
    v068_description
      URDF
      ..
    moveit_config
      ..

Now, in a fresh terminal (make sure you have not sourced setup.bash of your old workspace), build the new workspace.

If successful, source /path/to/catkin_ws/devel/setup.bash.

If I source the setup.bash then I can use rosrun and execute the joint_trajectory_action and industrial_robot_simulator files solo without any errors, but I cannot source the setup.bash and re-execute the moveit_planning_execution.launch.

This should be sorted after you source the new workspace: all your pkgs now live in a single workspace.

The second:

[FATAL] [1443558286.149773220]: Parameter '~moveit_controller_manager' not specified. This is needed to identify the plugin to use for interacting with controllers. No paths can be executed.

I believe this could be due to the setup of your MoveIt configuration package. In particular the files in config and the denso_vs068A2-AV6-NNN-AA_moveit_controller_manager.launch.xml file. The Create a MoveIt Package for an Industrial Robot tutorial should show you how to set it up.

General comment: it is not recommended to merge your MoveIt configuration with your description package. Also, you might be interested in the wiki/denso packages. They don't use the industrial_robot_client infrastructure, but are more tailored towards using ROS with Denso robots.