-
ROS index logo ROS Index
  1. Home
  2. Packages
  3. motoman_mh5_support
 
No version for distro humble. Known supported distros are highlighted in the buttons above.
No version for distro iron. Known supported distros are highlighted in the buttons above.
No version for distro jazzy. Known supported distros are highlighted in the buttons above.
No version for distro rolling. Known supported distros are highlighted in the buttons above.
No version for distro noetic. Known supported distros are highlighted in the buttons above.
No version for distro ardent. 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 crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. 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.

motoman_mh5_support package from motoman repo

motoman motoman_driver motoman_mh5_support motoman_msgs motoman_sda10f_moveit_config motoman_sda10f_support motoman_sia10d_support motoman_sia10f_support motoman_sia20d_moveit_config motoman_sia20d_support motoman_sia5d_support

API Docs
Browse Code

Package Summary

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

Repository Summary

Checkout URI https://github.com/ros-industrial/motoman.git
VCS Type git
VCS Version indigo-devel
Last Updated 2018-02-07
Dev Status MAINTAINED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Additional Links

Maintainers

No known maintainers.

Authors

  • Shaun Edwards
README
No README found. See repository README.
CHANGELOG

Changelog for package motoman_mh5_support

0.3.5 (2016-07-03)

  • No changes

0.3.4 (2016-07-03)

  • Fixed roslaunch test issues
  • mh5: remove 'solid' from binary visual meshes. Fix #60. Also removes executable bit (not needed).
  • Added comment with old joint limits and explanation.
  • Reduced joint_u limits to values measured from an MH5F.
  • Reversed MH5 base mesh. Was on backwards.
  • New concave meshes. Visuals are full-res, collisions are decimated.
  • added missing prefix to links (batch replace)
  • Contributors: Dave Hershberger, David Hershberger, Mathias Lüdtke, Shaun Edwards, gavanderhoorn, thiagodefreitas

0.3.3 (2014-02-07)

  • No changes

0.3.2 (2014-01-31)

  • Added build dependency on roslaunch to address missing roslaunch check missing macro
  • Contributors: Shaun Edwards

0.3.1 (2014-01-30)

  • Synchronized versions for bloom release
  • Generated mh5 and created required urdfs/meshes
  • Contributors: Shaun Edwards

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps Name
roslaunch
catkin
motoman_driver
robot_state_publisher
rviz
joint_state_publisher

System Dependencies

No direct system dependencies.

Dependant Packages

Name Deps
motoman

Launch files

  • launch/test_mh5.launch
  • launch/robot_interface_streaming_mh5.launch
    • Manipulator specific version of 'robot_interface_streaming.launch'. Defaults provided for mh5: - 7 joints Usage: robot_interface_streaming_mh5.launch robot_ip:= controller:=
      • robot_ip
      • controller
  • launch/load_mh5.launch
  • launch/robot_state_visualize_mh5.launch
    • Manipulator specific version of the state visualizer. Defaults provided for mh5: - 7 joints Usage: robot_state_visualize_sia20d.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_mh5_support at Robotics Stack Exchange

motoman_mh5_support package from motoman repo

motoman motoman_config motoman_driver motoman_mh5_support motoman_sia10d_support motoman_sia20d_moveit_config motoman_sia20d_support motoman_sia5d_support

API Docs
Browse Code

Package Summary

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

Repository Summary

Checkout URI https://github.com/ros-industrial/motoman.git
VCS Type git
VCS Version hydro
Last Updated 2014-02-08
Dev Status MAINTAINED
CI status Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Additional Links

Maintainers

No known maintainers.

Authors

  • Shaun Edwards
README
No README found. See repository README.
CHANGELOG

Changelog for package motoman_mh5_support

0.3.3 (2014-02-07)

  • No changes

0.3.2 (2014-01-31)

  • Added build dependency on roslaunch to address missing roslaunch check missing macro
  • Contributors: Shaun Edwards

0.3.1 (2014-01-30)

  • Synchronized versions for bloom release
  • Generated mh5 and created required urdfs/meshes
  • Contributors: Shaun Edwards

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps Name
roslaunch
catkin
motoman_driver
robot_state_publisher
rviz
joint_state_publisher

