Robotics

State and targets

Inspect independently reported poses and joint readings while editing explicit target values.

• Joint panel. Pairs host-reported joint positions with independent draft targets, supplied units and limits, and an explicit request action.
• Robot pose. Displays exact Cartesian translation and explicitly named orientation components for a selected supplied pose, with frame, time, and recorded status.

Mission planning

Order supplied mission steps and request actions without inventing execution status.

• Robot mission queue. Shows supplied mission order and recorded step states, with keyboard reorder requests and explicit host actions separate from pending and confirmed records.

Keep coordinate frames explicit

Every pose belongs to a supplied frame, timestamp and orientation representation. Components display exact values and do not transform frames, normalize quaternions or infer an orientation convention.

Keep reported state separate from targets

Joint targets do not update reported positions. The application supplies joint limits, accepts or rejects target requests and returns confirmed state. Missing limits or readings remain visible.

Execute in the controller

The host owns robot connectivity, permissions, motion planning, collision checks, interlocks and mission execution. Reordering a plan or requesting an action is not evidence that a robot moved.