Thread: [DIGImend-devel] Genius EasyPen M610
Brought to you by:
spb_nick
Menu
▾
▴
digimend-devel
|
From: Favux ... <fav...@gm...> - 2012-07-09 06:38:51
Attachments:
EasyPenM610.zip
|
Hi Nick, I'm sending this for LannaD because she's having touble e-mailing the devel list for some reason. She has what I think is a new model to us bought about a year ago. Genius EasyPen M610/ 6x10 Tablet/ UC-LOGIC Tablet WP1700U The tablet diagnostics are attached. Favux |
|
From: Nikolai K. <sp...@gm...> - 2012-07-09 09:54:52
|
Hi Dave, On Mon, Jul 9, 2012 at 9:38 AM, Favux ... <fav...@gm...> wrote: > I'm sending this for LannaD because she's having touble e-mailing the > devel list for some reason. She has what I think is a new model to us > bought about a year ago. > > Genius EasyPen M610/ 6x10 Tablet/ UC-LOGIC Tablet WP1700U > > The tablet diagnostics are attached. Thanks, Dave. I too received a message from her and I'm puzzled about the reason of the failures she encountered. I think this tablet is the previous version of M610X, produced before KYE started designing their own tablets. I'll take a look at the dump soon. Sincerely, Nick |
|
From: Favux ... <fav...@gm...> - 2012-07-10 06:37:24
|
Hi Nick, Forgive me if this is a silly question. I was wondering if there was any chance the method you discovered with Viktoria of "turning on" the new KYE tablets data reporting could be done from user space? Is there some way to toggle the usb protocol without having to do it in the kernel? I'm assuming it is the tablet's firmware we need to toggle. We seem to have LanaD's M610 coordinate and axes inversion problem licked with the appropriate 52-evdev.conf. But evdev usually treats the tablet as a mouse only occasionally handling it as a tablet. Maybe when restarting from Windows? Being able to do that would let KYE users get some functionality out of their "new" tablets while waiting for the kernel driver's to be made. Favux |
|
From: Viktoria S. <vik...@fr...> - 2012-07-10 08:18:28
|
Hi! When Nick was working on the Genius Mousepen i608X driver he sent me a modified usbhid-dump, which was succesfully turned the tablet into tablet mode. After that I could get pressure from the pen. So maybe it is possible to write a little program which turns on the tablet, but I don't remember how the mouse worked in that case. If I got time I can run a little test with that modified usbhid-dump, to see how it is working. Kind regards: Viktoria "Favux ..." <fav...@gm...> írta: >Hi Nick,> > Forgive me if this is a silly question.> > I was wondering if there was any chance the method you discovered with> Viktoria of "turning on" the new KYE tablets data reporting could be> done from user space? Is there some way to toggle the usb protocol> without having to do it in the kernel? I'm assuming it is the> tablet's firmware we need to toggle.> > We seem to have LanaD's M610 coordinate and axes inversion problem> licked with the appropriate 52-evdev.conf. But evdev usually treats> the tablet as a mouse only occasionally handling it as a tablet.> Maybe when restarting from Windows?> > Being able to do that would let KYE users get some functionality out> of their "new" tablets while waiting for the kernel driver's to be> made.> > Favux> > ------------------------------------------------------------------------------> Live Security Virtual Conference> Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/> _______________________________________________> DIGImend-devel mailing list> DIG...@li...> https://lists.sourceforge.net/lists/listinfo/digimend-devel> |
|
From: Favux ... <fav...@gm...> - 2012-07-10 14:59:15
|
On Tue, Jul 10, 2012 at 3:18 AM, Viktoria S. <vik...@fr...> wrote: > Hi! > > When Nick was working on the Genius Mousepen i608X driver he sent me a modified usbhid-dump, which was succesfully turned the tablet into tablet mode. After that I could get pressure from the pen. So maybe it is possible to write a little program which turns on the tablet, but I don't remember how the mouse worked in that case. If I got time I can run a little test with that modified usbhid-dump, to see how it is working. That would be great Viktoria S. I'd really appreciate that. Although as Nick points out it is a UC-Logic tablet I'm hoping things are similar enough that the same or very similar method would work for LannaD's tablet. Favux |
|
From: Nikolai K. <sp...@gm...> - 2012-07-10 08:37:06
|
Hi Dave, On Tue, Jul 10, 2012 at 9:37 AM, Favux ... <fav...@gm...> wrote: > I was wondering if there was any chance the method you discovered with > Viktoria of "turning on" the new KYE tablets data reporting could be > done from user space? Is there some way to toggle the usb protocol > without having to do it in the kernel? I'm assuming it is the > tablet's firmware we need to toggle. Yes, it is easy to make a userspace utility using libusb, or, probably, hidapi. However, see below. > We seem to have LanaD's M610 coordinate and axes inversion problem > licked with the appropriate 52-evdev.conf. Um, which coordinate inversion problem? Could you please CC your replies to Lana to DIGImend-devel, even though she can't send her messages there? > But evdev usually treats the tablet as a mouse only occasionally handling > it as a tablet. Maybe when restarting from Windows? I doubt that Windows could affect that. The devices are supposed to be reset on reboot, I think. However, this behavior is indeed strange. X.org logs for both cases would help to understand the issue. > Being able to do that would let KYE users get some functionality out of > their "new" tablets while waiting for the kernel driver's to be made. I don't think that it would help much without the kernel changes. My guess is that the tablets would at least need a HID_QUIRK_MULTI_INPUT in drivers/hid/usbhid/hid-quirks.c. Still, M610 is not a KYE tablet. It's UC-Logic tablet. So, I don't think the KYE tablet-enabling routine would help. But it maybe worth a try. Unfortunately, I lost the ability to have an external IP for my home server, so I can't give you a tarball link to the KYE-tailored usbhid-dump, but you can checkout "kye" branch of git://digimend.git.sourceforge.net/gitroot/digimend/usbhid-dump.git and run "./bootstrap && ./configure && make dist" to produce one. Sincerely, Nick |
|
From: Favux ... <fav...@gm...> - 2012-07-10 15:22:39
|
On Tue, Jul 10, 2012 at 3:36 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Dave, > > Yes, it is easy to make a userspace utility using libusb, or, probably, > hidapi. However, see below. I'm interested in something like that. > Um, which coordinate inversion problem? Could you please CC your replies to > Lana to DIGImend-devel, even though she can't send her messages there? The discussion is a continuation of the Ubuntu forms thread LannaD started. Not e-mail correspondence. > I doubt that Windows could affect that. The devices are supposed to be reset > on reboot, I think. However, this behavior is indeed strange. X.org logs for > both cases would help to understand the issue. Right but when LannaD installed some tablet drivers in Windows and then rebooted to Ubuntu the tablet was magically recognized as a tablet. LannaD has been looking at the Xorg.0.logs but I don't know if copies of all of them have been preserved. I have one or two partials. We're usually seeing a mouse with relative axes and occasionally a tablet with absolute axes. I'm reasoning by analogy from toggling the KYE to get tablet reporting and other examples. For instance the Wacom Graphire bluetooth starts defaulted to low speed bluetooth. And low speed only reports mouse data. The bluetooth has to be toggled to go into high speed protocol mode so it will report the tablet data. > I don't think that it would help much without the kernel changes. My guess > is that the tablets would at least need a HID_QUIRK_MULTI_INPUT in > drivers/hid/usbhid/hid-quirks.c. Earlier LannaD had the tablet "working" before several reinstalls of different Ubuntu releases. An attempt to use the WizardPen driver in Lucid was made. Now we're back in Precise and I did manage to compile the WizardPen driver in Precise. Again looking for a stop gap alternative until there was a kernel driver. We've been trying to replicate that former "working" state on the thread. > Still, M610 is not a KYE tablet. It's UC-Logic tablet. So, I don't think > the KYE tablet-enabling routine would help. But it maybe worth a try. Well you did say it was an earlier version of a current KYE, KYE made, tablet. So I was hoping. > Unfortunately, I lost the ability to have an external IP for my home server, > so I can't give you a tarball link to the KYE-tailored usbhid-dump, but you > can checkout "kye" branch of > git://digimend.git.sourceforge.net/gitroot/digimend/usbhid-dump.git and run > "./bootstrap && ./configure && make dist" to produce one. Thanks, I'll check it out. Basically I'm just wondering if it would be possible to give users a temporary work around so they can at least use their tablets to draw. LannaD's is not the first time I've seen someone claim to have a non-supported tablet kind of working. Since the tablet buttons won't work and maybe even the stylus buttons I don't think a stop gap solution like that would decrease the likely hood of folks sending in tablet diagnostics to get a true kernel driver. But if the kernel won't permit it and instead blocks it oh well. I would like an alternative to instructing folks to work with the kernel. I just don't think we'll ever get that many digital artists enthusiastic about doing that. Favux |
|
From: Nikolai K. <sp...@gm...> - 2012-07-11 19:36:36
|
Hi Dave, On 07/10/2012 06:22 PM, Favux ... wrote: >> Yes, it is easy to make a userspace utility using libusb, or, probably, >> hidapi. However, see below. > > I'm interested in something like that. Can you please submit a bug for this, so it is not lost? I'll try to find some time to implement it. >> Um, which coordinate inversion problem? Could you please CC your replies to >> Lana to DIGImend-devel, even though she can't send her messages there? > > The discussion is a continuation of the Ubuntu forms thread LannaD > started. Not e-mail correspondence. Ah, OK. I've found the thread now. Will take a look. >> I doubt that Windows could affect that. The devices are supposed to be reset >> on reboot, I think. However, this behavior is indeed strange. X.org logs for >> both cases would help to understand the issue. > > Right but when LannaD installed some tablet drivers in Windows and > then rebooted to Ubuntu the tablet was magically recognized as a > tablet. LannaD has been looking at the Xorg.0.logs but I don't know > if copies of all of them have been preserved. I have one or two > partials. We're usually seeing a mouse with relative axes and > occasionally a tablet with absolute axes. I'm still unsure how this could happen unless device somehow changes the report descriptor, or there is a bug somewhere in the kernel or X.org. > I'm reasoning by analogy from toggling the KYE to get tablet reporting > and other examples. For instance the Wacom Graphire bluetooth starts > defaulted to low speed bluetooth. And low speed only reports mouse > data. The bluetooth has to be toggled to go into high speed protocol > mode so it will report the tablet data. UC-Logic has configuration commands for their tablets too. It's just I haven't seen any of their tablets requiring it for pen input. I've seen some frame button configuration happening, but not pen. >> I don't think that it would help much without the kernel changes. My guess >> is that the tablets would at least need a HID_QUIRK_MULTI_INPUT in >> drivers/hid/usbhid/hid-quirks.c. > > Earlier LannaD had the tablet "working" before several reinstalls of > different Ubuntu releases. An attempt to use the WizardPen driver in > Lucid was made. Now we're back in Precise and I did manage to compile > the WizardPen driver in Precise. Again looking for a stop gap > alternative until there was a kernel driver. The WizardPen driver may help, judging from the report descriptor. However, this mouse/tablet switching might affect it. To me this model feels to be somewhere in the middle between the classical (WP8060U, WP5540U, etc) and some of the latest models (TWHL850). >> Still, M610 is not a KYE tablet. It's UC-Logic tablet. So, I don't think >> the KYE tablet-enabling routine would help. But it maybe worth a try. > > Well you did say it was an earlier version of a current KYE, KYE made, > tablet. So I was hoping. I doubt it. The report IDs are different, this tablet has two interfaces, but KYE tablets always have one. > Basically I'm just wondering if it would be possible to give users a > temporary work around so they can at least use their tablets to draw. > LannaD's is not the first time I've seen someone claim to have a > non-supported tablet kind of working. Since the tablet buttons won't > work and maybe even the stylus buttons I don't think a stop gap > solution like that would decrease the likely hood of folks sending in > tablet diagnostics to get a true kernel driver. I'm all for it. It's just finding and maintaining such solutions requires a lot more time, so I can't afford it. > But if the kernel won't permit it and instead blocks it oh well. I > would like an alternative to instructing folks to work with the > kernel. I just don't think we'll ever get that many digital artists > enthusiastic about doing that. In this case, the WizardPen driver will very likely work. Linux and Windows took opposite design decisions for handling multiple report IDs, it seems. I think Windows, basically, routes them to separate input devices and Linux, by default, to a single device. Some devices might have worked better out of the box in Linux if not for this (including this tablet), but I'm not sure about the whole picture. Sincerely, Nick |
Thanks for helping keep SourceForge clean.
X