Skip to content

Verify RF MOSFET absolute values and steps on deployed host - #676

Merged
DRSDavidSoft merged 4 commits into
mainfrom
fix/rf-pwm-verification
Oct 14, 2026
Merged

DRSDavidSoft merged 4 commits into
mainfrom
fix/rf-pwm-verification

Conversation

@DRSDavidSoft

Copy link
Copy Markdown
Collaborator

Documents the existing host-owned RF Board command for arbitrary curve-aware percentages and advertised Increase/Decrease actions with configurable channel steps. Adds framed command conversion/invalid-value tests and non-actuating RF persistence/step-preservation regressions. Current host main was deployed to Cafe through its own updater before these tests and fresh CI, as requested. Live connection and renamed channel action catalog were verified. Two compact autonomous AVR prototypes failed the reserved identity boundary; production firmware and EEPROM were restored unchanged, with the default footprint build passing. No physical output, RF assignment, firmware flash or app installation was performed. Exact deployment and fit evidence is in docs/RF-APPLICATION-ACTIONS.md. Focused stable-path Go suites passed; fresh multi-target CI remains running.

@DRSDavidSoft

Copy link
Copy Markdown
Collaborator Author

The deployment-first main CI run 38467880758 has now completed successfully: full AVR firmware and host/VirtualBoard builds for all five targets passed. Post-deployment focused stable-path appconfig/control/ipcjson tests, including the new arbitrary-value and RF step-preservation regressions, passed; go vet ./... is clean. The restored unchanged full AVR firmware also rebuilt with 68 flash bytes free and 231 estimated SRAM bytes free (96 required). This PR adds only tests/documentation, not new production behavior; its own required checks are still pending and normal auto-merge is enabled. No physical output, RF table/config assignment or firmware was changed on Cafe.

@DRSDavidSoft

Copy link
Copy Markdown
Collaborator Author

Time-specific runtime follow-up: a later readback found Cafe running a different CI candidate, 0.0.0-ci.1574, source hash b03da8e97569f2073f7694979bcf7975196458094b6a9d34429115809bacc9f1, executable SHA-256 5b879b21d2d5ef0b7227cf1cd63ad13ebee673cfc30fed1fce8a295227a29573. I did not overwrite that concurrent runtime. Its live snapshot remains connected/error-free and its RF catalog retains host Board commands and the renamed PWM Increase/Decrease actions. The earlier op-3cf502807cf36e56 acknowledgement remains a completed deployment receipt, not a claim that its exact executable is still the active one. Physical MOSFET endpoint/dropout investigation #672 remains separate and unresolved; parser/configuration tests and RF assignment availability do not prove electrical output behavior.

@DRSDavidSoft

Copy link
Copy Markdown
Collaborator Author

Reconciled current main through ordinary merges. The stale absolute-value fixture incorrectly rejected PWMGet for zero percent: current semantic Off deliberately uses read/write/read to retain confirmed brightness recall. Updated the wire fixture and asserted two reads for zero, zero reads for positive absolute values, and no transport reads/writes for invalid percentages. Focused stable-path Go test passed; fresh multi-target/CodeQL checks run on e558d9c. No production deadline, Off persistence, RF mapping, EEPROM or hardware behavior was weakened.

@DRSDavidSoft

Copy link
Copy Markdown
Collaborator Author

Integrated current RF learning and shared Off-persistence source is preserved on e558d9c. Stable-path cmd/controller, appconfig, control, ipcjson and tui suites all passed after the fixture repair. Review comments/reviews and all review-thread pages were read; no unresolved review findings exist on this PR. Required hosted gates are being followed without overrides; runtime replacement will use the final merged host package through Cafe's own updater, not firmware/EEPROM writes.

@DRSDavidSoft
DRSDavidSoft merged commit f514951 into main Oct 14, 2026
23 checks passed
@DRSDavidSoft
DRSDavidSoft deleted the fix/rf-pwm-verification branch October 14, 2026 10:09
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.

1 participant