DiscoverFoundations of Amateur Radio
Foundations of Amateur Radio
Claim Ownership

Foundations of Amateur Radio

Author: Onno (VK6FLAB)

Subscribed: 327Played: 14,184
Share

Description

Starting in the wonderful hobby of Amateur or HAM Radio can be daunting and challenging but can be very rewarding. Every week I look at a different aspect of the hobby, how you might fit in and get the very best from the 1000 hobbies that Amateur Radio represents. Note that this podcast started in 2011 as "What use is an F-call?".
611 Episodes
Reverse
Foundations of Amateur Radio Have you ever stopped to consider who else is using your radio spectrum? I'm asking because we talk about amateur bands as-if they're set aside for the exclusive use by the amateur community. We "own" those bands, 80m, 40m, 15m, 10m, 2m and 70cm are "my" bands, and presumably, if you're licensed, you have a favourite band, a place you think of as "home", where you find your friends, elusive contacts, where your station works best, whatever the criteria might be. The other day I was in conversation with a few amateurs from across the equator, I'm south of it, they're north. As it happens, we were talking about the 70cm band, which, depending on where on the globe you're licensed, falls somewhere between 420 and 450 MHz. We were discussing the selection of new hardware to use a mode called LoRa, after Long Range. It's a so-called "Chirp Spread Spectrum" or CSS mode, capable of long range, low power, data communications and it's used all over the world across a variety of frequencies. While proprietary, there are several reverse engineered open source implementations, including several using GNU Radio, which means that radio amateurs can play with this. I was under the impression that LoRa hardware was specifically for the ISM band for industrial, scientific and medical purposes, things like microwave ovens, NFC, garage door openers, Wi-Fi and Bluetooth. LoRa being only one of many different users on those allocations. Mind you, ISM is explicitly not for applications in the field of telecommunications, which is odd if you consider Wi-Fi or Bluetooth, but that's perhaps a hint at what's coming. I'll note that in this same frequency space are allocations of so called LPID or Low Power Impact Devices, and SRD, or short-range devices, but I'll ignore that distinction, since we have bigger fish to fry, and much of this applies all over the radio spectrum, not just the 70cm band. Imagine my surprise when I was informed that the LoRa hardware, licensed for ISM use in Europe, was using frequencies in the 70cm amateur band. Until that moment I was pretty sure that ISM users and amateur radio users didn't share any frequencies beyond some in the 2.4 GHz allocation, ultimately what started my amateur radio journey back in 2010. In my case, all those years ago, the promise of higher power to control a drone on 2.4 GHz was what lured me in, only to discover that my Foundation license wasn't enough to make that happen. In researching further, I discovered that not only do radio amateurs share the allocation with ISM users, we're both considered secondary users behind the military as a primary user. Over the years I've decried on more than one occasion the poor documentation associated with our band plans, the absolutely impenetrable maze of radio spectrum allocations, rules, and exceptions, that govern how radio is used, not to mention the lack of governance and oversight on a global scale where some countries see fit to regulate spectrum outside their borders without repercussion. Those concerns aside, if you want to be a good citizen on radio spectrum use, it's pretty hard to achieve beyond "I tried, I really did". One term I came across was "harmonisation", something that radio spectrum use sourly lacks. Even if there was any, you'd have so many exceptions that you might as well put it on display at the local planning department in Alpha Centauri with just as much opportunity to make a fuss about it as a hitchhiker that comes to mind. Here's the thing, when you look at a band plan, any band plan, the one from your peak body, your regulator, your local IARU region or even the ITU, you'll find information pertaining to your service, in your area, and if you're really, really lucky, you'll discover if you're a primary user or not. What you likely won't discover is who else is there. Now for the kicker. An ISM user is considered "unlicensed". You and I probably realise that the license is vested in the transmitter, but on the whole as a class of user, the humans are unlicensed. You as a radio amateur can likely legally use such gear on an amateur radio allocated frequency within your own license restrictions, which might mean that you are permitted to use a bigger antenna, or more power, or some other benefit. Now, here's my question. If an ISM user with LoRa equipment, using a perfectly legal ISM frequency, which happens to also be an amateur allocation, uses it to communicate with a radio amateur, on the same frequency as a licensed amateur, using the same gear with say a bigger antenna, is that legal? To put it differently, are two users of different classes, both using the same communications equipment, permitted to talk to each other on the same frequency? Before you answer, how would you know if they're amateurs or not? While contemplating that, where is this documented and can you prove it? I'm Onno VK6FLAB
Foundations of Amateur Radio There is a sense of glee associated with discovering that your interests unexpectedly join together, case in point, the 2026 Earth - Venus - Earth bounce, yes, Venus. Much like an Earth - Moon - Earth, or EME bounce, this is the act of transmitting a signal from Earth to Venus and receiving it back on Earth. While humans have been using our Moon as a reflector, since accidentally in 1944 and on purpose in 1946, Venus is a harder nut to crack at 42 million kilometres distance - at its closest approach. The first radio echo was received in 1958. Radio amateurs have managed to receive a signal off Venus in 2009, 2014, 2025 and now in 2026. Unlike the earlier achievements where the signal was a carrier, spectacular in its own right, the most recent effort was an actual message, "VENUS ECHO". A week later on the weekend of 24 and 25 October the volunteers at Dwingeloo and Stockert sent and received a different message. Here's where it gets interesting. The team has published the raw received data for the second message, even included the code they used for their own previous attempt and set a challenge, for anyone to decode the message. Clicking on the information link opens with the header "Venus MFSK - modulation, coding, demodulation. When reading that, I started giggling, since I'd been subjected to MPSK not ten minutes earlier in a completely different context, the decoding of an FM RDS signal, a digital signal embedded in a regular commercial FM broadcast. It's the information your fancy radio uses to tell you which song is playing, for example. That particular activity came about when I started hunting for example flowgraphs for FM decoders. As you know, I've been exploring GNU Radio and recently managed a little breakthrough in getting actual radio audio across the network from an RTL-SDR dongle. Although the audio quality was poor and in glorious mono, it was plenty clear to determine which station I was tuned to without needing to check the frequency. I started on the journey of discovering precisely what VLC expects as an incoming raw audio stream, which turns out to be completely configurable - which changed my problem into, what does GNU Radio use to stream audio to an audio sink - the block that represents speakers on your computer. I came unstuck with how the audio channels were being dealt with, so I kept hunting. On my journey I came across an article by "John E. Post", I kid you not, in the February 2020 edition of Nuts and Volts magazine, titled: "FM Reception with the GNU Radio Companion". The article describes in great detail what an FM signal looks like, how to decode it and how to build GNU Radio flowgraphs to make that happen. It also comes with an archive of four separate decoders, including two stereo FM decoders. When I opened the files on my current copy of GNU Radio I discovered that there were several broken and missing blocks. This happens when GNU Radio updates code and makes old blocks obsolete. The blocks show as "Missing Block" in angry red and any blocks connected to one of these also turns red, so plenty of visual indicators that something is seriously wrong. I attempted to discover these examples on GitHub, or anywhere else outside the archive, but failed, so I decided to create a new repository, called 202002-Post, since that's what the archive was called, and began the process of translating old blocks into new ones. A partial conversion was achieved using a script called "GNU Radio Companion File Converter" by "M Khanfar". I was successful in translating the FM mono receiver and set out to make the RDS one into something that runs inside the current version of GNU Radio. In the middle of the spaghetti of blocks is one called "digital_mpsk_receiver_cc", as you might guess, angry red, so I set out on the hunt to make it work, when after several hours of spelunking I discovered a decade old GitHub issue where it was depreciated. The promised replacement examples were not in evidence and I was left with a picture of a solution involving two different blocks, a "Costas Loop" and a "Clock Recovery". I'm not going into either of these today, but together they appear to create at least a partial replacement for the now depreciated MPSK receiver block. And that's when I read the Venus decode challenge. So, what does all these mean? Consider it a convergence of concepts. On the one hand I'm working on a, some might say, boring, RDS receiver, on the other hand, it appears that the same techniques are being used to bounce signals off Venus. If it wasn't for my seemingly random exploration of GNU Radio, FM broadcast, RDS and MFSK, there's no way I'd even link that with a Venus bounce and decode. Right now, I'm wondering what I don't yet know to decode the raw signal and I'm keen to figure it out. I'm not ever going to be the first to decode this, since the EVE2026 team have already achieved this, but I'd like to discover if I know enough to do this for myself, or not. That for me is precisely what this amazing hobby of amateur radio is all about. If you want to have a go, you can find the details for the Venus decoding challenge on the https://www.camras.nl website or search for their callsign PI9RD. Also, has anyone written any automatic layout tools for GNU Radio blocks, like Graphviz, because I'm getting thoroughly sick of overlapping blocks and really painful, almost "goto" like, constructs. Oh, before I go, yes, MPSK and MFSK, not the same thing, phase versus frequency, lots to learn. I'm Onno VK6FLAB
Foundations of Amateur Radio The shaving of the Yak progresses, it's now making noise! Before you get too excited, the noise is one-way, it's barely distinguishable from hash and it's fragile, so keep that in mind as we dive into the world of .. something. If you have no idea what I'm talking about, you're in good company, half the time I'm struggling, but today I'm working on a project to bring software defined radio to the masses, well, radio amateurs who haven't dipped their toes yet and I'm calling this effort Bald Yak. In case you're unfamiliar, the Bald Yak project aims to create a modular, bidirectional and distributed signal processing and control system that leverages GNU Radio. It's called Bald Yak because by the time I'm done, the Yak is likely well and truly shaved. So, last time we congregated around the campfire I discovered that what I need to build is something that has a collection of things that talk to each other across a network. Seems pretty obvious now that I say it, but it wasn't always that way, remember, I'm inventing this from scratch, or so I tell myself. I will note that the deeper I dig, the more it looks like a lack of documentation, which really comes with no surprise, but I persist, if only to determine that it can be done, that I can do it, and that I understand how it works. The underlying drive for all this is for me to gain a deep understanding of the whole ecosystem, since I firmly believe that we're well and truly committed to software driven radio. So, what did I discover? First of all, thank you to all of you who sent messages with your own ideas on how to make two devices talk to each other. I explored at least a dozen of them. I'll give you some highlights. First cab off the rank is OpenWebRX, radio in a web browser, very popular. I installed it, ran it, configured it, got noise, was able to pick a band across the network and decoded plenty of stuff. Looked like a contender until I discovered two significant issues. One is that it expects a menu entry for each slice of frequency range, with 2.4 MHz being the widest possible for an RTL-SDR dongle, so its 1.7 GHz range would need 708 entries. Someone made a good start, but if you want to tune to something that overlaps two entries, you need another menu entry. Then there's the weird flex that it doesn't decode FM Broadcast in stereo. There's a whole description on why not, but I lost interest. I also tried OpenWebRX+ which adds a bunch of functionality, but not enough to overcome those fundamental problems. I explored several other web based tools, one looked really promising right until it demanded that I install some random binary off the Internet .. hard pass. I didn't go down the path of AllStarLink across the room, mainly because I have no desire to start the rounds of configuration, or manage the lack of ability to change frequency, to name two issues. I did fire up RTL-TCP and managed to connect to it from my Mac using SDR++, it even worked, but boy, the SDR++ user interface is hard work, too many buttons and not enough consistency, like why do I need to set the gain for each mode, and why doesn't it support SoapySDR on MacOS? RTL-TCP is a tool that essentially puts an RTL-SDR dongle on the network. It's excellent, once you figure out how to make it work inside Docker, has great documentation, talks to GNU Radio, everything you'd want, except that it's only one-way and it only talks to RTL-SDR dongles. I started comparing SoapySDR to RTL-TCP and then landed back with SoapySDR, since it does the same job, with a bonus that I discovered by accident, since the documentation is .. let's call it .. challenged. One of the things that people who contacted me missed, probably because it was obvious to me, was the notion that I want to use automatic service discovery, something that has myriad names, ZeroConf, Bonjour, Avahi, mDNS and plenty others. I tried many of them as search terms with GNU Radio and found nothing. Then I tried the same with SoapySDR and discovered that it supports mDNS out of the box. It's not something I'd seen before, since all the examples I found previously hard code an IP address into the flow graph, which means that it might work on my computer and network, but it won't work on yours until you change things, hardly something I want to inflict on unsuspecting users. So, the way it works is that you run a thing called "SoapySDR Server" on the machine with the RTL-SDR dongle, and GNU Radio running Soapy Source with the remote driver can find it .. most of the time. There's still plenty of hair pulling here, a flow graph that ran yesterday stopped working today, until I rebooted the server twice, no other changes, so fun. To be honest, it feels a little like Windows 95 Plug and Play, or as we used to call it, Plug and Pray, excellent idea, shame about the implementation. Then I came across a flow graph by Handiko YB1SDL who created a git repository with the title "How to Stream the Audio Out from GNU Radio into VLC Media Player" .. which of course was catnip to an aspiring geek like me. Turns out that VLC can listen on a UDP port and GNU Radio can send data to it. The quality of the audio is very poor as noted by Handiko, but I think that's due to neither of us understanding how to scale it properly, but that's par for the course. So, right now I have three devices talking to each other, a SoapySDR Server with an RTL-SDR dongle on a single board computer, a GNU Radio flow graph running in a Docker container on my main server, and VLC running on my Mac. What does this buy me? Well, the Mac audio is a bonus, I'd like to be able to listen to the radio, but GNU Radio talking to an unnamed server that's just sitting on the network is precisely what I envisaged when I started this whole malarkey. Mind you, it's not stable enough to show and tell, and I have no idea what it does if there's more than one radio on the network, but that's more opportunity to explore. I'll also note that this is precisely why I'm doing all this in GNU Radio, so I can learn how it works. There's one other thing. I'm documenting all this so it inspires you to start playing with this ecosystem, because ultimately I picture this environment as the radio equivalent of a massive bag of LEGO scattered all over the living room floor, something which brings me all kinds of joy. So, what are your GNU Radio adventures like, and what have you tried and where are you stuck? I'm Onno VK6FLAB
Foundations of Amateur Radio After spending a full day banging my head against a wall, again, this morning I hit on a phrase that hadn't occurred to me, "peer-to-peer audio" and with it came an insight into the problem I've been working on since I conceived of Bald Yak. In case you're unfamiliar, the Bald Yak project aims to create a modular, bidirectional and distributed signal processing and control system that leverages GNU Radio. It's called Bald Yak because by the time I'm done, the Yak is likely well and truly shaved. While it might seem superfluous rehashing my frustrating day, I think it helps to describe more fully what I'm trying to achieve, so bear with me. It started with me needing to have music to listen to. I normally stream something off the Internet, "SBS Chill" if you're interested, but having a shower thought, it occurred to me that I might create a spreadsheet of the things I could hear via RF in my shack. It's been a while since I was on any frequency other than the local VK6RLM repeater where I host F-troop, and I wanted to get back to doing some more hands-on radio. After listening to "ABC Classic FM" on my amateur radio transceiver, I scanned up and down the FM broadcast band and heard plenty more stations. The audio wasn't cutting it, I mean, who wants to listen to Claude Debussy or Wolfgang Amadeus Mozart performed in glorious mono? I thought of using an RTL-SDR dongle to do the tuning and listening, the tool "rtl_fm" is perfect for the job. One problem. How do I get the audio from the device with the dongle, to my ears? I suppose I could plug in a pair of speakers and have at it, but I'm not alone and my office is central to the house, so anything here is heard everywhere. Headphone cables are too short and my antenna is also on the opposite side, so challenging. Mind you, I already bridged this gap once with RemoteRig, which essentially replaces the serial cable between the head and body of a radio with a network connection, for me that's across the room, but it could easily be across the Internet. All of this is complicated by my current computing set-up. I'm typing on a keyboard connected to a MacBook in turn connected to an external monitor. That monitor is also connected to a Debian Linux computer running Proxmox where my old workstation is running in a virtual machine and in the process of being resurrected. It also runs several other virtual machines where I'm running GNU Radio in a Docker container. One noted absence from that setup is audio. Right now, I record my podcast audio onto a Zoom H5 handheld recording studio in my wardrobe, then transfer the audio file to my old workstation where all the scripts live to make my podcast live. I edit the audio by launching Audacity on the Mac and opening that file across the network. I hear the editing through the Zoom H5 re-connected to the Mac as a sound-card. Otherwise audio is non-existent, not excellent for listening to radio or anything else for that matter. Ideal, no, not even close, but that's just one example of still recovering from my hardware crash over two years ago now. Mind you, audio was already challenging with software running inside Docker, but that's a whole other thing. I spent the day looking for ways to get audio across the room. I played with "ffmpeg" and RTSP streaming, only to discover that you need to install and configure more software in the form of a server, which is no longer included with ffmpeg. Also, apparently for reasons best understood by Apple, QuickTime Player no longer supports RTSP URLs, so go-figure. I looked at "pipewire", apparently needs a GUI to configure it, needs extra software installed and doesn't appear to be readily cross-platform, though I didn't dig too deep once I discovered the GUI requirements, I might come back to it. I explored running a Bluetooth audio server on a Raspberry Pi to stream audio to my headphones, much like I'm listening to right now, but that too seemed cumbersome, and included all manner of pairing, trusting and ad hoc piconet interactions that didn't fill me with joy. I suppose I could run a virtual USB cable across the network using "USBip Hot Plug" between two Raspberry Pi's and have a go, and I might still try that. Ultimately I didn't find anything that came close to a real solution to fix my audio issue, but this morning it occurred to me that essentially the thing I was looking for needed to be two-way, since if I'm going to make this work, Bald Yak would need to deal with a received signal as well as a transmitted one. For reasons I don't understand, let's call it my ah-ha moment, I imagined a picture of blocks scattered about, each doing their own thing and signal lines travelling between them. The phrase "peer-to-peer" came to mind and I started searching. I came across a tool called "SonoBus", a cross platform open source application that allows users to create a distributed network of audio users, specifically supporting both recording and playback. Looked excellent, right until I discovered that the last release was three years ago and there were 178 pending issues and 17 pull requests. Mind you, looking at it again now, there are branches that were updated less than three months ago, so it's still being developed and ultimately why I'm mentioning it. I toyed with the notion that I/Q signals are essentially two channels per sample, much like an audio stream is a left and right channel, so there was the possibility of shoehorning a radio signal into this platform, right until I realised that I need to still do weird stuff like change frequency, mode and perhaps antenna and the like. So, we're back to square one, but with it comes an understanding that part of Bald Yak is going to need something that does peer-to-peer signal streams. That gives me a description of what it needs to do. Essentially pipe data across the network between devices. It should be lightweight, offer the choice of lossless or lossy streams, since a command needs to be guaranteed to get to the other end, but you might decide that audio doesn't. It should be cross-platform, needs to be network and device agnostic, should follow Unix philosophy where programs do one thing and do it well, work together and handle text streams, because that is a universal interface. Mind you, I suspect that a text stream in this case is going to be a byte stream, but that's beside the point. It might transpire that such a thing already exists, "netcat" comes to mind for example, which if true would progress my efforts one step closer. All in all, it's been a good week. I'm Onno VK6FLAB
Foundations of Amateur Radio On the 15th of May, 2011, my amateur license still wet, I started documenting my experience with my newly adopted hobby. Now, sixteen years and 800 episodes later, I'm still at it. In reading my initial words from all those years ago, it strikes me that the impetus for that adventure is still with me today. In the intervening years much has changed and evolved. Some less so. First some history. I started this documentation process as a response to a new amateur who bemoaned the power limits of their license. At the time, it wasn't an isolated event, just the final straw. Regular disparaging and derogatory comment was levelled at this "toy" Foundation license, the one I'd just obtained and the one I was exploring. As it happened, I made an observation about this whilst volunteering to help with the production of the local amateur radio news. Ever keen on more content, I was encouraged to voice my concerns into a microphone and my journey began with something I whimsically called "What use is an F-call?", F-call being the colloquialism for the Foundation call, the introductory license in Australia. Recording done, I transcribed my words and the first episode was committed to disk. Since then I've written all episodes, then recorded and edited them. For just over four years, 206 episodes, I shared my experience and learned as I discovered more things to do and play with. Audience numbers were growing and I started receiving emails from listeners around the world. I renamed my efforts into "Foundations of Amateur Radio", still a nod to my Foundation license origins, but only if you were in the know. The content was the same, with one slight difference, I didn't assume that the listener was based in Australia, mind you, every now and then, I get an email asking about some word I used, but I think that's half the fun. Given that all this is being done manually, over the years I've made some errors with track numbering in my audio files, so it took me some time to work out what the actual episode number for today's effort is. I'm in the process of renumbering all of them, so it's consistent, but that's fraught, since all of my contributions have been archived all over the place, including in the Digital Library of Amateur Radio and Communications, the DLARC, so I have some things to figure out. Suggestions welcome. Over the years much of my amateur radio activity has been triggered by the need to write a new article before my self-imposed deadline. While that sounds like it's backwards for a person claiming to document their journey, it's given me a framework to keep exploring, asking, learning, trying and attempting to explain and encourage. As a consequence, I get the opportunity to talk to nascent amateurs during their course and one thing I mention is the sheer volume of activities associated with this hobby. Sparked by something I've noticed new amateurs appear to experience regularly, around two years or so into the hobby, they get to the point of boredom, "What else is there to do?", they ask. I point out that I too hold a Foundation license and based on my experience, I've yet to find an end of things to try and experiment with. Deadlines and Yak shaving aside, my amateur experience has not been without its testing times. Several instances of bullying behaviour occurred over the years which are not fun to experience or witness. I've seen amateurs leave the hobby because of it and if you're ever the target of such behaviour, reach out, [email protected] is my address. I can't fix things, but I can listen. One thing to observe about bullying behaviour is that it's often intense and confrontational. It's easy to forget that the vast majority of radio amateurs are lovely people who share your particular interest in all things RF to greater and lesser degree. In other words, don't let it define you if you're in the middle of this. It does make me want to make mention that there are still amateurs around who think that racism and misogyny are accepted forms of communication and behaviour. Fortunately they're slowly becoming extinct, but you'll find pockets here and there. What of the future? My journey is well and truly on the path of Software Defined Radio. It's probably fair to say that the number of such radios across the planet today far exceeds the number of "hardware" radios ever built, even if you only count mobile phones. I think that the nature of software means that we can build any future we imagine and change it when the need arises. I think that my experiments with 10 mW beacons point at the potential for other new forms of global communication, like JTTY, a new weak signal mode announced on 23 September 2026 with the release of WSJT-X v3.2, in much the same way as over a century earlier on the 2nd May 1925 amateurs proved they could communicate with any part of the world at any time of the day or night, when Ernest J. Simmonds G2OD and Charles Maclurcan A2CM made a daylight contact between England and Australia on what we now call the 20m band using 100 Watts. While we build that future together, permit me a moment of thanks. Your emails, messages and words of encouragement mean the world to me and it's a pleasure to see what you've been up to and learn from your experience. Thank you, it's very much appreciated. So, what have you been up to in amateur radio this week? I'm Onno VK6FLAB
loading
Comments