Carlos J. Rosales

Hi, many thanks for your support. Ok, between 3 & 4, I would definitely go for the 4... even if we don't finally get access ;) > I think the...

Oh, btw, I just checked on the newest github member management and now one can add external collaborators to an organization. So, even if I would be glad to, I...

My two-cents from a long-time-user point of view.... and facing new-comers having issues with naming conventions in ros-controls..... Since the proposed controllers send torque to the `hardware_interface::EffortJointInterface`, their namespace should...

That looks good, we are mostly using that way (without the debugging part) in our hardware, all namespaced. One question, in line 70 of the hardware interface you have getParam('joints')....

Thanks, I believe it is very useful to have an example like this. I usually ask before creating a PR, so one comment related to my previous comment: Is there...

> because often times there will be multiple hardware interfaces for different parts of the robot. That's is my use case right now, that's why I'm concerned. [Here it is](https://github.com/CentroEPiaggio/vito_robot)....

Hi again, and sorry if I bother here with a long post, I just want to give you an opinion form an user's point of view. #### Context I understand...

Hey @TheDash , how are you doing with the simulation? Could you point out the repos you say above? I'm starting to work on the new 2F models, and I'd...

@athackst Yes, I'm looking at it to develop it for the 2F models, since unfortunately, it can't be used for these, I believe. So that's what I am onto now....

Hi all... and it is still open. We are starting our migration to `foxy` this year, and we need `namespaces` in a multi-robot scenario as well. We have detected three...