dokutan
m913: Fire configuration (also Enter and snipe)
For the fire sequence, I've got a generated configuration from the stock settings. I believe the fire button was set to triple fire:
± sudo ./result/bin/mouse_m908 -R -
# Model: 913
# Configuration created with mouse_m908 -R.
# This configuration can be send to the mouse with mouse_m908 -c.
# Note: this feature is incomplete for the M913.
# Battery level: 80 %
# The M913 has two profiles that can be switched using the 'mode switch' button on the bottom of the mouse.
# Reading the settings can only be done for the active profile, therefore only profile1 is used in this config.
[profile1]
report_rate=125
# DPI settings
# Currently active DPI level: 2
dpi1=1000
dpi2=2000
dpi3=4000
dpi4=8000
dpi5=16000
# Button mapping
button_left=left
button_right=right
button_middle=middle
button_fire=unknown, please report as bug: 4 14 3 3a
button_1=keyboard_key
button_2=keyboard_key
button_3=keyboard_key
button_4=keyboard_key
button_5=keyboard_key
button_6=keyboard_key
button_7=keyboard_key
button_8=keyboard_key
button_9=keyboard_key
button_10=keyboard_key
button_11=keyboard_key
button_12=keyboard_key
As you can see, the program wanted me to report a bug :-)
Unfortunately, I didn't capture -D on the stock settings, before changing settings. Binding the fire command doesn't work. Testament to your incredible effort - thank you very much - I haven't even had to install a vm with the windows software so far, but let me know how I can help with any capturing or reversing, now that I already bought this thing.
I also can't seem to bind Enter, which you may already track in https://github.com/dokutan/mouse_m908/issues/29, and the snipe command also doesn't work.
Thanks, i have added initial support for the fire button in 6f4e9b5c9fdfc43cd241a0a3d8f9e1736a9588bf, i hope this works. If you can provide examples of the bytes for other fire button configurations and the snipe button, i can try to add them as well.
The same applies to Enter, however that might be more complicated (a button gets set as a keyboard key but the actual keycode is configured somewhere else), so a complete capture of the usb communication might be needed in that case.
I tried with button_fire=fire:3:1 as well as button_fire=fire, but it doesn't seem to work, and -R - shows button_fire=none.
Just wanted to provide my observations for now. I'll ping back here when I managed to get a VM setup and some capture traces.