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

error when connecting DX100 controller

asked 2019-02-27 08:04:09 -0600

nd gravatar image

updated 2019-02-27 08:27:17 -0600

Hello, I am trying to connect with DX100 controller via Ethernet. I have completed all step according to tutorial.

But when I am launching roslaunch motoman_driver robot_interface_streaming_dx100.launch robot_ip:=10.20.30.10 according to this, http://wiki.ros.org/motoman_driver/Tu... I am getting this error,

 /robot_ip_address: 10.20.30.10
 * /rosdistro: kinetic
 * /rosversion: 1.12.14

NODES
  /
    joint_state (motoman_driver/robot_state)
    joint_trajectory_action (industrial_robot_client/joint_trajectory_action)
    motion_streaming_interface (motoman_driver/motion_streaming_interface)

auto-starting new master
process[master]: started with pid [16267]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to 7ff70826-3a94-11e9-a310-e094677543f1
process[rosout-1]: started with pid [16280]
started core service [/rosout]
process[joint_state-2]: started with pid [16288]
process[motion_streaming_interface-3]: started with pid [16298]
process[joint_trajectory_action-4]: started with pid [16305]
[ERROR] [1551274510.017293580]: Failed to find topic_list parameter
[ERROR] [1551274510.019096560]: Cannot find user-specified joint names. Tried ROS parameter 'controller_joint_names' and the URDF in 'robot_description'.
[ERROR] [1551274510.019235316]: Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111)
[ERROR] [1551274510.025299639]: Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111)
[ERROR] [1551274510.025411427]: Failed to receive message length
[ERROR] [1551274510.025449442]: Failed to receive incoming message
[ERROR] [1551274510.029772460]: Failed to find topic_list parameter
[ERROR] [1551274510.032185826]: Cannot find user-specified joint names. Tried ROS parameter 'controller_joint_names' and the URDF in 'robot_description'.
[ERROR] [1551274510.032383954]: Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111)
[ERROR] [1551274510.036218270]: Cannot find user-specified joint names. Tried ROS parameter 'controller_joint_names' and the URDF in 'robot_description'.
[ERROR] [1551274510.037383101]: Failed to initialize joint_names.
[ERROR] [1551274510.057214554]: Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111)
[ERROR] [1551274510.307608223]: Timeout connecting to robot controller.  Send new motion command to retry.
[ERROR] [1551274515.026198348]: Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111)
[ERROR] [1551274515.026460781]: Failed to receive message length
[ERROR] [1551274515.026616096]: Failed to receive incoming message
[ERROR] [1551274520.027295751]: Failed to connect to server, rc: -1. Error: 'Connection refused' (errno: 111)

It is written in tutorial, Make sure the ROS trajectory node has been enabled by invoking the robot_enable service.

I can enable it by rosservice call.

But how can I enable it before launching above (roslaunch motoman_driver robot_interface_streaming_dx100.launch robot_ip:=10.20.30.10) command.

When I am starting controller in teach pendent I get Alarm like,

MotoROS: Controller cfg invalid
  [102]

But when I reset this alarm, it goes. is this a problem?

Thanks.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
0

answered 2019-02-27 08:31:33 -0600

gvdhoorn gravatar image

updated 2019-02-27 08:40:51 -0600

When I am starting controller in teach pendent I get Alarm like,

MotoROS: Controller cfg invalid
  [102]

But when I reset this alarm, it goes. is this a problem?

yes, this is a problem. From the Troubleshooting section on error 8003:

Your robot controller requires internal configuration changes to support the MotoROS driver.

For DX100: Please contact your local Yaskawa Motoman office to order the MotoROS runtime. In North/South America, the part number for this configuration is 180014-1. In Europe, the part number for this configuration is 171403.

Did you order the runtime license as was clarified in #q316165?

If so, I believe Yaskawa should also have updated your controller configuration with the necessary parameters to be able to run MotoROS on your DX100. If that hasn't happened -- or wasn't done correctly -- I believe you can run into errors such as the one you show.

As is stated under the Requirements - MotoPlus Runtime License section (emphasis mine):

The MotoROS application and source is available for public download. However, ordering this part number will ensure your controller is updated with correct system software, the MotoROS driver is installed, and all internal parameters are properly configured.

Can you confirm you've had your controller configuration updated for MotoROS?

edit flag offensive delete link more

Comments

@millete: FYI.

gvdhoorn gravatar image gvdhoorn  ( 2019-02-27 08:32:24 -0600 )edit

I will contact them and update it here.

nd gravatar image nd  ( 2019-02-27 09:01:05 -0600 )edit

So just to be clear: you haven't yet received/purchased the runtime license, or the parameter update wasn't done (correctly)?

gvdhoorn gravatar image gvdhoorn  ( 2019-02-27 09:34:44 -0600 )edit

haven't purchased license.

nd gravatar image nd  ( 2019-02-27 09:38:18 -0600 )edit

That would definitely be a problem then -- as I also wrote in #q316165.

gvdhoorn gravatar image gvdhoorn  ( 2019-02-27 09:48:14 -0600 )edit

is there any problem with robot_enable service call after I launch roslaunch motoman_driver robot_interface_streaming_dx100.launch robot_ip:=10.20.30.10 ?

nd gravatar image nd  ( 2019-02-27 14:27:21 -0600 )edit

I don't see any output in the log messages that you posted that is unexpected, given that MotoROS is just not running on your controller.

Diagnosing any of those errors right now is not very productive, as they're most likely caused by the 8000 error.

gvdhoorn gravatar image gvdhoorn  ( 2019-02-28 03:31:03 -0600 )edit

@gvdhoorn after updating controller with ALL.PRM file, which was from yaskawa. there is still alarm coming when starting controller, MotoROS config invalid [105]. what can be the problem now?

nd gravatar image nd  ( 2019-04-24 05:03:13 -0600 )edit

Question Tools

1 follower

Stats

Asked: 2019-02-27 08:04:09 -0600

Seen: 790 times

Last updated: Feb 27 '19