The ADALM-Pluto transmits. A TRANSMIT stage in SIGNAL PATH drives the Pluto's transmitter over its network protocol, with no libiio and no SoapySDR: CW, AM, NFM, USB and LSB from the microphone or a built-in tone, a power control that reads as the board's own attenuation, the frequency following the receiver unless you press SPLIT, and a PTT you hold with the mouse or the spacebar, or LATCH for hands-free. It never transmits at startup or from a saved config, a latch releases itself after 60 seconds, and if the window stops responding the key is released. The board's tuning and attenuation limits are read off the device. The page says it plainly: the Pluto puts out about +7 dBm, and whether you may radiate that on the frequency you have set is your responsibility and your licensing authority's.
SDRplay says why it is not listed. If the SDRplay API on the machine is older than 3.07, the Source section now says so with the version it found, instead of staying silent while the log carried the sentence.
A saved I/Q file that is not there is remembered. Unplug the drive a recording lived on and FoxSDR starts on the signal generator with the file still saved and its path in the box, ready for Open when the drive is back, the way a saved radio has been kept since 0.92.0.
No Pluto has been on the desk this was built on: the transmit path is proven byte for byte against a fake of the Pluto's own daemon and by the modulators' measurements, and the first real transmission into a dummy load is the test that counts. Reports from Pluto owners will be read closely.
SHA-256 of foxsdr-setup-0.95.0.exe:
3851f76237b18ccf5b0d5808d12533d2e7768905ced8de4d5420d727898d7de6