docs(traffic): what the sliced captures settled, and flag FB4s getting no frames - #115
Merged
Merged
Conversation
…g no frames The show machine's 169.254.45.4 announces itself on 9022 in every capture but has zero TCP 3348 traffic in any of them: BEYOND streams to five of the six FB4s, so that projector could only ever be dark. decode now reports it per device, since being on the network and being driven are different things. PROTOCOL.md also records why OSC can land and still do nothing (RGBA panel closed = no 16062 broadcast and gated livecontrol addresses), that no capture yet contains a SYN so the connection setup remains unseen, that 9022 is only discovery while 3348 carries the ~62/s frames, and the documented FB4 OSC/ArtNet routes that don't involve this protocol at all.
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
A second, action-sliced capture set from the show machine (idle baseline → hand-sent OSC →
signals probewalk → idle tail, 8 files) turned up one thing worth acting on, sodecodenow reports it andPROTOCOL.mdrecords the rest.169.254.45.4(FB4E, id 566604) is getting no frames. It announces itself on UDP 9022 in every capture we have, but has zero TCP 3348 traffic in any of them — BEYOND streams to five of the six FB4s, so that projector could only ever have been dark. Announcing and being driven are different things, and only the second one lights a laser, so the device list now says which:Documented, not code:
livecontrolcolour addresses, so "arrived" and "changed the colour" were never the same claim. Silence on 16062 is now written down as the first thing to check.operation_mode, and in ArtNet mode is a 16-/39-channel DMX fixture. Both control colour/brightness over SD-card content rather than arbitrary geometry. Untested — noted so it isn't rediscovered from scratch.31 tests (4 new:
streaming_ipsboth directions, discovery traffic isn't a stream, and the flag firing/not firing per device).Link to Devin session: https://app.devin.ai/sessions/ec43152136134467a853ec0bbf783ea9
Requested by: @pyramation