unitree-g1/context/open-questions.md

id	title	status	source_sections	related_topics	key_equations	key_terms	images	examples	open_questions
open-questions	Open Questions & Known Unknowns	established	<nil>	[hardware-specs joint-configuration sdk-programming safety-limits]	[]	[]	[]	[]	[]

Open Questions & Known Unknowns

This file catalogs what we know, what we don't know, and what would resolve the gaps. When a question gets answered, move it to the Resolved section with the answer and source.

---

Hardware & Mechanical

Open

• Q: What are the per-joint velocity limits (dq_max) for all joints?

  • Partial: Position limits are known for major joints. Velocity limits not published.
  • Would resolve: SDK configuration files, URDF damping/velocity tags, or actuator datasheets.

• Q: What are the exact link masses and inertia tensors for dynamics modeling?

  • Partial: Total mass ~35 kg known. Per-link breakdown should be in URDF.
  • Would resolve: Parse URDF from unitree_ros/robots/g1_description/.

• Q: What is the ankle joint range of motion?

  • Partial: Ankle joints exist (pitch + roll) but ranges not in public specs.
  • Would resolve: URDF joint limits, or physical measurement.

• Q: What are the exact gear ratios per joint actuator?

  • Partial: Planetary gearboxes used, ratios not published.
  • Would resolve: Actuator datasheets.

• Q: What is the IP rating and environmental protection?

  • Partial: Not documented anywhere.
  • Would resolve: Official compliance documentation.

Open (Dexterous Hands)

• Q: What are the Dex3-1 per-finger force limits?

  • Partial: 33 tactile sensors, force-position hybrid control confirmed. Max force not documented.
  • Would resolve: Dex3-1 actuator datasheet or testing.

• Q: What is the exact INSPIRE hand DOF configuration per finger?

  • Partial: Known to be 5-finger, "advanced." Per-finger DOF not documented.
  • Would resolve: INSPIRE DFX documentation page (partially available).

---

Software & SDK

Open

• Q: What is the complete Python vs C++ API coverage parity?

  • Partial: Python SDK uses pybind11 wrapping C++. Unclear if 100% coverage.
  • Would resolve: Side-by-side API comparison.

• Q: What firmware version ships on currently-sold G1 units?

  • Partial: v3.2+ mentioned in documentation. Actual shipping version unclear.
  • Would resolve: Checking a new unit, or Unitree support inquiry.

• Q: What is the LLM integration capability in firmware v3.2+?

  • Partial: "Preliminary LLM integration support" mentioned. Details sparse.
  • Would resolve: Testing on EDU unit with Jetson, or official documentation update.

---

Control & Locomotion

Open

• Q: Can the G1 run (not just walk)? What is the true max speed?

  • Partial: Walking max is 2 m/s. H1-2 can run at 3.3 m/s. G1 running gait not confirmed.
  • Would resolve: Testing or official confirmation.

• Q: What is the exact RL policy observation/action space?

  • Partial: Inputs include IMU + joint encoders. Exact dimensions not documented.
  • Would resolve: Official policy architecture documentation or code inspection.

• Q: Can a custom locomotion policy be deployed natively to the RK3588 locomotion computer?

  • Partial: Root access achieved via BLE exploits (UniPwn, FreeBOT). The ai_sport binary is the stock policy. Nobody has publicly documented replacing it. Config files use FMX encryption (partially cracked).
  • Would resolve: Full reverse engineering of master_service orchestrator and ai_sport binary, or Unitree providing official developer access.

---

Simulation

Open

• Q: What are the optimal domain randomization parameters for G1 sim-to-real?
  • Partial: Standard parameters (friction, mass, noise) used. Optimal ranges not published.
  • Would resolve: Research papers with ablation studies.

---

Safety & Deployment

Open

• Q: What are the official safety certifications (CE, FCC, etc.)?

  • Partial: Not documented in any available source.
  • Would resolve: Official compliance documentation.

• Q: What is the recommended operating temperature and humidity range?

  • Partial: Not documented. Indoor operation recommended as best practice.
  • Would resolve: Official operating manual detailed specs.

• Q: What is the low-battery cutoff voltage and auto-shutdown behavior?

  • Partial: 13-cell LiPo at ~48V nominal, but cutoff threshold not documented.
  • Would resolve: Battery management system documentation.

• Q: What is the Jetson Orin NX power draw under computational load?

  • Partial: Standard Orin NX specs suggest 10-25W. G1-specific thermal management unclear.
  • Would resolve: Power measurement on running unit.

---

Motion Capture & Balance (Phase 2)

Open

• Q: What is the max recoverable push force for the stock G1 controller?

  • Partial: Light push recovery confirmed. Max impulse not quantified.
  • Would resolve: Physical push testing with force measurement, or Unitree internal documentation.

• Q: Can GR00T-WBC run at 500 Hz on the Jetson Orin NX?

  • Partial: Orin NX has 100 TOPS. RL inference typically < 1ms. But GR00T-WBC may have WBC optimization overhead.
  • Would resolve: Benchmarking GR00T-WBC on Orin NX, or NVIDIA documentation on compute requirements.

