Lennart Nachtigall

Sorry for that. But for someone who is not really involved in the ros2control development adding something, especially adding test looks rather difficult/ time consuming at the moment, as there...

@saikishor Thanks a lot!

@saikishor Thanks a lot. Just for my understanding: If a controller fails activation now, a command mode switch is issued so that the hardware interface can release internally locked hardware?...

@saikishor I just tested your PR and for me it didn't work so far. It could be that I did something wrong. What I did was: 1. Clone your repository...

So I removed the installed packages: `sudo dpkg --force-all --remove ros-iron-controller-interface ros-iron-controller-manager ros-iron-hardware-interface` just to make sure the ones from the workspace are used. Log while failing activation: `[ros2_control_node-14] [ERROR]...

@saikishor I made a mistake while rebasing onto iron. When I do it properly I run into a lots of conflicts. When I try to resolve them it doesn't compile...

@saikishor Thanks. Cherry-picking worked :) When I now have the controller failing I run into an endless loop of ros2control trying to activating the controller - failing - stopping the...

@saikishor shouldn't be the issue of running into an endless loop of activation -> failing... be addressed first?

@saikishor > EDIT: How many times does it print the ....Releasing Interfaces! error? As I am seeing the activation failure message again and again (of the controller) I would say...

@saikishor I just tested in a clean dockerized environment instead of my host installation and it seems to work fine. I will review and approve the PR then.