docs(traffic): full Pangolin protocol report, from all ten captures - #117
Merged
Conversation
Contributor
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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
tools/traffic/PROTOCOL.mdbecomes a standalone report you can work a show day from, after re-runningdecodeover all ten captures. Two findings in it are new:The hand-sent OSC was addressed to zones that don't exist.
00-osc-only.pcapngcontains 90 packets, 15 each to zones 240–245, while the only zones BEYOND has ever broadcast are 1–6. The{n}comes straight fromprojectorMap[i]inencodeBeyondMessages, so this is a project-config fault independent of the closed RGBA panel — a second reason those sends could not have changed a colour.Frames and control messages share one budget. Idle captures: ~62 frames/s, zero
0x00010E02control messages. The paint capture: 16–23 frames/s plus 31–37 control/s, with the combined rate pinned near 53–54/s. So control is interleaved while live content changes, at the cost of frames. Also documents a previously unrecorded message type,0x00028010— 32 B, all-zero body, FB4→BEYOND, the one body in the protocol that isn't opaque.The report now also has: the device/port inventory (including
53.5reconnecting on a different ephemeral port between capture sets, which is the cheapest chance at the never-captured handshake), a worked hex example of the 32-byte header, a per-capture evidence table, an explicit confirmed-vs-inferred split, a four-item "what's missing and the exact capture that closes it" section, and a diagnostic playbook keyed to wire evidence.One code change, from spotting nonsense in the output:
Link to Devin session: https://app.devin.ai/sessions/ec43152136134467a853ec0bbf783ea9
Requested by: @pyramation