Drone DetectorPluto+ SDR
--:--:--Z
Starting…
–dB
Level of the drone's video downlink at the antenna (relative dB; the gain is taken out). Higher means closer or better aimed. Walls, your body and the drone's own power control change it too.

Remote ID tracks

–

Spectrum · last sweep

average peak O4 video downlink O4 control link DroneID burst

Detection log

StartLastedSignalsPeak

Settings

Latch alarm: after a drone leaves, the alarm stays amber until acknowledged. Detect at power-on off: the Pluto+ starts paused with the radio free for other programs (SDR++, Python scripts). Lower a gain if a strong access point nearby overloads the receiver (see clip % below). Remote ID: once per sweep the receiver listens 136 ms on Wi-Fi channel 6 (2437 MHz) for ASTM F3411 Remote ID (serial number, position, height, pilot position); any drone broadcasting it raises the alarm. RID tracking: while a drone's Remote ID position is coming in, listen this many more times per sweep (after the 5.1 and 5.8 GHz groups, on the channel it was heard on) for a denser track; each listen adds about 0.5 s to the sweep. Bluetooth RID: the channel 6 listen also covers Bluetooth advertising channel 38 (2426 MHz), where Remote ID add-on modules and many non-DJI drones send it (Bluetooth 4 advertising; Bluetooth 5 long range is not decoded); it costs about 0.1 s of processor time per listen and no extra listen. Other channels: Wi-Fi channels besides 6 where a drone might send Remote ID beacons (1-13, 36-165, comma separated; empty = channel 6 only): one more 136 ms listen per sweep, on the next of them in turn, staying on a channel for 30 s after Remote ID was heard there; it adds about 0.4 s to each sweep. Gain RID 5 GHz: the gain for listens on 5 GHz channels.

Own drones · Geofence

Own drones: a drone whose Remote ID serial number is on this list (up to 4) shows blue (friendly) here and on TAK maps, its visits don't latch, and Home Assistant gets a …-friend event that turns the drone alert into a quiet notification, or clears it (“none”). The video link and DroneID bursts carry no serial number, and the Air 3S sends Remote ID only while its motors run, so the alarm starts before the detector can know whose drone it is. “Hold drone alert” waits up to that long for an own drone's Remote ID before alerting (0 = alert at once). A second drone flying at the same time is told apart only if it sends Remote ID too.
Geofence: when a Remote ID drone that is not on the list comes within this distance of the detector position (set under TAK), Home Assistant gets a …-fence event and TAK shows “INSIDE THE FENCE”; with “Pilot inside alerts too”, also when its pilot does. 0 = off. Tracks are kept in the Pluto's RAM until it restarts (CSV or KML download on each track).

Phone alerts · Home Assistant

When the alarm starts or ends, the Pluto+ posts to Home Assistant (one webhook per event: …-drone, …-gone, …-test, …-start), and the automation "Alert: DJI drone detected" notifies the phone. With Remote ID heard, the alert carries the serial number and height, and the webhook data the drone and pilot positions. The saved URL is never shown here, because this page has no login; enter a new one to replace it.

TAK · Cursor on Target

Puts drones on TAK maps (ATAK, WinTAK, iTAK) as Cursor-on-Target events over UDP. 239.2.3.1:6969 is the TAK mesh multicast that ATAK and WinTAK listen on by default; for a single device, enter its address and a UDP input port set up in its network preferences. Remote ID drones appear as unknown UAS tracks with their pilots. With the detector's position, the detector appears as a sensor, and O4 / DroneID alarms, which give no drone position, as a drone marker at the detector that goes away when the alarm ends. For the position, right-click (WinTAK) or long-press (ATAK) the detector's spot on the TAK map and copy its coordinates: MGRS (18S UJ 23479 06481) or decimal degrees (38.8895, -77.0353). It is stored on the Pluto+ and shown on this page.

Diagnostics

The self-test sends a test signal (a Wi-Fi Remote ID beacon, two Bluetooth Remote ID advertisements, a DroneID burst and O4 bursts) round the AD9361's internal digital loopback, with the transmitter powered down and fully attenuated so nothing goes out, and checks that the detector's own receivers find all of them. It runs a minute after the start and then once a day (not during an alarm); the detector is deaf for about 0.2 s.
Recent sweeps
AgeO4 burstsDroneIDSyncSNRRemote IDResult
Wi-Fi heard (the last Remote ID listen on each channel)
Bluetooth heard (advertising channel 38 in the channel 6 listen, 37 in channel 1's)
Snapshot capture