No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.

Package Summary

Tags No category tags.
Version 0.1.0
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/ros-industrial/motoman.git
VCS Type git
VCS Version kinetic-devel
Last Updated 2019-11-12
Dev Status MAINTAINED
Released UNRELEASED

Package Description

Additional Links

Maintainers

  • Jakub Marsik (KM Robotics)
  • G.A. vd. Hoorn (TU Delft Robotics Institute)

Authors

  • Jakub Marsik
README
No README found. See repository README.
CHANGELOG
No CHANGELOG found.

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

Launch files

  • launch/load_gp180_120.launch
  • launch/robot_interface_streaming_gp180_120.launch
    • Manipulator specific version of 'robot_interface_streaming.launch'. Defaults provided for gp180_120: - joints Usage: robot_interface_streaming_gp1180_120.launch robot_ip:= controller:=
      • robot_ip
      • controller
  • launch/test_gp180_120.launch
  • launch/robot_state_visualize_gp180_120.launch
    • Manipulator specific version of the state visualizer. Defaults provided for gp180_120: - joints Usage: robot_state_visualize_gp180_120.launch robot_ip:= controller:=
      • robot_ip
      • controller
  • test/launch_test.xml
    • launch_test.xml - ROSlaunch tests Usage Instructions: 1. Add the following to your CMakeLists.txt: find_package(roslaunch) roslaunch_add_file_check(test/launch_test.xml) 2. Create a test directory under your package 3. Add the "launch_text.xml" file and fill out the test below. Use the following conventions: a. Encapsulate each launch file test in it's own namespace. By convention the namespace should have the same name as the launch file (minus ".launch" extension) b. Create tests for each possible combination of parameters. Utilize sub-namespaces under the main namespace. Notes: 1. XML extension is used in order to avoid beinging included in roslaunch auto-complete. 2. Group tags with namespaces are used to avoid node name collisions when testing multpile launch files

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged motoman_gp180_support at answers.ros.org

No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.