ROS IndexNo version for distro humble showing indigo. Known supported distros are highlighted in the buttons above.
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro jazzy showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro kilted showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro rolling showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro ardent showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro bouncy showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro crystal showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro eloquent showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro dashing showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro galactic showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro foxy showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro iron showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro lunar showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro jade showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | hydro-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
| Name | Deps |
|---|---|
| reemc_bringup |
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.15 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | kinetic-devel |
| Last Updated | 2023-05-29 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.15 (2023-05-29)
- Merge branch 'fix_invalid_initial_state' into 'erbium-devel' check for a valid initial state of the trajectory before executing the motion See merge request app-tools/play_motion!13
- added tests for invalid case
- check for a valid initial state of the trajectory before executing the motion
- Contributors: Jordan Palacios, Sai Kishor Kothakota
0.4.14 (2023-04-24)
- Merge branch 'fix_time_offset_for_multi_waypoints' into 'erbium-devel' fix the trajectory ofsetting that delays the trajectory See merge request app-tools/play_motion!12
- fix the trajectory ofsetting that delays the trajectory
- Contributors: Sai Kishor Kothakota
0.4.13 (2023-04-21)
0.4.12 (2023-04-21)
- Merge branch 'scale_approach_trajectory' into 'erbium-devel' Scale the approach trajectory to the given time, when the approach trajectory... See merge request app-tools/play_motion!11
- Scale the approach trajectory to the given time, when the approach trajectory is faster than expected
- Contributors: Jordan Palacios, Sai Kishor Kothakota
0.4.11 (2023-02-13)
- Update tests
- clean merge request
- update code style
- cleaned code
- updated move_joint_test.py
- removed printf statements
- remove redundant launch in move_joint.test
- Add tests
- Contributors: David ter Kuile
0.4.10 (2021-09-17)
- Fix test race condition
- Contributors: Victor Lopez
0.4.9 (2021-08-26)
- Merge branch 'gallium-fixes' into 'erbium-devel' Fix tests for gallium See merge request app-tools/play_motion!7
- Use robot_state_publisher instead of deprecated state_publisher
- Use xacro instead of deprecated xacro.py
- Merge branch 'revert_wait_for_server' into 'erbium-devel' Revert "Added waitForServer to the joint trajectory controller action client" Reverted because the waitForServer always fails since the Action Clients have no dedicated thread. This can cause that sending a goal right after controllers are changed or read for the first time, the goal will abort. See merge request app-tools/play_motion!8
- Revert "Added waitForServer to the joint trajectory controller action client" This reverts commit 24bff740e6e79723aedd618428cfda2daf0e58a5.
- Merge branch 'move_joint_wait_for_server' into 'erbium-devel' Added waitForServer to the joint trajectory controller action client See merge request app-tools/play_motion!6
- Added waitForServer to the joint trajectory controller action client
- Contributors: Jordan Palacios, Sai Kishor Kothakota, saikishor, victor
0.4.8 (2019-09-09)
- Fixes for shadowed variables
- Contributors: Jordan Palacios
0.4.7 (2019-05-22)
- Merge branch 'melodic_fixes' into 'erbium-devel' changes for melodic deprecated MoveGroup (was renamed to MoveGroupInterface) See merge request app-tools/play_motion!5
- changes for melodic deprecated MoveGroup (was renamed to MoveGroupInterface)
- Contributors: Sai Kishor Kothakota, Victor Lopez
0.4.6 (2018-09-28)
- Merge branch 'use-weak-ref' into 'erbium-devel' Fix error when changing controllers during a motion See merge request app-tools/play_motion!4
- Fix error when changing controllers during a motion
- Contributors: Victor Lopez
0.4.5 (2018-01-11)
- fixed merge
- 0.4.4
- updated changelog
- added missing joint trajectory controller for test
- added missing position_controllers test
- added missing xacro test depend
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
| Name | Deps |
|---|---|
| talos_bringup |
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.15 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | kinetic-devel |
| Last Updated | 2023-05-29 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.15 (2023-05-29)
- Merge branch 'fix_invalid_initial_state' into 'erbium-devel' check for a valid initial state of the trajectory before executing the motion See merge request app-tools/play_motion!13
- added tests for invalid case
- check for a valid initial state of the trajectory before executing the motion
- Contributors: Jordan Palacios, Sai Kishor Kothakota
0.4.14 (2023-04-24)
- Merge branch 'fix_time_offset_for_multi_waypoints' into 'erbium-devel' fix the trajectory ofsetting that delays the trajectory See merge request app-tools/play_motion!12
- fix the trajectory ofsetting that delays the trajectory
- Contributors: Sai Kishor Kothakota
0.4.13 (2023-04-21)
0.4.12 (2023-04-21)
- Merge branch 'scale_approach_trajectory' into 'erbium-devel' Scale the approach trajectory to the given time, when the approach trajectory... See merge request app-tools/play_motion!11
- Scale the approach trajectory to the given time, when the approach trajectory is faster than expected
- Contributors: Jordan Palacios, Sai Kishor Kothakota
0.4.11 (2023-02-13)
- Update tests
- clean merge request
- update code style
- cleaned code
- updated move_joint_test.py
- removed printf statements
- remove redundant launch in move_joint.test
- Add tests
- Contributors: David ter Kuile
0.4.10 (2021-09-17)
- Fix test race condition
- Contributors: Victor Lopez
0.4.9 (2021-08-26)
- Merge branch 'gallium-fixes' into 'erbium-devel' Fix tests for gallium See merge request app-tools/play_motion!7
- Use robot_state_publisher instead of deprecated state_publisher
- Use xacro instead of deprecated xacro.py
- Merge branch 'revert_wait_for_server' into 'erbium-devel' Revert "Added waitForServer to the joint trajectory controller action client" Reverted because the waitForServer always fails since the Action Clients have no dedicated thread. This can cause that sending a goal right after controllers are changed or read for the first time, the goal will abort. See merge request app-tools/play_motion!8
- Revert "Added waitForServer to the joint trajectory controller action client" This reverts commit 24bff740e6e79723aedd618428cfda2daf0e58a5.
- Merge branch 'move_joint_wait_for_server' into 'erbium-devel' Added waitForServer to the joint trajectory controller action client See merge request app-tools/play_motion!6
- Added waitForServer to the joint trajectory controller action client
- Contributors: Jordan Palacios, Sai Kishor Kothakota, saikishor, victor
0.4.8 (2019-09-09)
- Fixes for shadowed variables
- Contributors: Jordan Palacios
0.4.7 (2019-05-22)
- Merge branch 'melodic_fixes' into 'erbium-devel' changes for melodic deprecated MoveGroup (was renamed to MoveGroupInterface) See merge request app-tools/play_motion!5
- changes for melodic deprecated MoveGroup (was renamed to MoveGroupInterface)
- Contributors: Sai Kishor Kothakota, Victor Lopez
0.4.6 (2018-09-28)
- Merge branch 'use-weak-ref' into 'erbium-devel' Fix error when changing controllers during a motion See merge request app-tools/play_motion!4
- Fix error when changing controllers during a motion
- Contributors: Victor Lopez
0.4.5 (2018-01-11)
- fixed merge
- 0.4.4
- updated changelog
- added missing joint trajectory controller for test
- added missing position_controllers test
- added missing xacro test depend
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
| Name | Deps |
|---|---|
| talos_bringup |
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.
Recent questions tagged play_motion at Robotics Stack Exchange
No version for distro noetic showing indigo. Known supported distros are highlighted in the buttons above.
|
|
play_motion package from play_motion repoplay_motion play_motion_msgs |
ROS Distro
|
Package Summary
| Tags | No category tags. |
| Version | 0.4.4 |
| License | BSD |
| Build type | CATKIN |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/pal-robotics/play_motion.git |
| VCS Type | git |
| VCS Version | indigo-devel |
| Last Updated | 2017-11-23 |
| Dev Status | DEVELOPED |
| CI status | Continuous Integration |
| Released | RELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Plays a pre-recorded motion on a robot
Additional Links
No additional links.
Maintainers
- Victor Lopez
Authors
- Paul Mathieu
- Adolfo Rodriguez Tsouroukdissian
play_motion
This tool is used to play pre-recorded motions on ros_control compliant robots via a simple actionlib interface.
Any robot that implements control via joint_trajectory_controller can be put into motion with play_motion.
Starting from version 0.4, play_motion will by default compute a collision-free trajectory between the robot’s
current state and the first motion waypoint. This requires your robot to have a running
moveit setup, and to configure play_motion to use it. If you’re not interested in the
motion planning capability, it’s possible to disable it altogether. Refer to the config/ folder
for configuration examples.
How-to
- Prepare one (or more!) motion. They need to be loaded as rosparams. You will find samples in the
config/folder.
rosparam load config/your_motion_file.yaml
- Launch play_motion (without motion planning capabilities, for simplicity)
rosparam set /play_motion/disable_motion_planning true
rosrun play_motion play_motion
- Fire an actionlib client that publishes on /play_motion action server, enter the name of your motion on the
motion_namefield and setskip_planning=trueto not use motion planning.
That’s it!
CHANGELOG
Changelog for package play_motion
0.4.4 (2017-11-23)
- add command line run_motion executables
- Contributors: Jordi Pages
0.4.3 (2016-03-30)
- Add play_motion continuous test
- Migrate package to format 2, catkin lint fixes
- Contributors: Victor Lopez
0.4.2 (2015-11-17)
- Fix crash when malformed motion was requested
- Contributors: Sammy Pfeiffer
0.4.1 (2014-11-21)
- Update package maintainer/authors
- Add missing configuration for depender projects
- Refactor argument names to convention
- Add function alternatives where NodeHandle defaults to one of play_motion
- log error when error code is 0
- Add default values and units to sample config.
- Add new parameter to configure the minimum approach time to use when skip_planning = true.
- Contributors: Adolfo Rodriguez Tsouroukdissian, Bence Magyar, Daniel Pinyol, Víctor López
0.4.0 (2014-04-23)
- Add install() rule for headers
- Fetch time_from_start as a double. (#28)
- MoveIt! integration (#36)
- Allow to disable motion planning altogether.
- Silence compiler warnings.
- Add move_joint script (#33)
- Don't compute approach time if specified.
- Handle first waypoints with time_from_start == 0.
- Add service call to query available motions.
- Isolate move_group async spinner from rest of node (#31)
- Make planning optional. Deprecate reach_time.
- First prototype of motion planning support.
- Refactor how controllers are checked.
- Allow cast from int to double in xmlrpc helpers (#28)
- Contributors: Adolfo Rodriguez Tsouroukdissian, Paul Mathieu
0.3.7 (2014-11-07)
- Barium release
0.3.6 (2014-04-07)
0.3.5 (2014-02-25)
- Harmonize doxygen tags
- Fix crash with empty motion names (#20).
- Minor doc fix.
0.3.4 (2014-02-24)
- catch and show unexpected exceptions in main()
- Refactor populateVelocities. Document it.
- Propagate controller action state to internal API Fixes #15
- Refactor some stuff in play_motion.cpp
- Refactor and document MoveJointGroup
- Replace test_depend with build_depend
- Use existing msg types for traj points. Refs
#4.
- Move from the custom structs to trajectory_msgs types.
- Waypoints can now have accelerations.
0.3.3 (2014-02-20)
- Fix dependencies (add sensor_msgs)
- Add install target for play_motion_helpers lib
- take messages out into new package play_motion_msgs
0.3.2 (2014-02-05)
- Refactor and add a datatypes.h
- Remove unneeded import
- Fix bug: calling the motion callback more than once
0.3.1 (2013-12-04)
- Populate velocity data
- Velocities are populated only for motions that don't specify velocities for at least one waypoint.
- Good compromise: Smoother than Fritsch-Butland, while still
File truncated at 100 lines see the full file
Wiki Tutorials
This package does not provide any links to tutorials in it's rosindex metadata.
You can check on the ROS Wiki Tutorials page for the package.
Package Dependencies
System Dependencies
No direct system dependencies.
Dependant Packages
No known dependants.
Launch files
No launch files found
Messages
No message files found.
Services
No service files found
Plugins
No plugins found.