[DIGImend-users] Monoprice MP1060-HA60 tablet axes swapped
Brought to you by:
spb_nick
Menu
▾
▴
[DIGImend-users] Monoprice MP1060-HA60 tablet axes swapped
|
From: Toby J. <iro...@gm...> - 2015-12-28 14:28:35
|
Hello mailing list, I have received the following Monoprice tablet, which is a rebranded UC-Logic and has apparently been discussed on this list previously: http://www.monoprice.com/product?p_id=6814 I'm using Ubuntu 14.04, kernel 3.13, and it seems the tablet is being recognized but the axes are wrong. If I open Gimp and go to its input device config page, I can see that X, Y, and Pressure are being reported on axes 3, 4, and 5 respectively, while it seems that Gimp expects them to be on axes 1, 2, and 3. The tablet is not working as a mouse for the general OS, and I can't get it to work in Inkscape because that app apparently doesn't let me reassign axes. In Gimp if I reassign the axes it is working quite well; no stuttering or jumps, and I can get the full range of motion for all 3 axes (X and Y maps correctly edge to edge, and pressure goes from 0 to max). So in reading the previous messages for this tablet I think that this may be a newer hardware revision because the names were showing up differently for me. Following is the output from xinput list and xinput list-props for the first (of 3) devices reported (id=13): ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=11 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=12 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=13 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=14 [slave pointer (2)] ⎜ ↳ UC-LOGIC TWHA60 id=15 [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)] ↳ HD Webcam C615 id=8 [slave keyboard (3)] ↳ USB Keyboard id=9 [slave keyboard (3)] ↳ USB Keyboard id=10 [slave keyboard (3)] Device 'UC-LOGIC TWHA60': Device Enabled (150): 1 Coordinate Transformation Matrix (152): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (277): 0 Device Accel Constant Deceleration (278): 1.000000 Device Accel Adaptive Deceleration (279): 1.000000 Device Accel Velocity Scaling (280): 10.000000 Device Product ID (266): 21827, 1921 Device Node (267): "/dev/input/event20" Evdev Axis Inversion (281): 0, 0 Evdev Axis Calibration (282): <no items> Evdev Axes Swap (283): 0 Axis Labels (284): "Abs X" (351), "Abs Y" (352), "Abs Z" (604), "Abs Rotary X" (605), "Abs Pressure" (353) Button Labels (285): "Button Left" (153), "Button Middle" (154), "Button Right" (155), "Button Wheel Up" (156), "Button Wheel Down" (157) Evdev Middle Button Emulation (286): 0 Evdev Middle Button Timeout (287): 50 Evdev Third Button Emulation (288): 0 Evdev Third Button Emulation Timeout (289): 1000 Evdev Third Button Emulation Button (290): 3 Evdev Third Button Emulation Threshold (291): 20 Evdev Wheel Emulation (292): 0 Evdev Wheel Emulation Axes (293): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (294): 10 Evdev Wheel Emulation Timeout (295): 200 Evdev Wheel Emulation Button (296): 4 Evdev Drag Lock Buttons (297): 0 So I'm really hoping that this is a simple matter of changing an evdev configuration to "re-map" the axes and then everything will just start working correctly? Even though there's no entry under "Virtual core keyboard" even the hot-keys on the side are working, and clicking the pen buttons seems to be recognized although I'm not sure yet whether they are mapped correctly either. I apologize if this is a duplicate but from all the previous posts I found, this issue doesn't really seem to be the same as anyone else was previously having. Many thanks for your time, Toby |
