New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for GAOMON PD1560 #110
Comments
Output generated by uclogin-tools: uclogic-decode-gaomon-pd1560.txt |
Out of curiosity, how did you get your system to even see it as a HUION product? Mine doesn't even show up using "xsetwacom list." Here's what shows up under some simple investigations:
Using evtest...
Edit: and pressing the buttons while testing with evdev shows..
|
Probably it was captured by evdev driver. Try to edit your
Also I've added a new conf like this:
Also more correct (but still hacky) modification of the driver:
|
I do not have a However, I do seem to have an equivalent xsetwacom can now see and interact with the tablet ^_^ Thanks! However, directly tinkering with the drivers on LInux is something I've never done before. Where exactly would I be inserting that if-then line of coding? |
Well.. I applied it over anpaza's repository. Here is short instruction (didn't checked it):
Copy and paste lines in my previous comment before this line:
save and exit. Then compile and install driver like this:
Also I have this script to initialize device parameters. The pen display is configured to be second display to the right of main display:
|
Sorry for the late reply. Thanks, that did the trick! Now it's seeing the full sensitivity range, too, or at least much better than it had before (something I previously forced myself to "get used to" instead). Of course I switched up the keybindings to suite my preferences. Some of those variables I'll have to look into, such as the "Coordinate Transformation Matrix." I like to know what's actually being done inside the code, after all. :) |
@danghai, do you think you could add this tablet to the tablets repo? |
Everyone concerned with this issue, you're welcome to join the new #DIGImend channel on irc.freenode.net, discuss this and other issues, and help each other! Come and say "Hi!" |
I just recently bought this device, and it works great! Though there are two things that are really bugging me, and one of them is really strange... If I go to Windows, and then switch back to Linux, the Tablet will not recognize anything the stylus does. The other thing is that Windows show significantly less lag on input. I already tweaked the Sample and Supress values of the xinput, and that fixed a great deal (why was it so smoothed out in the first place, I find it really strange). Does anyone know how to improve latency of this device? Sorry for necro-ing this old thread, but I'm really at a loss, I much rather work on Linux over Windows. |
Okay, so quick answer to my previous comment in regards to that strange Windows thing. To solve it you need to have the Windows Gaomon driver UNINSTALLED. Uninstalled it now, powered down pc, restarted, switched OSes without a hitch. I have a feeling though that the lag just might be something out of my reach... Will report later! |
Hi. Maybe it can help. I have similar problem, that tablet does not recognize the pen. To fix it, I have to do: And then it works. |
Thanks! Do you know of a way of reducing pen latency though? That is my biggest concern right now... If I can't get this at least imperceptibly on par with Windows, then I'm going to have to work there, which I really didn't want... |
@danghai I can't right now, but I'll do that tomorrow in the afternoon. Thanks for the help! |
But just to make sure, you would like the output of xinput, and maybe lsusb? I can also present xsetwacom --list devices, a little bit of evtest, and the list-props of both the pen and the display. |
@danghai sorry, I do not own this device anymore. |
What a brainfart, I didn't read the tags and thought you were talking to me, @danghai... Sorry guys! |
Hi @veryprofessionaldodo, |
Okay, so this was what I can give to you, I followed the guide you recommended thoroughly, and these were the files that have all the info. Thanks for the help :) test_results.txt |
@veryprofessionaldodo Thanks, would you mind to provide your |
They present an error, described here. |
@veryprofessionaldodo, could you please use the latest development version of uclogic-tools from here: https://github.com/DIGImend/uclogic-tools/archive/master.zip (I need to make a release of that). |
I had installed it from the AUR, but it looks like it isn't that up to date. I uninstalled my previous version, installed directly from the repository, and now I get these results. |
And I think I got it. The difference in latency in Windows is barely perceptible, and something I'll easily get used to. I have made this script in case anyone wants to use it, with button bindings made for Krita. This is my particular setup in terms of display, if you want to know more about the coordinate transformation matrix go here https://github.com/linuxwacom/xf86-input-wacom/wiki/Dual-and-Multi-Monitor-Set-Up |
@teleportingtortoise, please try the new release: https://github.com/DIGImend/digimend-kernel-drivers/releases/v8 |
@spbnick Thank you, the new release seems to work with this pen display without any noticeable issues. |
So it seems the PD1560 works OK for a while. Does anyone know if the smaller version, PD1161 can work also? |
@jonnor I just tried it out with my PD1161 on manjaro. Seems to work all fine. Just getting the transformation set up now. |
What about the PD2200? Thinking of getting it, or one of the XP-Pen Artist 22 Pro models, but I want to be sure it will work on linux first. |
@BloodyMess As I remember PD1650 had noticable lags and pen offset with digimend drivers when comparing to windows version. XP-PEN 22E HD Pro still works well for me, see #168 for details. I use it almost every day. There is a newer version of this display on market, can't say anything about it. |
@loentar Have you tried the methods that @veryprofessionaldodo and @teleportingtortoise say they've had success with? I went ahead and ordered the PD2200. I would have gone with the XP-Pen 22E, but it doesn't have support for detecting/reporting stylus tilt. It also isn't fully laminated, and I don't want to deal with parallax. |
@BloodyMess Unfortunately no, I sold it before theirs solution. I wanted a larger pen display with better characteristics at that moment. Well, if you haven't had a pen display before, the parallax effect is unavoidable. The difference between PD1650 and 22E was very noticable. PD1650 had a parallax gap about 2.5mm in worst case on the right bottom edge. I'm not sure if the "laminate" technology can solve the parallax effect, because it's more connected to the display itself not the pen sensor. But I hope they greatly improved their sensor, 3 years is a pretty long period to make it work better. Once you have a chance to try PD2200, please say how it works for you. |
This issue hasn't been updated in a long time. Has their been any developments? |
@NamesNetworkNic I haven't had any problems with my Gaomon PD1560 on Linux, using standard drivers and digimend-drivers-git-dkms from AUR. |
pd1560 is an high-precision pen display produced by Gaomon company.
This pen display is recognized by this driver as HUION tablet and partially works in compatibility mode. Pressure sensor is not fully working (cropped at 2047 but max is 8191) as well as the last button is cannot be bound with
xsetwacom
because it is recognized as X axis.With the pull request #114 which enables high-precision mode for HUION tablets issues with pressure and buttons are fixed. But it introduces another issue. This tablet has maximum X = 68834 which cause 16-bit overflow and it's not usable on the very right side (cursor jumps back to the left side after x> 65535).
As temporary fix I applied this code in
uclogic_raw_event
:As @anpaza mentioned in that pull request, 32-bit mode is the correct way to work with this tablet. But it needs to detect this model and re-mix the bytes to make the event HID-compliant.
The string 0x79 is not actually string and contains value 0x03. Also there is another string number 0xC9 which looks like some OEM id:
The text was updated successfully, but these errors were encountered: