Repository navigation
Complete real-handset RF capture, mapping, gesture, removal, and transmit validation #73
Description
Original request
Relevant excerpt, lightly grammar-corrected for publication. Credentials, personal data, private paths, and unrelated transcript content are omitted.
Resume real RF key learning when human interaction is needed, and use a unique repeating attention melody for the assisted steps.
Source: session origin-main, authored turn 82.
Parent epic: #13
Requirement
Complete real-handset RF capture, mapping, gesture, removal, and transmit validation
Acceptance criteria
- Review/remove stale Remote A data and capture A/B/C/D one at a time.
- Map each stable RF identity to an explicitly confirmed action.
- Verify short burst, click, hold, repeat, inferred release, list/remap/remove, and latency.
- Transmit on INT1 and confirm reception on another receiver.
- Resume the guided human sequence with buttons B, C, and D after WAIT/ringtone; do not silently infer or auto-assign mappings.
Current evidence and gaps
Remote A has useful live evidence, but the complete handset set, CRUD, latency regression, stale record cleanup, and physical TX test remain open.
Traceability
- Canonical checklist section: Final hardware validation and handoff
- Includes only curated, issue-relevant prompt excerpts; complete transcripts, credentials, secrets, and private paths remain unpublished.
Activity
DRSDavidSoft commentedon Oct 6, 2026
Software integration acceptance has advanced: learned RF protocol/readback/TX, Pealayer RX->playback acknowledgement, native Windows key/program actions, RF assignment reassignment and coordinator-restart recovery are verified on the isolated VirtualBoard path. Real-handset/radio range/waveform delivery is NOT proven; this issue remains open. Exact evidence and physical-test boundaries: https://github.com/ToghrolTP/pealayer/blob/fix/hardware-monitor-layout/docs/RF-CONTROLS.md . Coordinator contract: docs/RF-APPLICATION-ACTIONS.md in PR588.
DRSDavidSoft commentedon Oct 22, 2026
Continuation checkpoint: e23be3d on wip/strip-framing-trace (GitHub ref verified).
The four existing on-board seat mappings remain left up/down and right up/down. Coordinator and Pealayer report connected; no new handset packet was captured during the bounded learning attempt, and no mappings or saved learning preferences were changed. First-button learning has now been rearmed with single-capture stop, awaiting the human A-button press. No new motion command was sent.
Next action: read the captured complete waveform, confirm the human button label and desired seat action, append one mapping preserving the old handset, read back, then continue B/C/D and physical press/release acceptance. Rainbow/MOSFET and the three catalogued lighting effects remain a subsequent phase; none has physical acceptance from this pass.
The checkpoint also preserves the pre-existing, uncommitted UartProtocol bench trace encountered in the diagnostic worktree. It is unvalidated and has not been built/uploaded during this pass. Its original dirty working copy was preserved. The checkpoint worktree and all seven Pealayer worktrees are clean; no stale worktree metadata was found. Existing recovery source remains a48acbd / #697. Private configuration, snapshots and native UI capture stay local. Validation: live read-only status/catalog and git diff --check; no firmware build or stress test.
DRSDavidSoft commentedon Oct 22, 2026
New handset step A completed: one distinct 24-bit/protocol-1 button was learned and assigned on the board to left seat up. An independent board catalog readback confirmed the assignment. All other learned identities/actions and all host bindings were compared before/after and remained unchanged. This is configuration/readback evidence; physical press/release acceptance is still pending.
Single-capture learning is armed for the human B press next (intended left seat down); C/D will follow. No firmware/app source, runtime binary or saved learning preferences changed. Recovery/WIP checkpoints remain #697 at a48acbd and wip/strip-framing-trace at e23be3d. Private waveform identities and settings stay local.
DRSDavidSoft commentedon Oct 22, 2026
The human has now confirmed all four new remote directions and stopping on release. Both seats subsequently read back stopped. The old handset mappings and host bindings remain preserved; this completes the new-handset mapping/physical test scope, not RF transmit/CRUD or unrelated stress acceptance.
A three-pixel rainbow has started via Pealayer and is still awaiting human visual confirmation. The subsequent MOSFET and three-effect checks remain open. Durable continuation: wip/strip-framing-trace at 5a1cf74 (GitHub ref verified), docs/RF-LIGHTING-CONTINUATION.md. Pealayer hardware-preview dispatch fix is separately saved in ToghrolTP/pealayer#212 at f5fb6a19db711adefa634ff11e0b48e6871c074e; hosted checks/package and Cafe deployment are pending. No firmware or application binary was replaced in this pass. Private state/captures remain local.