Gyration Air Mouse Not Working

[tmwillett]

Unfortunately, I got the same results with event9 as with event10..  Nothing.  Do I need to configure my xorg.conf file to recognize the buttons?  I've tried to configure it and show it with 9 and 12 buttons, but it doesn't make a difference with that option, but are there others that be more specific?

[tmwillett]

I've made a little progress on this, but I'm stuck again.  I still do not get any output from the actual device (/dev/input/mouse2 - or event9, or event10), but I do get output when I do a cat to the /dev/hidraw1 device.  I've tried dumping it to hexdump, and it gives me some consistent data, but I can't make heads or tails of what it is, or how I can use it..  See below:

dcerouter_1017654:/dev/input# ls -al by-id
total 0
drwxr-xr-x 2 root root 100 2011-05-25 18:49 .
drwxr-xr-x 4 root root 380 2011-05-25 18:49 ..
lrwxrwxrwx 1 root root   9 2011-05-25 18:49 usb-Movea__Inc._Movea_RF_Receiver-event-kbd -> ../event9
lrwxrwxrwx 1 root root  10 2011-05-25 18:49 usb-Movea__Inc._Movea_RF_Receiver-event-mouse -> ../event10
lrwxrwxrwx 1 root root   9 2011-05-25 18:49 usb-Movea__Inc._Movea_RF_Receiver-mouse -> ../mouse2

Pressing the left button out of the group of 3 extra buttons on the Air Mouse (not the normal left mouse button) gives me the following output:

dcerouter_1017654:/dev# cat hidraw1 | hexdump -C
00000000  01 00 00 00 00 05 08 01  00 00 00 00 05 00 01 00  |................|
00000010  00 00 00 05 08 01 00 00  00 00 05 00 01 00 00 00  |................|
00000020  00 05 08 01 00 00 00 00  05 00 01 00 00 00 00 05  |................|
00000030  08 01 00 00 00 00 05 00  01 00 00 00 00 05 08 01  |................|
00000040  00 00 00 00 05 00 01 00  00 00 00 05 08 01 00 00  |................|
00000050  00 00 05 00 01 00 00 00  00 05 08 01 00 00 00 00  |................|
00000060  05 00 01 00 00 00 00 05  08 01 00 00 00 00 05 00  |................|
00000070  01 00 00 00 00 05 08 01  00 00 00 00 05 00 01 00  |................|
^C

Pressing the middle button out of the 3-button group gives me this output:

dcerouter_1017654:/dev# cat hidraw1 | hexdump -C
00000000  01 00 00 00 00 05 40 01  00 00 00 00 05 00 01 00  |......@.........|
00000010  00 00 00 05 40 01 00 00  00 00 05 00 01 00 00 00  |....@...........|
00000020  00 05 40 01 00 00 00 00  05 00 01 00 00 00 00 05  |..@.............|
00000030  40 01 00 00 00 00 05 00  01 00 00 00 00 05 40 01  |@.............@.|
00000040  00 00 00 00 05 00 01 00  00 00 00 05 40 01 00 00  |............@...|
00000050  00 00 05 00 01 00 00 00  00 05 40 01 00 00 00 00  |..........@.....|
00000060  05 00 01 00 00 00 00 05  40 01 00 00 00 00 05 00  |........@.......|
00000070  01 00 00 00 00 05 40 01  00 00 00 00 05 00 01 00  |......@.........|
00000080  00 00 00 05 40 01 00 00  00 00 05 00 01 00 00 00  |....@...........|
^C

And finally, pressing the right button out of the 3-button group gives me this output:

dcerouter_1017654:/dev# cat hidraw1 | hexdump -C
00000000  01 00 00 00 00 05 10 01  00 00 00 00 05 00 01 00  |................|
00000010  00 00 00 05 10 01 00 00  00 00 05 00 01 00 00 00  |................|
00000020  00 05 10 01 00 00 00 00  05 00 01 00 00 00 00 05  |................|
00000030  10 01 00 00 00 00 05 00  01 00 00 00 00 05 10 01  |................|
00000040  00 00 00 00 05 00 01 00  00 00 00 05 10 01 00 00  |................|
00000050  00 00 05 00 01 00 00 00  00 05 10 01 00 00 00 00  |................|
00000060  05 00 01 00 00 00 00 05  10 01 00 00 00 00 05 00  |................|
00000070  01 00 00 00 00 05 10 01  00 00 00 00 05 00 01 00  |................|
00000080  00 00 00 05 10 01 00 00  00 00 05 00 01 00 00 00  |................|
^C

As you can see, each button gives consistent data, but I can't really make heads or tails out of what it actually converts to.  Any ideas on how I can possible take this hexdump data and turn it into something that I can make a template out of for the HID device?

I've stumped quite a few people on this already, but these are new mice vs those old 1005's that are hard to find, and LMCE could greatly benefit from it being added if we can figure out the codes.

As usual, any help is GREATLY appreciated.

TIA

[tschak909]

I use a Beagle USB sniffer to help decode protocol bits. That may have to happen here, as I do not recognize those frames right off the bat.

-Thom

[tmwillett]

Hmm..  $400 for a Beagle sniffer.  Not exactly cheap.  I may have to cut my losses and abandon this effort for an older remote until someone else can fix the problem.  That's what I get for trying to be bleeding edge.  ;-)  Is the Gyration 3101US a stable remote to use, or is there a better choice?  I'm planning on having a core/hybrid and 4 MediaDirectors.  I want to use the same thing on all of them.

Thanks!

[tschak909]

Yes, the 3101 works well as an on screen remote. Keep in mind there are other choices as well, such as running the Orbiter software on a tablet.

-Thom