Arctis Nova Elite Support

[drspangle]

Just got the new Arctis Nova Elite and discovered it has the exact same OLED display on the base station as the Nova Pro Wireless. The base station looks identical in every way, except for the inputs on the back. Hopefully we can get support for this so I can avoid burn-in, because it seems to behave just like the old base station and there's no screen saver, just a dimming after a set time interval.

Here's the dump from it:

-----
product=Arctis Nova Elite
pid=0x2244
interface=3
path=\\?\HID#VID_1038&PID_2244&MI_03&Col01#8&17060a60&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=50, first 16 bytes: [06, c0, ff, 09, 01, a1, 01, 85, 01, 09, f0, 15, 00, 26, ff, 00]
-----
product=Arctis Nova Elite
pid=0x2244
interface=3
path=\\?\HID#VID_1038&PID_2244&MI_03&Col02#8&17060a60&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=49, first 16 bytes: [06, 00, ff, 09, 01, a1, 01, 85, 07, 09, f0, 15, 00, 26, ff, 00]
-----
product=Arctis Nova Elite
pid=0x2244
interface=4
path=\\?\HID#VID_1038&PID_2244&MI_04#8&2a36269e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=37, first 16 bytes: [05, 0c, 09, 01, a1, 01, 85, 01, 09, cd, 09, e9, 09, ea, 09, b5]
-----
product=Arctis Nova Elite
pid=0x2249
interface=0
path=\\?\HID#VID_1038&PID_2249&MI_00#a&165ade68&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=51, first 16 bytes: [06, c0, ff, 09, 01, a1, 01, 06, c1, ff, 09, f0, 15, 00, 26, ff]
-----
product=Arctis Nova Elite
pid=0x2249
interface=1
path=\\?\HID#VID_1038&PID_2249&MI_01#a&298afaa6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
usage=1
report desc sz=23, first 16 bytes: [05, 0c, 09, 01, a1, 01, 19, 00, 2a, ff, 0f, 15, 00, 26, ff, 0f]
-----

[drspangle]

Random update, it turns out the new base station firmware actually does have a screen saver. Still, I would love for it to support the other ggoled features.

[JerwuQu]

Hey!

The report descriptors look a bit different so I have low hopes it would work as-is, but do give the build a try: https://github.com/JerwuQu/ggoled/actions/runs/20332510533

[drspangle]

Unfortunately it didn't work, here's what I got when I tried to run ggoled fill

thread 'main' (39744) panicked at ggoled_cli/src/main.rs:171:33:
called `Result::unwrap()` on an `Err` value: Too few matching devices connected
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I'm not sure that's the most helpful error message. Can I do something else to give more helpful debugging info?

[JerwuQu]

Ah, as expected. The error message is because it checked the USB descriptors and didn't find any matching USB devices. I could adjust the logic to accept the descriptors but it's very unlikely that the actual protocol would be the same even if opening them.

Supporting this device would require a Wireshark USB capture from when interacting with the device via SteelSeries GG to implement the protocol (if changed). I'd prefer someone else to do it though as I cannot test properly without owning the device.

[drspangle]

I tried capturing the traffic from Wireshark but was unable to isolate the device, there just too much noise coming from other devices that share the same root hub. There's got to be a better way. @JerwuQu Do you have documentation describing how you were able to isolate the device traffic previously?

[JerwuQu]

Merry Christmas! No, I didn't document it as it was done early in this project's stages.

Wireshark has the possibility to only watch a single USB bus, so that you only get data related to that device. Then I'd suggest muting audio completely as it made the line go notably more quiet. Otherwise, some noise is fine as it can be filtered out later on.
Then go into SteelSeries GG and launch an app that puts text onto the display and mark the times at which you changed the text to help correlate with the USB capture.

[drspangle]

I seem to be struggling to isolate the device because I have other devices on every root hub connected to my machine (including ARGB stuff, which I can't disconnect for some reason). I've read that there are ways to isolate the device by using a VM, I'll see if I can have some success with that approach.