HOW TO set up a Waltop tablet in Lucid & Maverick

[Favux]

Well that seemed to work in Xorg.0.log. It's saying:

[    24.770] (II) XINPUT: Adding extended input device "WALTOP International Corp. Media Tablet stylus" (type: STYLUS)

And you see the stylus in xinput list and xsetwacom list?

If so we're back to a dead battery in the stylus. You said it wasn't working in Windows either.

[aapo4]

xsetwacom list       
WALTOP International Corp. Media Tablet stylus	id: 10	type: STYLUS

Yes, this time without eraser and pad.

It didn't worked under Windows and I got new piece of hardware for warranty. This device is quickly tested under Windows, mouse cursor is moving and clicking works (not sure any pressure stuff).

And device is 'working' with evdev driver under Ubuntu. So I think it is not dead battery.

[Favux]

OK, you've got me stumped. The Xorg.0.log seems to show the stylus being placed on the Wacom driver correctly. The xsetwacom list command shows the stylus on the Wacom X driver. So it doesn't appear the Ignore Option blocked the stylus from the driver. It should be working. But the stylus doesn't move the pointer arrow?

Have you tried the stylus script attached to the HOW TO? See if that kick starts anything. Are you using the default xf86-input-wacom 0.10.8 for Maverick or did you update it? The script needs to be updated for 0.10.11 or later.

[maslot]

I found a solution for strange behaviour of WALTOP tablet with ID 172f:0037 (I own Aiptek Hyperpen Mini)
If your tablet works like in this post http://ubuntuforums.org/showpost.php...6&postcount=21 you can try my magic.
Find a young virgin and black cat, stand in moonlight and wisper this spell:

sudo su
lsusb -v

I checked it on two computers and it works for me.

[Favux]

I think that is a kernel issue although it may have been an issue with xf86-input-wacom-0.10.8.

I checked if the tablet models are in xf86-input-wacom's wcmUSB.c and they are:

	{ WALTOP_VENDOR_ID, 0x501, 100000, 100000, &usbBamboo    },

for

[    4.618767] generic-usb 0003:172F:0500.0003: input,hidraw2: USB HID v1.10 Mouse [WALTOP International Corp. Media Tablet] on usb-0000:00:1d.1-1/input0

and for Waltop tablet with Vendor ID=172f and Product ID=0037 (172f:0037; Aiptek Hyperpen Mini)

	{ WALTOP_VENDOR_ID, 0x37,  80000,  80000, &usbGraphire4  },

I wonder if 172F would be a problem instead of 172f, in other words could it be case sensitive?


Edit: Nope, that isn't it. In xf86WacomDefs.h it is already:

#define WALTOP_VENDOR_ID 0x172F

[aapo4]

I'm using wacom-driver 0.10.99 from git. Mouse cursor is not moving with pen.

I modified script a little bit:

DEVICE_NAME="WALTOP International Corp. Media Tablet stylus"

xsetwacom set "$DEVICE_NAME" Suppress "4"  # data pt.s trimmed, default is 4, 0-20
xsetwacom set "$DEVICE_NAME" RawSample "2"  # data pt.s filtered, default is 2, 0-100 
xsetwacom set "$DEVICE_NAME" Threshold "27"  # pressure, default is 27, range is 0-2047
xsetwacom set "$DEVICE_NAME" PressureCurve "5 10 90 95" # Bezier curve, default is 0,0,100,100
xsetwacom set "$DEVICE_NAME" TabletPCButton "on"  # stylus tip + button, or "off" for hover mode
xsetwacom set "$DEVICE_NAME" Mode "Absolute"  # or Relative cursor movement

Are these values sane? E.g. what mean 'Enable Touch'? Should area not be square? Should there been entry 'Wacom Screen Area'?

xinput list-props "WALTOP International Corp. Media Tablet stylus"
Device 'WALTOP International Corp. Media Tablet stylus':
	Device Enabled (128):	1
	Coordinate Transformation Matrix (130):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	Device Accel Profile (274):	0
	Device Accel Constant Deceleration (275):	1.000000
	Device Accel Adaptive Deceleration (276):	1.000000
	Device Accel Velocity Scaling (277):	10.000000
	Wacom Tablet Area (300):	0, 0, 16383, 16383
	Wacom Rotation (301):	0
	Wacom Pressurecurve (302):	5, 10, 90, 95
	Wacom Serial IDs (303):	1280, 0, 2, 0
	Wacom Capacity (304):	-1
	Wacom Pressure Threshold (305):	27
	Wacom Sample and Suppress (306):	4, 2
	Wacom Enable Touch (307):	0
	Wacom Hover Click (308):	1
	Wacom Enable Touch Gesture (309):	0
	Wacom Touch Gesture Parameters (310):	50, 20, 250
	Wacom Tool Type (311):	"STYLUS" (296)
	Wacom Button Actions (312):	"None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0), "None" (0)
	Wacom Debug Levels (313):	0, 0

