![]() ![]() Then back in Wireshark, I started a capture on the USB bus for the mouse, then immediately went in to the VM/SetPoint, and changed the button assignment from DPI +/- to Keystroke Assignment, then immediately went back to Wireshark and stopped the capture. ![]() ![]() (Note: After this point, I needed a second mouse plugged in, because I had to give control over my regular mouse to the Windows VM so that the SetPoint software could see that it existed as something more than a generic mouse.)Ĥ) In the VM, I then launched the SetPoint software, and went to the screen that lets you set custom actions for various buttons. Then I added a new USB Filter populated from an existing device, and selected my Logitech mouse's receiver (Vendor ID 046d, Product c245, for you) and then started up the VM. My steps (better ones almost certainly exist):ġ) Have a Windows VM (with the Logitech SetPoint software installed I used VirtualBox, because that's what I already had set up with WinXP for work), Wireshark, and gcc installed on your system.Ģ) Then I ran the following steps in a terminal: sudo modprobe usbmonģ) Within Wireshark, choose to 'List the available capture interfaces.', and make a note of which USB bus number generates a ton of packets when you move your mouse around (mine was usbmon3, but I imagine that's purely based on which USB port your receiver is plugged in to).ģ) From within VirtualBox (I needed to run as sudo in order to share the USB Controller), I edited the settings of the XP VM, and enabled both the USB Controller and the USB 2.0 (EHCI) Controller. If you want, I can walk you through the steps I used to determine how to switch it off (I now have a script that I simply need to run on startup, as a very hack-y workaround, but it's working at least), but it involves setting up a VM and having a secondary mouse and sniffing the raw USB traffic, and unfortunately seems likely to be very mouse-specific. I did some testing on my own, and eventually was able to figure out the codes to send the signal to switch the mouse into "Driver Mode", which then allowed me to use easygestures/xev to reassign the buttons. I believe that lomoco called it "Logitech SmartScroll / Cruise Control." On the G400, lomoco doesn't work and I am unaware of an alternative.Īlso, here is some output from xinput, in case it is helpful. On the MX 518 mouse, in order to make those buttons able to be altered / binded, they had to first be disabled. One of the things that makes these buttons different than the rest is that applications such as xev do not recognize pressing them as an event, by default. On the previous mouse (MX 518), buttons 11 and 12 were the DPI keys. What I would like to do is lock the DPI of my mouse to a single value and remap the DPI+ and DPI- buttons to PgUp and PgDn on my keyboard. Running $ lomoco -s shows 001.003: 046d:c245 Unsupported Logitech device: Unknown. This causes issues because, while the MX518 was supported by lomoco, the G400 mouse is unsupported. Instead of another 518, they sent me a Logitech G400 mouse because the 518 has been discontinued. I had the Logitech MX-518 mouse, but it had been having issues with responsiveness, causing me to call support for a replacement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |