Also known as: MSi001, Mirics MSi001
MSi001 is a wideband RF tuner chip from the British fabless company Mirics, and the front-end half of the two-chip design at the heart of the SDRplay RSP family of software-defined radio receivers.1 Where a budget dongle uses a Rafael Micro or Elonics tuner ahead of an RTL2832U, an SDRplay RSP pairs the MSi001 tuner with the Mirics MSi2500, which combines the analog-to-digital converter and USB interface. Together the two chips give the RSP line its wide, continuous coverage and better dynamic range than an 8-bit dongle.
Overview
The MSi001 is a multi-standard, multi-band tuner originally designed for consumer digital-TV and radio reception (DVB-T, DAB, FM). Its appeal for SDR is continuous coverage from roughly 1 kHz up to about 2 GHz in one chip — no gap and no separate upconverter — spanning LF, HF, VHF, and most of the UHF range in a single tuning path. It supports both zero-IF and low-IF modes, letting the downstream software choose the architecture that best rejects images and DC artefacts for a given band and bandwidth.
How the pairing works
On its own the MSi001 only downconverts and filters; it needs a companion to digitise the result. That companion is the MSi2500, which contains the RSP’s ADC and the USB controller that ships IQ samples to the host. This split is deliberate: the tuner handles the analog RF and the MSi2500 handles conversion and transport, and SDRplay’s own API manages the two together as one receiver. Compared with the 8-bit RTL2832U path, the MSi2500’s higher-resolution converter gives the RSP line noticeably more dynamic range, which is why SDRplay receivers cope better with strong nearby signals and offer selectable capture bandwidths up to several MHz.
In practice
The MSi001 is not sold as a loose hobbyist part; you encounter it inside an SDRplay RSP. It is the common thread across the family — the single-tuner RSP1A, the dual-tuner RSPduo (two MSi001 front ends for diversity or dual reception), and the higher-end RSPdx with extra filtering and a wider front end. All are receive-only. Because Mirics keeps the tuner’s programming behind the SDRplay API, these receivers are typically used through SDRplay’s driver rather than a generic librtlsdr-style interface.
Relevance to GopherTrunk
GopherTrunk targets the RTL-SDR and Airspy paths as its tested front ends, and SDRplay’s MSi001-based RSP receivers use a different driver stack (the SDRplay API, typically bridged through SoapySDR) rather than the raw-IQ librtlsdr interface GopherTrunk speaks natively. Where a SoapySDR bridge is available, an RSP’s wide continuous coverage and better dynamic range make it a capable IQ source for channelising trunked control channels, but it is not a drop-in the way an RTL-SDR is. The MSi001 matters here mainly as the silicon that explains why an SDRplay behaves differently from a dongle — a higher-resolution, gap-free front end. See the hardware guide for GopherTrunk’s supported devices.
Sources
-
Software-defined radio — Wikipedia, for background on tuner-plus-ADC SDR front ends such as the Mirics chipset. ↩