ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Revision history [back]

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

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

click to hide/show revision 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

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.

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 .

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 .

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.

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.

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.