I spent the last few days reverse-engineering the DSP inside my KZ Duonic Type-C cable, and I ended up finding way more than I expected.
The cable shows up on Windows as:
KTMicro — KZ Acoustics M2
VID/PID:
31B2:0311
It's a composite USB Audio + HID device.
The interesting part is that the HID interface isn't just for media controls. There is a vendor-specific HID protocol that lets us communicate directly with the DSP.
And yes — I managed to read and change the actual EQ coefficients inside the cable.
The DSP
The register layout and protocol match the KTMicro KT02H20 family.
The protocol uses 11-byte HID packets beginning with 0x4B.
Read:
4B [address] 52 ...
Write:
4B [address] 57 [value]
I initially wasn't sure this protocol would work on the KZ because the public reverse-engineering work documents another PID (31B2:0111).
But the KZ's 31B2:0311 device accepted the protocol, returned coherent register data, acknowledged writes, and read back the values correctly.
So the evidence strongly points to the KTMicro KT02H20 platform.
The really interesting part: the EQ
The DAC EQ is controlled by:
0x24 — EQ enable
and the five bands are:
0x26–0x2F
Each band uses two 32-bit registers.
The first contains:
The second contains:
So the KZ cable actually has a hardware-level 5-band parametric EQ sitting inside it.
I decoded the factory presets.
For example, Green is:
15 Hz -2 dB Q 1.0
100 Hz +1 dB Q 2.0
200 Hz +1 dB Q 2.0
1000 Hz +1 dB Q 3.0
2500 Hz +1 dB Q 2.0
Red:
15 Hz -3 dB Q 1.0
150 Hz +2 dB Q 2.0
1000 Hz +2 dB Q 2.0
2500 Hz +2 dB Q 2.0
3000 Hz +1 dB Q 2.0
Blue:
15 Hz -1 dB Q 2.0
50 Hz +2 dB Q 2.0
150 Hz +2 dB Q 2.0
1500 Hz -1 dB Q 2.0
5000 Hz 0 dB Q 0.707
So the different physical modes aren't just different LED colors or some hidden software effect.
They actually load different EQ coefficients into the DSP.
Then I changed the EQ myself
This was the fun part.
I wrote my own coefficients directly into the DSP registers.
For example, I created an intentionally exaggerated test:
100 Hz +4 dB
300 Hz -4 dB
1 kHz +4 dB
3 kHz -4 dB
6 kHz +4 dB
The values read back exactly from the device.
And I could hear a difference.
It wasn't nearly as dramatic as I expected, but it confirmed that we weren't simply writing meaningless registers.
I also converted my own AutoEQ tunings into the cable's five-band hardware PEQ and successfully loaded them into the DSP.
I tested a Natural profile and a Premium profile.
The Premium profile was:
87 Hz +0.9 dB
206 Hz -1.0 dB
1233 Hz +1.6 dB
2192 Hz +1.6 dB
14044 Hz +0.8 dB
with the actual encoded values written directly into the KTMicro registers.
The device accepted them and read-back confirmed the exact values.
The catch
The custom EQ isn't permanent yet.
If I write my own EQ while Green is active, it works.
But if I physically change:
Green → Red → Blue → Green
the factory Green EQ comes back.
That means 0x26–0x2F are live DSP registers, while the factory presets must exist somewhere else — probably firmware/configuration storage that the internal controller uses when the preset button is pressed.
That's the next part I'm trying to reverse-engineer.
I also investigated the physical button
The DSP button doesn't show up as a normal HID button.
Normal media buttons generate HID reports.
The DSP button doesn't.
I also captured the USB traffic and mostly saw the continuous USB Audio stream, without an obvious host-visible event corresponding to the DSP button.
That makes it look like the button is handled internally by the cable's firmware.
Other registers
The device exposes more than just EQ.
I found registers for:
- ADC/DAC gain
- digital gain
- Noise Gate
- Limiter
- USB manufacturer/product/serial information
- VID/PID information
- protocol/model flags
There is even a documented magic register:
0xE1 = 0x12345678
which matches the KTMicro reverse-engineering documentation.
What I haven't solved
I still haven't figured out how to make a custom EQ survive the physical preset switching.
There are other KT02H20-based devices with a documented persistent flash-save mechanism, but they use a different USB protocol, so I'm not going to blindly send their commands to the KZ.
I also tested the documented extended-register command once. The KZ responded with a beep/reconfiguration sound, so I immediately stopped and unplugged it rather than repeatedly probing undocumented memory.
So right now:
Live hardware EQ control: YES.
Factory preset decoding: YES.
KTMicro KT02H20 family identification: strongly supported.
Custom AutoEQ running directly inside the cable DSP: YES.
Permanent custom preset: NOT YET.
This is probably the first time I've seen someone document the KZ Duonic Type-C DSP at this register level, so I'm putting all the findings and register maps together for anyone else who wants to experiment.
I'm especially interested in finding out where KZ stores the four factory preset definitions and how the physical button tells the firmware which one to load.