Skip to content
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

Not detecting Intuos Pro Medium (PTH-651-ENES) #5

Open
battlesnake opened this issue Nov 24, 2019 · 3 comments
Open

Not detecting Intuos Pro Medium (PTH-651-ENES) #5

battlesnake opened this issue Nov 24, 2019 · 3 comments

Comments

@battlesnake
Copy link

battlesnake commented Nov 24, 2019

Wired:

$ lsusb | grep -i wacom
Bus 002 Device 022: ID 056a:0315 Wacom Co., Ltd PTH-651 [Intuos pro (M)]

Wireless:

$ lsusb | grep -i wacom
Bus 002 Device 017: ID 056a:0084 Wacom Co., Ltd ACK-40401 [Wireless Accessory Kit]

Product is PTH-651-ENES (Intuos pro medium)

Result in both cases, when starting wacom-utility built from 6bad1ce on Arch Linux with kernel version 4.14.123:

image

I have xf86-input-wacom installed, and can use the tablet to move the cursor around and Krita detects the extra features (e.g. pressure).

I have xsetwacom installed also:

$ xsetwacom --version
0.38.0
@battlesnake
Copy link
Author

I've fixed some system-related issues as per guidance in libwacom issue.

kcm-wacomtablet / kde_wacom_tabletfinder can see the tablet now and map it, but wacom-utility gives the same output as previously - "no graphics tablet detected". There's no diagnostic info logged to STDOUT/STDERR either.

@marginalhours
Copy link

Hi @battlesnake I was in a similar position to you with the device not being detected -- I think it's down to the right hex identifier missing from wacom_data.py.

You might be able to get it to show up using similar changes to mine? #6 - I think just adding:

self.Tablets.append(Tablet(" PTH-651-ENES", "Intuos Pro Medium", 0x315))

to the list in wacom_data.py should be enough to get it to show up when attached via the wired connection, although there will probably be more work to get any buttons working or to get it working over a wireless connection.

@battlesnake
Copy link
Author

Thanks, PR created also including the wireless device ID

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants