Conversation
Signed-off-by: ahcorde <ahcorde@gmail.com>
|
@ahcorde @destogl It seems after looking around in the code that adding the namespace while creating the controller_manager is not enough. This should maybe be done also for the ignition_ros_control node And also for since this will initialize our context inside the namespace and then whenever we try to create a new controller_manage it will do it inside the same context and thus the same namespace. Testing this seems to work and will give us separated controller_manager instances in different namespaces but when we try to spawn our controllers they will be without namespace. |
destogl
left a comment
There was a problem hiding this comment.
Can you also please remove other obsolete CM namespace parameter and address comment above?
|
Hi @ahcorde, I don't know if you had time to look at my last comment. Having tested those changes locally seemed to fix the namespacing for the create3 with multiple instances of the robot in the same simulation. We had however to prefix our controllers in the config files and our controller nodes appear like this : And in the case of no namespacing it seemed to be working fine so i suppose these changes should not cause problems for normal applications that do not involve namespacing. Tell me if i should put this in a separate PR. |
Signed-off-by: ahcorde ahcorde@gmail.com
Minor fix to allow CM to be run in the defined namespace, ref ros-controls/gazebo_ros2_control#122
Related PR ros-controls/gazebo_ros2_control#147