Add Monster Tulpar TD3 AIO LCD control-traffic captures - #22
Open
orcunulutas wants to merge 1 commit into
Open
Conversation
USBPcap captures of the 1d6b:0130 controller recorded while the official Monster Windows application was running (Windows 11 25H2). Filtered to the target device only; media upload traffic removed. The usb2 file contains brightness and rotate commands with device responses; the other files cover enumeration and keep-alive polling. See the folder README for details.
14 tasks
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
1 participant
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
USB traffic captures for the Monster Tulpar TD3 AIO LCD controller (
1d6b:0130).These are the raw captures from which the device control protocol in
liquidctl/liquidctl#921 was
reconstructed. Recording them here as requested in that PR's checklist.
Contents
Monster Tulpar TD3 AIO LCD/01 - control traffic - orcunulutas/:monster-td3-usb2.pcapngPOST brightness+POST rotatecommands with device responsesmonster-td3-usb3.pcapngmonster-td3-usbpcap.pcapngMonster application was running, on 2026-08-21.
address 8); all traffic of other devices removed.
0x5c-prefixed block records and theirPOST transport 1/POST transported 1framing are not included, so thefiles contain no screen image payloads. (A reference copy of the media
captures can be provided to maintainers on request.)
Notes
The official Windows application keeps the LCD awake by uploading a fresh
.osdfile roughly once per second, so thePOST power/STATE allkeep-alive cycle documented in the liquidctl protocol doc was reconstructed
from separate Linux testing rather than these Windows captures. The folder
README describes all of this in detail.
Related: liquidctl/liquidctl#921