Open user030276 opened 2 years ago
I have added Gladius III to the rogdrv. You can test if it works.
Thank you kyokenn! You rule!
user@m5:~/dev/rogdrv$ rogdrv --console --debug
[2022-08-31 16:08:54,447] [DEBUG] searching for device Gladius2 (VendorID: 0x0B05, ProductID: 0x1845)
[2022-08-31 16:08:54,485] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:08:54,486] [DEBUG] 0 devices found
[2022-08-31 16:08:54,486] [DEBUG] searching for device Gladius2Origin (VendorID: 0x0B05, ProductID: 0x1877)
[2022-08-31 16:08:54,486] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:08:54,486] [DEBUG] 0 devices found
[2022-08-31 16:08:54,486] [DEBUG] searching for device Gladius2OriginPink (VendorID: 0x0B05, ProductID: 0x18CD)
[2022-08-31 16:08:54,486] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:08:54,486] [DEBUG] 0 devices found
[2022-08-31 16:08:54,486] [DEBUG] searching for device Gladius3 (VendorID: 0x0B05, ProductID: 0x197B)
[2022-08-31 16:08:54,486] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:08:54,487] [DEBUG] found 3 subdevices:
[2022-08-31 16:08:54,487] [DEBUG] /dev/hidraw1: ASUSTeK ROG GLADIUS III interface 0
[2022-08-31 16:08:54,487] [DEBUG] /dev/hidraw2: ASUSTeK ROG GLADIUS III interface 1 [using as keyboard]
[2022-08-31 16:08:54,487] [DEBUG] /dev/hidraw3: ASUSTeK ROG GLADIUS III interface 2 [using as control]
[2022-08-31 16:08:54,487] [DEBUG] opening control subdevice
[2022-08-31 16:08:54,487] [DEBUG] opening device "/dev/hidraw3"
[2022-08-31 16:08:54,487] [DEBUG] opening keyboard subdevice
[2022-08-31 16:08:54,487] [DEBUG] opening device "/dev/hidraw2"
So far, so good. Next:
user@m5:~$ rogdrv-config profile -p 1
All 4 light profiles are correctly set, starting from 1.
$rogdvr-config dpi --preset The number of DPI presets prints as 2. The actual number should be 4. No change with any number and --preset Pressing the DPI button changes the DPI, and prints 'device is in invalid state...' and is shown below:
user@m5:~$ rogdrv-config dpi -p 1 --debug
[2022-08-31 16:21:53,057] [DEBUG] searching for device Gladius2 (VendorID: 0x0B05, ProductID: 0x1845)
[2022-08-31 16:21:53,095] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:21:53,096] [DEBUG] 0 devices found
[2022-08-31 16:21:53,096] [DEBUG] searching for device Gladius2Origin (VendorID: 0x0B05, ProductID: 0x1877)
[2022-08-31 16:21:53,096] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:21:53,096] [DEBUG] 0 devices found
[2022-08-31 16:21:53,096] [DEBUG] searching for device Gladius2OriginPink (VendorID: 0x0B05, ProductID: 0x18CD)
[2022-08-31 16:21:53,096] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:21:53,096] [DEBUG] 0 devices found
[2022-08-31 16:21:53,096] [DEBUG] searching for device Gladius3 (VendorID: 0x0B05, ProductID: 0x197B)
[2022-08-31 16:21:53,096] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:21:53,097] [DEBUG] found 3 subdevices:
[2022-08-31 16:21:53,097] [DEBUG] /dev/hidraw1: ASUSTeK ROG GLADIUS III interface 0
[2022-08-31 16:21:53,097] [DEBUG] /dev/hidraw2: ASUSTeK ROG GLADIUS III interface 1 [using as keyboard]
[2022-08-31 16:21:53,097] [DEBUG] /dev/hidraw3: ASUSTeK ROG GLADIUS III interface 2 [using as control]
[2022-08-31 16:21:53,097] [DEBUG] opening control subdevice
[2022-08-31 16:21:53,097] [DEBUG] opening device "/dev/hidraw3"
[2022-08-31 16:21:53,097] [DEBUG] opening keyboard subdevice
[2022-08-31 16:21:53,097] [DEBUG] opening device "/dev/hidraw2"
[2022-08-31 16:21:53,098] [DEBUG] getting DPI and polling rate
[2022-08-31 16:21:53,098] [DEBUG] number of dpi presets: 2
[2022-08-31 16:21:53,098] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:55,409] [DEBUG] < 03 12 08 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:55,409] [DEBUG] device is in invalid state, retrying (1/10)
[2022-08-31 16:21:55,410] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:56,815] [DEBUG] < 03 12 08 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:56,815] [DEBUG] device is in invalid state, retrying (2/10)
[2022-08-31 16:21:56,816] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:58,018] [DEBUG] < 03 12 08 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:58,018] [DEBUG] device is in invalid state, retrying (3/10)
[2022-08-31 16:21:58,019] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:59,006] [DEBUG] < 03 12 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:59,006] [DEBUG] device is in invalid state, retrying (4/10)
[2022-08-31 16:21:59,007] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:59,695] [DEBUG] < 03 12 08 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:59,695] [DEBUG] device is in invalid state, retrying (5/10)
[2022-08-31 16:21:59,696] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:00,159] [DEBUG] < 03 12 08 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:00,159] [DEBUG] device is in invalid state, retrying (6/10)
[2022-08-31 16:22:00,160] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:00,575] [DEBUG] < 03 12 08 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:00,575] [DEBUG] device is in invalid state, retrying (7/10)
[2022-08-31 16:22:00,576] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:00,968] [DEBUG] < 03 12 08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:00,968] [DEBUG] device is in invalid state, retrying (8/10)
[2022-08-31 16:22:00,969] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:01,318] [DEBUG] < 03 12 08 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:01,318] [DEBUG] device is in invalid state, retrying (9/10)
[2022-08-31 16:22:01,319] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:01,704] [DEBUG] < 03 12 08 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:22:01,704] [DEBUG] device is in invalid state, retrying (10/10)
Traceback (most recent call last):
File "/usr/local/bin/rogdrv-config", line 10, in <module>
sys.exit(rogdrv_config())
File "/usr/local/lib/python3.7/dist-packages/rog/__main__.py", line 402, in rogdrv_config
app.run()
File "/usr/local/lib/python3.7/dist-packages/rog/__main__.py", line 93, in run
method()
File "/usr/local/lib/python3.7/dist-packages/rog/__main__.py", line 252, in dpi
dpis, rate, response, snapping = self._device.get_dpi_rate_response_snapping()
File "/usr/local/lib/python3.7/dist-packages/rog/device/mixins.py", line 29, in get_dpi_rate_response_snapping
dpis, rate, bresponse, snapping = super().get_dpi_rate_response_snapping()
File "/usr/local/lib/python3.7/dist-packages/rog/device/base.py", line 424, in get_dpi_rate_response_snapping
response = self.query(bytes(request))
File "/usr/local/lib/python3.7/dist-packages/rog/device/base.py", line 212, in query
raise DeviceError()
rog.device.base.DeviceError
user@m5:~$
$ rogdrv-config dpi -d 800 --debug no change with any number given to -d debug reports number is halved
giving maximum dpi of 26000 is out of range
user@m5:~$ rogdrv-config dpi -d 26000 --debug
[2022-08-31 16:28:11,860] [DEBUG] searching for device Gladius2 (VendorID: 0x0B05, ProductID: 0x1845)
[2022-08-31 16:28:11,898] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:28:11,898] [DEBUG] 0 devices found
[2022-08-31 16:28:11,899] [DEBUG] searching for device Gladius2Origin (VendorID: 0x0B05, ProductID: 0x1877)
[2022-08-31 16:28:11,899] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:28:11,899] [DEBUG] 0 devices found
[2022-08-31 16:28:11,899] [DEBUG] searching for device Gladius2OriginPink (VendorID: 0x0B05, ProductID: 0x18CD)
[2022-08-31 16:28:11,899] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:28:11,899] [DEBUG] 0 devices found
[2022-08-31 16:28:11,899] [DEBUG] searching for device Gladius3 (VendorID: 0x0B05, ProductID: 0x197B)
[2022-08-31 16:28:11,899] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:28:11,900] [DEBUG] found 3 subdevices:
[2022-08-31 16:28:11,900] [DEBUG] /dev/hidraw1: ASUSTeK ROG GLADIUS III interface 0
[2022-08-31 16:28:11,900] [DEBUG] /dev/hidraw2: ASUSTeK ROG GLADIUS III interface 1 [using as keyboard]
[2022-08-31 16:28:11,900] [DEBUG] /dev/hidraw3: ASUSTeK ROG GLADIUS III interface 2 [using as control]
[2022-08-31 16:28:11,900] [DEBUG] opening control subdevice
[2022-08-31 16:28:11,900] [DEBUG] opening device "/dev/hidraw3"
[2022-08-31 16:28:11,900] [DEBUG] opening keyboard subdevice
[2022-08-31 16:28:11,900] [DEBUG] opening device "/dev/hidraw2"
[2022-08-31 16:28:11,901] [DEBUG] setting DPI to 13000.0 for preset 1
Traceback (most recent call last):
File "/usr/local/bin/rogdrv-config", line 10, in <module>
sys.exit(rogdrv_config())
File "/usr/local/lib/python3.7/dist-packages/rog/__main__.py", line 402, in rogdrv_config
app.run()
File "/usr/local/lib/python3.7/dist-packages/rog/__main__.py", line 93, in run
method()
File "/usr/local/lib/python3.7/dist-packages/rog/__main__.py", line 249, in dpi
self._device.set_dpi(args.dpi, preset=args.preset or 1)
File "/usr/local/lib/python3.7/dist-packages/rog/device/mixins.py", line 33, in set_dpi
super().set_dpi(dpi / 2, preset=preset)
File "/usr/local/lib/python3.7/dist-packages/rog/device/base.py", line 463, in set_dpi
self.query(bytes(request))
ValueError: bytes must be in range(0, 256)
user@m5:~$
user@m5:~$ rogdrv-config dump -o omg.json ## creates 0 byte file, hangs.
user@m5:~$ rogdrv-config rate -r 500 --debug ^polling rate does not change, but this rate command does change DPI
OK ! Thank you very much again. Please tell me if you want anything specific tested or done. Good luck,
setting LED mode partly works the brightness 4 is dim there is a second color displayed --color aaaaaa gives white and then red in --mode reactive the different modes are all correct the side LED does not work in reactive mode, seems to work in all other modes
user@m5:~$ rogdrv-config led --debug --mode reactive --color aaaaaa --brightness 4
[2022-08-31 16:52:21,736] [DEBUG] searching for device Gladius2 (VendorID: 0x0B05, ProductID: 0x1845)
[2022-08-31 16:52:21,774] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:52:21,774] [DEBUG] 0 devices found
[2022-08-31 16:52:21,775] [DEBUG] searching for device Gladius2Origin (VendorID: 0x0B05, ProductID: 0x1877)
[2022-08-31 16:52:21,775] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:52:21,775] [DEBUG] 0 devices found
[2022-08-31 16:52:21,775] [DEBUG] searching for device Gladius2OriginPink (VendorID: 0x0B05, ProductID: 0x18CD)
[2022-08-31 16:52:21,775] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:52:21,775] [DEBUG] 0 devices found
[2022-08-31 16:52:21,775] [DEBUG] searching for device Gladius3 (VendorID: 0x0B05, ProductID: 0x197B)
[2022-08-31 16:52:21,775] [DEBUG] getting list of devices using "hidapi-cffi"
[2022-08-31 16:52:21,776] [DEBUG] found 3 subdevices:
[2022-08-31 16:52:21,776] [DEBUG] /dev/hidraw1: ASUSTeK ROG GLADIUS III interface 0
[2022-08-31 16:52:21,776] [DEBUG] /dev/hidraw2: ASUSTeK ROG GLADIUS III interface 1 [using as keyboard]
[2022-08-31 16:52:21,776] [DEBUG] /dev/hidraw3: ASUSTeK ROG GLADIUS III interface 2 [using as control]
[2022-08-31 16:52:21,776] [DEBUG] opening control subdevice
[2022-08-31 16:52:21,776] [DEBUG] opening device "/dev/hidraw3"
[2022-08-31 16:52:21,776] [DEBUG] opening keyboard subdevice
[2022-08-31 16:52:21,776] [DEBUG] opening device "/dev/hidraw2"
[2022-08-31 16:52:21,777] [DEBUG] setting LED all color to rgb(170,170,170) with mode reactive and brightness 4
[2022-08-31 16:52:21,777] [DEBUG] > 51 28 03 00 04 04 AA AA AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
left click generates some random keyboard output. the output keeps changing. here is left click.
[2022-09-01 09:31:44,182] [DEBUG] < 00 00 00 00 01 00 03 00 00 00 00
[2022-09-01 09:31:44,182] [DEBUG] < 00 00 00 00 01 00 03 27 00 00 00
[2022-09-01 09:31:44,313] [DEBUG] < 00 00 00 00 00 00 03 00 00 00 00
^ bytes "27 00" changes each click.
right click is OK.
middle mouse button / scroll wheel generates letter "a" or number 0 and maybe new line, and other characters. here is scroll wheel click.
[2022-09-01 09:27:36,184] [DEBUG] < 00 00 00 00 04 00 03 00 00 00 00
[2022-09-01 09:27:36,288] [DEBUG] < 00 00 00 00 00 00 03 00 00 00 00
back button outputs . character
[2022-09-01 09:39:00,733] [DEBUG] < 00 00 00 00 08 00 03 00 00 00 00
[2022-09-01 09:39:00,982] [DEBUG] < 00 00 00 00 00 00 03 00 00 00 00
forward button outputs m
[2022-09-01 09:39:46,844] [DEBUG] < 00 00 00 00 10 00 03 00 00 00 00
[2022-09-01 09:39:46,980] [DEBUG] < 00 00 00 00 00 00 03 00 00 00 00
The number of DPI presets prints as 2. The actual number should be 4.
I have changed number of DPI presets, forgot that all recent mice have 4 presets.
user@m5:~$ rogdrv-config rate -r 500 --debug ^polling rate does not change, but this rate command does change DPI
Correct number of DPI presets should solve it and also other options like angle snapping and button response delay.
[2022-08-31 16:21:53,098] [DEBUG] number of dpi presets: 2
[2022-08-31 16:21:53,098] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:55,409] [DEBUG] < 03 12 08 00 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[2022-08-31 16:21:55,409] [DEBUG] device is in invalid state, retrying (1/10)
This is bad, you can try to replug the mouse. Maybe it just stuck in some wrong state. If it still doesn't helps then the query command has changed and you will need an USB debugger to find the correct one.
$ rogdrv-config dpi -d 800 --debug
Can you show debug output of this one?
middle mouse button / scroll wheel generates letter "a" or number 0 and maybe new line, and other characters. here is scroll wheel click.
This is weird. Does the buttons actually work without a driver? You may not need to debug the events if the buttons are already working. :smiley:
Thank you for your reply kyokenn, and thank you for the help.
dpi presets do not change mouse dpi
user@m5:~$ rogdrv-config dpi --preset 3 --debug4
[2022-09-01 12:29:31,435] [DEBUG] number of dpi presets: 4
[2022-09-01 12:29:31,435] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
dpi flag does not change dpi
user@m5:~$ rogdrv-config dpi --dpi 400 --debug
[2022-09-01 12:31:04,643] [DEBUG] setting DPI to 200.0 for preset 1
[2022-09-01 12:31:04,643] [DEBUG] > 51 31 00 00 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
All buttons work without a driver.
With your driver they work and give the extra keyboard outputs.
Mouse polling is now correct! Way to go!
user@m5:~$ rogdrv-config rate -r 500 --debug
[2022-09-01 12:35:23,018] [DEBUG] setting polling rate to 500
[2022-09-01 12:35:23,018] [DEBUG] > 51 31 04 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
rogdrv-config prints that device is in invalid state whenever DPI button is pushed. The DPI changes normally.
Thank you again !
[2022-09-01 12:29:31,435] [DEBUG] > 12 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
This is only request (what the driver is sending to the mouse), but I also need a response (what the mouse answers) marked as "<".
Thank you for the reply!
There is no response.
With $ rogdrv --console --debug
running, and then running
$ rogdrv-config dpi --preset 2 --debug
there is no response, no < output in any debug window.
this is the same for the --dpi switch
With $ rogdrv --console --debug running, and then running
You may need to close it, because it could block the reading from device. Those 2 tools should not be running at the same time.
Thank you again.
With only $ rogdrv-config running the debug ouput and effect is the same
sorry if this is a double post. i am not sure what reply by email does.
With only $ rogdrv-config running the debug ouput and effect is the same
I see. So it's stuck and waiting for response indefinitely. You will need a USB debugger (like https://github.com/djpnewton/busdog ) and Windows PC or VM with ASUS Armoury to get the actual commands for getting/setting DPI.
I have switched back-end to ratbag-python, so there is a chance that I could work now.
Kyoken,
Greetings! Thank you for your project, rogdrv. I wonder if we can add my Gladius III.
Please say if you have any thoughts.
All the best,