- Joined
- Jul 30, 2026
- Messages
- 121
- Thread Author
- #1
Short answer: Install and verify the Industrial I/O host stack, connect Pluto by USB, confirm its IIO context and only then open GNU Radio or another application. The USB storage page is useful information, but I/Q applications communicate through the IIO device and network-style context.
Before you start
- Prove Pluto discovery through the Industrial I/O stack before opening GNU Radio or another SDR application.
- Separate USB mass storage, USB networking and I/Q streaming because each function can fail independently.
Step-by-step method
- Step 1: Connect Pluto with a known data cable and allow USB storage and network interfaces to enumerate. Keep the optional power input separate unless the setup specifically needs external power.
- Step 2: Install a current compatible libiio/IIO package and run an IIO information or context-discovery command. Confirm the device attributes can be read before launching a complex application.
- Step 3: In the application, select the Pluto/IIO source and the detected context, start around 1 to 2 MSPS, set RF bandwidth no wider than necessary and tune a known signal.
- Step 4: Use manual gain or a documented AGC mode, then run for ten minutes while checking USB stability. Save context URI, sample rate, RF bandwidth and gain mode.
Concrete example
A common USB context reaches the unit through its USB network interface. Start with a 1 MSPS receive stream, a modest RF bandwidth and a strong known signal. If context discovery fails, changing GNU Radio blocks will not fix the underlying IIO connection.How to judge the result
The setup is complete when IIO tools and the SDR application both identify Pluto, device attributes are readable and a repeated stream starts without lost connection.What to record
- Start with a moderate sample rate such as 1 to 2 MSPS for receive tests, then increase only after the baseline streams without loss.
- Record IIO context URI, local oscillator frequency, RF bandwidth, sample rate and gain mode for a reproducible Pluto setup.
- Treat any frequency-extension change as removal of software limits, not a guarantee of sensitivity, output power or filtering outside the original specification.
Common mistakes
- Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
- Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
- Treating the USB mass-storage volume as the I/Q data interface leads to confusion when the information page opens but no SDR source appears.