Skip to content
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

have the same node #1

Open
885288421 opened this issue Apr 8, 2022 · 1 comment
Open

have the same node #1

885288421 opened this issue Apr 8, 2022 · 1 comment

Comments

@885288421
Copy link

I have run:
ros2 launch rf2o_laser_odometry rf2o_laser_odometry.launch.py
[INFO] [launch]: All log files can be found below /home/agilex/.ros/log/2022-04-08-20-32-56-562713-agilex-15929
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [rf2o_laser_odometry_node-1]: process started with pid [15931]
[rf2o_laser_odometry_node-1] [WARN] [1649421176.752449874] [rcl.logging_rosout]: Publisher already registered for provided node name. If this is due to multiple nodes with the same name then all logs for that logger name will go out over the existing publisher. As soon as any node with that name is destructed it will unregister the publisher, preventing any further logs for that name from being published on the rosout topic.
[rf2o_laser_odometry_node-1] [INFO] [1649421176.753410054] [rf2o_laser_odometry]: Initializing RF2O node...

in another ros2 node list
WARNING: Be aware that are nodes in the graph that share an exact name, this can have unintended side effects.
/rf2o_laser_odometry
/rf2o_laser_odometry
/transform_listener_impl_559e9c2c7520

@tugbakara
Copy link

Have the same issue, did you solve?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants