Repository navigation
Conversation
…irmware (LAB-360) From the review of Will Dickson's arena-interface library, whose discrepancy table compares our JS with firmware 12bba7e. - GET_TELEMETRY_BLOCK defaults to 178 record bytes (the firmware's budget), not 180. The firmware clamps, so behavior on the wire is unchanged. - GET_PATTERN_INFO byte 11 is decoded as dutyCycle (the firmware name); stretch stays as an alias. The Studio and Console read dutyCycle and fall back to stretch for a stale cached wire module. - Comments: 01 C1 / 01 C2 on the IP and controller-info encoders, the GET_CRASHREPORT gate is 0xCB flags bit 3 (not the telemetry bit), GET_AO_VOLTAGE is a DAC register readback. - CLAUDE.md: crash-report gate text corrected. In-lab testing (after this is on Next, between sessions): 1. Studio Console, connected controller: select a pattern on the SD card and check the info line reads "duty cycle N" (a number, not "undefined"). 2. Telemetry-capable firmware: run any short protocol with Run logging on and check the run log still has controller rows (cc / cf / cs). 3. Old Console (arena_console.html): pattern info shows a "duty cycle" row. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This branch has not been deployed
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.
Summary
Small corrections to the G6 wire module, found by reviewing Will Dickson's Python library (willdickson/arena-interface), whose discrepancy table compares our JS with firmware
12bba7e. Tracked in LAB-360; firmware-side items are on LAB-343.GET_TELEMETRY_BLOCKdefaults to 178 record bytes (the firmware's budget), not 180. The firmware clamps, so nothing changes on the wire.GET_PATTERN_INFObyte 11 is decoded asdutyCycle(the firmware name);stretchstays as an alias. The Studio and Console readdutyCycleand fall back tostretch, so a stale cached wire module still works.01 C1/01 C2on the IP and controller-info encoders, theGET_CRASHREPORTgate is 0xCB flags bit 3 (not the telemetry bit),GET_AO_VOLTAGEis a DAC register readback.CLAUDE.md: crash-report gate text corrected.Tier
next candidate
Release notes
none
Test plan
pixi run test(73/73 files)pixi run prettier --checkon the changed JS filesarena_studio.htmlandarena_console.htmlIn-lab testing (on Next, between sessions)
cc/cf/cs).arena_console.html): pattern info shows a "duty cycle" row.The wider bench plan for the open follow-ups (stray input at connect,
g6-encoding.jsrow order, new encoders, Will's hardware suite) is in LAB-360.🤖 Generated with Claude Code