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
Remapping topics in gazebo nodes #486
Comments
I've experienced the same issue, and I've not found a way around it yet. Anyone track down the change that causes this failure? |
Umm interesting. Have you tried to do the same with any other node different that Gazebo? Is that working? |
Yes, strangely enough if I spool up many different nodes, it is only the Gazebo node that fails to remap. I can provide more code or a different example if needed. |
This commit in the kinetic-devel branch looks suspicious: a90e609 |
Thanks John for the commenting here. @jaredmoore the fix is now if the |
Sure thing, it might be a week or two as I'm in the middle of finals, but I will try and set some time aside. Thanks for the digging on this! |
I tested this on my installation after removing the apt-get acquired ros-gazebo-pkgs and building from the source on the devel branch. The fix appears to work correctly and I am now able to remap the Gazebo topic. It will be a few weeks before I can test it on my larger instance, but for now I am confident that this addresses the issue. Thank you all for your help! |
I'm currently troubleshooting a problem with remapping the clock topic in a gazebo node. A detailed explanation of the problem is here: http://answers.ros.org/question/242656/is-it-possible-to-remap-clock/
A synopsis is the following. Ros Kinectic/Gazebo7. Using
<remap>
either at launch file level, or within the<node>
tags launchinggzserver
is failing. Running it on a Ros Indigo/Gazebo2 VM allows the code to work. Has there been a change to the remapping policy, solely within the gazebo nodes for this package?gazebo_only.launch:
Test with:
Expected output:
/clock
should be remapped to/clock_remapped
and/rosout
should be remapped to/rosout_remapped
.On my Kinectic/Gazebo7 VM this does not work correctly, but on an Indigo/Gazebo2 VM it does properly remap the topics. Adding other nodes in either version gives them the remapped topics, but Gazebo still remains mapped to the
/clock
topic.The text was updated successfully, but these errors were encountered: