Any reader who has perused these blog pages will be aware that I have been using the KiwiSDR for some time now (I personally own four of them and I manage two more!) and have been happy with their performance, finding various ways to maximize their usefulness. I was intrigued when a "similar" device appeared that might prove to be useful - the "RaspberrySDR".
The exterior of the RaspberrySDR.
The case is well-built and compact, housing both the
SDR board and a Raspberry Pi 3+.
Click on the image for a larger version.
For those not familiar with the KiwiSDR, it is a Linux-based, stand-alone software-defined radio capable of receiving from (nearly) DC to at least 30 MHz using a variety of modes (SSB, AM, FM, Synchronous AM) and has several "extensions" that allow reception of several digital modes - including CW, RTTY, and WSPR - as well as provide a means of viewing FAX transmissions and SSTV. It also includes a provision for TDOA (Time Difference of Arrival) determination of transmitter location in conjunction with other similarly-equipped receivers.
This receiver does not have a front panel, but rather it is entirely used via a web interface. What this means is that it may be used remotely, by several people, simultaneously - each person getting their own, virtual receiver that they may independently tune.
Originally introduced as a Kickstarter project around 2016, the hardware has been augmented with continually-improved open-source software with the lions share of the work having been done by John Seamons. Using a 14 bit A/D converter clocked at about 66.66 MHz, an FPGA (Field Programmable Gate Array) and a GPS front-end chip, most of the number-crunching is done before the data is handed off to a single-board computer - originally the BeagleBone Green, but now also BeagleBone AI (BBAI): Both the KiwiSDR receiver board and the BeagleBone Green (BBG) have been sourced by Seeed Studios.
For a variety of reasons, the supply of KiwiSDRs has been a bit fickle - both due to the limited capacity of Seeed in response to demand of these devices and issues which have been impacted the supply of some critical parts. Another possible issue may be that there is likely to be a bit of "fatigue" on the part of some of the key people related to the KiwiSDR: Careful readers of blog entries from several years ago can see that a similar thing happened to me on a project on which I had previously worked - coincidentally, also an open-source SDR-based device.
The present day:
Because the KiwiSDR is based on open-source design of its hardware and software - ostensibly to encourage participation in enhancement of all aspects of its design - one may freely copy it within the constraints of the open-source license. It is not surprising, then, that several derivative versions have recently appeared on the scene, more or less following the "open source" philosophy - a topic that will be discussed later.
Using the base code found on GitHub and the openly-published schematics as a starting point, the "RaspberrySDR" has appeared - using, as you may have surmised, the Raspberry Pi - specifically the Raspberry Pi 3+. This single-board computer is of similar size as the BeagleBone Green and roughly similar capabilities - albeit a bit more powerful - and is certainly better-known than the other fruit, so it was a natural choice as the hardware interface between it and the receiver board is fairly trivial to adapt with a simple "conversion" board that adapted to the Pi's interface.
Also to be expected, a revised board specifically designed to interface with the Raspberry Pi has appeared from Chinese sellers, packaged with a Raspberry Pi, in a small, aluminum enclosure (with an external fan) for approximately $100 less than the KiwiSDR+Enclosure combination - and this revised version uses a higher-speed (125 MHz versus 66.66 MHz) and higher resolution (16 bits versus 14 bits) A/D converter so that its receive range is extended to a bit over 60 MHz, including the 6 meter amateur band - and there is the potential for improved receive performance in terms of dynamic range and distortion.
Having gotten my hands on one of these "RaspberrySDRs" - and already having available some KiwiSDRs for testing, I decided to put them side-by-side to compare the differences - specifically, to measure:
- Apparent noise floor and sensitivity
- Appearance of spurious signals
- Large signal handling capability
- Image response (Nyquist filtering)
Noise floor comparisons of the KiwiSDR using the BBAI and the RaspberrySDR using the Raspberry Pi3+:
The KiwiSDR using the BeagleBone AI:
Figure 3 shows the noise floor of a KiwiSDR using the Beaglebone AI with no connected antenna. As is typical of this device, there is a slight increase in the noise floor starting around 18 MHz: The reason for this is unknown, but it is surmised that this is intentional - an artificial boost in "software" (likely in the FPGA) that is used to compensate somewhat for the Sin(x)/x roll-off intrinsic to any analog-to-digital sampling scheme as one approaches the Nyquist limit - which, given the 66.66 MHz sampling rate of the KiwiSDR, would be 33.333 MHz.
This assumption would appear to be supported by the fact that as one approaches the Nyquist frequency, the S-meter reading does not drop as one might expect, but remains fairly constant and appears to be close to +/- 1 dB from below 1 MHz to 30 MHz as shown in the data below.
In numerical form, the measured noise floor of the KiwiSDR/BBAI combination using a 10 kHz AM bandwidth is:
- -117dBm @ 1 MHz
- -117dBm @ 5 MHz
- -116dBm @ 10 MHz
- -116dBm @ 15 MHz
- -114dBm @ 25 MHz
- -115dBm @ 30 MHz (29.9 MHz)
The RaspberrySDR using the Raspberry Pi3+:
The RaspberrySDR has a 125 MHz sampling clock and a 16 bit A/D converter so the landscape looks a bit different as it can (theoretically) receive to 62.5 MHz, but is limited to 62.0 MHz in firmware. Comparing the 0-30 MHz noise floor we can see some interesting differences in Figure 4:
Noise floor of the RaspberrySDR running on a Raspberry Pi3+. There is a similar rise in frequency - although it looks a bit different.
Click on the image for a larger version.
We can see a similar rise in the noise floor, but we get the impression that limiting our range to just 30 MHz hides its nature, so Figure 5 shows the noise floor over the full frequency range of 0-62 MHz:
In comparison, the noise floor of the RaspberrySDR+Raspberry Pi3+ as measured using AM with a 10 kHz bandwidth is as follows:
- -118dBm @ 1 MHz
- -118dBm @ 5 MHz
- -118dBm @ 10 MHz
- -116dBm @ 15 MHz
- -115dBm @ 25 MHz
- -112dBm @ 30 MHz
- -113dBm @ 40 MHz
- -116dBm @ 50 MHz
- -116dBm @ 60 MHz
The magnitude of the broad peak is more significant than on the KiwiSDR - being on the order of 6 dB rather than 3 dB. Because the RaspberrySDR is based on the (open source) KiwiSDR,
it is expected that a the RF processing will be similar - and this would
appear to be bourne out by the presence of the rise in the noise floor,
centered around approximately 36 MHz. It would seem likely that the
adaptation to the higher sample rate hardware is not fully realized as
the pre-emphasis in firmware - if it exists - is not properly
implemented as is evidenced by the numbers.
Comparison of S-meter calibrations:
To provide and additional data point in our measurement, we'll check the S-meter calibration. For our purposes we will use a frequency of 10 MHz and a level of -50dBm as our reference as that appears to be below the apparent amplitude peaking of either type of receiver. Using a known-consistent signal source, the results are as follows:
|Frequency||KiwiSDR with BeagleBone AI||RaspberrySDR with Raspberry Pi3+|
The effects of what appears to be pre-emphasis can clearly be seen: The effects of the Sin(x)/x roll-off on the A/D converter seems to have been more-or-less compensated on the KiwiSDR, but the attempt to do this seems to be misapplied on the RaspberrySDR. Based on the apparent noise floor and the absolute response to the -50dBm signals, we can make an estimate of the absolute sensitivity of the KiwSDR and RaspberrySDR on the various bands with simple math.
|Frequency||KiwiSDR Noise floor (dBm/Hz)||RaspberrySDR Noise floor (dBm/Hz)|
The chart above compares the apparent noise floor of both receivers, compensating for the 10 kHz AM detection bandwidth (40dB) and the measured offset of the S-meter at each frequency.
It is worth noting that above about 15 MHz, neither receiver has sufficient sensitivity to detect the expected IRU noise floor given a unity gain antenna: Approximately 10dB is required at 30 MHz to "hear" the noise floor in that case and even more gain would be appropriate at 6 meters.
This very topic has been discussed at this blog in the past - see the blog post "Limited Attenuation High-Pass filter" - LINK and its related articles for a discussion.
Overload signal level comparison:
Another test was done - the determination of the RF level at which the "OVL" message on the S-meter would show, indicating overload of the A/D converter. This test was done for both units at 10 MHz - the same frequency for which the S-meter was calibrated - and in the "Admin" tab the unit was configured so that just one "OV" occurrence per 64k cycles would be detected.
KiwiSDR OV indication:
The KiwiSDR's "OV" indication just started to indicate at -14dBm.
RaspberrySDR OV indication:
The RaspberrySDR's "OV" indication just starts to indicate at -9dBm.
The apparent difference between these is 5dB.
"Wait - shouldn't there be another 12dB of dynamic range with two more bits of A/D resolution?"
In theory, two additional bits of A/D conversion should yield and additional 12 dB of dynamic range - but this is not readily apparent in the numbers given above (at 10 MHz, 142dB between the noise floor and the "OV" indication for the KiwiSDR and 149dB for the RaspberrySDR) - so what's the deal?
First off, all things being equal (e.g. the same reference voltage for the A/D converter) one would expect the additional range to occur at the bottom of the signal range rather than the top, but this difference can be a matter of scaling via careful adjustment of the amount of amplification preceding the A/D converter and how the code is written.
Ideally, one would carefully balance the signal path so that the intrinsic noise of the amplification preceding the A/D converter would be comparable to the signal level required to "tickle" the LSB (Least Significant Bit) with no signal applied: A higher level than this risks "wasting" dynamic range with internal noise. Judging by the "even-ness" of the noise across the spectrum, I suspect that the output of the input amplifier is enough to light up one or two LSBs of the A/D converter.
It's possible that the "extra" 5 dB at the high end of the signal range is real and that signal dynamics
have been juggled a bit with some the extra 2 bits worth of range being present at the bottom end, but this would be difficult to divine without more thorough testing.
Without the availability of a schematic diagram of the front end of the receiver there are several unknowns:
- The LTC2208 has a pin that indicates an overload condition. It is presumed that in spite of other issues with the firmware (see below) that the "OV" indicator is working properly.
- The LTC2208 A/D converter has a low-level dither generator built into it: It is unknown if this feature is active.
- Shorting the RF signal path to eliminate the contribution of the pre-converter amplification would be instructional to ascertain noise contribution from that device.
- Probing the input of the A/D converter at/near overload to divine the actual range of the receiver itself to determine if the full dynamic range of the 16 bits is properly utilized would be revealing.
- The LTC2208 has a programmable gain amplifier and full-scale input voltage may be selected as being either 1.5 or 2.25 volts: The hardware configuration is unknown.
- At the time of writing this, I have not found in the code any modification of the FPGA image that takes advantage of the extra two bits of A/D resolution. This does not mean that no modification has been done, but rather that I have not (yet?) discovered it.
Nyquist Image response:
Any receiver has an image response - and an SDR is no exception. In this case, signals above the Nyquist frequency (half the sampling rate) will appear to "wrap around" and show up in the desired frequency range. Because it is impractical to build a "brick wall" low-pass filter, there are always compromises when designing such a filter, including:
- Complexity: How "fancy" should such a filter be in terms of component count? More components can mean improved performance, but this implies a more difficult design, higher expense and more performance-related issues such as loss, ripple, sensitivity to source/load impedance, etc.
- Trade-off of frequency coverage: It can be difficult to weigh the pros and cons of a filter in terms of its cut-off frequency. For example, setting the cut-off near the Nyquist frequency will improve performance at the high end of the available range, but at the risk of poorer image rejection. Conversely, setting it lower may sacrifice desired coverage. A case in point would be that for the KiwiSDR, with a Nyquist frequency of about 33.33 MHz, coverage to 30 MHz (the "top" of HF) is desirable, so a bit of compromise is warranted in terms of absolute image rejection.
How bad/good is it?
The image response of both the KiwiSDR and RaspberrySDR were measured and determined to be as follows:
|Generator frequency (% of Nyquist)||Nyquist image frequency on RX
||KiwiSDR Nyquist image attenuation|
|37 MHz (111%)||29.667 MHz||10dB|
|42 MHz (126%)||24.66 MHz||20dB|
|47 MHz (141%)||19.66 MHz||30dB|
|52 MHz (156%)||14.66 MHz||39dB|
|59 MHz (177%)||9.66 MHz||47dB|
|62 MHz (186%)||4.66 MHz||55dB|
|66 MHz (198%)||0.66 MHz||60dB|
|70 MHz (210%)||-3.33 MHz||65dB|
|Generator frequency (% of Nyquist)||Nyquist image frequency||RaspberrySDR Nyquist image attenuation|
|64 MHz (102%)||61 MHz||9dB|
|75 MHz (120%)||50 MHz||18dB|
|85 MHz (136%)||40 MHz||27dB|
|95 MHz (152%)||30 MHz||36dB|
|105 MHz (168%)||20 MHz||46dB|
|115 MHz (184%)||10 MHz||54dB|
|120 MHz (192%)||5 MHz||58dB|
|124 MHz (198%)||1 MHz||60dB|
|130 MHz (208%)||-5 MHz||65dB|
Doing a direct comparison between the two receivers one can see that based on the percentage of the frequency of the unwanted signal with relation to to the Nyquist frequency, the two receivers are pretty much identical in terms of image rejection, implying a very similar filter in each: I suspect that the RaspberrySDR's Nyquist filter is pretty much that of the KiwiSDR, but with its frequency having been rescaled proportionally.
Because the Nyquist frequency of the RaspberrySDR is approximately twice that of the KiwiSDR, in terms of "dB per MHz" the attenuation of RasperrySDR's Nyquist filter performance will be noticeably worse. For example, we know from the above information that for the U.S. FM broadcast band that the attenuation of the KiwiSDR's Nyquist filter will be at least 65dB - but we can see that for the RaspberrySDR that this attenuation will likely vary between about 30dB at the bottom end of the band (88 MHz) and 50dB at the top end (108dB) meaning that it is likely that strong, local FM broadcast signals will cause some interference to the RaspberrySDR in the 37-17 MHz range. implying that a simple blocking filter should have been built in The work-around for this problem - should it arise - is pretty simple: Install an FM broadcast band "blocking" filter such as those sold for the RTL-SDRs: An example of such a filter may be found HERE.
Effects of receiver noise floor with a strong, off-frequency signal:
Any receiver is affected by other strong signals within its front-end passband - and with direct-sampling SDRs such as these, any signal appearing at the antenna port can and will have an effect elsewhere within the receiver's passband - primarly due to nonlinearity of the A/D converter and, to a lesser extent, the phase noise of the various oscillators - real and virtual.
For this test, a very strong signal from a 10 MHz OCXO (that of an HP Z-3801 GPS receiver - likely a variant of an HP 10811) was used as its output has respectably good phase noise performance. Two tests were done - at -15dBm and another at -25dBm - each time measuring the change in the noise floor at different frequencies distant from 10 MHz.
With the 10 MHz signal set to -25dBm, NO change was observed in the noise floor at the frequencies listed below on either receiver - but there was a bit of increase in the noise floor with the application of the -15dBm signal - the magnitude of the increase of the noise floor is indicated in square brackets  in the chart below:
|Noise floor frequency||Noise floor of KiwiSDR [degradation]
||Noise floor of RaspberrySDR [degradation]
|11 MHz||-114dBm [2dB]||-116dBm [0dB]|
|15 MHz||-114dBm [2dB]||-114dBm [2dB]|
|25 MHz||-113dBm [1dB]||-112dBm [2dB]|
Assuming that the 10 MHz signal source is "clean", the above information shows that the two receivers behaved quite similarly. It also shows that if there are two additional bits of A/D resolution available in the signal pipeline on the RaspberrySDR, their effect is not readily apparent in the measurements above.
All is not well: A few glaring bugs!
There are several "features" that are readily apparent in this version of RaspberrySDR firmware (Version 1.402) that cause a few operational problems:
- Inconsistent RF level calibration. Occasionally, when powered up, the RF signal level calibration (S-meter, waterfall) will be way off requiring a setting of about -30dBm to yield correct S-meter calibration at 10 MHz rather than -19 - which is within a few dB of the setting of the KiwiSDR: Simply rebooting the SDR server will likely correct this.
- No obvious improvement in dynamic range or sensitivity due to the "extra" 2 bits of A/D resolution. As discussed, one would expect to see clear evidence of improved performance due to the additional two bits of A/D converter resolution, but either this is masked by the low-level noise of the input amplifier, problems in the processing of the A/D data itself, or issues related to handling of high signal levels (see the next topic, below). What difference there may be appears to be at the top end of the signal range rather than at the bottom.
- "Broken" S-meter at higher signal levels. The S-meter seems to be incapable of reading properly above about -33dBm: Signals higher than this will yield widely-varying numbers that have little to do with the actual signal level.
- "Motorboating" on strong, narrowband signals. It has been observed that at about the same time that the S-meter starts to malfunction (above about -33dBm) one will hear odd noises on a strong signal (unmodulated carrier received in AM mode using a 10 kHz bandwidth) indicative of a malfunctioning bit of code somewhere - likely related to the broken S-meter. The nature (sound) of this effect appears to change depending on the applied signal level. It is not (yet) known to what extent this issue has a "global" effect: That is, does a single, strong signal cause this effect on other/all signals within the receiver's 0-62 MHz passband?
- The "Firmware Update" function in the "Admin" screen doesn't work at all. Make of that what you will.
An interesting notion - Direct reception of the 2 meter amateur band:
In theory it should be possible to modify the RaspberrySDR to directly receive the amateur 2 meter band. Because the sample rate of the receiver's A/D converter is 125 MHz, one can undersample the 144-148 MHz 2 meter band which would appear in the range of 19-23 MHz. Because this is just above the sampling frequency, the "direction" of the frequency conversion (e.g. increasing frequency at the antenna will show as increasing on the display) will be correct which means that a standard transverter offset (e.g. a local oscillator frequency of 125 MHz) could be used.
To do this one would need to - at the very least - bypass the Nyquist low-pass filter, and with the noise floor likely to be much worse than the 158dBm/Hz seen at HF so significant low-noise amplification AND strong band-pass filtering (to quash spurious responses) would be required - probably something on the order of 25dB.
Based on the specifications of the LTC2208, undersampling should work into the hundreds of MHz, possibly covering other amateur bands - but the need for appropriate amplification and filtering applies!
The "elephant" in the room
It is immediately obvious - particularly from the board layout and screen shots - that the RaspberrySDR has heavily "borrowed" its design from the KiwiSDR and this is, to a large extent, entirely fair game since the KiwiSDR is a self-declared open-source hardware and software design. Having said this, a few issues have been raised considering the RaspberrySDR:
- Is the RaspberrySDR being produced entirely in accordance with the KiwiSDR Open Source license? Likely not. For example, elements of the KiwiSDR "branding" appear all over the RaspberrySDR - from the derivative (parody?) logo on the board (see Figure 2) to the name "KiwiSDR" being present within the web interface itself. The former may be an intentional, perhaps perceived as a slight - and the latter is rather hard to eliminate entirely - particularly if one wishes to maintain a branch of the code that echoes the continued development of the KiwiSDR - not to mention effort flowing in the other direction (e.g. improvements by others being incorporated into the KiwiSDR base).
- Another board with similar capabilities (16 bit A/D, 125 MSPS) has appeared - apparently similar to this RaspberrySDR board - but it interfaces with the BeagleBone: I have not used one or seen one in person, nor do I know anything about hardware/software support.
- The RaspberrySDR source code itself seems to be somewhat obscured. While there is a RaspberrySDR fork on Github (see note below), it is apparently not the very same code that is what is made available as a Raspberry Pi image only (as far as is known at the time of writing) from a link provided by the online seller. In other words, I have not been able to find any sort of equivalent of a Github repo for the RaspberrySDR - a fact not exactly in keeping with the spirit of "open source".
- Github user "FlyDog" has produce the fork mentioned above and his repo may be found HERE. As mentioned above, I haven't been able to get this code to work with this board.
- The schematic of the RaspberrySDR does not seem to be available at the time of this writing - again, not in the spirit of open source.
- The primary author of the KiwiSDR code announced recently on the KiwiSDR message board that certain parts of the KiwiSDR's code - presumably elements not previously released under an open-source license - would be available only as binary "blobs" in the future. The intent of this action - as it seems to be interpreted by many of the readers (including me) - is, in addition to protect certain elements, is to increase the difficulty of replicating the software in the future - and some might argue that this goes against the spirit of "open source" that was embodied in the original Kickstarter definition of the KiwiSDR. Whether this is true or not, the reader should not overlook the fact that the primary author has spent (and continues to spend) a lot of time, effort and money in the maintaining of the KiwiSDR software, hardware manufacture and certain elements of infrastructure about the KiwiSDR (Proxies, DDNS, TDOA to name three) and there is an understandable desire to "encourage" involvement (including buying "official" KiwiSDR boards, for example) that would go toward maintaining this. The presumed argument is that follow-on versions based on the open source hardware and code - whether strictly adherent to the open-source licenses or not - are not compatible with his intent going forward.
Is it worth getting?
Is the RaspberrySDR a good deal? It all depends on what you want to do with it. At the moment, the ongoing support for it in terms of software development is a bit ambiguous as the "open source" nature of this fork seems to be a bit opaque, which is unfortunate.
For a general-purpose receiver that does not need the (useful!) facilities unique to the KiwiSDR network (proxy, TDOA, etc.) and for a receiver that includes the 6 meter band, this unit may fill a niche.
Again, the reader is cautioned that the "official" KiwiSDR brings to the amateur community several valuable features - including the TDOA - that require ongoing support which translates directly to people buying the "official" KiwiSDR boards, as I have clearly done.
- For a general-purpose web-enabled remote receiver with decent performance, both the KiwiSDR and RaspberrySDR seem to be a good deal and the RaspberrySDR works reasonably well despite the bugs mentioned above. The RaspberrySDR has the advantage that it also covers the 6 meter amateur band and has the potential of improved performance by virtue of its 16 bit (versus 14 bit) A/D converter.
- The KiwiSDR kit with the Beaglebone Green and case - even though it costs more (approximately US$100 more than the RaspberrySDR) - has the distinct advantage of ongoing support along with the other infrastructure features mentioned above. Like any open-source project, there will come the day when such support will cease and it will be up to others to try to build on what is in the repository at that time.
- The current hardware of the KiwiSDR is starting to show its age for the reasons mentioned above and the existence of the RaspberrySDR shows that a relatively minor modification can potentially improve performance without a major rework of either hardware or software.
- With the understanding that the time and resources of the primary author and frequent contributors to the KiwiSDR are limited in the ability to undertake such a change, I believe that it would be a mistake to overlook the potential (and "inspiration") of parallel work being done by others when it comes to keeping the KiwiSDR project up to date and relevant.
This page stolen from ka7oei.blogspot.com