Repository navigation
feat(piper-x): integrate dual-arm CAN and RGB-D hardware - #40
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
command_limitsprofile matches ARX's collision-checking scope while retaining native command bounds, step/speed limits, feedback freshness and tracking checks.Validation
twine check --strictpassed.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:
execution_uncertainon final right-arm withdrawalBoth 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.