Skip to content

feat(piper-x): integrate dual-arm CAN and RGB-D hardware - #40

Merged
1rubbishyuan merged 5 commits into
Open-RUA:mainfrom
NanZihao:codex/piper-x-pr
Nov 15, 2026
Merged

1rubbishyuan merged 5 commits into
Open-RUA:mainfrom
NanZihao:codex/piper-x-pr

Conversation

@NanZihao

Copy link
Copy Markdown

Piper-X was not available through the mainline robot integration interface. This adds its native CAN/RealSense Body runtime and environment adapter so dual-arm installations can use the existing Direct tools and official UNI CLI with Codex.

Implementation

  • Compose the shared gripper, scene, skill and episode tools through the prepared episode lifecycle. Offer Direct and observation-only profiles; do not change shared tool schemas or planner SDKs.
  • Bind each installation to explicit hardware identities, SDK/firmware versions, hash-pinned model assets, calibration and camera capture settings. Keep vendor SDKs, models, credentials and measured station files external.
  • Support calibrated per-arm kinematic offsets consistently in FK, IK, tracking, arrival and image-time wrist geometry. Acquire paired RGB-D with native intrinsics and skip identity rectification for zero-distortion images.
  • Keep collision validation as the default. An explicit operator-supervised command_limits profile matches ARX's collision-checking scope while retaining native command bounds, step/speed limits, feedback freshness and tracking checks.
  • Recover small measured joint-limit excursions using a separate acknowledged entry prefix. Targets stay inside native limits, affected boundary joints receive a 0.03 rad margin, and the agent must reobserve and replan. Stationary evidence remains separate from uncertain execution.
  • Preserve quarantine across every page of the operation journal. Enforce device restrictions on stop, receipt, event, lease and stream access, including narrower credentials with the same principal name.
  • Package configuration templates and attribution in both distributions. No station paths, keys, calibration data, vendor binaries or evaluation outputs are included.

Validation

  • Piper-X CPU suite, including FCL mesh checks: 146 passed, 3 subtests passed, no skips.
  • Shared tool composition/configuration checks: 8 passed.
  • Main and runtime distributions: independent sdist-to-wheel builds, byte-for-byte content checks, runtime source parity and twine check --strict passed.
  • Installed-wheel smoke checks: main CLI offline Piper configuration validation; separate runtime environment CLI help and packaged resources.
  • Diff whitespace and source checks for credential literals and station-specific paths passed.

Hardware evidence and remaining limitation

Two supervised trials on 2026-11-13 used the same implementation/configuration, the official Codex path, sequential left-apple/right-orange placement, 640x480 RGB-D at 15 Hz and a 30-minute episode limit:

Trial Visual placement result Runtime acceptance Duration
1 Both fruits in the basket Rejected: execution_uncertain on final right-arm withdrawal 11m 48s
2 Both fruits in the basket Accepted; final withdrawal and idle stopping confirmed 10m 18s

Both trials successfully completed the joint-entry prefix. Trial 1 exceeded the existing 30 mm tracking threshold (30.66 mm); its unknown receipt/quarantine was preserved, and subsequent stationary feedback did not turn it into a pass. The cause remains unresolved, and trial 2 is not evidence of a fix. Neither run had an automatic physical-task judge (task_success=null); placement was reviewed using the final in-episode images.

The journal-recovery and authorization fixes added in PR review have CPU regression coverage only and were not deployed for those trials. The collision profile has no hardware validation in this evaluation. Keep this PR in draft pending review of the integration and the remaining tracking limitation.

max and others added 5 commits November 11, 2026 22:31
Keep Piper-X Body, CAN/RGB-D drivers, configuration and environment code inside the integration. Reuse the existing wholepath tools and replanning executor, including typed recovery receipts and lifecycle stopping. Preserve request reconciliation without replay and observation-only operation.

Validate with 86 Piper CPU tests, shared tool composition checks and main/runtime package builds. Hardware deployment and validation remain separate.
Use an interior margin for all boundary joints on the recovering arm and
keep stationary evidence separate from uncertain execution outcomes.
Restore quarantine across the complete journal and enforce device scope
for receipts, stopping, leases and streams. Add regression coverage and
document the limited hardware validation and unresolved tracking failure.

Co-Authored-By: Claude <noreply@anthropic.com>
@NanZihao
NanZihao marked this pull request as ready for review November 14, 2026 00:23
@1rubbishyuan
1rubbishyuan merged commit 02b78d6 into Open-RUA:main Nov 15, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants