Four DJI receivers, two USB IDs
You'd expect each DJI receiver to have its own USB product ID. They don't: four receivers share two. Here's how Mic Control works out which one is plugged in, and how it handles models nobody here has tested.
The problem
When a USB device is plugged in, the first thing software sees is its vendor and product ID. For DJI’s wireless mic receivers the vendor is always 0x2ca3, and the product IDs look like this:
| USB ID | Control interface | Receivers |
|---|---|---|
2ca3:4011 |
6 | DJI Mic Mini, DJI Mic Series Mobile Receiver |
2ca3:4015 (4115 in 4-channel mode) |
4, alternate setting 1 | DJI Mic 3, DJI Mic Mini 2S |
So the ID tells you the family: which interface to open and which dialect of DJI’s DUML framing to speak. It doesn’t tell you the model, and the models don’t support the same settings. The Mobile Receiver has no auto power-off; the Mini 2S has Safety Track and the Mic 3 doesn’t; the Mic 3 has lossless audio and receiver gains and the Mini 2S doesn’t. Send a setting a receiver doesn’t have and, at best, it gets rejected.
Step 1: open by family
Mic Control opens the receiver as the most likely model for its USB ID. Within a family the transport is identical, so this is safe: same interface, same endpoints, same framing. Status pushes start arriving straight away.
Step 2: ask the receiver who it is
Then it asks. Two read-only requests, first documented for the Mobile Receiver by piedol/lavdeck, work on the Mic 3 as well:
- Get version (command set
0x00, id0x01, empty payload). The Mic 3 receiver answers with the hardware nameDM303_RX, NUL-padded, followed by its firmware version in reversed bytes:0a 00 01 03is03.01.00.10. - Get capability (command set
0x5B, id0x12). On the Mic 3 it only returns three one-byte flags per unit, so it isn’t a usable feature list.
For the 4015 family, DM303_RX means a Mic 3; any other answer means a Mini 2S. For the 4011 family, the identity push gives it away: the Mobile Receiver reports the product name DJI Mic Mini 2 for itself, and the Mic Mini reports DJI Mic Mini. As soon as the answer arrives, Mic Control switches to the right model, keeping the interface it already opened.
Transmitters are easier: they report their own product name in the identity push, so a Mic 2 transmitter on a Mobile Receiver shows exactly the controls a Mic 2 has.
The 4-channel surprise
On the Mic 3 the product ID isn’t even constant. Switch the receiver to four-channel mode and it re-enumerates as 2ca3:4115: the operating system sees the device disappear and come back with a new ID, and the USB audio input reconnects. Mic Control accepts both IDs for the family and finds the receiver again on its own. If you record while switching modes, your recording app may need you to pick the input again; there’s more on that in mono, stereo or 4CH.
Two more channel-mode values, 0x03 and 0x06, are acknowledged by the Mic 3 but change nothing; 0x03 even makes the receiver re-enumerate and come back in mono. They’re never sent.
Supporting hardware nobody here has tested
Mic Control is tested on one setup: a Mic 3 with firmware 03.01.00.10 and two transmitters. The Mini 2S, the Mobile Receiver and the Mic 2 transmitters are supported from other people’s work, all of it tested on real hardware:
- usokawa/dji-mic-mo and kroqdotdev/lavboard for the Mini 2S receiver;
- piedol/lavdeck and a pull request to the original project for the Mobile Receiver;
- nicolasmmb/DJI-Mic-Utility for the Mic 2 transmitters.
Two rules keep that safe:
- Only send what someone confirmed. For untested combinations, Mic Control sends only commands another project has seen work on that hardware. A Mic 2 transmitter acknowledges voice tone and gain commands but its status doesn’t change, so those controls aren’t shown for it at all.
- Check every answer. Each command asks for an acknowledgement. On the Mic 3, the acknowledgement’s result byte is
0x00when the setting was applied and0xffwhen the receiver refused it. A refusal becomes an error message on screen instead of a switch that silently doesn’t work.
There’s one more quirk worth knowing if you write your own tool: on the Mic 3, the first command after opening the interface is sometimes dropped, neither applied nor acknowledged. Unanswered commands are re-sent, and that one goes through on the second try.
What isn’t supported, and why
The DJI Mic 2’s own receiver and the original DJI Mic from 2021 have no documented USB control interface. The Mic 2 IDs seen in the wild, 2ca3:002d and 2ca3:0a69, are file-transfer modes. Without a control interface there’s nothing to talk to, so Mic Control doesn’t pretend.
The full tables are in the protocol notes. If you have a Mini 2S, a Mobile Receiver or a Mic 2 and can test, an issue on GitHub with what works and what doesn’t is the most useful thing you can send. The models and what Mic Control can do with each are summed up in DJI Mic Mini on your computer.