echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
It looks like a problem some other users are having as well. Check this post.
echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
Logitech Cordless Click Plus - more usable with btnx "out of the box" than any of the other systems I've tried. btnx thinks it's an mx600.
Seems to work fine for left, right, middle (scroll click), back and forward buttons.
ATM tilt left/right also map to back/forward respectively, and there is a little button on the top is equivalent to middle click (Logitech use to pop up a quick window selector by default in windows).
I have been trying various other howto's so there may be some other activity going on that makes these functions overlap.
When I run btnx from the command line I get
Detected mouse: mx600 Vendor=046d Product=c50e
Did not find additional event handlers. No problem.
Device and event handler detection complete.
-Using event: event2
Opened handler: /dev/input/event2
Opened handler: /dev/input/uinput
Opened handler: /dev/input/uinput
No startup errors
Hex dump attached.
Ray
It has the same problem as the MX1000, MX610, and MX600 because they all use the same product IDs. That's why btnx thinks its an MX600. Not really a problem, the right configuration file just has to be copied after installation.
And if you have configured your mouse before, it will cause some problems. The troubleshooting section has some possible solutions for that.
The mouse wheel click seems to send a lot button presses sometimes. But you probably don't want btnx to handle that anyway, so it shouldn't be a problem.
But I'll look at this more later (maybe tomorrow), when I have more time.
echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
I presume the product ID is actually the RF USB device. On Windows the Logitech software can tell what device(s) is/are connected to the wireless receiver in so it must have some means of interrogating the input device itself to identify it.
I wonder if it would be possible to capture the data that is used by the windows software with some kind of USB traffic sniffer, and then clone it in your software.
Thanks,But I'll look at this more later (maybe tomorrow), when I have more time.
Ray
This is probably correct. And it's most likely a proprietary protocol.
Linux machines need a custom kernel to sniff USB traffic (at least Ubuntu distros). The best way to go about it would be to sniff the USB traffic on a Windows machine with SetPoint software installed.I wonder if it would be possible to capture the data that is used by the windows software with some kind of USB traffic sniffer, and then clone it in your software.
Thanks,
Ray
However, it's all the same to btnx, because btnx would need to be a kernel module to accomplish this. I'm not sure though, it might be possible to talk with the mouse through the USB interface library in user space, but even this might be troublesome because of the closed protocols involved.
Not that this matters once btnx-config is released. It's getting quite close to a state where it can be released for testing.
echo -e "\x6f\x61\x73\x61\x6c\x6f\x6e\x65\x6e\x40\x67 \b\x6d\x61\x69\x6c\x2e\x63\x6f\x6d"
It compiles! Ship it!
This looks really neat. I'm excited as the proud owner of an MX Revolution.
I have 1 quick question, though. I browsed through your SVN repository, and there're many more recent tags than 0.2.11 (the latest in SVN is 0.2.8), yet I'm only seeing a tar for 0.2.11, and 0.2.11 is listed as the most recent version on http://ollisalonen.com/btnx.html. Is 0.2.8 usable and you forgot to tar it up, or should we stick with 0.2.11?
Thanks! I'm excited to try this out.
Last edited by Fangs404; June 30th, 2007 at 10:34 PM.
jman@Bedpan:~/Programs/btnx-debug$ sudo ./btnx
Detected mouse: mxrevo Vendor=046d Product=c51a
Device and event handler detection complete.
-Using event: event3
Opened handler: /dev/input/event3
Opened handler: /dev/input/event4
Opened handler: /dev/input/uinput
Opened handler: /dev/input/uinput
No startup errors
Interpreted a sidescroll! Here is the hexdump:
f3bf 4686 0000 0000 a1f2 0006 0000 0000
0002 0000 fff2 ffff f3bf 4686 0000 0000
a202 0006 0000 0000 0000 0000 0000 0000
Got rawcode: 0x02000600
Sending event: key=0x006a mod1==0x0038 mod2==0x0000 mod3==0x0000
^[[1;3C
jman@Bedpan:~/Desktop$ sudo ~/Programs/btnx-debug/btnx
Detected mouse: mxrevo Vendor=046d Product=c51a
Device and event handler detection complete.
-Using event: event3
Opened handler: /dev/input/event3
Opened handler: /dev/input/event4
Opened handler: /dev/input/uinput
Opened handler: /dev/input/uinput
No startup errors
Interpreted a sidescroll! Here is the hexdump:
2abc 4687 0000 0000 e902 0006 0000 0000
0002 0000 0008 0000 2abc 4687 0000 0000
e90b 0006 0000 0000 0000 0000 0000 0000
Got rawcode: 0x02000600
Sending event: key=0x006a mod1==0x0038 mod2==0x0000 mod3==0x0000
^[[1;3CInterpreted a sidescroll! Here is the hexdump:
2acd 4687 0000 0000 3d02 0006 0000 0000
0002 0000 0011 0000 2acd 4687 0000 0000
3d04 0006 0000 0000 0002 0001 0001 0000
2acd 4687 0000 0000 3d0e 0006 0000 0000
0000 0000 0000 0000
Got rawcode: 0x02000600
Sending event: key=0x006a mod1==0x0038 mod2==0x0000 mod3==0x0000
^[[1;3CInterpreted a sidescroll! Here is the hexdump:
2aef 4687 0000 0000 34f5 0006 0000 0000
0002 0000 ffee ffff 2aef 4687 0000 0000
34f8 0006 0000 0000 0002 0001 fffe ffff
2aef 4687 0000 0000 3502 0006 0000 0000
0000 0000 0000 0000
Got rawcode: 0x02000600
Sending event: key=0x006a mod1==0x0038 mod2==0x0000 mod3==0x0000
^[[1;3C
All I was doing was moving the mouse around. No scrolling, or other buttons.
Last edited by Bedpan.ca; July 1st, 2007 at 05:15 AM. Reason: More...
Bookmarks