VLAI L1 Community

What is the VLAI L1 workspace reach?

The VLAI L1 has a 63cm arm span per arm. Combined with its motorized linear lift (adjustable height 106cm to 162cm at 30mm/s), the robot covers table-level, shelf-level, and floor-level tasks without repositioning. Each arm has 7 DOF plus a gripper, with ±0.02mm repeat positioning accuracy.

Does the VLAI L1 work with ROS2?

Yes. The VLAI L1 natively supports ROS2 + MoveIt2 — no middleware translation layer is required. Isaac Sim, Isaac Lab, and MuJoCo simulation environments are bundled with Developer tier and above. The RoboticsCenter SDK connects via ROS2: run pip install roboticscenter, then rc connect --device l1.

What end effectors does the VLAI L1 support?

The L1 ships with self-developed 8Nm grippers (one per arm). Developer Max tier supports wrist camera modules for visual feedback. Third-party end effectors with standard mechanical interfaces can be mounted on the Developer and above tiers. The browser teleop panel lets you switch the active end-effector type per arm independently: Gripper (default), Dexterous hand, or Suction cup.

What are the four VLAI L1 tiers and their prices?

The L1 comes in four tiers:

Youth Edition (~$3,950 / ¥28,800) — basic education use, 2kg payload, no SDK.

Developer Edition (~$8,050 / ¥58,800) — full SDK, ROS2, Isaac Sim/MuJoCo, 6kg payload.

Developer Pro (~$12,150 / ¥88,800, recommended) — adds VR teleoperation and VLA training support, V3 controller (70 TOPS), 1-year warranty.

Developer Max (~$17,600 / ¥128,800) — wrist cameras, agent integration, V5 controller (128 TOPS), 2-year priority support.

How long is the lead time to receive a VLAI L1 in the US?

Typical lead time for US delivery is 6–8 weeks from order confirmation. RoboticsCenter is the US distributor and handles warranty service, SDK access, and platform integration. Contact roboticscenter.ai/contact to place an order.

Can I test the VLAI L1 SDK without the physical robot?

Yes. Run rc connect --device l1 --mock to start a fully simulated L1 session. All SDK methods, the browser teleop panel, and data recording work identically in mock mode. This is useful for CI pipelines, workflow prototyping, and testing before your unit ships.

What data gets captured in a collection session?

Every rc connect session captures: joint position/velocity/effort for all 16 DOF at ~500Hz, camera streams (chest RGB on Developer+, wrist RGB on Developer Max), gripper force estimates, base odometry, and raw teleop operator commands. Sessions auto-upload to your platform workspace on close. Press Space to mark episode boundaries and L to annotate frames in real time.

What is the latency for browser teleoperation?

The L1's CAN-FD control loop runs at <10ms on the onboard controller. Network round-trip (browser to cloud to robot) adds 20–80ms depending on your connection. For latency-critical tasks, co-locate the operator machine on the same LAN as the robot. Developer Pro and Max tiers support VR headset control via OpenXR for immersive low-latency teleoperation.