No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro bouncy. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.
No version for distro lunar. Known supported distros are highlighted in the buttons above.
|
schunk_canopen_driver package from schunk_canopen_driver reposchunk_canopen_driver |
Package Summary
| Tags | No category tags. |
| Version | 1.0.7 |
| License | FZI all rights reserved |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/fzi-forschungszentrum-informatik/schunk_canopen_driver.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2017-11-02 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
Package Description
The schunk_canopen_driver package
Additional Links
No additional links.
Maintainers
- Georg Heppner
Authors
- Felix Mauch
- Georg Heppner
This is the driver package for the SCHUNK LWA4P and other CanOpen enabled devices.
It was developed on behalf of SCHUNK GmbH, Lauffen/Neckar, Germany
at the FZI Research Center for Information Technology in Karlsruhe, Germany.
The package contains the following core components:
- The independent C++ CanOpen driver library
- The ROS abstraction layer for it
- 3D model and kinematics description for visualization and planning
These main components are distributed under a LGPL license.
Furthermore this package contains a build system that is not
part of the CanOpen Driver but which is needed to build it:
- icmaker (BSD License)
and depends on two other packages:
-fzi_icl_core containing the icl_core (LGPL License)
-fzi_icl_can containing the icl_can (LGPL License)
These components were independently developed at the
FZI Research Center for Information Technology in Karlsruhe, Germany.
Please refer to the wiki page for installation and usage.
See license folder for the license texts.
CHANGELOG
Could not convert RST to MD: No such file or directory - pandoc
Wiki Tutorials
See ROS Wiki Tutorials for more details.
Source Tutorials
Not currently indexed.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/standalone_profile_position.launch
- File description This launchfile shows the simplest usage of the driver. In this mode, single joint configurations can be commanded very simply with an action interface. This might be useful, if you only want to command a single configuration or calibrate the nodes' zero position. For executing more complex trajectories we suggest the use of the interpolated position mode which uses ros_control.
-
- pcan_device [default: auto]
- launch/move_to_home_position.launch
- File description Purpose of this launch file is to give an easy "reset" functionality. The launch file will start a node that resets the arm to ZERO position (completely streched out) and then terminates
-
- debug [default: false]
- frequency [default: 30]
- pcan_device [default: auto]
- launch/ros_control.launch
- File description For executing more complex trajectories the interpolated position mode with ros_control offers a very powerful, yet effective command interface. It offers a FollowJointTrajectory interface as well as multiple services for handling the robot.
-
- trajectory_controller_name
- launch/standalone_interpolated_position.launch
- File description This is intended to launch the robot driver together with a ros_controller and a URDF model
-
- pcan_device [default: auto]
- trajectory_controller_name [default: pos_based_pos_traj_controller_arm]
- launch/visualize_arm_test.launch
- launch/driver.launch
- File description Brings up the main driver node. This file is meant to be used as include (see the standalone files for that) In case ROS-Control is used the corresponding actions have to be taken in a seperate file (see standalone_interpolated_position.launch)
-
- debug [default: false]
- frequency [default: 30]
- pcan_device [default: auto]
- with_ros_control [default: true]
- do_autostart [default: true]
- trajectory_controller_name [default: pos_based_pos_traj_controller]
Messages
No message files found.
Plugins
No plugins found.
Recent questions tagged schunk_canopen_driver at answers.ros.org
|
|
schunk_canopen_driver package from schunk_canopen_driver reposchunk_canopen_driver |
Package Summary
| Tags | No category tags. |
| Version | 1.0.7 |
| License | FZI all rights reserved |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/fzi-forschungszentrum-informatik/schunk_canopen_driver.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2017-11-02 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
Package Description
The schunk_canopen_driver package
Additional Links
No additional links.
Maintainers
- Georg Heppner
Authors
- Felix Mauch
- Georg Heppner
This is the driver package for the SCHUNK LWA4P and other CanOpen enabled devices.
It was developed on behalf of SCHUNK GmbH, Lauffen/Neckar, Germany
at the FZI Research Center for Information Technology in Karlsruhe, Germany.
The package contains the following core components:
- The independent C++ CanOpen driver library
- The ROS abstraction layer for it
- 3D model and kinematics description for visualization and planning
These main components are distributed under a LGPL license.
Furthermore this package contains a build system that is not
part of the CanOpen Driver but which is needed to build it:
- icmaker (BSD License)
and depends on two other packages:
-fzi_icl_core containing the icl_core (LGPL License)
-fzi_icl_can containing the icl_can (LGPL License)
These components were independently developed at the
FZI Research Center for Information Technology in Karlsruhe, Germany.
Please refer to the wiki page for installation and usage.
See license folder for the license texts.
CHANGELOG
Could not convert RST to MD: No such file or directory - pandoc
Wiki Tutorials
See ROS Wiki Tutorials for more details.
Source Tutorials
Not currently indexed.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/standalone_profile_position.launch
- File description This launchfile shows the simplest usage of the driver. In this mode, single joint configurations can be commanded very simply with an action interface. This might be useful, if you only want to command a single configuration or calibrate the nodes' zero position. For executing more complex trajectories we suggest the use of the interpolated position mode which uses ros_control.
-
- pcan_device [default: auto]
- launch/move_to_home_position.launch
- File description Purpose of this launch file is to give an easy "reset" functionality. The launch file will start a node that resets the arm to ZERO position (completely streched out) and then terminates
-
- debug [default: false]
- frequency [default: 30]
- pcan_device [default: auto]
- launch/ros_control.launch
- File description For executing more complex trajectories the interpolated position mode with ros_control offers a very powerful, yet effective command interface. It offers a FollowJointTrajectory interface as well as multiple services for handling the robot.
-
- trajectory_controller_name
- launch/standalone_interpolated_position.launch
- File description This is intended to launch the robot driver together with a ros_controller and a URDF model
-
- pcan_device [default: auto]
- trajectory_controller_name [default: pos_based_pos_traj_controller_arm]
- launch/visualize_arm_test.launch
- launch/driver.launch
- File description Brings up the main driver node. This file is meant to be used as include (see the standalone files for that) In case ROS-Control is used the corresponding actions have to be taken in a seperate file (see standalone_interpolated_position.launch)
-
- debug [default: false]
- frequency [default: 30]
- pcan_device [default: auto]
- with_ros_control [default: true]
- do_autostart [default: true]
- trajectory_controller_name [default: pos_based_pos_traj_controller]
Messages
No message files found.
Plugins
No plugins found.
Recent questions tagged schunk_canopen_driver at answers.ros.org
No version for distro ardent. Known supported distros are highlighted in the buttons above.
|
|
schunk_canopen_driver package from schunk_canopen_driver reposchunk_canopen_driver |
Package Summary
| Tags | No category tags. |
| Version | 1.0.7 |
| License | FZI all rights reserved |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/fzi-forschungszentrum-informatik/schunk_canopen_driver.git |
| VCS Type | git |
| VCS Version | master |
| Last Updated | 2017-11-02 |
| Dev Status | MAINTAINED |
| Released | RELEASED |
Package Description
The schunk_canopen_driver package
Additional Links
No additional links.
Maintainers
- Georg Heppner
Authors
- Felix Mauch
- Georg Heppner
This is the driver package for the SCHUNK LWA4P and other CanOpen enabled devices.
It was developed on behalf of SCHUNK GmbH, Lauffen/Neckar, Germany
at the FZI Research Center for Information Technology in Karlsruhe, Germany.
The package contains the following core components:
- The independent C++ CanOpen driver library
- The ROS abstraction layer for it
- 3D model and kinematics description for visualization and planning
These main components are distributed under a LGPL license.
Furthermore this package contains a build system that is not
part of the CanOpen Driver but which is needed to build it:
- icmaker (BSD License)
and depends on two other packages:
-fzi_icl_core containing the icl_core (LGPL License)
-fzi_icl_can containing the icl_can (LGPL License)
These components were independently developed at the
FZI Research Center for Information Technology in Karlsruhe, Germany.
Please refer to the wiki page for installation and usage.
See license folder for the license texts.
CHANGELOG
Could not convert RST to MD: No such file or directory - pandoc
Wiki Tutorials
See ROS Wiki Tutorials for more details.
Source Tutorials
Not currently indexed.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
- launch/standalone_profile_position.launch
- File description This launchfile shows the simplest usage of the driver. In this mode, single joint configurations can be commanded very simply with an action interface. This might be useful, if you only want to command a single configuration or calibrate the nodes' zero position. For executing more complex trajectories we suggest the use of the interpolated position mode which uses ros_control.
-
- pcan_device [default: auto]
- launch/move_to_home_position.launch
- File description Purpose of this launch file is to give an easy "reset" functionality. The launch file will start a node that resets the arm to ZERO position (completely streched out) and then terminates
-
- debug [default: false]
- frequency [default: 30]
- pcan_device [default: auto]
- launch/ros_control.launch
- File description For executing more complex trajectories the interpolated position mode with ros_control offers a very powerful, yet effective command interface. It offers a FollowJointTrajectory interface as well as multiple services for handling the robot.
-
- trajectory_controller_name
- launch/standalone_interpolated_position.launch
- File description This is intended to launch the robot driver together with a ros_controller and a URDF model
-
- pcan_device [default: auto]
- trajectory_controller_name [default: pos_based_pos_traj_controller_arm]
- launch/visualize_arm_test.launch
- launch/driver.launch
- File description Brings up the main driver node. This file is meant to be used as include (see the standalone files for that) In case ROS-Control is used the corresponding actions have to be taken in a seperate file (see standalone_interpolated_position.launch)
-
- debug [default: false]
- frequency [default: 30]
- pcan_device [default: auto]
- with_ros_control [default: true]
- do_autostart [default: true]
- trajectory_controller_name [default: pos_based_pos_traj_controller]
Messages
No message files found.
Plugins
No plugins found.
Recent questions tagged schunk_canopen_driver at answers.ros.org
No version for distro hydro. Known supported distros are highlighted in the buttons above.