System Dependencies

No direct system dependencies.

Dependant Packages

Name Deps
motoman

Launch files

  • launch/test_mh5.launch
  • launch/robot_interface_streaming_mh5.launch
    • Manipulator specific version of 'robot_interface_streaming.launch'. Defaults provided for mh5: - 7 joints Usage: robot_interface_streaming_mh5.launch robot_ip:= controller:=
      • robot_ip
      • controller
  • launch/load_mh5.launch
  • launch/robot_state_visualize_mh5.launch
    • Manipulator specific version of the state visualizer. Defaults provided for mh5: - 7 joints Usage: robot_state_visualize_sia20d.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_mh5_support at Robotics Stack Exchange

motoman_mh5_support package from motoman repo

motoman motoman_ar2010_support motoman_driver motoman_es_support motoman_gp110_support motoman_gp12_support motoman_gp180_support motoman_gp200r_support motoman_gp25_support motoman_gp35l_support motoman_gp4_support motoman_gp50_support motoman_gp70l_support motoman_gp7_support motoman_gp88_support motoman_gp8_support motoman_hc10_support motoman_hc20_support motoman_ma2010_moveit_config motoman_ma2010_support motoman_mh110_support motoman_mh12_support motoman_mh50_support motoman_mh5_support motoman_motomini_support motoman_motopos_d500_support motoman_ms210_moveit_config motoman_ms210_support motoman_msgs motoman_resources motoman_sda10f_moveit_config motoman_sda10f_support motoman_sia10d_support motoman_sia10f_support motoman_sia20d_moveit_config motoman_sia20d_support motoman_sia30d_support motoman_sia50_support motoman_sia5d_support

API Docs
Browse Code

Package Summary

Tags No category tags.
Version 0.3.5
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 2023-12-20
Dev Status MAINTAINED
CI status Continuous Integration
Released UNRELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Additional Links

Maintainers

  • Shaun Edwards
  • G.A. vd. Hoorn (TU Delft Robotics Institute)

Authors

  • Shaun Edwards
README
No README found. See repository README.
CHANGELOG

Changelog for package motoman_mh5_support

0.3.5 (2016-07-03)

  • No changes

0.3.4 (2016-07-03)

  • Fixed roslaunch test issues
  • mh5: remove 'solid' from binary visual meshes. Fix #60. Also removes executable bit (not needed).
  • Added comment with old joint limits and explanation.
  • Reduced joint_u limits to values measured from an MH5F.
  • Reversed MH5 base mesh. Was on backwards.
  • New concave meshes. Visuals are full-res, collisions are decimated.
  • added missing prefix to links (batch replace)
  • Contributors: Dave Hershberger, David Hershberger, Mathias Lüdtke, Shaun Edwards, gavanderhoorn, thiagodefreitas

0.3.3 (2014-02-07)

  • No changes

0.3.2 (2014-01-31)

  • Added build dependency on roslaunch to address missing roslaunch check missing macro
  • Contributors: Shaun Edwards

0.3.1 (2014-01-30)

  • Synchronized versions for bloom release
  • Generated mh5 and created required urdfs/meshes
  • Contributors: Shaun Edwards

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Package Dependencies

Deps Name
catkin
joint_state_publisher
motoman_driver
motoman_resources
robot_state_publisher
rviz
xacro
roslaunch

System Dependencies

No direct system dependencies.

Dependant Packages

Name Deps
motoman

Launch files

  • launch/test_mh5.launch
  • launch/robot_interface_streaming_mh5.launch
    • Manipulator specific version of 'robot_interface_streaming.launch'. Defaults provided for mh5: - 7 joints Usage: robot_interface_streaming_mh5.launch robot_ip:= controller:=
      • robot_ip — IP of controller
      • controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
  • launch/load_mh5.launch
  • launch/robot_state_visualize_mh5.launch
    • Manipulator specific version of the state visualizer. Defaults provided for mh5: - 7 joints Usage: robot_state_visualize_sia20d.launch robot_ip:= controller:=
      • robot_ip — IP of controller
      • controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
  • 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_mh5_support at Robotics Stack Exchange

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