• Q: What is the end-to-end latency from mocap capture to robot execution?

  • Partial: DDS latency ~2ms. XR teleoperate latency not documented. Video-based pose estimation adds 30-100ms.
  • Would resolve: End-to-end timing measurement with each mocap source.

• Q: Does residual policy overlay work with the proprietary locomotion computer, or does it require full replacement?

  • Partial: rt/lowcmd can send joint commands. Unclear if these override or add to stock controller output.
  • Would resolve: Testing: send small corrections to leg joints while stock controller is active. Observe behavior.

• Q: What AMASS motions have been successfully replayed on physical G1?

  • Partial: AMASS retarget exists on HuggingFace. Which specific motions have been executed on real hardware is not documented publicly.
  • Would resolve: Testing with the retargeted dataset, or finding lab reports from groups using it.

• Q: What is the minimum viable sensor set for push detection (IMU only vs. IMU + F/T)?

  • Partial: G1 has IMU and joint encoders but no force/torque sensors at feet. External force must be estimated.
  • Would resolve: Compare push detection accuracy: IMU-only vs. IMU + momentum observer vs. added F/T sensors.

---

Resolved

Hardware & Mechanical (Resolved)

• Q: What are the exact DOF configurations for each G1 variant?

  • A: Base = 23-DOF (6+6+1+5+5), Mid = 29-DOF (6+6+3+7+7), Full = 43-DOF (29 body + 14 hand). [T0 — Official spec sheet]

• Q: What are the per-joint torque limits?

  • A (partial): Knee max = 90 Nm (base) / 120 Nm (EDU). Other joints not published. [T0 — Official spec sheet]

• Q: What is the maximum payload capacity?

  • A: 2 kg per arm (standard), 3 kg per arm (EDU). [T0 — Official spec sheet]

Sensors & Perception (Resolved)

• Q: What is the full sensor suite across G1 variants?

  • A: Intel RealSense D435i (RGBD), Livox MID360 (3D LiDAR), IMU, 4-element microphone array, 5W speaker, dual joint encoders, per-motor temperature sensors. Dex3-1 adds 33 tactile sensors per hand. [T0 — Official product page]

• Q: What are the camera specifications?

  • A (partial): Intel RealSense D435i — standard specs 1280x720@30fps (depth), 1920x1080@30fps (RGB), 87°×58° FOV. G1-specific configuration may differ. [T0/T3 — D435i datasheet + inference]

Software & SDK (Resolved)

• Q: What is the current stable SDK2 version and Python API coverage?

  • A: unitree_sdk2 v2.0.2 (C++, BSD-3). Python wrapper via unitree_sdk2_python using pybind11, Python ≥3.8. CycloneDDS 0.10.2 required. [T0 — GitHub]

• Q: What ROS2 distributions are officially supported?

  • A: Ubuntu 20.04 + ROS2 Foxy, Ubuntu 22.04 + ROS2 Humble (recommended). [T0 — unitree_ros2 README]

• Q: What control modes are available via SDK?

  • A: Position (q), velocity (dq), torque (tau), force-position hybrid. Via MotorCmd_ structure on rt/lowcmd topic. Enable/disable per motor. [T0 — Developer guide]

Simulation (Resolved)

• Q: Are there official URDF/MJCF models available?
  • A: Yes. MJCF in MuJoCo Menagerie (g1.xml, g1_with_hands.xml). URDF in unitree_ros/robots/g1_description/. USD in unitree_model (deprecated → HuggingFace). [T0 — GitHub repos]

Hardware & Architecture (Resolved)

• Q: What processor runs on the locomotion computer?

  • A: Rockchip RK3588 (8-core ARM Cortex-A76/A55, 8GB LPDDR4X, 32GB eMMC), running Linux 5.10.176-rt86+. Runs 26 daemons including ai_sport (the stock locomotion policy). [T1 — arXiv:2509.14096, arXiv:2509.14139]

• Q: How to replace the stock locomotion policy with a custom one?

  • A: Enter debug mode (L2+R2 on remote while robot is suspended in damping state). This shuts down ai_sport. Then send motor commands from Jetson or external PC via rt/lowcmd DDS topic. All published research groups use this method. Native deployment to the RK3588 has not been publicly achieved. [T1 — Community + research papers]

Control & Locomotion (Resolved)

• Q: What locomotion controller is running on the stock G1?

  • A: Gait-conditioned reinforcement learning with multi-phase curriculum. Biomechanically inspired reward shaping. Trained in simulation, deployed via sim-to-real transfer. [T1 — arXiv:2505.20619]

• Q: What are the achievable walking speeds and terrain capabilities?

  • A: Max 2 m/s walking. Verified on tile, concrete, carpet. Light push recovery. Smooth gait transitions. [T0/T1 — Official specs + testing]

• Q: What sim-to-real transfer approaches work best for the G1?

  • A: Domain randomization in Isaac Gym/MuJoCo, with Sim2Sim cross-validation. Zero-shot transfer demonstrated for locomotion and fall recovery. DDS interface identical in sim and real (switch network config only). [T1 — Multiple papers]