Does Evo-1 run on reBot Arm B601-DM?
We have found no published evidence for Evo-1 on reBot Arm B601-DM. Unknown means nobody has reported a result either way, so this page makes no claim.
Inferred: LeRobot supports reBot Arm B601-DM natively since 0.6.0 and Evo-1 as --policy.type=evo1 since 0.6.0, so its tools connect them. No run has been published. Check action and state dimensions, camera count and compute before relying on it. Sources: reBot Arm B601-DM framework support, Evo-1 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.
Evo-1 inference speed by hardware robot-independent · inference cost only
| Compute | Runtime | Precision | Cams | p50 / p95 ms | Inference | Platform | Source |
|---|---|---|---|---|---|---|---|
| Jetson Orin Nano 8GB (Super) | ONNX (split) | fp16 | 1 | 289.18 / 292.12 | 3.45 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. Untrained action head: measures inference cost of the EVO1 architecture only; the author marks it as never to control a robot. Author labels the precision "mixed FP16". | T3 · community reported |
| Jetson Orin Nano 8GB (Super) | TensorRT | fp16 | 2 @640x480 | 332.77 / 333.63 | 3 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 448x448; 32 denoising steps; latency is runtime-only over a pre-materialized observation ring. Whole-board RAM in use 2.76 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 | 2 | 414.67 / 424.72 | 2.41 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. Author labels the precision "mixed FP16". System RAM 6001 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/rebot-b601/evo1)<iframe src="https://caniembody.pages.dev/embed/rebot-b601/evo1" width="380" height="132" style="border:0" title="Evo-1 on reBot Arm B601-DM | CanIEmbody"></iframe>History
No record yet. Source file: data/compat/rebot-b601__evo1.yaml