ClawMetry Back to dashboard

Asimov 1

See the robot state and the evidence behind each action.

Observation only

Hardware qualification is pending. SDK evidence does not establish physical robot validation.

Reading stored robot evidence.

Bring your first robot run into view

Import a Menlo SDK recording to inspect measured joints, alerts, and recorded commands.

clawmetry asimov import-recording /path/to/run.jsonl --robot-id my-asimov

Observe a connected robot

Use a Menlo Observe credential. Run the collector on the computer that can reach the robot.

clawmetry asimov observe --robot-id my-asimov --duration 60

Live observation requires Python 3.12 and the optional Menlo SDK. Read the connection guide.

Start ClawMetry after the import. Open this screen from its dashboard.

This screen reads stored evidence. It cannot move or stop a robot.

Robot

Mode: Not reported
Battery: Not reported
Recorded events: Not reported
Dropped evidence: Not reported

Measured joints

Latest stored sample. Missing values stay unknown.

Latest measured joint values with explicit units
Joint	Position (rad)	Velocity (rad/s)	Current (A)	Temperature (°C)

Orientation

Quaternion, in w, x, y, z order.

Not reported

Angular velocity (rad/s)

Not reported

Gravity in body coordinates

Not reported

Source alerts

Alerts reported by this source.

Battery measurements

Command evidence

A returned SDK call does not confirm movement. Command outcomes remain unknown.

No command evidence is stored in the loaded events.

Source and receipt clocks

Source time comes from the robot or recording. Receipt time comes from the collector computer.

These clocks can differ. The sequence orders stored evidence.