Skip to content

docs(protocol): dual clutch runs 3 to 5, and the OLED frame order is validated - #107

Merged
mescon merged 1 commit into
masterfrom
docs/dual-clutch-runs-3-5
Sep 17, 2026
Merged

mescon merged 1 commit into
masterfrom
docs/dual-clutch-runs-3-5

Conversation

@mescon

@mescon mescon commented Sep 17, 2026

Copy link
Copy Markdown
Owner

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).

…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
mescon enabled auto-merge September 17, 2026 15:45
@sonarqubecloud

Copy link
Copy Markdown

@mescon
mescon merged commit 50197d2 into master Sep 17, 2026
17 checks passed
@mescon
mescon deleted the docs/dual-clutch-runs-3-5 branch September 22, 2026 14:17
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