You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the franka_bringup package has launch files which load a static controllers.yaml file, which has all of the *_example_controller controllers. I think it would be helpful to have a parameter that defaults to the controllers.yaml file in the franka_bringup package. This way, users could benefit from using franka_bringup, while still loading their own controllers.
If this capability isn't added, I think users have to execute ros2 param set commands as shell processes, either in launch files or manually in a terminal.
@BarisYazici do you agree that a controller_manager_parameters parameter, which defaults to controllers.yaml, is acceptable? If so, I can submit a PR with this change.
The text was updated successfully, but these errors were encountered:
…ainer-libfranka-build-release to humble
* commit 'be436d8422f4c0b1c0615ad4f650978f92364530':
remove pytest
add launch testing to the dockerfile
add hardware-interface-testing package to Dockerfile
fix: devcontainer libfranka build type release
Right now, the
franka_bringup
package has launch files which load a staticcontrollers.yaml
file, which has all of the*_example_controller
controllers. I think it would be helpful to have a parameter that defaults to thecontrollers.yaml
file in thefranka_bringup
package. This way, users could benefit from usingfranka_bringup
, while still loading their own controllers.If this capability isn't added, I think users have to execute
ros2 param set
commands as shell processes, either in launch files or manually in a terminal.@BarisYazici do you agree that a
controller_manager_parameters
parameter, which defaults tocontrollers.yaml
, is acceptable? If so, I can submit a PR with this change.The text was updated successfully, but these errors were encountered: