Also known as: BladeRF, blade RF, bladeRF 2.0 micro
Reader-supported. GopherTrunk is free, open-source software. Some
hardware links on this page go to Amazon with our Associates tag
(gophertrunk-20); if you buy through them we may earn a small
commission at no extra cost to you. Links to out-of-production gear may go to
eBay searches instead; we have no affiliate relationship with eBay and earn
nothing there. It never changes which gear we recommend, and
the software stays free either way. How GopherTrunk is funded →
BladeRF is a line of USB 3.0 software-defined radio transceivers from the company Nuand, distinguished from cheaper receivers by an on-board FPGA and a full-duplex transmit and receive path.1 Where an RTL-SDR is a receive-only dongle, a BladeRF is a two-way radio platform that can both listen and transmit while running custom real-time DSP in fabric before samples ever reach the host.
Key takeaways FPGA-equipped full-duplex transceiver — overkill for scanning. Nuand’s bladeRF pairs a 12-bit front end with an on-board FPGA and true transmit/receive; the 2.0 micro covers ~47 MHz–6 GHz with up to ~56 MHz of bandwidth. GopherTrunk uses none of the FPGA or TX capability — just its wideband IQ. GopherTrunk support is network only: it drives the bladeRF over a SoapySDR/rtl_tcp bridge, not as a direct USB device, because the pure-Go USB drivers cover only RTL-SDR, HackRF, and Airspy. At $480–$720 it’s far more radio than trunk-tracking needs. Like every receiver, it can’t decode AES encryption.
GopherTrunk support: network only. GopherTrunk drives the bladeRF over the network via SoapySDRServer/SoapyRemote (or an
rtl_tcp-style bridge), not as a direct USB device — you run thelibbladeRF-backed SoapySDR module and server on the machine it’s plugged into and mount it over TCP. GopherTrunk’s pure-Go USB drivers cover only RTL-SDR, HackRF, and Airspy. See the hardware guide and rtl_tcp notes.
Overview
Nuand launched the original BladeRF in 2013 through a Kickstarter campaign, positioning it between the low-cost hobbyist dongles and the far pricier USRP research platforms. Two things set the family apart: a genuine transmit capability with independent RX and TX chains (true full duplex), and a user-programmable FPGA that lets developers offload filtering, channelisation, or an entire modem into hardware. That FPGA is the defining feature — it is why the BladeRF appears in GNU Radio flowgraphs, cellular-network experiments, and custom protocol work rather than just spectrum monitoring.
Variants
Two hardware generations exist, with meaningfully different coverage:
- BladeRF x40 / x115 (2013). The original board pairs a Lime Microsystems LMS6002D RF transceiver with an Intel/Altera Cyclone IV FPGA (40k or 115k logic elements — the number in the model name). It tunes roughly 300 MHz – 3.8 GHz with up to ~28 MHz of usable bandwidth and 12-bit converters.
- BladeRF 2.0 micro xA4 / xA5 / xA9 (2018). The current generation moves to the Analog Devices AD9361 transceiver (the same silicon behind many mid-range SDRs) and a Cyclone V FPGA. It extends coverage to about 47 MHz – 6 GHz, widens the channel to as much as ~56 MHz, and adds a 2×2 MIMO option, bias-tee outputs, and an expansion header. The suffix again denotes FPGA size (xA4 = 49k, xA9 = 301k logic elements).
Both generations use 12-bit analog-to-digital and digital-to-analog converters — a large dynamic-range improvement over the 8-bit RTL2832U — and connect over USB 3.0 (SuperSpeed) to sustain the high sample rates that wide bandwidth demands.
In practice
The FPGA and the transmit path put the BladeRF in a different class of use than a scanner dongle. Typical projects include running a small GSM or LTE base station in a lab, building custom modems, passive radar, and any workflow where DSP must happen at line rate before the USB bus becomes a bottleneck. The trade-off is cost and complexity: at $480–$720 it is many times the price of an RTL-SDR, transmitting legally requires appropriate licensing and filtering, and getting the most from the board means writing or loading FPGA images. For pure reception it is often overkill compared with a purpose-built receiver.
Relevance to GopherTrunk
GopherTrunk is a receive-only trunking decoder, so it uses none of the BladeRF’s transmit capability and does not load custom FPGA images. Where a BladeRF can help is as a plain wideband IQ source through a SoapySDR-style interface: its 12-bit front end and wide capture bandwidth can channelise several control channels at once, much like an Airspy does in GopherTrunk’s wideband role. For most users a BladeRF is more radio than trunk-tracking needs — an RTL-SDR pool or an Airspy is the cheaper, better-matched tool — but if you already own one, it is a capable capture front end. See the hardware guide for GopherTrunk’s tested devices.
Where to buy
The bladeRF is sold by Nuand and its distributors, and listed on Amazon. Before buying one for GopherTrunk, note the integration path: it is supported over the network only, through a SoapySDR/rtl_tcp bridge rather than GopherTrunk’s direct USB drivers — see the hardware guide. For pure trunk-tracking a RTL-SDR pool or an Airspy is the cheaper, better-matched tool; the bladeRF earns its keep on FPGA and transmit projects, and doubles as a capable capture front end if you already own one.
As an Amazon Associate, GopherTrunk earns from qualifying purchases — at no extra cost to you. It never changes what we recommend.
Sources
Frequently asked questions
Does GopherTrunk support the bladeRF?
Yes, but network only. GopherTrunk’s pure-Go USB drivers cover RTL-SDR, HackRF, and Airspy — not Nuand’s libbladeRF stack. You drive the bladeRF over the network via a SoapySDRServer/SoapyRemote (or rtl_tcp) bridge: run the Soapy module and server on the machine it’s plugged into, then mount it over TCP. See the hardware guide.
Does GopherTrunk use the bladeRF's FPGA or transmit path?
No. GopherTrunk is a receive-only decoder and treats the bladeRF as a plain wideband IQ source over the bridge — it loads no custom FPGA images and never keys the transmitter. The FPGA and TX chain are the bladeRF’s strengths for other projects, not for trunk-tracking.
Is a bladeRF worth it just for scanning?
For most users, no. At $480–$720 it is many times the price of an RTL-SDR, and its 12-bit front end and wide capture bandwidth — while capable of channelising several control channels at once — are more radio than trunk-tracking needs. If you already own one it makes a capable capture front end; if you’re buying for scanning, an RTL-SDR pool or an Airspy is cheaper and better matched.
bladeRF x40 or bladeRF 2.0 micro for GopherTrunk?
The 2.0 micro (AD9361, Cyclone V) is the current generation, covering ~47 MHz–6 GHz with up to ~56 MHz bandwidth — the one to get for VHF/UHF trunking coverage. Either way it feeds GopherTrunk only through the SoapySDR/rtl_tcp bridge, not as a direct USB device.