-
Notifications
You must be signed in to change notification settings - Fork 221
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
Add support for ROS2 humble #47
base: ros1-master
Are you sure you want to change the base?
Conversation
it should be merged into a |
@nakai-omer I had to change Line 219 of laserscan_multi_merger.cpp otherwise the range was limited. See here. Just wondering if you have the same issue? |
@ryanpennings Thanks for the feedback. In our implementation we use the |
I had the same limited range issue as @ryanpennings and the fix worked. Also, I had to set QoS for the publisher to be reliable in order for the merged scan to show up in rviz2. |
@samiamlabs Can you please check what is the max_range param from your laser scan message, and whether is matches your configured range_max in this package? I will merge this line fix if needed. |
I have already checked that. I could not find a |
@samiamlabs Thanks for the update. I have added @ryanpennings fix to this PR. |
Hi maintainers and author @nakai-omer |
@vineet131 From my point of view, it can be merged, it is working for us with ROS2 Humble. |
Thank you! So maintainers @axelfurlan and @trigal can we have this PR merged? Edit: Asking again including @iralab |
Hello authors @JackFrost67 @axelfurlan @trigal @iralab Once again I wanted to ask if this PR can be accepted so that ROS2 upstream support for this repo can be obtained. It would be of help to us. Thank you. |
Hello mantainers @JackFrost67 @axelfurlan @iralab any update about the possibility to merge the PR, for us it is working well in ROS Humble! |
Hi,
We have ported this lib to ROS2 humble, could probably work on older ROS2 versions as well, just the static transform arguments have changed in humble.
We tried to make only small changes, without major refactoring, in order to be able to easily migrate fixes from current implementation to this branch.