Does X-VLA run on Reachy 2?
We have found no published evidence for X-VLA on Reachy 2. Unknown means nobody has reported a result either way, so this page makes no claim.
Inferred: LeRobot supports Reachy 2 natively since 0.4.0 and X-VLA as --policy.type=xvla since 0.4.3, so its tools connect them. No run has been published. Check action and state dimensions, camera count and compute before relying on it. Sources: Reachy 2 framework support, X-VLA framework support.
If you have run it (or failed to), a link to a public log, issue, checkpoint or video is enough. Open a pre-filled report. Failures are as valuable as successes.
X-VLA inference speed by hardware robot-independent · inference cost only
| Compute | Runtime | Precision | Cams | p50 / p95 ms | Inference | Platform | Source |
|---|---|---|---|---|---|---|---|
| Jetson Orin Nano 8GB (Super) | TensorRT | fp16 | 3 @640x480 | 342.59 / 343.47 | 2.92 Hz | jetpack 7.2.1 · power_mode MAXN_SUPER, clocks pinned with jetson_clocks (GPU 1020 MHz, CPU 1728 MHz) · tensorrt 10.16.2.10conditionsboard: Jetson Orin Nano Engineering Reference Developer Kit Super (8 GB) · l4t: R39.2.1 · os: Ubuntu 24.04.4 LTS · python: 3.12.3 · desktop: running Inference cost only; not task success. 300 s run on synthetic 640x480 observations resized by the exported policy to 224x224; 10 denoising steps; latency is runtime-only over a pre-materialized observation ring. Whole-board RAM in use 3.04 GB (unified memory, desktop running). Actions were gated against the stock policy (cosine >= 0.99999) before timing. | T3 · community reported |
| Jetson Orin Nano 8GB (Super) | ONNX (split) | fp16 | 3 | 391.55 / 407.33 | 2.55 Hz | jetpack 7.2 (L4T R39.2.x, per the repo host-setup doc at this commit) · power_mode MAXN_SUPER, pinned clocks · cuda 13.2 · tensorrt 10.16.2 (system, via ONNX Runtime TensorRT EP)conditionsboard: Jetson Orin Nano Super 8 GB developer kit · os: Ubuntu 24.04 · onnxruntime-gpu: 1.24 Inference cost only; not task success. Deterministic synthetic observations, pinned MAXN_SUPER clocks. Configured EP priority 12 graphs TensorRT. System RAM 5395 MB in use. | T3 · community reported |
| Jetson Orin Nano 8GB (Super) | PyTorch eager | fp32 | 3 | 2313.5 / 2320.89 | 0.43 Hz | jetpack 7.2 (L4T R39.2.x, per the repo host-setup doc at this commit) · power_mode MAXN_SUPER, pinned clocks · cuda 13.2 · lerobot 0.6.1conditionsboard: Jetson Orin Nano Super 8 GB developer kit · os: Ubuntu 24.04 Inference cost only; not task success. Deterministic synthetic observations, pinned MAXN_SUPER clocks. Stock LeRobot X-VLA policy in PyTorch FP32 (LeRobot 0.6.1 env). At 30 Hz control the 30-step chunk is overrun (author's control-rate fit). System RAM 5450 MB in use. | T3 · community reported |
Embed this cell
Badge for READMEs and model cards. It always shows the current state.
[](https://caniembody.pages.dev/compat/reachy2/xvla)<iframe src="https://caniembody.pages.dev/embed/reachy2/xvla" width="380" height="132" style="border:0" title="X-VLA on Reachy 2 | CanIEmbody"></iframe>History
No record yet. Source file: data/compat/reachy2__xvla.yaml