Thread: [DIGImend-devel] Genius EasyPen M610 questions
Brought to you by:
spb_nick
Menu
▾
▴
digimend-devel
|
From: Nikolai K. <sp...@gm...> - 2012-07-16 20:36:06
|
Hi Lana,
Thanks for the dumps! I've taken a look at them and the coordinate reporting
and the pen report descriptor surely look strange.
The coordinate ranges don't constitute a round number or close to it, which
is unusual and suspicious. Could you please repeat pen coordinate dump?
This time, please slowly move your pen horizontally, from out the left side
of the working area, through the middle, and out on the right side. Then do
this vertically, starting from the top. Please ensure that the pen both
starts and stops outside the working area. It doesn't have to be a very
straight line.
First like this:
`:
.-~---------------------------.
| * * * * |
| .-----------------------. |
| | | |
| | | |
| --------------------------> |
| | | |
| | | |
| | | |
| `-----------------------' |
| |
`-----------------------------'
Then like this:
`:
.-~---------------------------.
| * * * * | |
| .---------- | ----------. |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| `---------- | ----------' |
| \|/ |
`-----------------------------'
Please repeat this three times and send me the resulting file.
Have you figured out any pattern behind "spontaneous" mouse/tablet switching
Dave has described?
Will you be able to test a kernel package? Which distribution release do you
use, is it 32 or 64 bits?
Thank you!
Sincerely,
Nick
|
|
From: Nikolai K. <sp...@gm...> - 2012-07-19 07:01:42
|
Sorry, forgot to include DIGImend-devel. Lana, please "Reply to all" this message and send me whatever message you get from the maillist server, if it gets rejected. Thanks! Sincerely, Nick On 07/19/2012 12:44 AM, Nikolai Kondrashov wrote: > Hi Lana, > > On Wed, Jul 18, 2012 at 9:10 AM, Lana Druzetich > <lan...@gm...> wrote: >> Hello. I did another pen coordinates dump, and, strangely, my tablet stopped >> responding afterwards. > > First of all, thanks for the dumps! What part of the system stopped > responding to the tablet input? Do you get anything from dumping? > >> Since the last time we spoke, I switched to 64 bit Windows 7, and 64 bit >> Ubuntu, and one of the problems I had before is gone now (the tablet is >> always recognized as a tablet, never as a mouse), except when I unplug it >> live, and then plug it back in (I have to restart my PC to get it working >> again, but now restarting fixes it every time). The tablet is, however, is >> still heavily miscalibrated at first, and I have to enter some unusual >> values to get the whole surface area working (40000 0 42000 20000). I'm >> pretty sure I damaged the tablet's firmware, back when I used Ubuntu 10, and >> wizardpen, since Windows (XP, 7 x86, and 7 x64) wouldn't recognize it since >> then, that is, they do recognize it, but as a USB composite device, not by >> it's id (PW1700U). Another gem is the fact that when i install drivers from >> Windows update, the tablet works, but I get the same miscalibration I get in >> Ubuntu at start, and I can not fix it in Windows. For comparison purposes, >> when I plugged in a similar tablet (WP5540U, I never used this one on >> Ubuntu, if that means anything) it was instantly recognized in both Windows >> (by it's name, and as a single USB device) and Ubuntu (hotplugging worked >> just fine), and it required no calibration in either system. >> >> I hope this clears things up a bit. > > Thanks for the description! I've implemented WP5540U driver quite a long > time ago and it is a very simple and straight-forward device, although, as > usual, not standard compliant. > > I doubt that you damaged the firmware, there is usually no way to do that. > However, it could have been quirky to start with. > > I think this mouse/tablet flipping is due to switching of the tablet modes. > I have a suspicion that the firmware designers used some strange way of > triggering it and it is getting switched accidentally by some sequence of > events on the USB bus. > > Now, if we won't find this sequence, there is a high possibility we can work > around this random switching in the kernel driver. > > The modes differ slightly by the report IDs and format. I have full report > format for the default mode sent by you previously, and pen coordinates for > the proprietary mode. Can you please do pen buttons and frame buttons dump > for the proprietary mode? > > You can see which mode your tablet is in by starting a dump and seeing which > report ID is used to report pen movement. If the first byte of each report > is 09 - it is the default mode, if it is 07 - it is the proprietary mode. > > This is an example of default mode reports: > > 002:002:000:STREAM 1341769148.182056 > 09 80 F0 57 E6 A4 00 00 > > 002:002:000:STREAM 1341769148.186029 > 09 80 F0 57 E6 A4 00 00 > > 002:002:000:STREAM 1341769148.190024 > 09 80 F0 57 E6 A4 00 00 > > These are proprietary mode reports: > > 002:003:000:STREAM 1342590809.450792 > 07 C0 7E A0 22 77 00 00 > > 002:003:000:STREAM 1342590809.462649 > 07 C0 2F A0 22 77 00 00 > > 002:003:000:STREAM 1342590809.470647 > 07 C0 D0 9F 22 77 00 00 > > I need pen buttons and frame buttons dumps for the second (proprietary) > mode. However, if it refuses to switch to it again, I can do a good guess as > to how it would work and do without the dump. > > Thank you! > > Sincerely, > Nick > > P.S. Could you please "Reply to all" this message and send me whatever error > message you get back from the maillist server, if it gets rejected? |
|
From: Lana D. <lan...@gm...> - 2012-07-20 12:05:25
|
Bus 002 Device 003: ID 5543:000d UC-Logic Technology Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x5543 UC-Logic Technology Corp.
idProduct 0x000d
bcdDevice 0.00
iManufacturer 1 UC-LOGIC
iProduct 2 Tablet WP1700U
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 160mA
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.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 254
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 0x0008 1x 8 bytes
bInterval 5
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.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 139
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 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered) |
|
From: Nikolai K. <sp...@gm...> - 2012-07-25 18:45:17
|
Hi Lana, On 07/20/2012 03:05 PM, Lana Druzetich wrote: > Okay, here they are. One detail, though. While I was dumping the pen > buttons, the first two digits were "05", and the dumping wouldn't stop > after a minute expired. However, once I restarted the terminal, it was > fine. Thank you! The pen issue sounds strange, but let's dismiss it as an accidental quirk for now. I'm currently trying to organize the backlog of work I have and am not sure when I'll be able to come to implementing the driver. However, I hope to get a steady, if slow, progress soon instead of frantic running around trying to do everything at once I used to do, up to the point where I couldn't do anything. Sorry for the delay. Sincerely, Nick On 07/20/2012 03:05 PM, Lana Druzetich wrote: > Okay, here they are. One detail, though. While I was dumping the pen buttons, the first two digits were "05", and the dumping wouldn't stop after a minute expired. However, once I restarted the terminal, it was fine. > > On Thu, Jul 19, 2012 at 9:01 AM, Nikolai Kondrashov <sp...@gm... <mailto:sp...@gm...>> wrote: > > Sorry, forgot to include DIGImend-devel. > > Lana, please "Reply to all" this message and send me whatever message you > get from the maillist server, if it gets rejected. > > Thanks! > > Sincerely, > Nick > > > On 07/19/2012 12:44 AM, Nikolai Kondrashov wrote: > > Hi Lana, > > On Wed, Jul 18, 2012 at 9:10 AM, Lana Druzetich > <lan...@gm... <mailto:lan...@gm...>> wrote: > > Hello. I did another pen coordinates dump, and, strangely, my tablet stopped > responding afterwards. > > > First of all, thanks for the dumps! What part of the system stopped > responding to the tablet input? Do you get anything from dumping? > > Since the last time we spoke, I switched to 64 bit Windows 7, and 64 bit > Ubuntu, and one of the problems I had before is gone now (the tablet is > always recognized as a tablet, never as a mouse), except when I unplug it > live, and then plug it back in (I have to restart my PC to get it working > again, but now restarting fixes it every time). The tablet is, however, is > still heavily miscalibrated at first, and I have to enter some unusual > values to get the whole surface area working (40000 0 42000 20000). I'm > pretty sure I damaged the tablet's firmware, back when I used Ubuntu 10, and > wizardpen, since Windows (XP, 7 x86, and 7 x64) wouldn't recognize it since > then, that is, they do recognize it, but as a USB composite device, not by > it's id (PW1700U). Another gem is the fact that when i install drivers from > Windows update, the tablet works, but I get the same miscalibration I get in > Ubuntu at start, and I can not fix it in Windows. For comparison purposes, > when I plugged in a similar tablet (WP5540U, I never used this one on > Ubuntu, if that means anything) it was instantly recognized in both Windows > (by it's name, and as a single USB device) and Ubuntu (hotplugging worked > just fine), and it required no calibration in either system. > > I hope this clears things up a bit. > > > Thanks for the description! I've implemented WP5540U driver quite a long > time ago and it is a very simple and straight-forward device, although, as > usual, not standard compliant. > > I doubt that you damaged the firmware, there is usually no way to do that. > However, it could have been quirky to start with. > > I think this mouse/tablet flipping is due to switching of the tablet modes. > I have a suspicion that the firmware designers used some strange way of > triggering it and it is getting switched accidentally by some sequence of > events on the USB bus. > > Now, if we won't find this sequence, there is a high possibility we can work > around this random switching in the kernel driver. > > The modes differ slightly by the report IDs and format. I have full report > format for the default mode sent by you previously, and pen coordinates for > the proprietary mode. Can you please do pen buttons and frame buttons dump > for the proprietary mode? > > You can see which mode your tablet is in by starting a dump and seeing which > report ID is used to report pen movement. If the first byte of each report > is 09 - it is the default mode, if it is 07 - it is the proprietary mode. > > This is an example of default mode reports: > > 002:002:000:STREAM 1341769148.182056 > 09 80 F0 57 E6 A4 00 00 > > 002:002:000:STREAM 1341769148.186029 > 09 80 F0 57 E6 A4 00 00 > > 002:002:000:STREAM 1341769148.190024 > 09 80 F0 57 E6 A4 00 00 > > These are proprietary mode reports: > > 002:003:000:STREAM 1342590809.450792 > 07 C0 7E A0 22 77 00 00 > > 002:003:000:STREAM 1342590809.462649 > 07 C0 2F A0 22 77 00 00 > > 002:003:000:STREAM 1342590809.470647 > 07 C0 D0 9F 22 77 00 00 > > I need pen buttons and frame buttons dumps for the second (proprietary) > mode. However, if it refuses to switch to it again, I can do a good guess as > to how it would work and do without the dump. > > Thank you! > > Sincerely, > Nick > > P.S. Could you please "Reply to all" this message and send me whatever error > message you get back from the maillist server, if it gets rejected? > > > |
Thanks for helping keep SourceForge clean.
X