dokutan
dokutan
Could you post the output of ``mouse_m908 -R -``, ``mouse_m908 -D -`` and ``lsusb``? If you have the official software installed, you could install wireshark and capture the usb traffic...
Opening this issue is a perfectly fine way to get in touch. Here are some links that should help get you started: [https://bytepunk.wordpress.com/2017/03/25/reverse-engineering-a-usb-mouse/](https://bytepunk.wordpress.com/2017/03/25/reverse-engineering-a-usb-mouse/) [https://github.com/pez2001/razer_chroma_drivers/wiki/Reverse-Engineering-USB-Protocol](https://github.com/pez2001/razer_chroma_drivers/wiki/Reverse-Engineering-USB-Protocol) [https://github.com/dokutan/rgb_keyboard/tree/master/doc](https://github.com/dokutan/rgb_keyboard/tree/master/doc) (from my other usb reverse...
I am glad the usb capture worked out. I have added an annotated version of my captured data in the documentation directory in case you want to have a look...
I had a look at the captured data, changing the profile is identical to the M908, and the rest appear to be very similar as well. However there is one...
You need to completely close the Redragon application, start a capture and then open the Redragon application again. Maybe look in the Taskmanager to make sure it is not running...
Sorry, i meant the version from the ``m709`` branch. Testing this version should tell whether the duplicated packets are neccessary.
That is good to hear, i just finished implementing everything required to have support for multiple mice in the ``multiple-models`` branch. All that is left now is to implement the...
I have added support for sending settings to the M709 in the ``multiple-models`` branch, does ``` mouse_m908 -M709 -c example709.ini ``` work (correctly)? TODO: - Test sending settings - Sending...
Sorry, the reading capture does not seem to contain any useful data, maybe the M709 deos not support that feature? Could you post the output of ``mouse_m908 -M709 -D -``...
The GMMK Pro is currently not supported by this program, and from my limited knowledge seems to use a different protocol. If that is the case, adding support to this...