Pose Display
PROPosition and orientation readout (x/y/z + roll/pitch/yaw)
When to reach for it
Pose Display is the numeric readout: x, y, z plus roll, pitch, yaw, with optional frame ID and velocity chips. Reach for it when you want exact numbers instead of a picture. For a visual trail and tap-to-send nav goals on the same odometry, use Map 2D (Pro).
Worked example: end-effector pose
Topic /ee_pose, Message Type geometry_msgs/msg/PoseStamped, Pose Path pose: PoseStamped nests position and orientation directly under pose, so a blank path shows nothing. Source Unit Meters, Display System Metric, Display Unit Millimeters, so the readout renders in mm though the topic publishes meters. Show Velocity off, since PoseStamped carries no twist to read.
Watch out for
- An empty Pose Pathdoes not fall back to the message's top level: the widget walks the dot path regardless, so a blank field shows dashes everywhere. The default is
pose.poseon the default/odomtopic. - Source Unit is never checked against the data. Pick the wrong one and the whole display silently rescales, with no error to flag it.
- Show Frame ID surfaces whatever string sits in the header, unvalidated. The default
/odomtopic is a locally-drifting frame, so x/y/z wanders even on a stationary robot unless the source publishes in a globally-consistent frame likemap.
Configuration fields
The topic this widget reads from. While connected, tap to pick one the robot advertises.
The ROS message type, like sensor_msgs/msg/Image. Fills in when you pick a topic.
Dot-path to the field to read, like pose.position.x. Blank uses the message's main value.
Messages per second this widget takes from the topic. Lower saves data, higher shows more.
0.1 to 60, step 0.1Source coordinate frame from the message header (e.g. odom, map, base_link).
Where to read the frame ID from. Auto walks header.frame_id.
String field path to read as the source frame name.
Linear velocity in m/s. Needs Odometry or TwistStamped: PoseStamped has no velocity.
Auto tries Odometry, then TwistStamped. Custom reads any number or x/y/z vector field.
Numeric or x/y/z vector field. Vectors show their magnitude.
Show a name on the widget.
The unit your topic publishes positions in. Must match the data: most ROS topics use meters.
Metric or imperial for the readout. Only the display converts, not the data.
shown when Display System is Metric
shown when Display System is Imperial