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

  • Thiago de Freitas

Authors

  • Thiago de Freitas
README
No README found. See repository README.
CHANGELOG

Changelog for package motoman_sda10f_support

0.3.5 (2016-07-03)

  • No changes

0.3.4 (2016-07-03)

  • Support for multiple motion group control
  • Contributors: Shaun Edwards, Thiago de Freitas, thiagodefreitas

0.3.3 (2014-02-07)

0.3.2 (2014-01-31)

0.3.1 (2014-01-30)

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Launch files

  • launch/robot_interface_streaming_sda10f.launch
    • Manipulator specific version of 'robot_interface_streaming.launch'. Defaults provided for sda10f: - 7 joints Usage: robot_interface_streaming_sda10f.launch robot_ip:= controller:=
      • robot_ip
      • controller
  • launch/load_sda10f.launch
  • launch/test_sda10f.launch
  • launch/robot_state_visualize_sda10f.launch
    • Manipulator specific version of the state visualizer. Defaults provided for sda10f: - 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.

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

  • Thiago de Freitas

Authors

  • Thiago de Freitas
README
No README found. See repository README.
CHANGELOG

Changelog for package motoman_sda10f_support

0.3.5 (2016-07-03)

  • No changes

0.3.4 (2016-07-03)

  • Support for multiple motion group control
  • Contributors: Shaun Edwards, Thiago de Freitas, thiagodefreitas

0.3.3 (2014-02-07)

0.3.2 (2014-01-31)

0.3.1 (2014-01-30)

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Launch files

  • launch/robot_interface_streaming_sda10f.launch
    • Manipulator specific version of 'robot_interface_streaming.launch'. Defaults provided for sda10f: - 7 joints Usage: robot_interface_streaming_sda10f.launch robot_ip:= controller:=
      • robot_ip
      • controller
  • launch/load_sda10f.launch
  • launch/test_sda10f.launch
  • launch/robot_state_visualize_sda10f.launch
    • Manipulator specific version of the state visualizer. Defaults provided for sda10f: - 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.
No version for distro hydro. Known supported distros are highlighted in the buttons above.
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.