You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each robot should have its own RViz node, since we want to control and view them individually.
Since the robots are spawned in different namespaces, their descriptions belong to those individual namespaces i.e. in the topic {namespace}/robot_description, accessing /robot_description gives us nothing. Other subscribers and publishers should also created to occupy the same namespace.
ros2 node info /arm4/rviz2 shows the following when using the default view_robot.rviz to create the node:
Each robot should have its own RViz node, since we want to control and view them individually.
Since the robots are spawned in different namespaces, their descriptions belong to those individual namespaces i.e. in the topic
{namespace}/robot_description
, accessing/robot_description
gives us nothing. Other subscribers and publishers should also created to occupy the same namespace.ros2 node info /arm4/rviz2
shows the following when using the default view_robot.rviz to create the node:Is there a way to parameterize the rviz config file or use it as a template that could be dynamically updated based on what robots are being spawned?
The text was updated successfully, but these errors were encountered: