No version for distro humble showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro jazzy showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro kilted showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro rolling showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro ardent showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro bouncy showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro crystal showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro eloquent showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro dashing showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro galactic showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro foxy showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro iron showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro lunar showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro jade showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro indigo showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro hydro showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro melodic showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.
        
      
    Recent questions tagged motoman_sia30d_support at Robotics Stack Exchange
No version for distro noetic showing kinetic. Known supported distros are highlighted in the buttons above.
      
      
      
      Package Summary
| 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 | 2025-04-10 | 
| Dev Status | MAINTAINED | 
| Released | UNRELEASED | 
| Contributing | 
        
          Help Wanted (-)
        
         Good First Issues (-) Pull Requests to Review (-)  | 
    
Package Description
Additional Links
Maintainers
- Eric Marcil
 - G.A. vd. Hoorn (TU Delft Robotics Institute)
 
Authors
- Eric Marcil
 
 README 
            
            No README found.
             See repository README.
            
            
           CHANGELOG
          
            
              No CHANGELOG found.
            
          
        Package Dependencies
| Deps | Name | 
|---|---|
| catkin | |
| joint_state_publisher_gui | |
| motoman_driver | |
| motoman_resources | |
| robot_state_publisher | |
| rviz | |
| xacro | |
| roslaunch | 
System Dependencies
            
              No direct system dependencies.
            
          
        Dependant Packages
            
              No known dependants.
            
          
        Launch files
- launch/load_sia30d.launch
                
 - launch/robot_interface_streaming_sia30d.launch
                
- 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of 'robot_interface_streaming.launch'.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_interface_streaming_sia30d.launch robot_ip:=
 - launch/robot_state_visualize_sia30d.launch
                
- 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
controller:=  - 
                    
- robot_ip — IP of controller
 - controller — Series of the controller (dx100, dx200, fs100 or yrc1000)
 
 
 - 
  Manipulator specific version of the state visualizer.
  Defaults provided for sia30d:
   - 7 joints
  Usage:
    robot_state_visualize_sia30d.launch robot_ip:=
 - launch/test_sia30d.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.