Repository navigation
docs(protocol): dual clutch runs 3 to 5, and the OLED frame order is validated - #107
Merged
Merged
Conversation
…validated fsfarmscaper's power-cycle and Reset runs (#97): the dual clutch setting survives full power removal, fn2 byte 0 is the enable flag rather than a constant, the on-wheel Reset disables and returns the bite point to 100 but keeps the paddle, and the wheel reports the saved state unsolicited a few seconds after the HID++ handle opens. Revision 7.7. Section 12.3 still said the OLED fn3 frame order was unvalidated, while the per-layout table a few paragraphs above records what an RS50 drew on 2026-09-02. The sentence now points at the table. WnDTech's tester, who read the descriptors that started that thread, is credited.
mescon
enabled auto-merge
September 17, 2026 15:45
|
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.



Folds fsfarmscaper's three follow-up runs on #97 into section 12.6 (persistence across a power cycle, byte 0 as the enable flag, Reset semantics, the connect-time state report), checked against the attached logs. Fixes a stale sentence in 12.3 that still called the OLED fn3 frame order unvalidated. Credits WnDTech (#20).