xinput test "WALTOP International Corp. Media Tablet stylus" prints same row each time I touch drawing area with pen:
motion a[0]=0 a[1]=0 a[2]=0 a[3]=0 a[4]=0 a[5]=-900
(But it detects when I touch it)

[artspace]

Sorry for my English... I'm from Taiwan. I have a strange problem with my newly bought Waltop based tablet/screen digitizer (branded ACCU) in which my stylus pointer remains "tip pressed" all the time (please see the attached pict).

I actually followed the instruction on Favux's post and installed wizardpen driver on my 10.0.4 Lucid (amd64 version) which had the xserver-xorg-input-wacom installed and used to work absolutely great with my Wacom Intuos 2 tablet (it was unplugged right before I installed the ACCU screen).

The lsusb shows:

Bus 004 Device 002: ID 172f:0051 Waltop International Corp.

xinput-list:

⎜   ↳ WALTOP International Corp. PEN-INPUT DEVICE	id=12	[slave  pointer  (2)]

The cat /proc/bus/input/devices:

I: Bus=0003 Vendor=172f Product=0051 Version=0110
N: Name="WALTOP International Corp. PEN-INPUT DEVICE"
P: Phys=usb-0000:00:1d.2-1/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0/input/input7
U: Uniq=
H: Handlers=mouse2 event7 
B: EV=1b
B: KEY=c03 70001 0 0 0 0
B: ABS=ffffff000100000f
B: MSC=10

and my 70-wizardpen.conf is (already modified and calibrated):

Section "InputClass"
   Identifier "wizardpen"
   MatchIsTablet "on"
   MatchDevicePath "/dev/input/event7"
   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad|WALTOP|Waltop"
   Driver "wizardpen"
	Option		"Device"	"/dev/input/event7"
	Option		"TopX"		"0"
	Option		"TopY"		"0"
	Option		"BottomX"	"7200"
	Option		"BottomY"	"5400"
EndSection
Section "InputClass"
   Identifier "wizardpen ignore mouse dev"
   MatchIsTablet "on"
   MatchDevicePath "/dev/input/mouse*"
   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad|WALTOP|Waltop"
   Driver ""
EndSection

Any suggestion? I think I am almost to get it working (or maybe not...).

Many thanks!

[Favux]

Hi artspace,

Let's try this first:

Section "InputClass"
   Identifier "wizardpen"
   MatchIsTablet "on"
#   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   MatchProduct "WALTOP|Waltop"
   MatchDevicePath "/dev/input/event*"
   Driver "wizardpen"
	Option		"TopX"		"0"
	Option		"TopY"		"0"
	Option		"BottomX"	"7200"
	Option		"BottomY"	"5400"
EndSection
Section "InputClass"
   Identifier "wizardpen ignore mouse dev"
   MatchIsTablet "on"
#   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   MatchProduct "WALTOP|Waltop"
   MatchDevicePath "/dev/input/mouse*"
   Option "Ignore" "yes"
EndSection

[artspace]

Hi artspace,

Let's try this first:

Section "InputClass"
   Identifier "wizardpen"
   MatchIsTablet "on"
#   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   MatchProduct "WALTOP|Waltop"
   MatchDevicePath "/dev/input/event*"
   Driver "wizardpen"
	Option		"TopX"		"0"
	Option		"TopY"		"0"
	Option		"BottomX"	"7200"
	Option		"BottomY"	"5400"
EndSection
Section "InputClass"
   Identifier "wizardpen ignore mouse dev"
   MatchIsTablet "on"
#   MatchVendor "UC-LOGIC|KYE Systems|Ace Cad"
   MatchProduct "WALTOP|Waltop"
   MatchDevicePath "/dev/input/mouse*"
   Option "Ignore" "yes"
EndSection

Thank you so much for such prompt reply!!!

BTW, I have tried it but there's no change...

[Favux]

OK, post the output of:

xinput list

and then using the "device name" from that for the stylus/tablet the output of:

xinput list-props "device name"