Define the machine
Robot body, cameras, state vector, action representation, and local safety interface.
Mech starts with the machine. Choose the body, cameras, state, and action space. Then qualify the exact VLA route, prove it on real hardware, and deploy it through cloud or edge.
Joint order, cameras, limits, and control rate.
xArm 6Model processor, normalization, and task data.
checkpointMap output into the robot's validated executor.
6D + gripMeasure success, latency, starvation, and stop.
stationA VLA becomes useful only when one exact checkpoint matches one exact embodiment and survives a real closed-loop episode.
Robot body, cameras, state vector, action representation, and local safety interface.
Use π0.5, MolmoAct2, SmolVLA, or your own weights only where the route is compatible.
Run episodes on a Station or connected robot before any production deployment.
The policy prepares the next action chunk while the local executor runs the current one. Mech watches the queue, latency, and stale observations.
An HTTP 200 proves almost nothing. Mech promotes a route only after repeatable episodes, bounded latency, disconnect recovery, and viable cost.
Did the robot finish the real job?
Did the queue ever run dry?
Did the local stack fail safely?
Can the same route be reproduced?