Arctis Pro Wireless (not Nova)

[JerwuQu]

Since the original poster keeps closing the issue, I'm opening it here.

So I have 2 Arctis Pro wireless. The hardware IDs are slightly different to the Nova as there are 2 devices under "Sound, video and game controllers" in device manager. I confirmed the REV_0112 is based on the firmware, as my second was on REV_0111

Arctis Pro Wireless Game

USB\VID_1038&PID_1294&REV_0112&MI_03
USB\VID_1038&PID_1294&MI_03

Arctis Pro Wireless Chat

USB\VID_1038&PID_1294&REV_0112&MI_00
USB\VID_1038&PID_1294&MI_00

Originally posted by @ArronaxKP in #2

[ArronaxKP]

If I can help with this if you let me know. I don't know Rust but I'm more than happy to test out code if needed

[JerwuQu]

That'd be awesome!

I made a build here where I added the product ID.

If we're lucky, ggoled_app.exe works right away, but I kinda doubt it.
If it doesn't work, run ggoled.exe clear in cmd and it should give you an error you can paste here.

Make sure to unplug any other SteelSeries headset devices while testing!

[ArronaxKP]

Will test it tomorrow. And let you know if it works

[ArronaxKP]

As expected it failed (same error opening open the window app as well)

D:\Software\steelseries-ggoled>ggoled.exe clear
thread 'main' panicked at ggoled_cli\src\main.rs:156:33:
called Result::unwrap() on an Err value: No matching devices connected
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Screenshot of hardware IDs:

In case its helpful, here is all the devices:

[JerwuQu]

Thanks for testing.

I added a hidden command called ggoled.exe dump-devices which will print out all SteelSeries USB devices and some info about them. I'd be glad if you could try running it!

Available in the latest branch build here.

[ArronaxKP]

Here is the output:

D:\Software\steelseries-ggoled\x86_64-pc-windows-gnu (1)>ggoled.exe dump-devices
-----
pid=0x1290
interface=0
path=\\?\HID#VID_1038&PID_1290&MI_00#a&386a28db&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=61, first 16 bytes: [06, 00, ff, 09, 01, a1, 01, 09, 01, 15, 00, 26, ff, 00, 75, 08]
-----
pid=0x1294
interface=5
path=\\?\HID#VID_1038&PID_1294&MI_05&Col01#a&1427c6cd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=51, first 16 bytes: [05, 0c, 09, 01, a1, 01, 85, 01, 09, e9, 09, ea, 15, 00, 25, 01]
-----
pid=0x1294
interface=5
path=\\?\HID#VID_1038&PID_1294&MI_05&Col02#a&1427c6cd&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=388, first 16 bytes: [06, 00, ff, 09, 01, a1, 01, 09, 0a, a1, 02, 85, ff, 09, 0b, 17]
-----
pid=0x1290
interface=1
path=\\?\HID#VID_1038&PID_1290&MI_01#a&1492eb19&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=34, first 16 bytes: [06, c0, ff, 09, 01, a1, 01, 09, 01, 15, 00, 26, ff, 00, 75, 08]
-----

[JerwuQu]

Thanks!

There's another build here that tries to use the correct interface number. Try ggoled.exe clear again and see if it works.

If this doesn't work, the device likely uses another variant of the USB protocol and there's not much I can do without owning the device myself.

[ArronaxKP]

Kind of as expected, it looks like its not that simple. Thankfully the original had a screensaver so prevents the screen burn in, but would have been nice if this did work. Completely get it, without the device in hand its hard to investigate. Thanks for trying though.

E:\x86_64-pc-windows-gnu (1)>ggoled.exe clear
thread 'main' panicked at ggoled_cli\src\main.rs:167:33:
called Result::unwrap() on an Err value: No OLED device found
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace