You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presented here are diagnostics as instructed for an XP-Pen Artist 12 (2nd Gen), 28bd:094a, and its product page. The "2nd Gen" appears to be a significant revision--I couldn't find the VID:PID here.
They provide "a driver" download, though it appears to my untrained eye to depend on X, and doesn't work with Wayland. Dumping its handshake, however, led me to make my own evdev, uinput proof of concept, which you're welcome to crib for other important values. In particular: the layout of bytes coming from Interface 2 is pretty transparent, but the exact sequence of bytes used to kick it into a mode where it communicates over the endpoints in Interface 2 is quite opaque (to me, at least).
While doing the collection, I also attempted to collect dumps after sending the handshake from the program above--however (and this could just be my naivete) the usbhid-dump program invariably terminated with an EIO, Failed to set report protocol (even with -i 2). I included the descriptors again, just in case there's a variance: they're in the "special" file set.
Without further ado, the files in the default operating mode:
My driver works under wayland however you will have issues mapping the pen/stylus to the pen display if you are using multiple displays as no compositor except sway is able to do so at the moment. Works fine if you are using X11 of course.
Hello, folks!
Presented here are diagnostics as instructed for an
XP-Pen Artist 12 (2nd Gen)
,28bd:094a
, and its product page. The "2nd Gen" appears to be a significant revision--I couldn't find the VID:PID here.They provide "a driver" download, though it appears to my untrained eye to depend on X, and doesn't work with Wayland. Dumping its handshake, however, led me to make my own evdev, uinput proof of concept, which you're welcome to crib for other important values. In particular: the layout of bytes coming from Interface 2 is pretty transparent, but the exact sequence of bytes used to kick it into a mode where it communicates over the endpoints in Interface 2 is quite opaque (to me, at least).
While doing the collection, I also attempted to collect dumps after sending the handshake from the program above--however (and this could just be my naivete) the
usbhid-dump
program invariably terminated with anEIO
,Failed to set report protocol
(even with-i 2
). I included the descriptors again, just in case there's a variance: they're in the "special" file set.Without further ado, the files in the default operating mode:
... also available as a gzipped tarball.
After the handshake--note that the captures were done on
usbmon0
, with Wireshark, due to the aforementioned issue withusbhid-dump
:...apologies that they're
pcapng.gz
--that's the format GitHub will accept. Here's the tarball, without those files compressed.Let me know if you need anything else!
The text was updated successfully, but these errors were encountered: