Skip to content
Design System
GitHub

Joint state

v0.24.1Beta

A robot arm's joints for monitoring (ROS sensor_msgs/JointState with the URDF's limits): each joint's position in degrees or millimetres on a thin track between its limits, velocity and effort, near-limit and at-limit in words with an icon, and loading, empty and stale states.

Arm 2 · UR10e

  • shoulder_pan_joint

    Position 42.0°

    range -360.0° to 360.0°

    Velocity 12.5 °/sEffort 12 %

  • shoulder_lift_joint

    Position -87.3°

    range -360.0° to 360.0°

    Velocity -4.0 °/sEffort 46 %

  • elbow_joint

    Position 91.4°

    range -180.0° to 180.0°

    Velocity 3.2 °/sEffort 43 %

  • wrist_1_joint

    Position -94.1°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 16 %

  • wrist_2_joint

    Position -90.0°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 6 %

  • wrist_3_joint

    Position 0.4°

    range -360.0° to 360.0°

    Velocity 30.0 °/sEffort 1 %

Joint state default

Install
npx shadcn add @syncrobotic/joint-state

Also installs: lucide-react, @syncrobotic/cn, @syncrobotic/skeleton, @syncrobotic/empty-state, @syncrobotic/robot-icons

Overview

When to use

  • The arm panel of a robot's page, beside its camera.
  • Checking an arm's pose after a protective stop: which joint ran into its limit.
  • A cell's commissioning screen, watching each joint while it is homed.

Use something else

  • One level within a range (battery, storage, a single temperature): Meter.
  • Something that needs an operator to act (a joint fault, an over-torque stop): raise an Alarm; this panel shows the pose, the alarm asks for the action.
  • A value's history (a joint's torque over a shift): a line chart in Chart.

More examples

States and real uses. Each example is also a Storybook story and a visual regression test.

Arm 2 · UR10e

  • shoulder_pan_joint

    Position 42.0°

    range -360.0° to 360.0°

    Velocity 12.5 °/sEffort 12 %

  • shoulder_lift_joint

    Position -87.3°

    range -360.0° to 360.0°

    Velocity -4.0 °/sEffort 46 %

  • elbow_joint

    Near upper limit

    Position 168.5°

    range -180.0° to 180.0°

    Velocity 6.0 °/sEffort 43 %

  • wrist_1_joint

    Position -94.1°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 16 %

  • wrist_2_joint

    Position -90.0°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 6 %

  • wrist_3_joint

    Near lower limit

    Position -349.0°

    range -360.0° to 360.0°

    Velocity 30.0 °/sEffort 1 %

Joint state near limit

Arm 2 · UR10e

  • shoulder_pan_joint

    Position 42.0°

    range -360.0° to 360.0°

    Velocity 12.5 °/sEffort 12 %

  • shoulder_lift_joint

    Past lower limit

    Position -362.5°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 46 %

  • elbow_joint

    At upper limit

    Position 180.0°

    range -180.0° to 180.0°

    Velocity 0.0 °/sEffort 94 %

  • wrist_1_joint

    Position -94.1°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 16 %

  • wrist_2_joint

    Position -90.0°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 6 %

  • wrist_3_joint

    Position 0.4°

    range -360.0° to 360.0°

    Velocity 30.0 °/sEffort 1 %

Joint state at limit

Gantry 1

  • rail_x

    Position 1,240.5 mm

    range 0.0 mm to 3,200.0 mm

    Velocity 250.0 mm/sEffort 15 %

  • lift_z

    Position 312.5 mm

    range 0.0 mm to 900.0 mm

    Velocity -20.0 mm/sEffort 26 %

  • wrist_yaw

    Position -35.0°

    range -170.0° to 170.0°

    Velocity 0.0 °/sEffort 9 %

  • gripper_finger

    Near upper limit

    Position 39.8 mm

    range 0.0 mm to 40.0 mm

    Velocity 0.0 mm/sEffort 38.0 N

  • tool_spindle

    Position 1,250.0°

    No limits (continuous)

    Velocity 720.0 °/s

Joint state mixed

Arm 2 · UR10e

  • shoulder_pan_joint

    Position 42.0°

    range -360.0° to 360.0°

    Velocity 12.5 °/sEffort 12 %

  • shoulder_lift_joint

    Position -87.3°

    range -360.0° to 360.0°

    Velocity -4.0 °/sEffort 46 %

  • elbow_joint

    Position 91.4°

    range -180.0° to 180.0°

    Velocity 3.2 °/sEffort 43 %

  • wrist_1_joint

    Position -94.1°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 16 %

  • wrist_2_joint

    Position -90.0°

    range -360.0° to 360.0°

    Velocity 0.0 °/sEffort 6 %

  • wrist_3_joint

    Position 0.4°

    range -360.0° to 360.0°

    Velocity 30.0 °/sEffort 1 %

Joint state stale

Arm 2 · UR10e

Loading joint states…

Joint state loading

Arm 2 · UR10e

No joint states yet

Positions show here once the robot publishes them.

Joint state empty

Usage rules

  • For watching an arm's joints. It has nothing to press: jogging a joint is a control, with its own confirmation and a hold-to-run button.
  • Pass the values as ROS sends them (radians and metres) with each joint's unit; the panel shows degrees and millimetres. Never convert before passing them, or the limits and the position will disagree.
  • Give every joint its URDF lower and upper. Leave both out only for a continuous joint: it shows no track, and it can never be near a limit.
  • Keep margin at 5 % of the range unless the arm's safety configuration sets its own soft limits; then pass that fraction, so the panel warns where the controller will.
  • Pass updatedAt from the message's header.stamp when you have it: a robot that keeps publishing an old state still reads Stale. Keep staleAfterMs near three missed messages (1 s for a joint state at 10 Hz or faster).
  • List the joints in chain order (base to tool), as the URDF does, not alphabetically.

Changelog

  • 0.24.12026-11-21Without locale, numbers are written in English ("en") instead of the runtime's language, so server and browser render the same and the page hydrates without a mismatch; pass your app's locale. An invalid locale tag falls back to "en" instead of throwing. Without updatedAt, Stale now follows the values (position, velocity, effort), so a parent that rebuilds joints every render still sees Stale; a still arm then reads Stale too, so pass updatedAt. staleAfterMs={Infinity} never goes stale, an infinite URDF limit counts as no limit (no NaN marker), and ±0.05 round the same way.
  • 0.24.02026-11-21First release.

How to upgrade