
Foundations of Amateur Radio
Onno (VK6FLAB)Audio
- Format:
- Podcast
- New episodes:
- Weekly
- Typical length:
- about 6 minutes
- Latest episode:
About this show
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?".
Covers: amateur radio, ham radio, radio hobby, software defined radio, radio propagation, antenna design, radio astronomy, gnu radio, signal processing, amateur radio clubs
Show details and episodes come from the publisher's public feed at podcasts.itmaze.com.au. Last updated . Names, artwork and text belong to their publishers.
Recently on this show
Summary of recent episodes, drawn from the publisher's feed.
Foundations of Amateur Radio is a podcast that explores different parts of the amateur, or HAM, radio hobby for newcomers and anyone wanting to get more from it. Recent episodes cover decoding Venus radio echoes, a PlutoSDR used as a bench instrument, I/Q signals, pointing an antenna without moving it, and getting started with gear.
Cosmos
Similar in subject
- icqpodcast's Amateur / Ham Radio Podcast
Both cover: radio propagation, amateur radio - QSO Today Podcast - Interviews with the leaders in amateur radio
Both cover: ham radio, amateur radio - On the Air
Both cover: ham radio, amateur radio
Similar shows
Explore more
Episodes
What does expertise look like?
· 5 min
Foundations of Amateur Radio Over the years I've had the opportunity to operate my station with other amateurs in close proximity. From a community perspective, this is loads of fun; from a radio perspective it's been frustrating to put it mildly. For example if you're operating on say 40m and your friends are playing on 20m or 15m, if you're not careful, you'll all end up hating each other at the end of the weekend due to the harmonic nature of the amateur bands. Imagine my surprise when Keith W6KME mentioned in passing that together with the other members of the Conejo Valley Amateur Radio Club, callsign AA6CV, managed to operate 25 stations within a 300 meter circle from each other, without commercial electricity. Oh, did I mention, the antennas have to be within the circle and they operated on 80m, 40m, 20m, 15m, 10m and 6m, no doubt there were other bands that I'm not aware of, and if that wasn't impressive enough, about a third of the space was allocated to public information. You can see their efforts at cvarc.org Mind. Blown. Given my less than exciting experiences to date, my first question to Keith was about inter station interference and Keith pointed me at a freely available article published in the May 2026 edition of QST magazine, titled "Station Setup Techniques to Prevent Field Day RFI" by Conrad N2YCH, which discusses a whole range of stations, including the AA6CV field day station. Very informative. One takeaway was that this is within the realm of doable for all of us. Another takeaway was that the stations in the article all appear to be high power, which is not something I have experience with, nor the budget for. I recalled that my local friends had done some abortive attempts at using so-called coax-stub filters. Essentially several specific lengths of coax that act as filters at particular frequencies, either to pass that frequency, so you can hear it, or to block the frequency, so you don't hear it. If you have a roll of coax, this could be a pretty cost effective way of making some field day filters. Somewhat tangentially, the other day I was having a conversation with a friend about technology in the world. We're both of a similar age and memories of Commodore Vic 20, MOS Technologies, bulletin boards and serial port multiplexers punctuated our discussion. At one point my friend commented on the vast knowledge and expertise held by a respected colleague, the implication being that we did not fall into that category. Given that we'd just spent the better part of 90 minutes discussing technology going back multiple decades and their impact in the world today, I pointed out that we too fell into that "expert" category. It's funny, even though I've been in computing for over 40 years and written over 780 articles on the topic of amateur radio, I don't particularly think of myself as an "expert". I think I know enough to know that there's plenty I know absolutely nothing about, and lots I know enough about to know that I'm dangerous. Imagine my surprise when I searched for "rg6 coax stub filters" and discovered a post on Hackaday, called "Coax Stub Filters Demystified". It opens up with the sentence "Unless you hold a First Degree RF Wizard rating, chances are good that coax stubs seem a bit baffling to you." and goes on to introduce some interesting observations and links to a YouTube video by "Fesz Electronics" cunningly titled "Coax Stub Filters", which includes a whole lot of detailed information, simulation and visualisation of various aspects of this phenomenon, including the impact of different types of coax, combinations of these and countless other variations, that I think is aptly captured under "RF Wizard", even if some Hackaday comments were dismissive. It brings me back to the underlying conversation around expertise. Everyone brings their own journey to this hobby. For some a coax stub filter is trivial, for others it's magical if not magic. I think that given the complexity…
Not rated yetFailure is a dirty word
· 4 min
Foundations of Amateur Radio It's a curious thing, this hobby of ours, in that the more you want out of it, the more challenging it becomes. For example, you might start your journey with a VHF or UHF handheld radio, sometimes referred to as a Walkie-Talkie or a Handy, and you start listening to the local repeater, or you try to make contact with a friend. Then you discover that it doesn't always work, so you learn about interference, terrain and antenna gain. You start looking for higher elevation or a better antenna and you discover that now you hear more, but you still can't talk to your friends and before long you're building filters and testing other gear and the journey continues unabated. This same incremental experience happens across every aspect of the hobby and it happens to all of us, perhaps unwitting participants on this amateur radio journey. Sometimes this experience leads to becoming discombobulated, discontented, disinterested and ultimately leads to disengagement, which in my opinion, does not need to be the case. Throughout our community we often talk about failure, as-in, a failed contact, a failed activation, a failed antenna or failed design, and on and on it goes. It occurs to me that we're not the only people who have this experience. "But the student will find that experience is the best teacher. The reason why I get along with comparative ease now is because I know from experience the enormous number of things that won't work. For instance, I start on a new invention to-morrow. From the great number of experiments I have made, and the vast amount of information I have stored up, I am saved a great deal of time and trouble in not having to travel over barren ground." If that sounds somewhat familiar, and reminds you of a quote about light-bulbs and failure, you're in good company, since those words were written in 1882 by the very same inventor of the light-bulb, Thomas Edison. In other words, the process of doing something doesn't end in failure, it's an experience, a point of learning, or if you want to be scientific about it, it's another data point. Just because something didn't go as expected, doesn't mean that it failed, just that something unexpected happened. I'm talking about this because we live in an increasingly complex world where our chosen hobby is made up from the very foundation on which we understand everything around us, the electromagnetic spectrum and all that it implies. Our adventures, frustrating as we might find them, are built upon the shoulders of giants who became silent keys long before our parents walked this Earth. Your participation, little by little, increases our global knowledge, experience and understanding and when something unexpected happens, it's time to celebrate, rather than give up in disgust. I've only been playing with radios for a short time, especially when I compare it with my experience in other areas of technology, but I can say, that framing matters. "Failure" is, in my experience, regularly thought of in a negative light and all too often it leads people to stop playing, because who really derives joy from banging your head against a wall? So, next time, when you're about to use that dreaded F-word, consider what might happen if you thought of it as a piece of experience earned instead? I'm Onno VK6FLAB
Not rated yetBuilding a new resource: How do you get into Amateur Radio?
· 3 min
Foundations of Amateur Radio The other day I was asked a question on social media. Having answered this question several times before, I admittedly .. initially .. groaned, then provided the bare bones of a response. A little while later, I recalled that I had provided a detailed response to this same question, as it turns out, five years earlier on a different social media platform, so I added another response that included the link to that answer. It all still felt very incomplete and inadequate and I couldn't leave it alone. Which leads me to the anxiety generating question and my response to it. Here goes: "[h]ow do you get into amateur radio? Is there like a 101 guide you could link me?" This is a question I've been answering for quite some time. Searching for the word "start" across the titles of my podcasts, there's 17 articles on the topic. So, having searched previously and fruitlessly for something resembling a universal answer, this to disclaim that I didn't look again and perhaps someone else has done something about it, I started a new project, because of course I did. I named it: "Getting Started in Amateur Radio" and published it on my GitHub repository. The intent of the project is to give the visitor a gentle introduction to the hobby, provide some idea of why you need a license, how it's different from things like the Citizen's Band, how you'll be starting on a life-long journey and introducing the concept that each country is slightly different. Think of it as an onramp into the hobby and our community. To deal with those, essentially legal differences between countries, I also consulted the International Telecommunications Union, the ITU, and created a folder structure of Regions and within it a folder for each country that the ITU as a United Nations specialised agency recognises. Before you ask, Yes, I'm aware that the UN doesn't recognise some countries that you might. I don't know how the International Amateur Radio Union, the IARU, our global representative body deals with that. If you know, get in touch. Since I'm based in Australia, I started with populating the information there. It contains some information about the regulator, representative bodies, callsigns, links to more information and hopefully initial information sufficient to "find" the community. It's still a work in progress, but it gives a good idea of the intent. Now comes the hard part. You. My log processing tool, "awstats", tells me that there are 209 different countries in my logs that represent you listening, reading and sharing my articles. So, I daresay that between all of us there is enough to cover pretty much all of the globe and with it, personal knowledge on how to become an amateur in your country. So, as one amateur to another, let's get on-air and make some noise! Let's try and document what's needed to become an amateur in your country. Please supply issue tickets, patches, emails, whatever you like, to get the information pertinent to your experience into one central place, so next time someone asks any of us: "How do you get into amateur radio?", there's a place we can share, that you contributed to and that contains the information pertinent to anyone who'd like to play. Look forward to hearing from you. I'm Onno VK6FLAB
Not rated yetTelling Stories to Strengthen a Community
· 2 min
Foundations of Amateur Radio When was the last time you told a story? The hobby of amateur radio represents as diverse and disparate a group of humanity as I've come across in my life. While that might mark me as living a sheltered existence, I have been around the globe and experienced some of what life celebration looks like. One thing I never tire of is hearing stories from the people I meet, each unique and worthy of my time and consideration. Over the years, in the context of broadcast radio and subsequently producing amateur radio news for over seven years, I've had the opportunity to interview people and record their stories and share them with the world. There are stories I keep retelling and others I'll never share, depending on what I've been entrusted with. I'm mentioning all this because I think that our stories are what makes us a community, a group of humans with different lives who have a common itch to scratch, conveniently labelled "Amateur Radio". With social media increasingly manipulated into highlighting and emphasising our differences, it's good to remember that we can use it to celebrate our common ground, glued together by this crazy, beautiful, rewarding, frustrating and experimental hobby we share. So, next time you get on-air, behind a keyboard or rub your finger on glass, remember, we can share our stories and be richer for the experience. I should point out that the nature of the stories we tell each other is dependant on you. While telling tales with embellishment is attractive, I rather think that it's remarkable, all on its own, that we can use minuscule amounts of energy, captured by a piece of random wire to communicate with someone on the other side of the world, so much so, that glitter is rarely required. You don't need to feel compelled to narrate your life story either, although that's entirely up to you. I'd encourage you to share your adventures, one story at a time, to inspire those around you to embark on their next journey of discovery. And if you're shy and you're not sure how to start, start small, one story at a time, practice makes perfect. Also, if your circuit board narrative smells of chicken, you're holding the wrong end of the soldering iron. Meanwhile I'll persist with the recalcitrant SoapyAudio software in search for the final missing puzzle piece.. Ha! .. to make this infernal contraption do what I can imagine, if only that cursed Yak would stand still, but that's a story for another day. I'm Onno VK6FLAB
Not rated yetBald Yak 20: More Pi with the Soap
· 4 min
Foundations of Amateur Radio The thing I think I love most about the hobby of amateur radio is the challenges it represents, not in terms of life or emotional ones, though I will admit that there's some of those .. in no small part due to the variety and complexity associated with being human and a member of the community, more in terms of figuring out how stuff works and then how much stuff there is. I was first licensed in 2010 and since then I've attempted to document the experience of being an amateur and discovering just what that might mean. This week has been interesting, if not quite as productive as I was hoping for. I spent a full day working on SoapyAudio, you might recall, it's one of the potential puzzle pieces in my Bald Yak project. I can report that it compiles fine on a Raspberry Pi 2, and when I get a moment I suspect that it will also work just fine on a Pi Zero. When I got to the point of packaging it all up, I spent hours trying to get my head around the Debian packaging system. For reasons I don't understand, nobody appears to have written anything that monitors the standard 'make install' step, save for one project called 'checkinstall' which has some serious bugs, like overwriting the system password file, and is not recommended. While in the middle of that adventure I discovered that SoapySDR and associated modules, utilities and support tools are already packaged in Debian. I'll confess that I emulated a stunned mullet when I noticed that. While this might mean that I essentially spent three days shaving a Yak for apparently no good reason, it did allow me to discover that SoapyAudio is currently receive only, but adding transmit doesn't look like an unsolvable problem. I still don't know why I went down the compilation steps but it allowed me to peruse the source-code which helped discover how some of this hangs together and I'll hasten to add that my understanding is currently incomplete at best, but that's par for the course. After discovering the existing packaging I installed 'soapyremote-server' on the Pi and it worked out of the box .. something which I'm happy to say is a regular occurrence with Debian packages, perhaps this is why packaging is so complex, another thing to investigate as time permits. I then added an external USB sound card with the audio going into the rear DATA socket of my FT-857d, and together with the CT-62 compatible USB CAT cable, that's Computer Assisted Tuning, allowing remote control of the radio, the Pi was ready to be the network interface to my copy of GNU Radio. Well, not quite. There's some secret incantations that I have still to divine, but thanks to random forum posts with hints at how to format the command string required, I'm making progress. GNU Radio can see the Soapy Server, has passed the checks to control the radio, which happens behind the scenes thanks to Hamlib, but stumbles on the audio card side of things. If it weren't for other life affirming activities in my diary, I would be reporting success, but I can tell you that I can taste it. Now, why does this make me excited? Well, it means that I can now use my FT-857d across the room, technically across the Internet even, to receive and process RF within GNU Radio. You might recall that this is one of the stated aims of this whole endeavour. In terms of "50 things to do with an SDR", this one will end up in the "Listen to conversations on the 2-meter amateur radio band" pile. While it's not particularly exciting to listen to the local repeater across the room, something which I can do by turning up the volume or getting a long headphone lead, it represents a small milestone in the pursuit of my Bald Yak project which 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 .. micron by micron I'm getting closer. Also, "like a…
Not rated yetBald Yak 19: SoapyAudio adventures
· 5 min
Foundations of Amateur Radio Previously I've talked about a piece of software called SoapyAudio. It's part of the toolkit called SoapySDR which in turn is part of a whole ecosystem called the Pothos framework, coordinated by Pothosware, founded by Josh Blum. I'm mentioning this for two reasons, first to give credit to Josh and the many contributions he has made to the Software Defined Radio ecosystem and second, to indicate that there's several moving parts here. SoapyAudio is a module that connects an audio device, like a microphone or a speaker, more on that in a moment, to a tool called SoapySDR. This allows you to connect to that device, either directly, or over the network, from within any Soapy compatible SDR tool, like Cubic SDR, SDRangel, Quisk and SDR++ to name a few. Said differently, you can use the SoapyAudio module to pretend that your sound card is a Software Defined Radio, and use the associated SDR tools to use it. While interesting in and of itself, the idea comes into focus if you consider that you could connect your analogue radio to the sound card and now you have actual radio frequencies coming into your card, which you can use as an SDR. This works because SoapyAudio also includes Hamlib support, which in turn means that you can send commands like: Set the Frequency, or Set the Mode, to your radio using Hamlib, better yet, if you do this within your SDR software, all this happens behind the scenes. Now, before I dig in too much more, I mentioned a microphone and speaker. When you connect your radio to a computer, the microphone or line-in socket is used to receive audio from the radio, it leaves the radio and enters the computer via the microphone and gives you the ability to receive audio, alternatively, when you connect the computer speaker to the radio, it leaves the computer and enters the radio, to transmit audio. Right now I see no evidence that SoapyAudio supports the ability to transmit, and the ecosystem overview shows the module in a different location than the other radio modules. It might well transpire that none of this is going to work long-term, but the point of this is to learn how it works and to get an understanding of how data flows back and forth. Ideally, I'd end up with a module that would integrate into GNU Radio using the existing SoapySDR integration, but I'm nowhere near that, and my ongoing computing challenges keep banging me in the face, so small steps. If you're not quite sure how this is supposed to work, your radio is connected to your computer using audio in and out, as well as a serial or USB connection. The computer is running SoapyAudio which uses Hamlib to control the radio and uses SoapySDR to send and receive both control and radio signals through a tool called soapy-server, which I think will all run on a cheap Raspberry Pi which is in turn is connected to the network to another more beefy computer running GNU Radio and the SoapySDR module, allowing you to both control the radio over the network as well as receive and transmit. Well .. at least that's the plan. In order to bring that grand idea closer to fruition, I've just spent the past two days putting together a set of instructions, in the form of a Dockerfile, to attempt to help make that happen. I'll note upfront that this is a work in progress and there were plenty of trips to the local Yak Shaving compound to sharpen my blades, but I think by now you'll understand that this is par for the course. I'm sharing all this with you because in amateur radio and in any complex endeavour, progress is made by making small incremental improvements. We're up to the 19th, or 20th, if you count the introduction of my Bald Yak series and so far I have only very little tangible assets to show you. I suspect that this is going to be the case for some time to come. Perhaps my journey should be viewed as a way to pursue the things you're interested in and document your progress along the way, rather than a journey…
Not rated yetWhy not use LoTW?
· 9 min
Foundations of Amateur Radio The other day I witnessed a fellow amateur attempting to guilt another into using LoTW with comments about how their QSO partner would appreciate confirmation via the service, even if they didn't care for it. Before I continue, if you're unfamiliar, when two amateurs make a contact, or a QSO, with each other, then there's generally a log entry at both ends to record the event. Some amateurs, myself included, save up these contacts and count how many continents, countries, states and other entities are recorded in the log. Several amateur radio organisations allow you to claim an award for such a record. However, before they accept your word for it, they require confirmation of the contact, something that the amateur community refers to as a QSL. To recap, a QSO is the contact, a QSL is the confirmation of that contact. Traditionally this was achieved with postcards, known as QSL cards, transported across the globe through various postal services, and coordinated by so-called QSL bureaus, often run by the amateur radio peak body in each country. With the advent of the Internet, much of this process has turned electronic. LoTW is an example of an electronic QSL service, run by the ARRL, the American Radio Relay League. It's not the only such service, but today I'm looking specifically at the Logbook of The World, or LoTW. As I said, LoTW is not the only service and anyone telling you that you must use it is selling you something. Now, that's not why I don't use it, and again, you're free to, but you're not required to. For me there are several issues with LoTW. Having used it for a period, I feel comfortable in expressing some of its shortcomings, but I note that the last time I used it was almost a decade ago. I'll acknowledge that things might have improved or changed, but I have no evidence to suggest that it did. Let's start with how it works. You create a log in a specified format, using an application called TQSL you sign that log, ostensibly linking your identity to that log, then you upload that signed log to LoTW and wait for confirmations of contacts with other LoTW users. Signing is a process where you add information to a file that proves to the recipient that the log was created by you and wasn't modified in transit, which requires that you have a file called a certificate, which is created and sent to you via email by the ARRL, after they've authenticated you. So, first of all, in my opinion, the level of security is absurd and exceeds that of my bank, or my tax department. In addition, proving your identity comes with hurdles if you're not in America where an amateur who registers receives a postcard with an authentication code, made possible by the central database held by the FCC. For everyone else, the ARRL requires that you: "must send a copy of his/her Amateur Radio operating authorization in addition to a copy of one other government-issued document indicating his/her identity", via the post, snail mail, stamp, envelope, the whole thing. I'd also like to observe that at no time has the ARRL linked your identity to your email address, since they haven't asked for it at any point in the verification process. If that's not enough of a security nightmare, in Australia and other parts of the world, amateurs no longer hold a personal license, instead they are members of a so-called class license. There's no public record stating my ownership of my callsign, just that it's allocated. With increased privacy concerns, this is happening elsewhere too. In other words, proving that you are who you say you are is getting increasingly difficult and even if you did, you're sending that information to the ARRL, who you might recall paid a ransom to hackers who infiltrated their network. I've asked and never received a response about what actually happened to the information they continue to hold in relation to me, well that and an email from 2013 which states that "Data is never…
Not rated yetSome days are like running in place ...
· 4 min
Foundations of Amateur Radio Recently I discovered that the antenna that I had connected to my WSPR or Weak Signal Propagation Reporter beacon was not a 40m antenna, instead, it turns out to be a 15m antenna. The how and why of that mix-up isn't particularly helpful, so instead I set out to remedy the situation. Step one was simple, go into the garage and pull out the antennas and check if I had forgotten about an 80m antenna. As it happens, I'd forgotten about a 17 megacycles antenna. At the moment I couldn't tell you if it was intended for Maritime or Amateur use, but it doesn't really matter, since I'm not permitted to use those frequencies for transmit and I was on a mission. Oh, I also discovered that you can dislodge two shelves with stuff on them by moving an antenna. Fun. So, 7 MHz, or 40m it is. The antenna mount is clamped with G-clamps to the side of a steel roofed framework that's bolted to the house. It's been there for about eight years or so. From time-to-time I change over the antenna depending on my mood. Today I wanted to move the mount and after taking it down decided that it could do with a little maintenance, least of which due to the fact that the feed-point connector had detached itself. I also needed to remove the ground wire, which turns out to be a bit of a palaver, since my socket wrench adaptor has gone walkabout and the 10 mm socket that fits into the next size is too large. Eventually I found an imperial socket with a matching wrench to undo the thing. Then I set about moving the mount to a new location, tucked inside a tree, so plenty of branches to poke me in the eye, or the belly, depending on which was handy at the time, and discovered that the steel beam was thicker, to the point that my G-clamps were 2 mm too small. So, I spent some quality time comparing hardware store offerings, finally found a bigger G-clamp for a reasonable price, but in the process discovered customer reviews and photos showing that the clamps fail if you hand-tighten them. Me being the "if you can move it, it's not tight" kind of person, figured that this would not work. Found F-clamps at a different hardware store and went on my merry way to get one. The hardware store was undergoing maintenance, so hammer drills and stuff everywhere, more fun. After getting back home I discovered that the new location was great in theory, but in practice it turns out to be less than spectacular, since the beam has a slight curve in it, making for a poor clamping surface and no place to put two clamps. Back to the original location. Using the new clamps, fighting for space, I realised that I could re-use the old clamps, so swapped them over. Then I got to the point of connecting the feed-point and discovered that my 40m antenna is missing the mounting thread and the all-thread inside the old antenna wouldn't budge, neither would any of the threads in the other two antennas. So, at this point, three hours in, I came to the realisation that this was going to be a 15m antenna or no antenna. So, 15m it is. There is one actual change. I discovered that the feed-point connector is actually an SO-239 socket and the connector to it was a standard banana plug which in turn was connected to a BNC connector, with the shield connected to ground. I realised that I could use a BNC to PL-259 adaptor instead to connect the RG6 coax to my antenna. This means that the coax is now directly connected to the feed-point, rather than through a weird cobbled together BNC-to-wire-split-thinga-ma-bob-contraption. It looks very pretty. Measuring the result also shows some changes. On both 40m and 15m the SWR is still the same, on 10m it's a little worse and on 2m it's significantly better. All in all, I think this is a perfect example of 17 steps backwards and 18 steps forward. I suppose it could be worse. I'll let you know how the beacon goes. Now, I should probably log this. Something like: "QTH HF antenna mount maintenance, nothing…
Not rated yetKeeping track of your adventures
· 8 min
Foundations of Amateur Radio About a year ago I set upon a new adventure, to determine if the dummy load I own, traditionally seen as a device that doesn't emit any RF, to determine if it was in fact imbued with the ability to absorb RF, rather than share it around like an antenna might. At this point you might be shaking your head, but this wasn't embarked upon lightly. I had spent several years experimenting with lower and lower power levels and came to learn that even 10 mW can make it to the other side of the planet, 13,945 km away. In other words, extremely low power can, under the right conditions, make it across the globe. So, with that in mind I connected a dummy load to my WSPR beacon and configured it to transmit across each band between 80m and 10m and then set-up an RTL-SDR dongle to monitor those same bands as well as the remainder of the amateur bands within the range of the dongle. I did this because I wanted to make sure that if there was any chance of a harmonic appearing unexpectedly, there'd be a good chance I'd see it. Then for a year I did nothing. Well, not exactly, but we'll get to that. After downloading 16 months of WSPR reports I extracted all the records that had my beacon in it and separated them into two groups. Those that had VK6FLAB as the reporting station and those that didn't. Both contained a significant number of signal reports. After doing some analysis, charting the efforts and discovering other phenomena, I can report back a little of what I learned. The dummy load does radiate, but I only saw reports from the dongle which is in the same room. I have already talked about this and at the moment the working theory is that the coax between the beacon and the dummy load radiates, or the beacon itself does, or something else, because the RTL-SDR dongle is clearly and accurately decoding WSPR signals. I'm not sure how I'd go about verifying where the radiation is coming from exactly or if I'd need equipment that I don't have or know about. That said, somewhat to my surprise, the signal reports were not static, varying considerably by as much as 40 dB. Notice that we're talking about a signal that is being, at least ostensibly, transmitted into a dummy load and being received on an external antenna. The signal reports don't appear particularly affected by time of day or band, that said, there's a visible range of reports across the year, but it's hard to observe anything definitive since most of September and October is missing. At this point I cannot tell you why that's the case. More on this in a moment. I did notice that some odd things happened to reports throughout the year. For example, on 40m, the reports were significantly poorer in the first half to 2025. 17m and 15m on the other hand were worse in the second half of the year. On the 25th of April here in Australia we're permitted to change our callsign to use AX as a prefix, so my VK6FLAB callsign would be AX6FLAB. On that day I configured my beacon to use 40m and connected it to the antenna for the first time in a year. I had several reports across the Great Australian Bight over 2,000 km away. At midnight UTC the next day I changed the callsign back to its normal VK prefix and changed the bands to use 80m, 40m, 15m and 10m, and left it connected to the antenna. While the antenna is a mono-band antenna, I wanted to know if it would still radiate on bands it wasn't intended for. Turns out that yes, it does, very nicely in fact. Since activating it like this, I've been heard by 79 different stations, as far away as 15,649 km in the United States, and in Antarctica as well as across Europe and several reports in Africa, the bulk in the Asia Pacific. Something curious though. I noticed that there were no reports on 80m and only a few on 40m. Pretty evenly split are reports on 15m and 10m. This was odd to me, since I would have told you that the antenna is a 40m mono-band antenna. You might recall, built by Walter…
Not rated yetDealing with Complexity
· 6 min
Foundations of Amateur Radio Several years ago, I forget exactly when, I was gifted a device called a "Wio Terminal". It's a micro-controller in a box with a screen, buttons, Wi-Fi, Bluetooth and a boat load of sensors, ports and more. It's intended for experimentation and truth be told, exactly the right gift for a geek like me. It even has rubber feet to stop it from sliding off the desk, well, slow it down at least! The thing is, it remained sealed in its box until this week, when I finally gathered enough unrelated information, something I often refer to as "puzzle pieces", to understand what this device might do and how I might use it. Given that I'm talking about amateur radio, and not software development, I'll only mention that I got my initial "hello world" working and observe that I have some radio projects in mind for it. What this experience revealed to me was that complexity is hard, not to mention frustrating, and not limited to my adventures with computers. Let me elaborate. In amateur radio the answer to a great many questions is a phrase I've used before: "It depends", a valid, but ultimately immensely irksome response. Over the years I've attempted to dig into what exactly "it" depends on, with varying levels of success. While Earth rotates on its axis, that answer is unlikely to change, but I think I can make it potentially less aggravating, and here's how. When you come across a question where the answer is: "It depends", stop worrying about exactly "what" "it" depends on, instead, keep the question in mind whilst you go about your life. Looking back at my Wio Terminal experience, that's exactly what I did. While there's the frustration of not being able to report to my friend that I'd done anything useful with it, by having it float around my desk, albeit still in the box, I regularly noticed it, and when going about my day I'd continue to gather puzzle pieces that eventually hit a critical mass. In other words, whilst gathering apparently unrelated, facts, skills, articles, example code, cables, computing resources, how-to documents, forum posts and the like, including having discussions with others, eventually I had enough to realise that I had the answer to my question that wasn't "It depends", instead, I had a clear, well, clearer, understanding of what kinds of things I needed to achieve to make progress. Now I'll be the first to acknowledge that this journey isn't always a gentle stroll in the woods, "bear with a sore tooth" has been levelled more than once, but the point remains, figuring out how things work isn't a linear process and once you are aware of that, life becomes, well, at least in my mind, more interesting. Again, what does this have to do with amateur radio? Well, let's look at some innocuous questions that an amateur might ask: "What radio should I buy?", or "What antenna should I get?", or "Given the current propagation, can I make a contact with my friend on the other side of the planet?" The answer to each of these questions is: "It depends." If you have been in this community for a time, you'll understand some of the things "it" depends on, but the longer you are here, the more aware you become of other things "it" depends on, in other words, your understanding of the problem reveals that there are more considerations at play that might not be immediately obvious. At some point you'll get to the next unhelpful response in amateur radio: "Try it and report back." Equally annoying, since, at least on the face of it, you'll invariably be left with the feeling that nobody cares, least of all the person you asked. While I'll acknowledge that this is sometimes the case, on the whole, the response really reveals that there are too many unknown variables to form any coherent overview. That said, as the person answering, providing a range might be helpful to at least get a sense of what space to play in. What I mean by that is, sometimes figuring out what needs to happen…
Not rated yetWhat does amateur radio bring to your life?
· 5 min
Foundations of Amateur Radio The other day I went for a walk around the block for the first time in a while. It's something I did for a time and then for several reasons, mostly to do with health, didn't. For me it's the mental equivalent of having a shower with the added benefit of not having to dry my hair, in other words, it's a place I go to with the intent of generating shower thoughts. During my walk, away from the forces pulling me in all manner of directions, none of which have anything to do with amateur radio, away from my keyboard, away from my screen, away from technology challenges, although I'll admit that my phone was in my pocket, I took about twenty minutes to walk and daydream, to follow my thoughts and to see where they'd end up. I got to this point because sitting at my desk I was getting nowhere trying to put together my thoughts in any sequence at least resembling coherence. While it's happened before, it's not something that occurs often. The day before I'd started writing, almost as-if possessed, about what amateur radio means to me, but during my walk I started wondering about the people who leave this hobby and the community embracing it. I've often said that F-troop is a weekly net for new and returning amateurs, both people who have a license that's still hot off the printer, and others who have one typed up on an IBM Selectric, signed with a quill, ink faded with age, paper yellowed by sunlight, potentially with coffee mug rings on it, stashed somewhere in a drawer. I wondered about those returning amateurs and asked myself about the nature of leaving a hobby. It occurred to me that people leave for many different reasons, and it would be foolhardy to consider that all of those reasons are controllable by our community. While bullying and arguments exist, each responsible for their share of people leaving, it seems to me that some amateurs leave because there's too much other stuff going on in their lives, things that actively or passively prevent amateurs from participating. This is difficult for me to relate to because for me, amateur radio is an intrinsic part of my life, in that it often quietly shapes how I view the world and learn from it. I see it when I notice a television antenna pointing in the wrong direction, when I install a new Wi-Fi router somewhere, when a signal is lost to a manned mission around the Moon, when I open the garage door and when I read that researchers at the National Institute for Standards and Technology, better known as NIST, have developed a new method for creating chips that process photons similarly to how traditional chips process electrons which can generate a rainbow of colours, though they didn't use the letter "u" to describe them. While those examples might be somewhat obvious, amateur radio is also there when I see someone share a tiny electronic paper screen on social media and I consider how I might use that when I go portable. It's there when I'm walking in a park and when I'm looking at a beach, it's there when I see metal artworks or painters poles at the local hardware store and when I watch a movie with radios anywhere on screen. It's there when the topic of physics arises and when some electromagnetic phenomenon occurs. Like radio waves and air, it's pretty much part of my daily existence. I will add that this same depth of connection exists between me and computers. Watching "Flight of the Conchords" I cannot help but notice that Murray's computer keeps changing and that I miss the Commodore Vic 20 sitting behind him surrounded by ever changing New Zealand tourism posters. In other words, I cannot imagine ever not having radio or computers in my life. I'm mentioning all this because my experience isn't universal. While I'm sure that I'm not alone in this deep affinity, the community as a whole invariably ranges between people who could take or leave the hobby at a moment's notice and those who couldn't live without it and beyond our…
Not rated yetYou don't need an excuse to make noise!
· 3 min
Foundations of Amateur Radio The other day I came across a post on mastodon.radio by Keith W6KME announcing the resumption of the Micro Field Day, spelled using the 12th letter of the Greek alphabet, Mu. This was news to me, since I didn't know they'd stopped, let alone existed at all. Being the curious type, I stopped to investigate and discovered an initiative that could, and in my not so humble opinion, should, be replicated all over the planet. Essentially an informal monthly gathering of amateurs with their portable set-up, ranging from hand-held radios through lightweight backpack gear suitable for SOTA or POTA, or Summits or Parks on the Air, to car portable stations where your vehicle acts as the carry mule and perhaps the base of your antenna. In other words, it's for anyone who brings along their radio to play or if you're not yet ready to do that, come and participate as you feel inclined. So, what of the resumption, you ask. It turns out that the activity became so popular locally that some parks required paid bookings and insurance, which is somewhat challenging if you're not actually an organisation. The closest I've ever come to a Micro Field Day is when we celebrated a milestone anniversary for the weekly F-troop net that has now been running for over 15 years. The Bored Net Group website has plenty of information about what they get up to during a Micro Field Day, Random Metal Objects On The Air, shared club activities, picnic lunches, and activations at local lakes, landmarks and other places of interest. I'd also like to make a point here about documenting your activities so the rest of the community can learn from your experience and the Micro Field Day isn't the only, or even the first activity that the group organised. Special mention to Zak N6PK who started hosting the BORED net four times a day during the COVID-19 pandemic lockdown in March 2020. You'll find the full story when you check out their site at theborednet.net for that and oodles more inspiration. While I'm perfectly happy sitting at home behind a computer reading research on the resource comparison between half a dozen algorithms for calculating a Fast Fourier Transform, that's not the only thing that amateur radio represents. When I started running F-troop there was no place for new and returning amateurs to gather and ask questions and share their experiences. Today the log shows at least one new callsign for each week we've been on-air, representing nearly a thousand amateurs who activated their transmitter and shared their experience. There is no organisation behind F-troop, it's a couple of amateurs who regularly turn up and participate to act as a welcoming voice into the diverse community that represents amateur radio. In other words, it started because I felt like it and it continues because people keep coming back. The Micro Field Day is exactly the same in that it was started to scratch an itch. I'm making this explicit because some amateurs appear to be under the impression that they'll need a local club or organisation to organise activities for them. I'm here to tell you that you can start such an activity with your friends. Ultimately, where do you think clubs come from? So .. what are you waiting for? Get on-air and make some noise! I'm Onno VK6FLAB
Not rated yetWhat's in an S-unit?
· 10 min
Foundations of Amateur Radio The other day fellow amateur Randall VK6WR raised an interesting question. Using his HP 8920A RF Communications Test Set, which you might recall from our adventures in measuring radio harmonic power in 2023, that report is on my Github repository, but I digress, Randall wondered if the signal strength he was seeing on several radios were the same and discovered that in fact they were not. It made Randall ask who set the standard and following on from that, what does this look like in the real world? In 2014, episode 149 of the series "What use is an f-call?", I published an article titled "The simple S-unit". In it I referred to a standard for S-units defined in 1981. Unfortunately, I didn't provide any references, so, armed with more than a decade extra experience, Randall encouraged me to investigate. Twenty seconds into my search, I discovered IARU Region 1 Technical Recommendation R.1, which has four statements related to the topic at hand. Under the title "STANDARDISATION OF S-METER READINGS" it states that: 1. One S-unit corresponds to a signal level difference of 6 dB, 2. On the bands below 30 MHz a meter deviation of S-9 corresponds to an available power of -73 dBm from a continuous wave signal generator connected to the receiver input terminals, 3. On the bands above 144 MHz this available power shall be -93 dBm, 4. The metering system shall be based on quasi-peak detection with an attack time of 10 msec +/- 2 msec and a decay time constant of at least 500 msec. So. Job done, right? Yeah, nah, not so much. The web page I quoted from is linked from the Wikipedia S-meter entry and was archived in 2005 and at the time existed on a Swedish domain in the home directory of Kjell SM7GVF. The page has two additional interesting things, the words "Brighton 1981" and "Torremolinos 1990", both of which refer to IARU conferences. The reports for these meetings are online. In searching for any reference to the definition of the S-unit, the 1990 report shows that resolution "83-1" had the status of "Action completed", whatever that means. The 1981 conference document has all manner of interesting references, including "Log Forms and Summaries for International Contest Use", "Meteor Scatter qso procedure" and the definition of the standard way to determine Morse Code speeds using the word "PARIS" followed by a 7 bit word space, to name three. The one we're interested in is called "BM/134 - S-Meter Standards", appearing on page 33 and 34 of the 1981 report. It's a photocopy, so you can see the text from other pages superimposed. I'm making this observation because this is essentially a standards document, intended to be adhered to by industry and the amateur community. It gets better, or rather .. worse. The text that is referenced by Wikipedia uses numbers for the four elements, where BM/134 uses letters. The third item in BM/134 says that it applies for "bands above 30 MHz", but the document I just quoted appears to be unique in saying that it applies to "bands above 144 MHz". The fourth item, dealing with the way that the meter responds has been altered on BM/134. The text "+/- 2 ms and a decay time" are in a different font and at an angle. Worth noting that the change includes "ms" twice, rather than "msec" as the unit for milliseconds used elsewhere. Searching for a phrase within the standard, I discovered the Region 1 HF Manager Handbook v7.01, which appears to include the S-meter standard in chapter 11.1.2, but closer inspection reveals that the fourth item is missing, the one about quasi-peak detection. This is significant because the S-meter standard is based on a CW signal, not an SSB signal, which fluctuates. There's no reference as to where or when this was removed or by whom. These changes are repeated in subsequent versions of the HF Managers Handbook. There's other differences too, instead of using millivolt and microvolt as shown in the original BM/134 standard table,…
Not rated yetWhere is the spark .. gap?
· 8 min
Foundations of Amateur Radio The thing I love most about this amazing hobby of amateur radio is the sheer size of the community and the depth of knowledge that comes with it. Case in point, the other day I mentioned the spark gap transmitter at Grimeton in Sweden. A few hours after releasing my comments into the void I received a message from Paul SA7CND who lives, wait for it, 153 km from the transmitter. He's been on-site while it was running, transmitting on 17.2 kHz. Paul pointed out that the Grimeton transmitter is not a spark gap transmitter at all. It's actually an Alexanderson alternator, an entirely different beast, and all the more interesting for it. Invented by Swedish electrical engineer and inventor, Ernst Frederick Werner Alexanderson, he received a patent for it in 1911 whilst working for General Electric. He died in 1975, aged 97 with 345 patents to his name. Before I dig in, because you know I will, the transmitter at Grimeton was officially opened on the 1st of December in 1924. Built to increase Swedish independence after World War I revealed its vulnerability to foreign controlled transatlantic telegraph cables. Serving as a telegraphy station capable of transmitting traffic across the Atlantic ocean the station was in regular service until 1996. Unlike its scrapped brethren, the Grimeton transmitter is currently operated several times a year as a functioning transmitter using the callsign SAQ. Announcements are made on the station mailing list and the website at grimeton.org, but generally on Alexanderson Day in July and Christmas Eve in December. You'll need to tune to 17.2 kHz, something you can do with a sound-card, or with an SDR. Sound-card you say? Yes. Not for audio, but for RF. Connect an antenna to the microphone centre-pin input and have at it. Note that this will likely be highly susceptible to noise, so filtering and experimentation are to be expected. There's several tools around to play with this, GNU Radio, Quisk, SuperSID and SAQrx. Also, there's plenty of other VLF, or Very Low Frequency stations to listen to. I should probably add this as a 51st thing to do with SDR, but I digress. Back to Grimeton. As the last remaining functional Alexanderson alternator transmitter, it was added to the UNESCO World Heritage List in 2004. You can visit and see first hand what radio history looks like. As I said, if you pick your day, you can even watch it working. Failing that, there's plenty of YouTube videos showing the entire process, it's an absolute monster. There's even an amateur radio shack on-site with the callsign SK6SAQ. The website says that it's open sporadically, so I'd recommend you contact them before heading to Grimeton. I'll note that at the time that this station was being commissioned in 1924, it was already being superseded by valve oscillators, which brings me to how it works. Depending on where you live, you're likely familiar with the 50 or 60 Hz alternating current associated with household electricity. In 1891, Irish experimental physicist Frederick Thomas Trouton pointed out that if you could run an alternator at high enough speed it would create an alternating current at radio frequencies, said differently, creating a continuous wave at radio frequencies. Much experimentation followed and many giant shoulders supported this effort. It goes a little like this. Use an electric motor designed to spin at 900 revolutions per minute. Connect it to a gearbox. Connect that to a rotor with multiple poles. Then run the motor with a clutch to vary the speed. If that's not enough, to produce high power, the clearances between rotor and stator have to be kept to a millimetre. Then there is cooling and lubrication to consider, not to mention dealing with thermal expansion and contraction of a fast spinning and closely toleranced disk. At Grimeton, the whole transmitter weighs in at 50 tonnes, pretty much the opposite of portable operation. The rotor at Grimeton is a 1.6 meter…
Not rated yetBald Yak 18: Everything Everywhere All at Once?
· 7 min
Foundations of Amateur Radio The other day I was playing around with RDS, or Radio Data System, it's a digital signal that's often embedded in a commercial broadcast FM transmission. Among other things it contains information about the station, its content, frequencies and potentially other useful information, such as traffic alerts. If you recall I've been working on 50 things to do with a Software Defined Radio and decoding RDS is one of those things. The decoding effort aside, I imagined a screen where you could see the RDS information, in real-time, as it was being transmitted by all the local FM broadcast stations. You'd see what music each station was playing, what their local clock thought the time was, how much they transmit other data and what they might do for emergencies, like say a Tropical Cyclone heading this way. It occurred to me that this would be an example of a fundamental difference between a traditional radio and a Software Defined Radio or SDR. Specifically, we're taught that you tune a radio to a frequency, it demodulates or decodes what's there and plays the sound, or digital information, or whatever is being transmitted, on that frequency. If you want to hear something else, you need to change frequency and the radio decodes that new frequency. If you have multiple channels to choose from, there are ways to automatically switch frequency, one after the other. One of my friends recently discovered an old scanner in a box and according to the specifications, it can scan 20 stations per second. If all 1,000 stations are programmed, it takes 50 seconds to scan them all. A lot can happen in that time. The traditional solution is having more radios. Ideally you'd have one for every frequency you care about. Cost aside, logistically this is not fun. Imagine having to power a thousand radios, or find the one where the volume isn't right, or even find space for them, or antennas. In the SDR world that's not quite how it works. Instead of tuning to one frequency, you essentially tune to a range of frequencies and then, using software, decode one or more of those frequencies, at the same time. Listening to multiple broadcast FM stations like that might not make a whole lot of sense, but what about decoding RDS, or listening to aviation frequencies, or local amateur radio repeaters, or multiple digital modes? While that might sound far fetched, a $50 RTL-SDR dongle can manage 2.5 MHz of bandwidth over USB, by comparison, my $1,000 Yaesu FT-857d can receive all of 200 kHz in Wideband FM mode, and only whilst tuned to the broadcast band frequencies. In normal AM or FM mode it's 10 kHz, so you'd need 250 of them to listen to the same frequency range. Again, just so we're clear, in analogue radio you need to change frequency to decode a different signal. In SDR you can simultaneously decode as many signals as resources permit. For example, I can make a simple GNU Radio flowgraph, a little program, that accepts a command line setting, in GNU Radio it's called a parameter block, and run it with a frequency I'm interested in. Then I can run another copy of the same program with a different frequency. Rinse and repeat and I have as many receivers as I need. While we're at it, you don't need to run the same program multiple times, you can run an FM decoder, a RTTY decoder, an AM decoder, all at the same time, as long as the frequencies you're looking at fit inside the bandwidth of the receiver you're playing with. Just so we're clear, this is one receiver, one antenna, one power supply, with as many decoders as resources allow. In other words, these two methods, analogue and SDR, are not the same. Am I glossing over things? Sure. With such a wide bandwidth comes susceptibility to interference and signal overload, also the RTL-SDR dongle doesn't transmit, although, in 2014 Ismo OH2FTG managed to change the centre frequency of his dongle 300 times per second, causing the on board oscillator to leak in a…
Not rated yetBald Yak 17: Adventures in Radio Data Systems
· 5 min
Foundations of Amateur Radio While spending some quality time discovering what I don't know about GNU Radio, I explored the notion of attempting to at least understand a little more about how an FM signal works. Depending on your background, the letters FM mean different things. In amateur radio it's a way to encode information, generally audio, using something called frequency modulation. Outside the hobby, the letters point at commercial broadcast radio. While the two are related, they're not the same thing. In amateur radio use, FM is a single channel of mono-audio, however, in commercial broadcast radio, there's a whole lot more going on, interesting because it gives you ready-made access to a composite signal that's just complicated enough to be challenging without being so complex that you need to spend hours on understanding the thing. In essence, a commercial FM broadcast signal is multiple channels encoded in a specific and documented way. This is helpful, since you can compare the documentation against ready made examples and replicate the process for yourself. In case you're new here, I'm in the process of building a radio system, in software, using GNU Radio in a project called Bald Yak. Specifically, 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. One of the easy things to forget when you're using GNU Radio Companion, is that the blocks you're connecting together on the screen into a flowgraph actually represent software, generated when you either build or run the flowgraph. This code is currently generated in either Python or C++, making me wonder, what does the code look like, and more specifically, what code would be needed to decode FM? It turns out that an old friend, the PySDR.org website has a whole chapter dedicated to this process. Chapter 18, the End-to-End Example, details how you can decode one of the channels embedded within a commercial FM broadcast, the RDS or Radio Data System signal. If you're not familiar, the PySDR.org website represents a whole book about software defined radio and python. It goes into as much or as little detail as you want, to explain how this whole software malarkey works, and takes you by the hand down the path of discovery. So, armed with a working example, I followed along the bouncing ball and made a working RDS decoder and I think, understood most of it. There's a few interesting wrinkles that I've contacted the author, Dr. Marc Lichtman, about and we'll see what comes of that. Here's the kicker. The author, who is also a senior member of the GNU Radio team, started with a GNU Radio flowgraph and reverse engineered what was happening to get to the point of the code that's available in PySDR.org Chapter 18. This is significant because it creates a relationship between the code I have in front of me and the code generated by GNU Radio, which means that when I start with a new flowgraph, not only do I know the steps required, I also know that the outcome is predetermined, as-in, I already know that there's a solution. Having professionally written software for over 40 years, I can tell you that this is not often the case. I realise that I can search the Internet for an RDS decoder flowgraph, but that's unlikely to get me to a better understanding of what GNU Radio is doing. Once I've clarified with the author, I'll add the code to my GitHub project, "Fifty Things you can do with a Software Defined Radio", specifically, "Receive road traffic information", since among other things, that's carried by RDS. As an aside, Rohde and Schwarz have a lovely YouTube video on the topic, "Understanding the Radio Data System", which is giving me a whole set of ideas about things we might attempt with amateur radio repeaters, but that's a story for another time. Meanwhile, have you considered…
Not rated yetBald Yak 16: How do you decode FM?
· 6 min
Foundations of Amateur Radio How do you make a hole? That's a pretty straightforward kind of question, and by the time this sentence is finished, there's going to be at least as many answers as people who considered it. I didn't supply any parameters to this hole, so answers could include shovels, collapsing space, fire, a drill, or any number of other interesting approaches. If I narrowed it down to, say, a hole in wood, there'd still be plenty of options. Specifying the type of wood, the diameter and other parameters would further narrow down the selection of methods. What if I asked you: "How do you decode FM?" You might wonder if there's more than one way and I can assure you, just like with making a hole, there's plenty of ways to go about achieving this, even if I limit this to software implementations only. I must confess, when I recently set out to test my Soapy SDR library notions using a GNU Radio flowgraph to listen to FM radio, I searched the documentation, found a beginners tutorial and used the information there to make my first proof of concept FM receiver. I put it on GitHub and went about my business. After finally managing to hear the decode effort and being less than impressed, I started trying to understand the tutorial flowgraph. When I started looking at what would be needed to decode stereo FM broadcast radio, I discovered that there were several tutorials, examples and videos with slightly, or significantly different solutions to the problem. That's on top of the over a dozen standard FM related blocks supplied within GNU Radio. I then set about trying to discover the canonical implementation of an FM receiver and came up short. Instead I discovered even more implementations of FM receivers, each subtly different. You should know that there's a difference between how your local hit radio station does FM and how an amateur radio repeater does FM, let alone the local CB radio channels, satellite telemetry, wireless microphones or even hearing aids, so within the implementation of an FM receiver, there's additional complexity, which explains to some extent the variety of FM related blocks within GNU Radio. I think ultimately it's safe to say that there's an unlimited supply of implementations of an FM receiver within GNU Radio. It led me to ask, what is the .. for want of a better word .. "right" way and what does that actually mean? In GNU Radio, you string together blocks that process a signal. If you're familiar with flowcharts, the process is very similar. Unlike flowcharts on a piece of paper, in GNU Radio, or should I say, GNU Radio Companion, the tool you use to actually design flowgraphs, the little blocks represent underlying software and their connections represent how data flows between these bits of software. In other words, each block represents a series of programming instructions that process data and pass it on. It means that the more blocks you have in your flowgraph, the more instructions are running to process data. The more instructions, the more computing resources required. This is significant because in a complex system like this, we're likely to be doing more than one thing at a time, so preserving resources is important, if only to ensure that there's time available to process the next sample. As a result, there's a difference between implementing an FM receiver with two blocks, or with ten blocks. You might conclude that two blocks is more efficient, but that might not be true. For example, two blocks processing 2,000 samples per second each, are processing 4,000 samples per second in total. A block that converts the 2,000 samples into 200 samples, followed by nine blocks processing 200 samples per second each, is processing 3,800 samples in total. All things being equal, the ten blocks together are handling less data per second, so overall it's potentially using less resources. I say potentially, because it might be that one of those blocks is using a massive…
Not rated yetOne step forward ... three steps back.
· 5 min
Foundations of Amateur Radio Still excited from my minor victory in discovering a missing puzzle piece associated with the project I'm working on, I spent the past week introducing my head, if not literally, at least figuratively, to the surface of my desk in a traditional head-desk troubleshooting move that you might be familiar with. I suppose it's an improvement on the "Bear with a Toothache" approach. In short, the Yak is losing hair .. rapidly. You might be wondering why I'm telling you about it, since in the land of milk and honey nothing ever goes wrong and all the answers are presented on a silver platter, except when they're not. Within the amateur radio community, it appears to me that the inclination to fiddle is ingrained and widespread. Given that the hobby is all about experimentation and learning, that's not a bad thing, but there are times when this behaviour can be counterproductive. Specifically when you're troubleshooting. Faced with a problem, there are times when a systematic approach is warranted. For some, the first time they come across this phenomenon is during the practical test component of their amateur radio license. Presented with a station, they're asked to determine why it's not working. The problem might be a power supply that isn't plugged in, or a disconnected antenna, the mode button set to FM, the squelch closed, the RF gain set to zero, generally something simple. Those inexperienced in the art of troubleshooting are more likely than not inclined to try everything, sometimes all at once, in the hope that one of the changes will magically fix the issue, but in reality, often making the problem worse. There is a better way. I'm mentioning this because this skill applies to many aspects of life and in the decades that I've been here, it's not something I was ever taught. It's funny to think that a quote from nearly a century ago applies to this skill: "When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth." The salient point being "eliminating all which is impossible". In other words, you're not finding the problem, you're eliminating all the things that are not the problem. Another way is to think of it as finding all the things that don't need fixing. While that might sound weird, in deeply interdependent systems like an amateur radio station, or a computer, that approach can help you find the root cause of an issue and with it the path to a potential fix. Of course, this process invites you to examine where the issue might exist. Experience will teach you that you need to start small and grow the net, rather than cast wide and narrow it down. That's not to say that you need to stop paying attention to the bigger picture. In the example of an inoperative station, you might discover that the lights in the room are out and that this coincides with the radio being off. In other words, trying to discover if the antenna is disconnected makes little sense, since there is no power to the radio. In my case, I'm balancing my efforts between maintaining an existing system whilst attempting to deploy a new one to replace it. I'm working on several related issues on multiple fronts. Their common theme is audio, though the specifics differ depending on which computer I'm looking at. Then there's the installation and ongoing care and maintenance associated with keeping GNU Radio running. It's a balancing act because while this is happening, I still need to look for work, respond to email, deal with the regulatory requirements for accounting and tax returns, not to mention the myriad projects I have going on at any given time. At this point I could go into deep and disturbing detail about the technology issues I'm juggling and I could even justify it by pointing out that a problem shared is a problem halved, but truth be told, I'm not sure you're up for a treatise on the comings and goings of forced system security updates and…
Not rated yetBald Yak 15, Playing with Radio .. now with software
· 6 min
Foundations of Amateur Radio A little while ago I discussed a lovely article by programmer, artist, and game designer "blinry" called "Fifty Things you can do with a Software Defined Radio". This week it occurred to me that I could use their article as a framework to further explore my Bald Yak project. If you're unfamiliar, the Bald Yak project aims to create a modular, bidirectional and distributed signal processing and control system that leverages GNU Radio. For that to happen, I need a solid understanding of GNU Radio and its ecosystem. While I've been playing with it off and on for a decade or so, I have yet to build anything substantial for the simple reason that there was a puzzle piece missing. Last week I discovered it .. by accident. One of the fundamental things I'm attempting to achieve is the creation of a system that doesn't care which radio device you're using. In case you're wondering, I'm doing this because there is a proliferation of device specific software that cannot keep up with the influx of new hardware, doesn't consider the growing use of network connected radios, forced by increased RF noise levels in many communities across the world, not to mention, connecting increasingly expensive computing hardware to lightning rods. If everything goes to plan, it should be possible to use the project with any radio device. This is easier said than done. In GNU Radio this complex issue is addressed by having different blocks that represent different devices. You'll find receiver specific source blocks and equivalent sink blocks representing transmitters. While that's all fine and usable, it means that if I were to publish, say an FM receiver flowgraph, essentially a collection of blocks representing software that implements an FM receiver, I have to decide how I want to deal with the specific device. Do I select an RTL-SDR dongle as the device in my flowgraph and let you figure out how to make it work on the HackRF or the PlutoSDR sitting in your shack, or do I make it completely hardware agnostic, requiring you to wire it all together for your specific situation? Neither is desirable, or simple. Added to this is the problem that trying to make this work using a traditional analogue radio would cause more issues, since there isn't a Yaesu FT-857d block, nor is there one for an Icom IC-7400, let alone something from last century. Someone with some GNU Radio experience might point out that there are source and sink blocks for an audio device, which would allow you to plug one of those radios into a sound card and access the receiver, or transmitter, that way. While that would work, it requires that the radio is physically connected to a computer that's running GNU Radio. It would also give you all manner of headaches attempting to change frequency in the same way as you could using an RTL-SDR dongle. There are several ways to get remote radio control working across a network. For example, using 'rigctld' and 'Hamlib', we can change frequency on over 300 analogue radios, but even if you do, you'll discover that getting the audio across the network creates a whole range of new issues, not to mention that GNU Radio doesn't talk to Hamlib compatible radios. This is why many remote radio solutions are implemented as remote desktop sessions to a computer that is physically connected to the radio. While attempting to solve a completely unrelated challenge last week, I came across 'SoapySDR', described as a vendor and platform neutral SDR support library. Essentially it's a project that allows an application to interact with different devices without needing to support individual radios. This allows an application developer to write their software to support SoapySDR and from then on benefit from its ability to talk to lots of radios in a variety of different ways. For example, one of the in-built features is called 'SoapyRemote' which allows you to connect to a SoapySDR radio and interact with it across a…
Not rated yetHow to go about documenting your setup?
· 5 min
Foundations of Amateur Radio How to go about documenting your setup? Possibly the single most important thing that separates science from "fiddling around" is documentation. Figuring out how to document things is often non-trivial and me telling you that "unless you wrote it down, it didn't happen" only goes so far. If documentation isn't your thing, what about "I broke something and I don't know how it was before I fiddled" as an incentive instead? Recently I had cause to explore how to document how my station is configured. To give you a sense, the microphone is connected to a remote-rig, which is connected to a Wi-Fi base station, over Wi-Fi to a Wi-Fi slave, to another remote-rig, to the radio body, to the VHF port, through two coax switches, a run of RG213, to an antenna. When receiving, it goes from the antenna, to a run of RG213, through two coax switches, to the VHF port, to the radio body, to a remote-rig, to a Wi-Fi slave, to a Wi-Fi base station to a remote-rig, to the remote head, to a set of headphones. Of course, at this point I've written it down, so, job done .. right? Well, what about the data connection, the external speaker, the remote head display and other goodies, say nothing of the duplicate devices with similar names. All in all, the FT-857d has something like eleven ports, each remote-rig has ten, so just wording it is a start, but hardly qualifies as documented. What if we drew a picture instead? At this point you could pull out your crayons and start scribbling on a sheet of butcher's paper and that would be a fine start, but it would be difficult to share with me or anyone else and updating it would be a challenge, let alone versioning it. As it happens, we're not the first people to have this issue. In the 1980's and 1990's researchers at Bell Labs were trying to figure out how to draw graphs and from that work a language, 'DOT', since everyone is a fan of the "DAG Of Tomorrow", and a series of tools, which today are known as 'Graphviz', made the visualisation of relationships possible without the application of coloured wax on dried cellulose fibre. In my other, computing job, I had cause to visualise the relationship between a million or so nodes, allowing me to discover a specific node that was directing all traffic, where I could insert my debugging code, but it was only possible thanks to these free and open source tools. While the DOT language isn't particularly complex, it occurred to me that for someone not conversant with the syntax, we can start even simpler with a CSV text file that shows the relationships between each device and convert the CSV to DOT and in turn to a picture. For example, I documented the relationship between the radio and the antenna by adding five lines to a CSV file, essentially, FT857d to VHF port to VHF coax switch to VHF grounding switch to RG213 to antenna. In all, to document everything except power, since I haven't decided how I want to describe it, I used a CSV with 47 lines. On the face of it, that might sound ridiculous, but I can tell you, it shows all the sockets on the FT857d, all the sockets on both remote-rig devices and the relationships between them. With it anyone can duplicate my set-up. Having previously spent some quality time learning various aspects of the DOT language, I figured I could write a little script to convert CSV files to DOT, but being of the generation of software developers with the attitude, "Why write something if someone else already did?", I discovered that Reinier Post at the Eindhoven University of Technology has a delightful collection of scripts, including one appropriately named 'csv2dot'. Written in Perl, the only language that according to some looks just as impenetrable before and after encryption, the tool works as advertised and makes a DOT file that you can then visualise using Graphviz. Of course there's Python scripts lying around that claim to do the same, but I wasn't keen to install the kitchen…
Not rated yet