Using LimeSDR with Portsdown

From BATC Wiki
Revision as of 21:12, 29 March 2019 by G8GKQ (talk | contribs) (BATC Shop LimeSDR Minis)
Jump to: navigation, search


The Portsdown 2019 software supports the LimeSDR Mini and the LimeSDR USB.

With the Portsdown Filter Modulator board being discontinued, the LimeSDR Mini will become the standard modulator for use with the Portsdown system and is available for purchase in the BATC members shop. More details on the LimeSDR Mini can be found here LimeSDR Mini Information.

The LimeSDR Mini is slightly more expensive than the Portsdown Filter Modulator board but does not require the use of a separate ADF4351 Local Oscillator module and a Local Oscillator filter board. Note - the LimeSDR Mini is available from the BATC members shop at a slightly discounted price compared to the normal retail price from the US plus shipping and 22% import duty charges.

However, due to the limited CPU power of the Raspberry Pi, many LimeSDR transmit modes are limited to 1MS and below. For higher SRs, use of the Portsdown Filter-modulator board is recommended. (see limitations below).

Setting up the system

Either buy a pre-configured SD card from the BATC shop or download and install the standard Portsdown software on your own SD card - see this page for more details:

Hardware Installation

Whilst the LimeSDR could be plugged directly in to the RPi, both the Mini and the USB versions have a greater power consumption than the RPi can comfortably power from its USB Port. Therefore, it is recommended that a powered USB 2 Hub be connected to the RPi, and the LimeSDR be plugged into one of the ports on the hub.

The USB plug on the LimeSDR Mini is vulnerable to mechanical stress; it is recommended that the LimeSDR Mini (or LimeSDR USB) be mounted in a protective box with strain relief for a USB lead. One possible mechanical configuration is illustrated below. There are number of 3D printed cases which can be used to protect the unit see the thread on the members forum for more details.

Charles, G4GUO, has found the LimeSDR Mini fits in to a Hammond 1455C802 box - see for more details but the USB connector may still need additional support.

The BATC 8-band PTT drive and RF switching boards can be used with the Lime to provide band switching - see below for details on the GPIO port connections.

Installing the Lime Software

The LimeSuite software version 19.01.0 (Interface version v2019.1.0, Binary Interface 19.01-1) is loaded as part of the normal Portsdown build and update process. This may not be the latest version, but is compatible with other components of the Portsdown software and the latest DATV Express version.

Once installed, you can use your Portsdown to update the firmware and gateware on your LimeSDR (Mini or USB) to the compatible version.

Lime Configuration Menu

The "Lime Config" Menu is selected from Menu 3. Selecting "LimeUtil Info" displays the current version of LimeSuite.

The "Update Lime FW" button updates the Lime SDR firmware and gateware to the appropriate version for the installed LimeSuite. For Portsdown software versions 201903250 and later, the correct version is shown below. You should see the same screen after selecting "Lime FW Info".


The Lime firmware/gateware version that works with the Portsdown is also compatible with DATV Express versions V1.25lp12 and later.

BATC Shop LimeSDR Minis

The LimeSDR Minis purchased from the BATC shop are hardware version 1.2. Those purchased before 14 January 2019 will have firmware 1.26 loaded. Those purchased after 14 January 2019 will have the latest firmware at the time of sale loaded.

If you do not use the correct firmware, the transmitted spectrum will not be as clean. If you are unable to upgrade due to apparent problems with the Portsdown/LimeSDR combination, please report the details on the BATC forum.

Note that if you use a Windows PC or a different Linux build to upgrade the firmware to beyond 1.29, you can roll it back to the correct version for the Portsdown by selecting "Force Lime FW" on the touchscreen menu.

Basic Test

You can run a basic test on your LimeSDR Mini, by pressing the "Lime Report" button. Note that this test generates RF output and leaves the LimeSDR Mini generating a carrier on 1095 MHz at about -25 dBm.

WARNING - High Power Output During Calibration Before Transmit

When the LimeSDR is put into transmit mode, it first performs a self-calibration which transmits at high power both in-band and out-of-band. It is imperative that power amplifiers are not energised during this phase or they will be damaged and/or strong illegal transmissions will be made out-of-band.

First power tests with Lime Mini SDR Portsdown at M0YDH

There are 2 delayed PTT signals available to help you avoid this situation. The first is on the normal Portsdown PTT pin on the RPi. The second is on GPIO 7 on the LimeSDR Mini or Lime SDR USB. None of these signals go high until calibration is finished.


Select Lime Mini or Lime USB from the "Output to" Menu. The detected device should be "not greyed out". On Menu 1, you will see the Lime Gain button for the appropriate band (distinct Lime Gains between 0 and 100 are stored for each band). A setting of 88 is a good starting point for about 5 dBm of output at 437 MHz. More information about the LimeSDR Mini output power levels and controls can be found here LimeSDR Mini Output Power Levels.

Selecting the modulation button will allow you to choose between Carrier, DVB-S and DVB-S2 modes. Once a DVB-S2 mode is selected, the appropriate FECs are available on the FEC button. Note that different FECs are available (and not available) for different modulations.

The RPi has to work quite hard to generate the signals to drive the LimeSDR. All SRs at 1MS and below seem to be reliable, but SRs of 2MS and 4MS can suffer drop-outs, particularly in MPEG-2 transmission modes. For operation above 1MS, the Portsdown Filter-Modulator board is recommended, rather than the LimeSDR.


There are 3 transmission modes used by the LimeSDR with Portsdown: SDR without up-sampling, SDR with 2 x up-sampling and carrier mode. I have tried to level the powers across these 3 modes, but they will vary by 2 or 3 dB depending on the SR and Lime gain selected.

There is a failure mode where the LimeSDR refuses to transmit anything other than a carrier, or does not respond at all. It has not been possible to overcome these failures yet in software; the solution is to power down the LimeSDR (by disconnecting the power and USB leads), and then to reconnect them.

GPIO RF Switching for Multiple Bands

The BATC 4-band and 8-band PTT drive and RF switching boards can be used with the LimeSDR to provide multiband RF and PTT steering. They can remain connected to the RPi GPIO using the standard Portsdown GPIO interface board or (if you are prepared to accept the risk of damaging your LimeSDR Mini) connected to the Lime FPGA GPIO.

The LimeSDR Mini GPIOs 0, 1 and 2 give the same signals as the RPi Band LSB, NSB and MSB. GPIO 7 gives the PTT signal. These can be taken from J5 on the LimeSDR Mini or J18 on the LimeSDR USB The pin connections on the LimeSDR USB are different from those on the LimeSDR Mini. Note that these outputs are not buffered and if damaged could prevent the LimeSDR from working again. Our advice is the use the RPi GPIOs.

GPIO Test.jpg

The gain provided by the BATC 8-way RF switch is useful to maintain current levels (5 - 10 mW) at the output. There will be some component adjustments needed to ensure the correct levels are available. Details will be published soon.

On the Lime USB the output is from "TX1 Low" below 2 GHz and from "TX1 High" above 2 GHz. The Lime Mini only has a single output.

System Diagram

Here is the latest system diagram. Note that only one of the displays is required; either the 3.5 inch or 7 inch.

20190120 Portsdown 2019 Block.jpg

The digital variable attenuator is only required if you want fine (<3 dB steps) control over your PA drive levels. The Lime Gain control on the Portsdown can be used to set the coarse output level.


Thanks to Evariste F5OEO, Andrew Back at Myriad RF, Charles G4GUO and Malcolm G0UHY for their help in implementing this capability.