-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
A way to set a ROS namespace in the Agent #126
Comments
The name handling of the micro-ROS nodes is completely handled on the client-side. In fact, the micro-ROS agent does not do any modification on any property of the entities created by the client. I'll take a look at that. It would be important in your use case that the client knows in which namespace it is being exposed or it is ok if the agent just overrides the client name prepending a namespace? |
ping @bjsowa |
It's not important that the client knows in which namespace it is running. As long as all names are mapped correctly on the agent side it's ok for me. |
Amy update on this? |
@pablogs9 Any plan on continuing the PoC? The current implementation doesn't seem to work. Also, do you think it would be possible to implement Domain ID remapping? This is even more important for me than namespace remapping. |
No bandwidth to work on this right now. I'll keep this open for the future. If you make some advances do not hesitate to PR your progress. |
I would also like to set up the ROS namespace in the agent instead of in the microcontroller. Has a possible solution been found for this yet? #145 has also not been resolved so far. |
This is not working for me.
I also tried:
and, nothing, the topics comming from my board are located under / namespace. |
I was wondering is there were any news on this. On top of what is mentioned above, I also tried to remap topic to include a namespace, using SetRemap in an ActionGroup or the remapping option in the Node itself, to no avail. |
I would like to have the ability to set an arbitrary ROS namespace of the node from the computer running the Agent. The way of doing this in ROSSerial is to just run the
serial_node
under a namespace. In micro-ROS it's a little more problematic because the namespace has to be passed torclc_node_init_default
function, so it has to be retrieved before the ROS communication is initialized.The way I see it could work is when the Agent could be run with some parameters and the client had functions to retrieve these parameters. Then, I could just define the
namespace
parameter and retrieve it in the firmware before initializing the node.The text was updated successfully, but these errors were encountered: