digimend-users Mailing List for DIGImend (Page 3)
Brought to you by:
spb_nick
Menu
▾
▴
digimend-users — General discussion and user support
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(58) |
May
(72) |
Jun
(24) |
Jul
|
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(5) |
Feb
(23) |
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(7) |
Nov
(31) |
Dec
(11) |
| 2014 |
Jan
(13) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(10) |
Sep
(13) |
Oct
(15) |
Nov
(49) |
Dec
(4) |
| 2015 |
Jan
(49) |
Feb
(62) |
Mar
(81) |
Apr
(10) |
May
(4) |
Jun
(6) |
Jul
(17) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(8) |
| 2016 |
Jan
(8) |
Feb
(5) |
Mar
(7) |
Apr
(7) |
May
(3) |
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
|
From: Vince H. <Vi...@Pl...> - 2015-08-16 02:10:13
|
Fedora Kernel 4.1.4.100
I'm getting modprobe not found again....
Aug 11 19:10:21 desk2 hid-rebind: /sbin/hid-rebind: line 64: modprobe:
command not found
Aug 11 19:10:21 desk2 hid-rebind: /sbin/hid-rebind: line 64: modprobe:
command not found
Aug 11 19:10:21 desk2 hid-rebind: /sbin/hid-rebind: line 64: modprobe:
command not found
I compile and install v5 drivers
[vince@desk2 ~]$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech 2.4GHz Cordless Desktop id=9 [slave pointer (2)]
⎜ ↳ HUION PenTablet Pen stylus id=10 [slave pointer (2)]
⎜ ↳ HUION PenTablet Mouse id=11 [slave pointer (2)]
⎜ ↳ HUION PenTablet Consumer Control id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Logitech 2.4GHz Cordless Desktop id=8 [slave keyboard (3)]
↳ HUION PenTablet Keyboard id=12 [slave keyboard (3)]
↳ HUION PenTablet System Control id=14 [slave keyboard (3)]
[vince@desk2 ~]$ xsetwacom --list
HUION PenTablet Pen stylus id: 10 type: STYLUS
[vince@desk2 ~]$ xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech 2.4GHz Cordless Desktop id=9 [slave pointer (2)]
⎜ ↳ HUION PenTablet Pen stylus id=10 [slave pointer (2)]
⎜ ↳ HUION PenTablet Mouse id=11 [slave pointer (2)]
⎜ ↳ HUION PenTablet Consumer Control id=13 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Logitech 2.4GHz Cordless Desktop id=8 [slave keyboard (3)]
↳ HUION PenTablet Keyboard id=12 [slave keyboard (3)]
↳ HUION PenTablet System Control id=14 [slave keyboard (3)]
[vince@desk2 ~]$
[vince@desk2 ~]$ xsetwacom --set 10 button 1 key ctrl z
[vince@desk2 ~]$ xsetwacom --set 10 button 2 key shift e
[vince@desk2 ~]$ xsetwacom --set 10 button 3 key n
[vince@desk2 ~]$ xsetwacom --set 10 button 8 key shift =
Invalid offset into Wacom Button Actions property.
sigh.
---------------
Vince
|
|
From: Scott W. <sa...@um...> - 2015-08-02 16:01:32
|
I was 95% sure, but just to make sure, I tried again, this time holding it from the back (where there are no buttons). Same thing. Oh well, guess the new pen is busted. Not too huge of a deal, since Krita seems to ignore these right clicks, and it still honors real right clicks. Thanks! Scott On Sat, Aug 1, 2015 at 3:59 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Scott, > > On 07/26/2015 07:36 PM, Scott Walls wrote: >> >> Thanks so much for your help! I've attached a tarball of the output. > > > Alright, I see some right button bits set in the reports. Unless you were > clicking the top barrel button accidentally or intentionally, then your > tablet > or your pen is faulty and it's not a problem with the driver. > > Are you sure you weren't pressing the top barrel button somehow during the > test? > > Nick |
|
From: Nikolai K. <sp...@gm...> - 2015-08-01 10:59:25
|
Hi Scott, On 07/26/2015 07:36 PM, Scott Walls wrote: > Thanks so much for your help! I've attached a tarball of the output. Alright, I see some right button bits set in the reports. Unless you were clicking the top barrel button accidentally or intentionally, then your tablet or your pen is faulty and it's not a problem with the driver. Are you sure you weren't pressing the top barrel button somehow during the test? Nick |
|
From: Scott W. <sa...@um...> - 2015-07-26 16:36:38
|
Nick, Thanks so much for your help! I've attached a tarball of the output. Thanks, Scott PS: Sorry, I couldn't find any instructions on whether to post on the top or the bottom, so I went with the top because that's why my client does by default. On Sun, Jul 26, 2015 at 4:04 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Scott, > > On 07/23/2015 05:30 PM, Scott Walls wrote: > >> Sorry, it was late yesterday and I realized that the thread "Patching the >> hid-uclogic driver for UC-Logic tablet TWHA60 v3" is not old at all. So, I >> installed the latest master, and the problem is more-or-less fixed! Thanks >> so much! >> > > Glad to hear it works for you! > > However, now there's a problem where when I totally remove my pen from the >> tablet, it sends a right-click, which is pretty annoying. >> >> It is worth noting, possibly, that my pen was broken, so I'm now using a >> slightly different replacement pen. Monoprice claimed it would be totally >> compatible, though, and we know Monoprice is always right ;) >> > > This is strange. > > Could you please send the output of "usbhid-dump -m 5543:0781 -es" where > you > move the pen onto the tablet surface and then remove it, repeatedly? > > Thank you. > > Nick > |
|
From: Nikolai K. <sp...@gm...> - 2015-07-26 11:04:11
|
Hi Scott, On 07/23/2015 05:30 PM, Scott Walls wrote: > Sorry, it was late yesterday and I realized that the thread "Patching the > hid-uclogic driver for UC-Logic tablet TWHA60 v3" is not old at all. So, I > installed the latest master, and the problem is more-or-less fixed! Thanks > so much! Glad to hear it works for you! > However, now there's a problem where when I totally remove my pen from the > tablet, it sends a right-click, which is pretty annoying. > > It is worth noting, possibly, that my pen was broken, so I'm now using a > slightly different replacement pen. Monoprice claimed it would be totally > compatible, though, and we know Monoprice is always right ;) This is strange. Could you please send the output of "usbhid-dump -m 5543:0781 -es" where you move the pen onto the tablet surface and then remove it, repeatedly? Thank you. Nick |
|
From: Christopher B. <chr...@gm...> - 2015-07-23 16:21:32
|
On Wed, 22 Jul 2015 17:55:16 -0600 Simon Roberts <dan...@gm...> wrote: >Hi all, I was unable to subscribe to this list (errors from the mail >list manager program on sourceforge, claiming there was a bug in the >system?!) so I'm hoping this works anyway. > >I'm using a Huion610Pro tablet with the digimend driver (very nice, >thank you!) > >I am wondering, however if I can configure it to work on just one of >the two monitors on my system. I find that when it spreads it's >"reach" across about 4000 horizontal pixels from two monitors side by >side, the resolution is rather low. I don't need it on more than the >one window that I'm doing graphics on. The wacom driver seems to be >able to do this, through the Ubuntu settings panel, but I find no >equivalent for this. > >Can it be done? Can anyone point me at how? > >TIA, >Simon Attached is my script to do this on a triple head setup. You'll just need to edit the top config part to add your monitor ports. -- Regards, Christopher Barry Random geeky fortune: The Killer Ducks are coming!!! |
|
From: Scott W. <sa...@um...> - 2015-07-23 14:31:18
|
Sorry, it was late yesterday and I realized that the thread "Patching the hid-uclogic driver for UC-Logic tablet TWHA60 v3" is not old at all. So, I installed the latest master, and the problem is more-or-less fixed! Thanks so much! However, now there's a problem where when I totally remove my pen from the tablet, it sends a right-click, which is pretty annoying. It is worth noting, possibly, that my pen was broken, so I'm now using a slightly different replacement pen. Monoprice claimed it would be totally compatible, though, and we know Monoprice is always right ;) Scott On Wed, Jul 22, 2015 at 8:31 PM, Scott Walls <sa...@um...> wrote: > Hello! > > First of all, let me say in advance that I'm sorry if this is a repost. I > looked through the archives and haven't found anything that both is exactly > my problem and has an answer. There are a lot of similar things, but many > of them are out-of-date and some of the don't have answers. > > Actual description of the problem: > --- > So sometimes the tablet works for a couple of seconds, but something > happens and it starts working like a trackpad instead of a tablet. The > mouse only moves when I keep pressure on, and it's relative rather than > absolute. > > I found in a previous thing in the archive the following fix: > "quirks=0x5543:0x0781:0x0040", but all this seems to do is revert it back > to its initial state of working for about 3 seconds. > --- > > If you need anything pasted, xinput, relevant dmesg lines, Xorg.0.log, or > any other diagnostics, I know my way well enough around them (just tell me > whether to zip them or pastebin or just put them in-line). > > I'm fairly confident my tablet is the v3, but it's vaguely possible that > it's the v2. If you know of a way to tell, I can look for you. > > I've got a 64-bit machine running Arch, and I've got this kernel: > 4.1.2-2-ARCH #1. I'm pretty sure it's going through xf86-input-evdev. > > That's all of the info I can think to give off-hand, but obviously > anything you need, I can get. > > Thanks so much! > Scott Walls > |
|
From: Simon R. <dan...@gm...> - 2015-07-23 13:24:33
|
Indeed, I got the transformation matrix applied manually, so I'm sure I'll have it going smoothly soon. Again, many thanks, this was a huge help! Cheers, Simon On Thu, Jul 23, 2015 at 7:06 AM, Simon Roberts < dan...@gm...> wrote: > Ah, this is very helpful Martin, many thanks. > > I'm not familiar with perl, so it took a while to work out why > Data::Printer wasn't present and to make it so, and now it complains that > the Huion shows up as three separate devices! > > Somehow, the script issues an error "Warning: There are multiple devices > matching HUION PenTablet", but that text seems to come from one of the > commands it's issuing, not from the script itself. I think when I find > that, I should be able to make things work. > > Anyway, it's a great relief to know that it can be done at least. > > Thanks again, > Simon > > > On Thu, Jul 23, 2015 at 12:09 AM, Martin Rusko <mar...@gm...> > wrote: > >> Hi Simon, >> >> what you want can be done by calculating and setting Coordinate >> Transformation Matrix. You can find more information at >> https://wiki.archlinux.org/index.php/Calibrating_Touchscreen. >> >> Attached you can find small perl script which will do this for you. It >> uses xrandr and xinput commands. Let say xrandr says you have two monitors, >> LVDS1 and HDMI3. If you want your tablet to work on HDMI3 monitor, you will >> use it as ./tass.pl HDMI3. Or ./tass.pl LVDS1 will set X Window to have >> tablet for laptop screen. Calling ./tass.pl should just reset CTM, in >> other words tablet will be stretched across multiple monitors. >> >> The script is rather crude, hardcoded to work for tablets I have. But >> because you have also HUION tablet, it may work for you as well. Or will >> need some modification. >> >> Best Regards, >> Martin >> >> On Thu, Jul 23, 2015 at 1:55 AM, Simon Roberts < >> dan...@gm...> wrote: >> >>> Hi all, I was unable to subscribe to this list (errors from the mail >>> list manager program on sourceforge, claiming there was a bug in the >>> system?!) so I'm hoping this works anyway. >>> >>> I'm using a Huion610Pro tablet with the digimend driver (very nice, >>> thank you!) >>> >>> I am wondering, however if I can configure it to work on just one of the >>> two monitors on my system. I find that when it spreads it's "reach" across >>> about 4000 horizontal pixels from two monitors side by side, the resolution >>> is rather low. I don't need it on more than the one window that I'm doing >>> graphics on. The wacom driver seems to be able to do this, through the >>> Ubuntu settings panel, but I find no equivalent for this. >>> >>> Can it be done? Can anyone point me at how? >>> >>> TIA, >>> Simon >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> DIGImend-users mailing list >>> DIG...@li... >>> https://lists.sourceforge.net/lists/listinfo/digimend-users >>> >>> >> > |
|
From: Simon R. <dan...@gm...> - 2015-07-23 13:06:28
|
Ah, this is very helpful Martin, many thanks. I'm not familiar with perl, so it took a while to work out why Data::Printer wasn't present and to make it so, and now it complains that the Huion shows up as three separate devices! Somehow, the script issues an error "Warning: There are multiple devices matching HUION PenTablet", but that text seems to come from one of the commands it's issuing, not from the script itself. I think when I find that, I should be able to make things work. Anyway, it's a great relief to know that it can be done at least. Thanks again, Simon On Thu, Jul 23, 2015 at 12:09 AM, Martin Rusko <mar...@gm...> wrote: > Hi Simon, > > what you want can be done by calculating and setting Coordinate > Transformation Matrix. You can find more information at > https://wiki.archlinux.org/index.php/Calibrating_Touchscreen. > > Attached you can find small perl script which will do this for you. It > uses xrandr and xinput commands. Let say xrandr says you have two monitors, > LVDS1 and HDMI3. If you want your tablet to work on HDMI3 monitor, you will > use it as ./tass.pl HDMI3. Or ./tass.pl LVDS1 will set X Window to have > tablet for laptop screen. Calling ./tass.pl should just reset CTM, in > other words tablet will be stretched across multiple monitors. > > The script is rather crude, hardcoded to work for tablets I have. But > because you have also HUION tablet, it may work for you as well. Or will > need some modification. > > Best Regards, > Martin > > On Thu, Jul 23, 2015 at 1:55 AM, Simon Roberts < > dan...@gm...> wrote: > >> Hi all, I was unable to subscribe to this list (errors from the mail list >> manager program on sourceforge, claiming there was a bug in the system?!) >> so I'm hoping this works anyway. >> >> I'm using a Huion610Pro tablet with the digimend driver (very nice, thank >> you!) >> >> I am wondering, however if I can configure it to work on just one of the >> two monitors on my system. I find that when it spreads it's "reach" across >> about 4000 horizontal pixels from two monitors side by side, the resolution >> is rather low. I don't need it on more than the one window that I'm doing >> graphics on. The wacom driver seems to be able to do this, through the >> Ubuntu settings panel, but I find no equivalent for this. >> >> Can it be done? Can anyone point me at how? >> >> TIA, >> Simon >> >> >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> DIGImend-users mailing list >> DIG...@li... >> https://lists.sourceforge.net/lists/listinfo/digimend-users >> >> > |
|
From: Martin R. <mar...@gm...> - 2015-07-23 06:09:20
|
Hi Simon, what you want can be done by calculating and setting Coordinate Transformation Matrix. You can find more information at https://wiki.archlinux.org/index.php/Calibrating_Touchscreen. Attached you can find small perl script which will do this for you. It uses xrandr and xinput commands. Let say xrandr says you have two monitors, LVDS1 and HDMI3. If you want your tablet to work on HDMI3 monitor, you will use it as ./tass.pl HDMI3. Or ./tass.pl LVDS1 will set X Window to have tablet for laptop screen. Calling ./tass.pl should just reset CTM, in other words tablet will be stretched across multiple monitors. The script is rather crude, hardcoded to work for tablets I have. But because you have also HUION tablet, it may work for you as well. Or will need some modification. Best Regards, Martin On Thu, Jul 23, 2015 at 1:55 AM, Simon Roberts < dan...@gm...> wrote: > Hi all, I was unable to subscribe to this list (errors from the mail list > manager program on sourceforge, claiming there was a bug in the system?!) > so I'm hoping this works anyway. > > I'm using a Huion610Pro tablet with the digimend driver (very nice, thank > you!) > > I am wondering, however if I can configure it to work on just one of the > two monitors on my system. I find that when it spreads it's "reach" across > about 4000 horizontal pixels from two monitors side by side, the resolution > is rather low. I don't need it on more than the one window that I'm doing > graphics on. The wacom driver seems to be able to do this, through the > Ubuntu settings panel, but I find no equivalent for this. > > Can it be done? Can anyone point me at how? > > TIA, > Simon > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > DIGImend-users mailing list > DIG...@li... > https://lists.sourceforge.net/lists/listinfo/digimend-users > > |
|
From: Scott W. <sa...@um...> - 2015-07-23 03:31:32
|
Hello! First of all, let me say in advance that I'm sorry if this is a repost. I looked through the archives and haven't found anything that both is exactly my problem and has an answer. There are a lot of similar things, but many of them are out-of-date and some of the don't have answers. Actual description of the problem: --- So sometimes the tablet works for a couple of seconds, but something happens and it starts working like a trackpad instead of a tablet. The mouse only moves when I keep pressure on, and it's relative rather than absolute. I found in a previous thing in the archive the following fix: "quirks=0x5543:0x0781:0x0040", but all this seems to do is revert it back to its initial state of working for about 3 seconds. --- If you need anything pasted, xinput, relevant dmesg lines, Xorg.0.log, or any other diagnostics, I know my way well enough around them (just tell me whether to zip them or pastebin or just put them in-line). I'm fairly confident my tablet is the v3, but it's vaguely possible that it's the v2. If you know of a way to tell, I can look for you. I've got a 64-bit machine running Arch, and I've got this kernel: 4.1.2-2-ARCH #1. I'm pretty sure it's going through xf86-input-evdev. That's all of the info I can think to give off-hand, but obviously anything you need, I can get. Thanks so much! Scott Walls |
|
From: Simon R. <dan...@gm...> - 2015-07-22 23:55:39
|
Hi all, I was unable to subscribe to this list (errors from the mail list manager program on sourceforge, claiming there was a bug in the system?!) so I'm hoping this works anyway. I'm using a Huion610Pro tablet with the digimend driver (very nice, thank you!) I am wondering, however if I can configure it to work on just one of the two monitors on my system. I find that when it spreads it's "reach" across about 4000 horizontal pixels from two monitors side by side, the resolution is rather low. I don't need it on more than the one window that I'm doing graphics on. The wacom driver seems to be able to do this, through the Ubuntu settings panel, but I find no equivalent for this. Can it be done? Can anyone point me at how? TIA, Simon |
|
From: yoquesé n. <por...@gm...> - 2015-07-12 19:23:21
|
Bus 003 Device 004: 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 H58L
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.0b
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 177
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.0b
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) |
|
From: Dmitry U. <lo...@gm...> - 2015-07-09 18:02:32
|
After some research I've found solution with wacom driver. I've tried to assign buttons by index beginning with 1, but xsetwacom expects the button number, e.g. 1,2,3,8,9,10,11,12, not the 1,2,3,4,5,6,7,8 as I expected previously. The 4-7 buttons has special role in X. Please ignore my previous message. 2015-07-09 19:28 GMT+03:00 Dmitry Utkin <lo...@gm...>: > Hello, > > I have UGEE M708 <http://ugee.net/products_view.asp?articleid=28> tablet > and trying to get it working with digimend drivers under Ubuntu 14.04 amd64. > > The tablet is recognized as 5543:0081 UC-Logic Technology Corp. > > xinput output: > > $ xinput | grep UC > ⎜ ↳ UC-LOIC TABLET 1060 Pen id=12 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 Pad id=13 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 Mouse id=14 [slave pointer (2)] > ⎜ ↳ UC-LOIC TABLET 1060 Consumer Control id=16 [slave pointer (2)] > ↳ UC-LOIC TABLET 1060 System Control id=17 [slave keyboard (3)] > ↳ UC-LOIC TABLET 1060 Keyboard id=15 [slave keyboard (3)] > > > > Everything seems to work in exception the tablet's buttons are recognized > as mouse buttons: 1, 2, 3, 8, 9, 10, 11, 12. > > > Is there any method to get tablet's buttons recognized as a keyboard keys? > > Previously I used wizardpen driver, but it don't work with pressure > sensitivity in GTK3 and QT-based apps. > > > To resolve the problem i've tried several options > <http://sourceforge.net/p/digimend/mailman/message/33639528/>: custom > hwdb, wacom driver, map mouse keys to keyboard. But didn't find acceptable > solution - nothing solves my problem completely. > > > Wacom driver is partially solves the problem, but it recognizes only first > 4 buttons of 8. When I try to assign 5th or next buttons I see the message: > > Unsupported offset into 'Wacom Button Actions' property. > > > Thanks in advance. > > -- > Best regards, Dmitry Utkin. > > E-Mail: lo...@gm... > Skype: loentar > > -- Best regards, Dmitry Utkin. E-Mail: lo...@gm... Skype: loentar |
|
From: Dmitry U. <lo...@gm...> - 2015-07-09 16:28:48
|
Hello, I have UGEE M708 <http://ugee.net/products_view.asp?articleid=28> tablet and trying to get it working with digimend drivers under Ubuntu 14.04 amd64. The tablet is recognized as 5543:0081 UC-Logic Technology Corp. xinput output: $ xinput | grep UC ⎜ ↳ UC-LOIC TABLET 1060 Pen id=12 [slave pointer (2)] ⎜ ↳ UC-LOIC TABLET 1060 Pad id=13 [slave pointer (2)] ⎜ ↳ UC-LOIC TABLET 1060 Mouse id=14 [slave pointer (2)] ⎜ ↳ UC-LOIC TABLET 1060 Consumer Control id=16 [slave pointer (2)] ↳ UC-LOIC TABLET 1060 System Control id=17 [slave keyboard (3)] ↳ UC-LOIC TABLET 1060 Keyboard id=15 [slave keyboard (3)] Everything seems to work in exception the tablet's buttons are recognized as mouse buttons: 1, 2, 3, 8, 9, 10, 11, 12. Is there any method to get tablet's buttons recognized as a keyboard keys? Previously I used wizardpen driver, but it don't work with pressure sensitivity in GTK3 and QT-based apps. To resolve the problem i've tried several options <http://sourceforge.net/p/digimend/mailman/message/33639528/>: custom hwdb, wacom driver, map mouse keys to keyboard. But didn't find acceptable solution - nothing solves my problem completely. Wacom driver is partially solves the problem, but it recognizes only first 4 buttons of 8. When I try to assign 5th or next buttons I see the message: Unsupported offset into 'Wacom Button Actions' property. Thanks in advance. -- Best regards, Dmitry Utkin. E-Mail: lo...@gm... Skype: loentar |
|
From: Nikolai K. <sp...@gm...> - 2015-07-06 09:56:47
|
On 07/06/2015 11:30 AM, Jude Hungerford wrote: > Hi, > > I just wanted to let you know that the kernel drivers work for the Huion H58L (mentioned in the mailing list archive, but not visible in the table on the main site). > > I have kernel version 4.0.7 but I'm sure it would work with any version which supports the K58. > > Thanks for your great work making tablets accessible to Linux users, Thank you for the report, Jude! I'll add the tablet to the site on the weekend. Nick |
|
From: Jude H. <smi...@gm...> - 2015-07-06 08:30:45
|
Hi, I just wanted to let you know that the kernel drivers work for the Huion H58L (mentioned in the mailing list archive, but not visible in the table on the main site). I have kernel version 4.0.7 but I'm sure it would work with any version which supports the K58. Thanks for your great work making tablets accessible to Linux users, -- -- |
|
From: Nikolai K. <sp...@gm...> - 2015-06-08 18:49:48
|
Hi Dan, On 06/08/2015 12:41 AM, Dan Roberts wrote: > In case anyone is curious, I bought a replacement pen from amazon that > claimed to be compatible with the Huion H610 and my monoprice rebranded > tablet. I've only been using it for 10 minutes but it works perfectly, my > other pen is still generating "random" right and left click events when it's > in proximity with the tablet. So yes, *hardware failure, and in the pen > thankfully, not the tablet. * > * > * > For giggles, I tried disassembling my old (broken) pen as described here: > https://www.youtube.com/watch?v=qsrin9JXSQw and adjusting the tightness of > the white piece which carries the sense coil. *I immediately broke the > delicate coil wires*, but resoldered them successfully. Unfortunately, it > didn't resolve my issue (the random full-pressure events) I suspect that > with further adjustment of the white piece, I could fix my old pen, but the > coil wires are *very delicate* and so I don't really recommend doing it > unless it's a last resort before ordering a replacement. I may try again > since I have a replacement pen now. > > *TL;DR: My random "full pressure" events were apparently resolved by > replacing the pen (~15USD), there is some possibility of fixing the issue > also by disassembling the pen but it's easy to do more damage than good.* That's a great and educating story! Also a good example to refer to. Thank you for the update. Glad it worked for you! Nick |
|
From: Dan R. <ade...@gm...> - 2015-06-07 21:41:28
|
In case anyone is curious, I bought a replacement pen from amazon that claimed to be compatible with the Huion H610 and my monoprice rebranded tablet. I've only been using it for 10 minutes but it works perfectly, my other pen is still generating "random" right and left click events when it's in proximity with the tablet. So yes, *hardware failure, and in the pen thankfully, not the tablet. * For giggles, I tried disassembling my old (broken) pen as described here: https://www.youtube.com/watch?v=qsrin9JXSQw and adjusting the tightness of the white piece which carries the sense coil. *I immediately broke the delicate coil wires*, but resoldered them successfully. Unfortunately, it didn't resolve my issue (the random full-pressure events) I suspect that with further adjustment of the white piece, I could fix my old pen, but the coil wires are *very delicate* and so I don't really recommend doing it unless it's a last resort before ordering a replacement. I may try again since I have a replacement pen now. *TL;DR: My random "full pressure" events were apparently resolved by replacing the pen (~15USD), there is some possibility of fixing the issue also by disassembling the pen but it's easy to do more damage than good.* Cheers, Dan On Sun, Mar 29, 2015 at 9:09 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Dan, > > On 03/28/2015 11:39 PM, Dan Roberts wrote: > >> Hi Everyone, >> I've had my Huion H610 for almost a year now, and it has exhibited >> the same behavior the entire time I've owned it, across multiple drivers >> versions, and across changing the pen "tip". >> >> Occasionally when the pen is not touching the tablet, but in proximity, I >> receive events for full pressure (2047), sometimes in rapid succession. >> Pressure will spike from 0 to 2047 and back. When drawing in Gimp it sort >> of looked like the tool was "dripping", as max pressure events made large >> marks on the image. I instrumented hid-huion with a large amount of logging >> and observed that these events existed at the kernel level, and I was able >> to mitigate (or eliminate?) them by detecting instantaneous transitions >> between minimum and maximum pressure and throwing out these events. This >> was admittedly a pretty dirty hack, and I haven't ported it over to driver >> v5 yet. >> >> *Has anyone else with a H610 noticed this problem?* >> * >> * >> It seems there's some possibility it could be a hardware OR software >> issue, so I'm curious if anyone else has noticed this. >> > > I think I've heard about this before, but can't find any evidence ATM. I > suspect it's rather a hardware issue. You can check with "usbhid-dump -es". > If you see the pressure jumps there (the last two bytes in pen report), > then > it is 99% a hardware failure. > > Nick > |
|
From: Nikolai K. <sp...@gm...> - 2015-05-31 11:12:14
|
Hi Martin, On 05/29/2015 04:32 AM, Martin Shepherd wrote: > On the digimend tablets web page UC-Logic Tablet TWHA60 v3 is listed as > unsupported. I have this tablet, and I've just managed to get its stylus > working by making a very small change to hid-uclogic.c. With this change, > basic positioning, clicking the tip, and pressure sensitivity all appear to > work correctly (at least in inkscape). > > The report descriptor for interface 0 has a different size in this tablet > than previous versions, so the code that substitutes a fixed descriptor, > based on this size, does nothing. To resolve this, I added an extra if() to > check for the new descriptor size, and substituted a slightly different > fixed descriptor. The only changes needed in the fixed descriptor, were to > the logical maximums for X and Y, which should both be 2047, instead of the > previous values of 39999 and 24999. > > I have placed the diff between the 3.13.0-53-generic (Ubuntu) version of the > hid-uclogic.c file, and the fixed version, in the attached text file. I hope > that this is the correct place to post this. Contributions are welcome anywhere, although DIG...@li... would be a bit more appropriate. We actually have this tablet supported in the development version of our out-of-tree driver: https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip Here's the GitHub page for it: https://github.com/DIGImend/digimend-kernel-drivers I need to update the website though. Nick |
|
From: Martin S. <mcs...@gm...> - 2015-05-29 01:32:23
|
On the digimend tablets web page UC-Logic Tablet TWHA60 v3 is listed as unsupported. I have this tablet, and I've just managed to get its stylus working by making a very small change to hid-uclogic.c. With this change, basic positioning, clicking the tip, and pressure sensitivity all appear to work correctly (at least in inkscape). The report descriptor for interface 0 has a different size in this tablet than previous versions, so the code that substitutes a fixed descriptor, based on this size, does nothing. To resolve this, I added an extra if() to check for the new descriptor size, and substituted a slightly different fixed descriptor. The only changes needed in the fixed descriptor, were to the logical maximums for X and Y, which should both be 2047, instead of the previous values of 39999 and 24999. I have placed the diff between the 3.13.0-53-generic (Ubuntu) version of the hid-uclogic.c file, and the fixed version, in the attached text file. I hope that this is the correct place to post this. |
|
From: Ulrich L. <ulr...@t-...> - 2015-05-01 22:23:21
|
Hi,
I use the hid_uclogic driver with my Huion H610PRO and that works o.k.
However, I need to calibrate it.
I tried to put some stuff into /etc/X11/xorg.conf.d/52-tablet.conf and restarted X (CNTR ALT BACKSPACE).
However, from ls -ltu /etc/X11/xorg.conf.d/52-tablet.conf I see that the file has not been read.
So where have I to put the calibration information and what should it look like?
What I tried, was:
/etc/X11/xorg.conf.d/52-tablet.conf:
# HUION tablets
Section "InputClass"
Identifier "Custom tablet options"
MatchIsTablet "on"
MatchProduct "HUION Pentablet"
MatchDevicePath "/dev/input/event*"
Driver "hid_uclogic"
# Apply custom Options below.
Option "Calibration" "0 40000 0 25000"
EndSection
The system is
Linux honolulu 3.13.0-51-generic #84~precise1-Ubuntu SMP Wed Apr 15 21:46:23 UTC 2015 i686 i686 i386 GNU/Linux
Thanks for anyhelp,
ulrich
|
|
From: Nikolai K. <sp...@gm...> - 2015-04-10 15:06:19
|
On 04/09/2015 06:17 AM, Chris Hanna wrote:
> I dont know what happened, but the drivers dont work any more. The
> cursor doesnt move, I cant click with the pen or buttons, and nothing
> relating to the tablet shows up in xinput list, which is a setback from
> straight out of the box. Im using Ubuntu 14.04.2 Trusty Tahr, kernel
> version 3.16.0-33. Do you have any ideas on whats going on there?
That's unfortunate. I have no idea so far. Please send your /var/log/syslog
contents after plugging in the tablet. And also the output of these commands:
/lib/modules/`uname -r`/extra
/sbin/modinfo hid-huion
/sbin/modinfo hid-uclogic
Thank you.
Nick
|
|
From: Vince H. <Vi...@Pl...> - 2015-04-09 17:39:47
|
[vince@desk2 digimend-kernel-drivers-master]$ modinfo hid_uclogic filename: /lib/modules/3.19.3-200.fc21.i686+PAE/extra/hid-uclogic.ko version: 6 license: GPL author: Nikolai Kondrashov author: Martin Rusko srcversion: 5AE0FCF75FF4215B49E87D5 alias: hid:b0003g*v00005543p00000045 alias: hid:b0003g*v00005543p00000081 alias: hid:b0003g*v00005543p0000004D alias: hid:b0003g*v00005543p0000006E alias: hid:b0003g*v0000256Cp0000006E alias: hid:b0003g*v00005543p00000781 alias: hid:b0003g*v00005543p00000522 alias: hid:b0003g*v00005543p00000064 alias: hid:b0003g*v00005543p00000005 alias: hid:b0003g*v00005543p00000004 alias: hid:b0003g*v00005543p00000003 alias: hid:b0003g*v00005543p00000042 depends: vermagic: 3.19.3-200.fc21.i686+PAE SMP mod_unload 686 when I don't blacklist hid_huion then none of the presented devices recognize the frame buttons. My with the above version installed and the blacklist for hid_huion. my script is able to set the frame buttons on my huion h610n On Thu, Apr 9, 2015 at 4:30 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Vince, > > On 04/09/2015 06:23 AM, Vince Herried wrote: > >> I found that I have to black list hid_huin >> To get the drivers to work . >> > > Which version of the drivers were you using, on which kernel? > What happens if you don't blacklist it? > > Thank you. > > Nick > |
|
From: Nikolai K. <sp...@gm...> - 2015-04-09 08:30:41
|
Hi Vince, On 04/09/2015 06:23 AM, Vince Herried wrote: > I found that I have to black list hid_huin > To get the drivers to work . Which version of the drivers were you using, on which kernel? What happens if you don't blacklist it? Thank you. Nick |
170 messages has been excluded from this view by a project administrator.
