Friday, 13 March 2026

SDRConnect: The Linux Installation

There's a lot of chatter at the moment about how Windows 11 is forcing everyone towards a 'forever rent' model i.e. paying every month for cloud-based computing that you previously ran locally. It's being called 'the end of personal computing' by some.

Whether through use of Raspberry Pi SBCs or more concerted efforts in replacing a computer's OS, most amateur radio operators will have something answering to the Linux label in their shacks.

And so it has long been with me. But I'm no Linux expert - at all. I do enjoy the more interactive aspects of delving into the terminal and actually entering real commands from time to time. But it can also be a bit difficult and frustrating to get to grips with.

I'd tried to install SDRConnect on Linux Mint a few months ago, but I hadn't really gone to much effort to overcome the hurdles I met. Last night, I wiped my 12 year-old HP laptop clear of Windows and Zorin OS, installing only Ubuntu. What follows, though, also applies to Linux, which I tested this morning.

Most of what you need to know is actually on the SDRPlay website, but isn't really that obvious a place to hit during a stressed visit, trying to figure-out how to get the damned software running! It's on a PowerPoint-type page:


The commands are: cd Desktop (or cd Downloads, depending on where you have the downloaded SDRConnect .run file) Note that the directory names are case-sensitive.

Type ls to list the files in the relevant directory. Somewhere, you will see the SDRConnect file with a '.run' at the end. You can highlight and copy this filename to the clipboard to paste it when it comes to the commands.

Now type chmod 755 SDRConnect.[whatever the rest of the filename].run You can paste the filename from the clipboard.

Now type ./SDRConnect[rest of filename].run  Note there is no space between the ./ and the filename.

The user agreement and installation now goes ahead. But if you are missing some files, it will tell you to run the installation of SDRConnect again after downloading and installing the missing ones; it's usually very simple and just one file.  Just go back to the ./SDRConnect[etc] instruction, above, when the missing files are sorted.

You should now find SDRConnect installed and an icon and/or listing for the software.

Easy! Works for Ubuntu, Raspberry Pi and Linux. 

 

 

 

 

 

Friday, 6 March 2026

868MHz DX

It was a very bright, sunny day today, though icy cold when the sun went behind a cloud, up on the few high spots on Anglesey - Mynydd Parys. This is 139m above sea level, with a clear line of sight across the Irish Sea to Cumbria, the Isle of Man and the Mourne Mountains in Northern Ireland. It's a great place for radio, and where I lived for 13 years.

Beaming northern Cumbria...

I had a bit of a stroll up there and took my 8-element AliExpress Yagi along with a GPS-enabled Meshcore transceiver. A convenient concrete block to stop people driving over the historic copper mine tailings heaps provided a useful level surface on which to rest the antenna. 

Cumbria, seen early morning from Mynydd Parys, with background lighting revealing the landscape clearly.
 

Aiming it by eye at northern Cumbria, I was quite surprised to make a direct, 'zero hop' connection with a repeater on Lank Rigg at 137.6km distance. Given this is UHF and the power output only around 0.15W - admittedly boosted by the Yagi's ~10dBi gain to an effective 1.5W, that's pretty good going!  As you can see from the screengrab of the app, below, the direct 'ping' signal there was -13dB and -6.25dB back to me (the rest of the information on-screen is redundant for the ping test). I don't know what the antenna arrangements are in Cumbria.

 

Irish Sea area, showing me (north coast Anglesey, purple dot) and the MCC Lank Rigg repeater that heard me.

 

Cornwall, Some Years On.

Back in 2015 - still not that long ago to my mind - the RSGB waded into what became a political farce, about which I was reminded this morning on reading The Guardian, and its piece on widening celebration of Cornish identity in the region. 

The issue all those years ago? The regional secondary locator (RSL) that OFCOM had decided to grant, on a permanent basis, to Cornwall (Kernow in Cornish, hence the 'K').

Source of hostility by the RSGB in 2015...

This came about as a result, in 2014, of the Cornish being granted National Minority Status, recognised by the UK Government, under the European Framework Convention for the Protection of National Minorities. This brought them into line with the Scots, Welsh and Irish, who had enjoyed such recognition from a much earlier point.

Of course, the bigwigs at the RSGB had other ideas. They issued public announcements of support, whilst rabidly opposing it from the very outset, as soon as they thought they were behind closed doors in meetings with OFCOM.

OFCOM itself added, inevitably, to the mess. It formally involved Cornish MPs by telling them all about the new, permanent 'K for Cornwall' callsign, only to withdraw the whole thing, making it a mere temporary issue, ultimately negotiated to last a year.

The reason for the change of heart at OFCOM?  It was never explicitly said, but minutes obtained under FoIA at the time revealed pressure from the RSGB, to which OFCOM seemed unreasonably willing to bow. 

The RSGB raised the entirely specious spectre with OFCOM that, if Cornwall got its own, permanent RSL, then the country - Lord help us all - could be faced with "wide repercussions" - angry mobs from all over the UK, shaking their pointy antenna sticks at the government and threatening regime change and perhaps the collapse of global civilisation itself. The RSGB, desperately, added that operators across the world would be "confused" by the K RSL. Radio operators are not known for being confused by callsigns and geography.

The Guardian article today contains a beautiful line that anyone who is from one of the National Minorities will strongly identify with and understand: "I'm Cornish. I'm definitely not English". To the English ear, this sounds like a declaration of war; that having a minority identity means you are saying you hate the English. Which is, of course (usually), utter bilge.

Why did the RSGB react in this way, advancing ridiculous and clearly disingenuous arguments to overturn what OFCOM - a government agency - had already decided?  Seasoned critics opined, perhaps not unreasonably, that it was concern from within the ranks of the obsessive contesters, including from the within the ranks of the (non-Cornish) Board, that led them to believe they would be at some disadvantage in their pointless point-gathering of a weekend. Think about it: a hobby society, unaccountable to anyone, somehow forcing UK official policy to be changed, making a fool of OFCOM and its decision.

To the wider world, it was a non-story. To the Cornish and those in the UK who are not English, it was another typical English dirty trick, reminding us all of how petty, oppressive and loathsome they can be. Rather than celebrate Celtic cultures - here way, way before England and English ever existed - the English-centric RSGB and its black-suit-(but no black Board members)-and-tie ways decided to have a tantrum and break everything. They were clearly very satisfied with it all.

The Guardian today, celebrating growing Cornish pride, simply reminds us how disgracefully out-of-step with UK cultural history the RSGB was and, no doubt, still is. A word commonly used to describe such prejudiced responses to issues like the RSGB exhibited towards Cornwall is: 'gammon'.

If you're really bored, you can trawl through my blog to find the several posts I wrote at the time. If you're only mildly interested, you can just read my letter to the then Managing Director, or this summary from a bit earlier. Whilst it's a while ago now, it does tell you a lot about our so-called representative body, the Board of which today still contains some of those around at the time.