ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
1 | initial version |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
That's it. Easy once discovered, but a PITA until then.
I had to put a break point in gazebo::World::GetEntityByName() and massage gdb to get it to tell me
2 | No.2 Revision |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
That's it. Easy once discovered, but a PITA until then.figured out.
I had to put a break point in gazebo::World::GetEntityByName() and massage gdb to get it to tell me
3 | Mention the link_states issue |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
That's it. Easy once discovered, Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but a PITA until figured out.this has been patched and the scope will be published along with the name in "Electric Turtle".
I had to put a break point in gazebo::World::GetEntityByName() and massage gdb to get it to tell me
4 | Link to patch |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but this has been patched and the scope will be published along with the name in "Electric Turtle".
A patch for gazeboros in diamondback is available here.
5 | No.5 Revision |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but this has been patched and the scope will be published along with the name in "Electric Turtle".
A patch for gazeboros in diamondback is available here .
6 | No.6 Revision |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but this has been patched and the scope will be published along with the name in "Electric Turtle".
A patch for gazeboros in diamondback is available here .
7 | Link to patch |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but this has been patched and the scope will be published along with the name in "Electric Turtle".
A patch for gazeboros in diamondback is available here.
8 | No.8 Revision |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but this has been patched and the scope will be published along with the name in "Electric Turtle".
9 | No.9 Revision |
It turns out the scope token for models is '::'
so to get it to work, the link has to be referenced using a string like:
Robot_Name::My/Link/Name/Here_link
Currently the /gazebo/link_states topic does not publish the root scope (e.g. Robot_Name:: ) but this has been patched and the scope will be published along with the name in "Electric Turtle".