Skip to guide content

RoboBuddy Documentation

Windows Blockers

Unresolved native-Windows verification blockers

Terminal status for this returned bundle: NATIVE_WINDOWS_BLOCKED.

This is not an impossibility finding. It is the required narrow status because the packaging environment was Linux and had no Windows browser/device/robot access. Repeating source tests cannot substitute for the external evidence below.

Blocked external evidence

  1. Clean native-Windows setup and PowerShell execution - tools/setup-so101-windows.ps1, TLS setup/cleanup, and bridge launcher could be statically reviewed but not parsed/executed by Windows PowerShell here. - Required closure: Python 3.12.10 x64 environment creation, editable provenance, exact dependency resolution, second-run idempotence, repair behavior, and sanitized probe output on native Windows.

  2. LeRobot/Feetech real Windows robot I/O - The immutable LeRobot adapter imports are covered by source/read-only probes, but feetech-servo-sdk==1.0.0 is published as a source distribution and no physical COM-port test was authorized or available. - Required closure: current intended Windows host, actual USB/serial adapter/driver, exact SO-101, calibration, limit registers, bounded connect/retry behavior, and clean disconnect. - No-Windows-wheel and not-reproduced are not claims of technical impossibility.

  3. Bridge lifecycle on Windows - Listener ownership, /health, token authentication, restart, shutdown, feature postconditions, private-interface HTTPS binding, and failure cleanup need real Windows process/network APIs.

  4. Current Chrome and Edge Xbox behavior - Static JS and source contracts preserve xbox_standard_v1, but real Gamepad API mapping, timestamps, Bluetooth loss, multiple-controller selection, neutral qualification, deadman, hold, STOP, and re-arm must be repeated in both current browser channels on the intended controller/driver stack.

  5. Android TLS/WebXR source lifecycle - Requires a physical ARCore-supported Android device, imported mkcert public CA, same-LAN reachability, trusted HTTPS, one-time QR/cookie exchange, one authorized WebSocket, WebXR tracking, background/focus/pointer loss, release, disconnect, reconnect, and STOP checks. - Android Emulator is not accepted for this WebXR path.

  6. Physical SO-101 evidence - No robot motion was executed. Limits remain provisional and hardware gates remain disabled/unqualified. - Required closure: the existing H0/H1 read-only evidence first, then separately authorized and recorded supervised Xbox and Android qualification with Fine speed, clear workspace, observer, reachable cutoff, release-to-hold, stale/disconnect retirement, unreachable targets, STOP, and recovery.

  7. Complete application JavaScript suite - The received bundle is a patch-oriented source slice and omits unrelated full-checkout pages, including python.html. The source-slice npm test therefore reaches a pre-existing missing-page condition after its earlier checks. - Required closure: merge the returned slice into the complete SolU checkout and run the full JavaScript/Playwright suite there. Do not add replacement unrelated pages to this patch slice.

Still functional and verified in the returned source

  • Existing Xbox joint-space mapping and motion-authority files remain byte-for-byte unchanged.
  • run-app.bat remains byte-for-byte unchanged and does not enable any hardware Leader feature.
  • The Placo-independent native_dls_v1 backend is explicitly selected with no fallback.
  • Bundled URDF digest, target frame, semantic joint order, gripper exclusion, degree/radian boundary, workspace/limit checks, bounded solve, and classified diagnostics are implemented.
  • Independent standard-library FK oracle and immutable reference cases cover home/compact, interior, limit-adjacent, and near-singular configurations.
  • Position-only, weighted soft-orientation, malformed/non-finite, unreachable, digest/frame, and no-fallback behavior are covered by tests.
  • Phone source pairing/session/controller safety tests remain available without hardware motion.
  • SolU-local Windows setup, exact Python/dependency selection, native runtime probes, private-LAN TLS creation/cleanup, scoped firewall rule, and ownership-preserving launcher source are included.

Primary references

  • Python 3.12.10 Windows installer: https://www.python.org/downloads/release/python-31210/
  • Immutable LeRobot dependency boundary: https://github.com/huggingface/lerobot/blob/8a74e0ac6d01706d67fddfed682a09d694d9c8c0/pyproject.toml
  • Feetech 1.0.0 release artifacts: https://pypi.org/project/feetech-servo-sdk/1.0.0/
  • NumPy 2.2.6 Windows artifacts: https://pypi.org/project/numpy/2.2.6/
  • Placo v0.9.15 wheel matrix: https://github.com/Rhoban/placo/blob/v0.9.15/.github/workflows/wheels.yml
  • Gamepad API behavior: https://developer.mozilla.org/en-US/docs/Web/API/Gamepad_API/Using_the_Gamepad_API
  • Android WebXR requirements: https://developers.google.com/ar/develop/webxr/requirements
  • mkcert trust/private-key guidance: https://github.com/FiloSottile/mkcert/tree/v1.4.4