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
[ros2_control_node-7] [ERROR] [controller_manager]: Can't activate controller 'omnidirectional_controller': State interface with key 'joint_name/velocity' does not exist
#8
Closed
robotcopper opened this issue
Mar 31, 2024
· 3 comments
I am trying to use your controller in addition of the topic_based_ros2_control hardware interface.
The thing is that on my real robot i do not need of state interface. Indeed I am controlling my robot in open loop. So as you can expect, i set the open_loop param to True and as i saw it in the omnidirectional_controller.cpp it indeed unset the use of the state estimation tool.
However, in the omnidirectional_controller.cpp the controller keep looking for a state_interface even if the open_loop is True.
Or we could expect that only command would be send in open_loop, so in other words, just needing command_interface in the hardware_interface and not also a state_interface am i right?
So is it a bug? Did I miss something?
Here is what i expect to implement as hardware_interface:
PS: Thank you again for this very useful work you have made
The text was updated successfully, but these errors were encountered:
Hello @mateusmenezes95 ,
I am trying to use your controller in addition of the topic_based_ros2_control hardware interface.
The thing is that on my real robot i do not need of state interface. Indeed I am controlling my robot in open loop. So as you can expect, i set the
open_loop
param toTrue
and as i saw it in theomnidirectional_controller.cpp
it indeed unset the use of the state estimation tool.However, in the
omnidirectional_controller.cpp
the controller keep looking for astate_interface
even if theopen_loop
isTrue
.Or we could expect that only command would be send in
open_loop
, so in other words, just needingcommand_interface
in thehardware_interface
and not also astate_interface
am i right?So is it a bug? Did I miss something?
Here is what i expect to implement as
hardware_interface
:PS: Thank you again for this very useful work you have made
The text was updated successfully, but these errors were encountered: