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

Package Summary

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

Repository Summary

Checkout URI https://github.com/ros-industrial/motoman.git
VCS Type git
VCS Version jade-devel
Last Updated 2016-07-04
Dev Status MAINTAINED
Released UNRELEASED

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

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/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/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
  • launch/load_mh5.launch
  • 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.

Package Summary

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

Repository Summary

Checkout URI https://github.com/ros-industrial/motoman.git
VCS Type git
VCS Version indigo-devel
Last Updated 2016-07-04
Dev Status MAINTAINED
Released UNRELEASED

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

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/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/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
  • launch/load_mh5.launch
  • 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.

Package Summary

Tags No category tags.
Version 0.3.3
License BSD
Buildtool 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
Released RELEASED

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

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/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/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
  • launch/load_mh5.launch
  • 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.
No version for distro groovy. Known supported distros are highlighted in the buttons above.
No version for distro fuerte. Known supported distros are highlighted in the buttons above.
No version for distro electric. Known supported distros are highlighted in the buttons above.
No version for distro diamondback. Known supported distros are highlighted in the buttons above.