Re: [DIGImend-users] DIGImend: Need frame button diagnostics
Brought to you by:
spb_nick
Menu
▾
▴
Re: [DIGImend-users] DIGImend: Need frame button diagnostics
|
From: Benjamin T. <ben...@re...> - 2015-03-17 00:43:45
|
Hi Sergei, I bet Nick is already asleep in his timezone, so I answer :) On Mar 17 2015 or thereabouts, Sergey 'Jin' Bostandzhyan wrote: > Hi Nick, > > On Mon, Mar 16, 2015 at 11:47:05PM +0200, Nikolai Kondrashov wrote: > > Benjamin Tissoires and me are working on making digimend-kernel-drivers > > compatible with current and future versions of the Wacom driver > > (xf86-input-wacom), especially with regard to adding support for remapping > > frame buttons to arbitrary key combinations. > > thank you guys! It would be really cool to get this to work. > > > This concerns Huion, Yiynova, Ugee tablets, as well as UC-Logic TWHA60 v3 > > tablet. > > I have a Huion H610, you pinged me on IRC earlier and I tried xsetwacom with > the latest master head of the kernel driver. > > I get the following devices: > > xsetwacom --list devices > HUION PenTablet stylus id: 16 type: STYLUS > HUION PenTablet eraser id: 17 type: ERASER > HUION PenTablet pad id: 18 type: PAD > HUION PenTablet stylus id: 19 type: STYLUS > These names don't look like the ones I would have expected. You should have only one "HUION PenTablet Pen stylus", no "HUION PenTablet eraser" and one "HUION PenTablet Pad pad". So I think the new master of hid-uclogic is not handling the device as it should. can you output the few new lines in the dmesg while you are plugging the tablet? > > The only one that actually worked was id: 19, I did: > > xsetwacom --set 19 button 3 key + > > ...and then a click on the stylus key indeed produced a + > > I was however not able to map the keys of id's 16-18, I tried some > combinations and all I got was: > > xsetwacom --set 16 button 1 key + > Property 'Wacom Button Actions' does not exist on device. > > At the same time buttons >3 on device id 19 produced the following > error: > > xsetwacom --set 19 button 4 key + > Invalid offset into Wacom Button Actions property. > > I guess that's OK, because the stylus only has 3 buttons (the tip + 2 extra > buttons), but I'd also expect the pad (id 18) to be mappable. > > At the same time I am not sure what id's 16 + 17 are? xsetwacom sems to work OK (3 buttons on the stylus as you said). 16 and 17 are interfaces declared in the device but are not used. The new master should remove them. > > > We would like to ask everyone owning one of these tablets to please take some > > diagnostics information from their tablets and send them in reply to this > > message. > > [...] > > > Please send the output of either of these commands, plus "lsusb -v" output. > > ./uclogic-probe 6 3 > M 48 00 55 00 49 00 4F 00 4E 00 00 00 00 00 00 00 > P 50 00 65 00 6E 00 54 00 61 00 62 00 6C 00 65 00 74 00 00 00 > S 64 0E 03 40 9C A8 61 03 00 FF 07 A0 0F 08 00 > S 65 04 03 20 A0 > S 6E 04 03 00 30 > S 79 14 03 48 00 41 00 36 00 30 00 00 00 00 00 00 00 00 00 00 00 > S 7A 08 03 01 08 00 00 00 00 > S 7B 0C 03 48 00 4B 00 20 00 4F 00 6E 00 > > > > Part of the lsusb -v output: > > Bus 006 Device 003: ID 256c:006e > Device Descriptor: > bLength 18 > bDescriptorType 1 > bcdUSB 1.10 > bDeviceClass 0 (Defined at Interface level) > bDeviceSubClass 0 > bDeviceProtocol 0 > bMaxPacketSize0 64 > idVendor 0x256c > idProduct 0x006e > bcdDevice 0.00 > iManufacturer 5 HUION > iProduct 6 PenTablet > iSerial 0 > bNumConfigurations 1 > Configuration Descriptor: > bLength 9 > bDescriptorType 2 > wTotalLength 84 > bNumInterfaces 3 > bConfigurationValue 1 > iConfiguration 0 > bmAttributes 0xa0 > (Bus Powered) > Remote Wakeup > MaxPower 100mA > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 0 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 179 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x81 EP 1 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 2 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 1 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 1 Boot Interface Subclass > bInterfaceProtocol 2 Mouse > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 244 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x82 EP 2 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0010 1x 16 bytes > bInterval 2 > Interface Descriptor: > bLength 9 > bDescriptorType 4 > bInterfaceNumber 2 > bAlternateSetting 0 > bNumEndpoints 1 > bInterfaceClass 3 Human Interface Device > bInterfaceSubClass 0 No Subclass > bInterfaceProtocol 0 None > iInterface 0 > HID Device Descriptor: > bLength 9 > bDescriptorType 33 > bcdHID 1.11 > bCountryCode 0 Not supported > bNumDescriptors 1 > bDescriptorType 34 Report > wDescriptorLength 92 > Report Descriptors: > ** UNAVAILABLE ** > Endpoint Descriptor: > bLength 7 > bDescriptorType 5 > bEndpointAddress 0x83 EP 3 IN > bmAttributes 3 > Transfer Type Interrupt > Synch Type None > Usage Type Data > wMaxPacketSize 0x0008 1x 8 bytes > bInterval 8 > Device Status: 0x0000 > (Bus Powered) > > > I hope that helps, ping me if you need anything else. Thank you! Can you just confirm that you have an Huion H610 and not the "H610 Pro"? I have the Pro and get the same output than you, but I thought the H610 not Pro was declared as "HUION H610". Cheers, Benjamin > > Kind regards, > Jin > |
