is there ros support for yaskawa motoman nxc100?
if not, can I create it myself somehow?
ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
if not, can I create it myself somehow?
As for ROS-Industrial (with the motoman_driver
package), there is no support for the NXC 100 controller.
From an answer by Eric Marcel (Yaskawa America) on Does ROS SUPPORT the NXC100 Controller on the ROS-Industrial mailing list:
Unfortunately, the NXC controller is an older generation and doesn't support MotoPlus API on which the ROS driver is built. For a controller of similar size to the NXC, you would need to get the FS100 controller with a new robot.
There are some alternative ways to communicate with those controllers, but they will be less performant than MotoPlus and motoman_driver
:
Otherwise, for remote controller of the NXC you can use the "Ethernet Server function" or MotoCom API (for Windows). In theory, you might be able write a ROS driver to send motion instruction through the "Ethernet Server" but there are limitations. Communication response is fairly slow (around 60 ms) and you can only queue one motion at the time, so the robot need to reach its set destination before you can send the next destination.
So to answer your question:
is there ros support for yaskawa motoman nxc100?
No.
if not, can I create it myself somehow?
Yes, but there will be performance issues, and you would not be able to reuse the industrial_robot_client and / or motoman_driver packages (without modifications), and it will probably require quite some effort, as the MotoCOM API is apparently targeted mainly at Windows.
Asked: 2015-09-16 01:46:40 -0600
Seen: 209 times
Last updated: Sep 16 '15
Support Motoman Yaskawa gp-7 model
motoman stack on ros industrial
Package not found (rospack find: error)
Motoman control two groups asynchronously
Movegroups error with joystick_control.launch
How to load INIT_ROS.jbi file correctly?
Can I control ports input / output of an industrial robot?
Moveit tutorial cartesian path error, missing valid timestamp data?
FS100 - MotoROS integration implications when MotoSight/Fit/COM are already setup