Repository navigation
[Device] AQIRYS Polaris #1501
paradoximobiliar
started this conversation in
Device Support Request
Replies: 2 comments
USB captures from the AQIRYS software (wired,
|
| File | Action |
|---|---|
00-launch |
software start-up (handshake + full config read) |
01-idle |
software open, idle (status poll every 30 s) |
02-dpi-stage |
DPI stage changed (only an unsolicited 0x0a event from the mouse) |
03-dpi-value |
DPI value change (no write was captured) |
04-polling |
polling rate 1000 → 500 Hz |
05-led-mode |
lighting effect changed |
06-led-color |
lighting colour changed (ends on pure red) |
07-led-bright |
lighting brightness / speed changed |
08-button |
Forward button remapped to Middle click |
09-macro |
skipped, nothing written |
10-other |
another setting toggled (writes to 0x000a) |
11-reset |
restore defaults |
12-close |
software closed |
Transport
- Host → mouse: HID SET_REPORT (Feature), report ID
0x08, interface 1, 17 bytes. - Mouse → host: report ID
0x09, 17 bytes, on interrupt IN0x82(interface 1). - Every packet in the captures goes to the wired device. The 2.4 GHz receiver (
25a7:fa0f) was plugged in but got no vendor traffic during this session.
Packet format
[0] report id 0x08 (out) / 0x09 (in)
[1] command
[2] 0x00
[3] address hi
[4] address lo
[5] length (bytes of payload used, max 10)
[6..15] payload
[16] checksum = (0x55 - sum(bytes 0..15)) & 0xff
Commands seen
| cmd | meaning (inferred) | example out → in |
|---|---|---|
0x01 |
handshake / challenge | 08 01 00 00 00 04 0f 48 24 36 …97 → 09 01 00 00 00 04 5e b4 a2 e7 …ac |
0x02 |
start / unlock | 08 02 00 00 00 01 01 …49 → 09 02 00 00 00 01 01 …48 |
0x03 |
ready check (sent before every write) | → 09 03 00 00 00 01 01 …47 |
0x04 |
status / version poll (every 30 s) | → 09 04 00 00 00 02 07 01 …3e |
0x07 |
write config memory at addr/len (mouse echoes it back) | 08 07 00 00 00 02 02 53 …ef |
0x08 |
read config memory at addr/len | 08 08 00 00 00 0a …3b |
0x09 |
restore factory defaults | 08 09 00 … 44 → 09 09 00 … 43 |
0x0a |
unsolicited event from mouse (seen when DPI stage changed) | 09 0a 00 00 00 0a 01 01 61 …d5 |
Config memory map (read at start-up)
Values are stored with an inline checksum: 2-byte fields are [v, 0x55-v], and 4-byte entries are [a, b, c, 0x55-a-b-c].
0000: 01 54 01 54 00 55 00 55 00 55 01 54 09 09 00 43
0010: 12 12 00 31 0a 0a 00 41 12 12 00 31 17 17 00 27
0020: 20 20 00 15 00 00 00 55 bd bd 00 db ff 00 00 56
0030: 00 00 ff 56 00 ff 00 56 ff 00 ff 57 00 ff ff 57
0040: ff 80 00 d6 ff ff ff 58 7d 7d ff 5c 02 53 80 d5
0050: 03 52 00 55 ff 00 ff 57 03 52 80 d5 03 52 00 55
0060: 01 01 00 53 01 02 00 52 01 04 00 50 01 08 00 4c
0070: 01 10 00 44 00 00 00 55 04 28 03 26 02 01 00 52
0080: 07 00 00 4e 03 02 00 50 05 00 00 50 02 01 00 52
0090: 00 00 00 55 00 00 00 55 00 00 00 55 00 00 00 55
00a0: 04 e4 00 7f 96 ff 59
0x0000polling rate:01= 1000 Hz,02= 500 Hz (written as02 53).0x000a: some other option. It was toggled02/01in10-other.0x000c–0x002b: probably the DPI table, 8 ×[x, y, hi, ck](raw values09 12 0a 12 17 20 00 bd). The DPI value change in step 03 didn't produce a write, so the encoding is still unconfirmed.0x002c–0x004b: per-DPI-stage indicator colours, 8 ×[R, G, B, ck](red, green, blue, magenta, cyan, orange, white, lavender).0x0060–0x008f: button table, 4 bytes per button[type, code, mod, ck]. Type01= mouse button bitmask (01L,02R,04M,08back,10forward). Remapping Forward → Middle wrote01 04 00 50to0x0070.0x00a0(7 bytes): lighting[mode, R, G, B, speed?, brightness, ck], where ck =0x55 - sum(bytes 0..5). Modes00,01,02,04were seen. Brightness wentff→af, and byte 4 changed with speed/brightness (13,19,28,96).
I can capture more if it helps: wireless through the receiver, DPI value changes, a macro, or anything else.
0 replies
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Device type
Mouse
Device model
AQIRYS Polaris
vendorId:productId
25a7:fa0f (2.4 GHz receiver), 25a7:fa0c (wired)
Connection type
Multiple (tell us below)
What happens today?
Detected but shows as unsupported / no controls
Diagnostics
Can you help test?
Yes, and I can capture USB traffic (Wireshark / usbpcap)
Anything else?
Connection: dual mode, 2.4 GHz receiver (tested above) + wired USB-C (charging/wired mode).
Mine is the White version: https://www.aqirys.com/product/polaris-white
Specs: PixArt PAW3335, 16000 DPI, 1000 Hz polling, 7 programmable buttons, Kailh switches, RGB, onboard memory.
Vendor software (Windows):
Related: AQIRYS NYX request #1039 (same brand, possibly the same OEM platform).
Happy to capture USBPcap traces of the vendor software changing DPI / polling rate / RGB.
All reactions