|
Package Summary
Tags | No category tags. |
Version | 2.15.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-controls/ros2_controllers.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2022-12-13 |
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
Additional Links
Maintainers
- Bence Magyar
- Jordan Palacios
- Karsten Knese
Authors
joint_trajectory_controllers package
The package implements controllers to interpolate joint's trajectory.
For detailed documentation check the docs
folder or ros2_control documentation.
Changelog for package joint_trajectory_controller
2.15.0 (2022-12-06)
2.14.0 (2022-11-18)
- Fix parameter library export (#448)
- Contributors: Tyler Weaver
2.13.0 (2022-10-05)
- Generate Parameter Library for Joint Trajectory Controller (#384)
- Fix rates in JTC userdoc.rst (#433)
Fix for high CPU usage by JTC in gzserver (#428) * Change type cast wall timer period from second to nanoseconds. create_wall_timer() expects delay in nanoseconds (duration object) however the type cast to seconds will result in 0 (if duration is less than 1s) and thus causing timer to be fired non stop resulting in very high CPU usage. * Reset smartpointer so that create_wall_timer() call can destroy previous trajectory timer. node->create_wall_timer() first removes timers associated with expired smartpointers before servicing current request. The JTC timer pointer gets overwrite only after the create_wall_timer() returns and thus not able to remove previous trajectory timer resulting in upto two timers running for JTC during trajectory execution. Althougth the previous timer does nothing but still get fired.
Contributors: Arshad Mehmood, Borong Yuan, Tyler Weaver, Andy Zelenak, Bence Magyar, Denis
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged joint_trajectory_controller at answers.ros.org
|
Package Summary
Tags | No category tags. |
Version | 0.8.2 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-controls/ros2_controllers.git |
VCS Type | git |
VCS Version | foxy |
Last Updated | 2022-09-22 |
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
Additional Links
Maintainers
- Bence Magyar
- Jordan Palacios
- Karsten Knese
Authors
joint_trajectory_controllers package
The package implements controllers to interpolate joint's trajectory.
For detailed documentation check the docs
folder or ros2_control documentation.
Changelog for package joint_trajectory_controller
0.8.2 (2022-09-22)
[backport] Fix for high CPU usage by JTC in gzserver (#428) (#436) * Change type cast wall timer period from second to nanoseconds. create_wall_timer() expects delay in nanoseconds (duration object) however the type cast to seconds will result in 0 (if duration is less than 1s) and thus causing timer to be fired non stop resulting in very high CPU usage. * Reset smartpointer so that create_wall_timer() call can destroy previous trajectory timer. node->create_wall_timer() first removes timers associated with expired smartpointers before servicing current request. The JTC timer pointer gets overwrite only after the create_wall_timer() returns and thus not able to remove previous trajectory timer resulting in upto two timers running for JTC during trajectory execution. Althougth the previous timer does nothing but still get fired.
Contributors: Arshad Mehmood
0.8.1 (2022-08-03)
0.8.0 (2022-05-31)
0.7.0 (2022-01-24)
0.6.0 (2022-01-11)
0.5.1 (2021-10-25)
0.5.0 (2021-08-30)
- Add auto declaration of parameters. (#224)
- Bring precommit config up to speed with ros2_control (#227)
- Add initial pre-commit setup. (#220)
- Enable JTC for hardware having offset from state measurements
(#189)
- Avoid \"jumps\" with states that have tracking error. All test are passing but separatelly. Is there some kind of timeout?
- Remove allow_integration_flag
- Add reading from command interfaces when restarting controller
- Reduce docs warnings and correct adding guidelines (#219)
- Contributors: Bence Magyar, Denis
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged joint_trajectory_controller at answers.ros.org
|
Package Summary
Tags | No category tags. |
Version | 2.15.0 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-controls/ros2_controllers.git |
VCS Type | git |
VCS Version | master |
Last Updated | 2022-12-13 |
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
Additional Links
Maintainers
- Bence Magyar
- Jordan Palacios
- Karsten Knese
Authors
joint_trajectory_controllers package
The package implements controllers to interpolate joint's trajectory.
For detailed documentation check the docs
folder or ros2_control documentation.
Changelog for package joint_trajectory_controller
2.15.0 (2022-12-06)
2.14.0 (2022-11-18)
- Fix parameter library export (#448)
- Contributors: Tyler Weaver
2.13.0 (2022-10-05)
- Generate Parameter Library for Joint Trajectory Controller (#384)
- Fix rates in JTC userdoc.rst (#433)
Fix for high CPU usage by JTC in gzserver (#428) * Change type cast wall timer period from second to nanoseconds. create_wall_timer() expects delay in nanoseconds (duration object) however the type cast to seconds will result in 0 (if duration is less than 1s) and thus causing timer to be fired non stop resulting in very high CPU usage. * Reset smartpointer so that create_wall_timer() call can destroy previous trajectory timer. node->create_wall_timer() first removes timers associated with expired smartpointers before servicing current request. The JTC timer pointer gets overwrite only after the create_wall_timer() returns and thus not able to remove previous trajectory timer resulting in upto two timers running for JTC during trajectory execution. Althougth the previous timer does nothing but still get fired.
Contributors: Arshad Mehmood, Borong Yuan, Tyler Weaver, Andy Zelenak, Bence Magyar, Denis
Wiki Tutorials
Source Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged joint_trajectory_controller at answers.ros.org
|
Package Summary
Tags | No category tags. |
Version | 1.5.1 |
License | Apache License 2.0 |
Build type | AMENT_CMAKE |
Use | RECOMMENDED |
Repository Summary
Checkout URI | https://github.com/ros-controls/ros2_controllers.git |
VCS Type | git |
VCS Version | galactic |
Last Updated | 2022-09-23 |
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
Additional Links
Maintainers
- Bence Magyar
- Jordan Palacios
- Karsten Knese
Authors
joint_trajectory_controllers package
The package implements controllers to interpolate joint's trajectory.
For detailed documentation check the docs
folder or ros2_control documentation.
Changelog for package joint_trajectory_controller
1.5.1 (2022-09-23)
[backport] Fix for high CPU usage by JTC in gzserver (#428) (#437) * Change type cast wall timer period from second to nanoseconds. create_wall_timer() expects delay in nanoseconds (duration object) however the type cast to seconds will result in 0 (if duration is less than 1s) and thus causing timer to be fired non stop resulting in very high CPU usage. * Reset smartpointer so that create_wall_timer() call can destroy previous trajectory timer. node->create_wall_timer() first removes timers associated with expired smartpointers before servicing current request. The JTC timer pointer gets overwrite only after the create_wall_timer() returns and thus not able to remove previous trajectory timer resulting in upto two timers running for JTC during trajectory execution. Althougth the previous timer does nothing but still get fired.
Contributors: Arshad Mehmood
1.5.0 (2022-08-03)
1.4.0 (2022-02-23)
1.3.0 (2022-01-11)
1.2.0 (2021-12-29)
1.1.0 (2021-10-25)
- Move interface sorting into ControllerInterface (#259)
- Revise for-loop style (#254)
- Contributors: bailaC