> For the complete documentation index, see [llms.txt](https://docs-origin.anvil.bot/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-origin.anvil.bot/reference/technical-reference/querying-robot-state.md).

# Querying Robot State

The list of ROS2 topics you can listen on to get information about the state of the system

{% hint style="info" %}
If you are interested in observing the commands being issued to the robot via some nominal operation route (eg. Quest teleoperation), those topics are explained in [Commanding Robot Movement](https://docs-origin.anvil.bot/reference/technical-reference/commanding-robot-movement.md). That section outlines how to publish to them to command the robot, but you can listen to them harmlessly during regular operation.
{% endhint %}

## Joint States

**Topic Name**: `/joint_states`

**Message Type**: [JointState](https://docs.ros2.org/latest/api/sensor_msgs/msg/JointState.html)

This is a standard message that gives information on the state of each joint, including current position, velocity, and torque.

## End-Effector Pose

**Topic Name**: `/ee_pose_{left/right}`

**Message Type**: [Custom Message Types](https://docs-origin.anvil.bot/reference/technical-reference/custom-message-types.md#commandedeepose)

This message indicates the current pose of the end effector in cartesian space, in the coordinate frame whose ID is referenced in the message (this is always the "world" frame). In the transform tree of the robot, the end effector we reference here is the `follower_{l/r}_hand_tcp` frame.\
\
This reference image shows the position of the world frame for the OpenARM robot, with a couple other frames for reference:

<figure><img src="https://4223670213-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT8swLPls6cg6zxcYD7sj%2Fuploads%2FSwSByWEhfFs5m489Wcf6%2Fhand_frames_and_world_frame.png?alt=media&amp;token=91844e83-0ecb-4693-87a2-7262bbce7fdb" alt=""><figcaption></figcaption></figure>

## End-Effector Target Pose

**Topic Name:** `/quest_teleop/{left/right}_target_pose`

**Message Type**: [PoseStamped](https://docs.ros2.org/latest/api/geometry_msgs/msg/PoseStamped.html)

This message indicates the target pose we are trying to achieve with the end effector. This is only available during Quest teleop, and can be thought of as the position of the Quest controllers, transformed into robot space. Our inverse kinematics engine is calculating joint angles and driving the robot so that the end effector goes to this pose. In the transform tree of the robot, the end effector we reference here is the `follower_{l/r}_hand_tcp` frame.

## Coordinate Frames

**Topic Names**: `/tf` and `/tf_static`

**Message Type:** [TFMessage](https://docs.ros2.org/latest/api/tf2_msgs/msg/TFMessage.html)

These are standard messages that give detailed information on the transforms and coordinate frames in the robots, including their names and relative positions.
