Episodios

  • How small is small?
    Sep 6 2025
    Foundations of Amateur Radio I've owned a Yaesu FT-857d radio since becoming an amateur and at the time I was absolutely blown away by how much radio fits inside the box. It's smaller than most of the commercial radios I'd seen when I bought it. I came across a video by Michael KB9VBR, the other day showcasing a wooden cigar box with a complete, well, almost complete POTA, or Parks On The Air, activation kit. I say almost, since Dave KZ9V, the owner of the kit, points out that the box doesn't contain an antenna. It made me wonder how small is small? According to RigPix, the lightest transmitter on an amateur band, in this case, the 5 GHz or 5cm band, is an Amateur TV transmitter. Weighing in at 3.9 grams. The Eachine TX-06 is capable of FM with about 18 MHz of bandwidth with an audio sub-carrier. Of course, that's not a transceiver, but I thought it worth mentioning in case you needed an excuse for something tiny in your shack, besides, as far as I can tell, there's never too much Amateur TV in the world. I've built a crystal radio on a breadboard which is tiny, but it doesn't transmit, so to set the stage, I think we need to limit ourselves to transceivers, that is, a device capable of both transmitting and receiving, on amateur bands. Before continuing I'd like to express my thanks to Janne SM0OFV, for the rigpix.com database that he's been maintaining, in notepad, since 2000. Without the invaluable information documented for the currently 7,512 radios, I'd be spending an awful lot of time hunting for information. Moving on, the FaradayRF board is a transceiver, capable of using 900 MHz or the 33cm band. It comes in at 30 grams, but without a computer it's a circuit board with potential. The PicoAPRS by Taner DB1NTO, is a 2m transceiver specifically for APRS, weighs in at 52 grams and similar in look and a third of the weight of an Ericsson T18 mobile phone. Speaking of mobile phones, the PicoAPRS does WiFi and Bluetooth, can pair with your phone and act as an AX.25 modem. I'll confess, I'm drooling. Moving right along, for 70cm there's a Rubicson Walk 'n' talk, weighs in at 65 grams. Mind you, the RigPix database puts this under the "License-free / PMR446" section which comes with a sage warning, check your local laws before transmitting. There's a few Alinco DJ-C models for different markets that operate on 2m or 70cm, weighing in at 75 grams. The ADALM Pluto weighs 114 grams, but you'll need a USB power supply of some sort to make it do anything. It can operate between 70 MHz and 6 GHz, but the user interface is limited to a single button and LED, so if you want to interact with it, you'll need some external technology. Moving on to HF transceivers, weighing in at 199 grams, without the bag, but all the options, is the Elecraft KH1. Transmits on 40m, 30m, 20m, 17m and 15m and receives between 6 and 22 MHz. It's CW only, but you can receive SSB. If CW isn't your thing, RTTY and PSK can be used on the 40m band with a Silent System Handy PSK 40. Presumably the Handy PSK 20 runs on 20m. Both weigh in at 250 grams. The Zettl P-20xx SSB does SSB, AM, FM and CW, transmits on 10m, 11m, 12m and 15m as well as the MARS frequencies and receives between 14 and 30 MHz, weighs 300 grams. Even comes with CTCSS. Another Elecraft model, the KX2 weighs in at 370 grams, does 80m to 10m and the WARC bands, does SSB, CW and data. Mind you, you'll also need to add the weight for the microphone and paddles, and factor in a computer if you want to do more than PSK and RTTY. The Expert Electronics SunSDR2 QRP does 160m to 10m, the WARC bands and 6m. Weighs in at 500 grams, has a network port and two independent receivers. Operates at 5 Watts. There's no user interface, unless you count the reset and power buttons, so I'm not sure if it can operate on any mode with just a microphone, but given the "Depending on software" disclaimers throughout, I'm going to guess you'll need to bring a computer to make it sing. The Risen RS-918SSB does all HF amateur bands between 160m and 10m, has a user interface and display, even a big tuning knob, has built-in FreeDV and does FM, SSB and CW. I'd hazard a guess that this is the lightest self-contained transceiver that you can take out on a POTA mission to a park. Weighs 623 grams and comes with an internal battery. The Elecraft KX3 also does 160m to 10m, and 6m, with a 2m option. Weighs in at 680 grams, but that doesn't include any options. And finally, we pass 1 kilogram and hit 1,100 grams and discover a radio that does all bands and modes, the Icom IC-705 with a battery, but no antenna. The Yaesu FT-817, FT-817dn and FT-818 weigh 70 grams more, but that weight includes both a battery and antenna. Of course there are other options. For example, there's the (tr)uSDX by Manuel DL2MAN, and Guido PE1NNZ, does 80m, 60m, 40m, 30m and 20m, CW, SSB, AM and FM. Comes in a kit, weighs 140 grams. It's not on RigPix, so I only know about it because it was mentioned by Dave ...
    Más Menos
    8 m
  • Bald Yak 12, getting raw data from a remote receiver
    Aug 30 2025
    Foundations of Amateur Radio

    Over the past nine months or so I've been working on a project that I've called Bald Yak. 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.

    One of the, admittedly many, challenges I've set myself is getting data from a radio receiver into GNU Radio across the network, preferably the Internet. Today I can report a small step in the right direction and frankly I can't contain my excitement.

    Now, I need to acknowledge that I'm geeking out here. It's hard to contain excitement when you find something that seems to speak your language. It also means that I realise that I run the very real risk that I'm going to lose you before you get to why this is a milestone, so let's put that up front before I explain why.

    To whet your appetite, yes, you can access a KiwiSDR across the Internet and record raw data from it and control the process externally. This is a very big chunk of the problem I've been working on and turns out to actually be live and ready to play with.

    Fair warning this is technical, there are moving parts. I'll do my best to explain, but if I miss any, feel free to get in touch, you have my address, cq@vk6flab.com.

    In passing, recently I made mention of the KiwiSDR community and tools that could potentially allow access to a remote receiver, although at the time I pointed out that I wasn't sure if the tools I found could access remote receivers, or if they were intended to access hardware locally.

    KiwiSDR is one of a group of so-called Web SDR tools. Essentially a website where you can access a remote receiver and tune to the radio signals it can hear. SDR, or software defined radio, is a way to convert incoming antenna signals into the digital realm where computers, and in this case, the Internet, live.

    Turns out that a tool called "KiwiClient" takes a hostname and a port as a parameter, so much so that the in-built help shows this as the first example. What this means is that you can essentially run a copy of KiwiClient on your own computer and use it to access a KiwiSDR across the Internet.

    The first commit was on the 8th of May 2017 and thanks to the efforts of about 14 developers, KiwiClient is the software equivalent of a KiwiSDR multi-tool. This is exciting all by itself, but this gets better.

    You can specify more than one server. This means that you can record two, or more, signals from across the globe, and capture these simultaneously.

    You can set the decode mode, which I immediately used to tune to a local broadcast station and recorded it from two different receivers across the Internet, allowing me to not only compare the difference in delay between the signals, but also the reception differences. It's fascinating to hear the same station from two receivers, one in each ear, all manner of different propagation artefacts become apparent.

    Then I got a little more adventurous and discovered that one of the supported modes is I/Q, which means that I can, and did, download raw sample data across the network, which can then be used within GNU Radio. This is important because the aim for Bald Yak is to process the signals separately from the receiver.

    It gets better.

    There is a radio fax receiver that automatically saves pages as they are processed, something that you could use to access weather fax services.

    Then there's a tool you can link to "WSJT-X", which you might recall is an application that can decode weak signals. Not only that, the tool supports "fldigi", a digital radio mode application. Both those applications can control the radio using Hamlib rigctl, which means that KiwiClient supports changing frequencies of the receiver, across the Internet, though truth be told, I haven't yet tested that .. my available computing resources are still strictly limited.

    Oh, the software also has the ability to record waterfalls, do scanning, and provides tools to analyse waterfalls in jupyter notebooks.

    Getting this to work wasn't too hard. The instructions on the KiwiClient GitHub repository are pretty good. I've made an initial Dockerfile on my own GitHub repository to download and install the software. It's unimaginatively called "kiwiclient-on-docker". I've yet to discover a good way to add or update Dockerfile functionality to existing projects, feel free to make suggestions.

    Now I absolutely understand that this level of excitement might not universally translate and that's fine. It's yet another example of how rich and diverse our amateur radio community really is.

    What gets your excitement levels going?

    I'm Onno VK6FLAB

    Más Menos
    5 m
  • Using an SDR as measuring equipment
    Aug 23 2025
    Foundations of Amateur Radio

    The other day I stumbled on a random post by Gary N8DMT which caused me to view the world in a different way. The post outlined combining a PlutoSDR and an application called SATSAGEN to measure the frequency characteristics of a coupler.

    Aside from a detailed description, the post includes a couple of excellent photos showing the PlutoSDR connected to the coupler and the output piped back into the Pluto.

    Before I continue, a PlutoSDR is a Software Defined Radio or SDR, officially it's called the ADALM Pluto Software Defined Radio Active Learning Module. It's essentially a full-duplex radio and computer in a box. It runs Linux and connects to the world via USB, and of course radio, unofficially between 70 MHz and 6 GHz. I've talked about this device before. When I say full-duplex, I mean that it can transmit and receive at the same time.

    Gary's post triggered something unexpected in me. The notion that you could use two patch leads, one connected to the transmitter, the other connected to the receiver, joined together by a device that you might want to test.

    It immediately reminded me of another device that was given to me, a NanoVNA, a device that's specifically designed to measure things like impedance, frequency response, generate Smith charts and all manner of other characteristics.

    Not only that, it also reminded me of another device, a TinySA, specifically designed to analyse spectrum and to generate signals.

    Both the NanoVNA and TinySA are lovely tools, but in looking at the post it suddenly occurred to me that their functionality, at least superficially, appears to mirror the PlutoSDR, in that you can create a signal and then measure that signal.

    Turns out that I'm not the first to make this observation. For example, the YouTube channel "From Concept To Circuit" goes through the process of describing precisely the concepts behind both a spectrum analyser and a network analyser while showing the programming code in Python. The channel also provides that code in a GitHub repository, which includes several other very interesting examples, like a beamforming transmitter as well as a beamforming receiver, also covered on YouTube.

    Another example is a tool I already mentioned, SATSAGEN, by Alberto IU1KVL, which implements a wideband spectrum analyser. Although it's Windows only, Alberto includes information on how to run it using Wine under Linux and MacOS. As a bonus, SATSAGEN in addition to the PlutoSDR, also supports RTL-SDR dongles, HackRF, USRP, RSP1, AirSpy, and many others.

    If text is more your thing, "retrogram-plutosdr", shows a spectrogram in your terminal window. Check out the "r4d10n" GitHub repository belonging to Rakesh VU3RGP, who says that the "retrogram" project is "hacked from" the "RX ASCII Art DFT" example, which you can find on the Ettus Research GitHub repository.

    One thing to consider is that the various GitHub repositories I've pointed at, will give you access to the moving parts of how all this works.

    I will mention that my favourite tool in this space continues to be GNU Radio, but I understand that you might not want to roll your own tool from parts. That said, rolling your own is in my experience a great way to discover precisely what you don't know and to come away learning more, but then, that's just me.

    Regardless of your chosen tool, I think the takeaway should be that when you try something new, even if it's only new to you, the idea of writing down what you discovered and sharing it, is a fantastic way to grow our community. Remember, just because something is old hat to you, doesn't mean that it is to the person you share it with.

    Besides, based on the current global birth rate, there's at least a thousand babies born during the past four minutes, some of whom will become radio amateurs, so, share.

    Said differently, if you come across a person who has never heard of the "Diet Coke and Mentos" thing, it's your job to immediately drag them to the nearest grocery store and introduce them. In case you're wondering, xkcd 1053.

    Now, I'm going to update the firmware on my PlutoSDR and have a play, I already know about the Mentos, but if you don't, you're in for a treat.

    What are you going to do next?

    I'm Onno VK6FLAB

    Más Menos
    5 m
  • Listening to local RF via a web browser
    Aug 16 2025
    Foundations of Amateur Radio

    Recently I discussed the idea of listening to the radio spectrum across the internet for the purposes of getting signal into your shack when radios, or in my case, antennas are causing you challenges.

    I continued to explore and discovered a project by Jacobo EA1ITI, called "radioreceiver". Behind that unassuming name lies a tool born in 2014, that allows you to plug an RTL-SDR dongle into your computer, open up your web-browser, and listen to the radio signals that your dongle can receive.

    In case you're unfamiliar, an RTL-SDR dongle is a small USB device, looks a lot like a USB thumb drive, jump drive, data stick or flash drive, basically a hunk of plastic with a USB connector on it. An RTL-SDR dongle generally also has some form of antenna connector. It's typically sold as a digital radio and digital television receiver, but websites like rtl-sdr.com sell purpose built ones. They can be found starting at about $15.

    I realise that this is using a local receiver, with a local antenna, but it's inside a web browser, which is half of what I expected. When you hit the play button in the bottom of the screen, you'll be prompted by your web browser to give permission to access your RTL-SDR dongle and the fun starts. You'll see a live waterfall, hear audio, and have the ability to tune to any frequency you can reach. Depending on your dongle, typically somewhere between 500 kHz and 1.76 GHz.

    The application consists of seven files, a total of 352 kilobytes that you can store on any web server and run, with one caveat, in order for your web browser to talk to your dongle, it needs to be served using HTTPS. Jacobo has set-up radio.ea1iti.es and I've set-up sdr.vk6flab.com, both showing the same tool. You'll find the code on my VK6FLAB GitHub repository, and of course on Jacobo's.

    There are some things you need to know. You will need to use a web browser that supports WebUSB, currently that's Chrome, Edge, Opera and several others, sorry, Safari and Firefox don't .. perhaps it's time to talk to Apple and Mozilla. All is explained if you click on the little question mark at the bottom of the screen, it will even tell you if the browser you're using to read the help is compatible or not.

    If you have an Android phone, you can run this tool too, although you will need to find a way to connect your dongle to your phone. I'm currently limited in my ability to test this and you may need to install some drivers on Windows and Linux, but MacOS and presumably Android, works out of the box. The software also supports offline operation, so you can load it as a Progressive Web App, or PWA, and use it in the field away from the internet.

    Did I mention that all the decoding is happening inside the web browser, so you can see which code is doing what .. and before you ask, yes, it's minimised in the browser, which you can make into human readable code, but when you look at the source, it shows precisely what is happening, all written in Node.js, TypeScript and JavaScript.

    It supports CW, SSB, AM, Narrow and Wideband FM and decodes stereo, something which none of my amateur radios do.

    You might be able to tell that I'm excited. It's because this is providing the basic functionality of a radio inside a web browser, and I didn't need to install it to get started. On the Macintosh I tested this on, I literally opened the web page, plugged in a dongle and hit play. Just so we're clear, just because this is using a web page on a web server, you accessing it will only give you access to your radio not mine.

    This of course opens the doors to all manner of other fun stuff which I'm expecting to play with for the next little while, and yes, this is also Bald Yak adjacent, I'm aware.

    In the meantime, you can play with this right now, sdr.vk6flab.com is the place to go. Word of warning, it's addictive and easy to forget it's a radio with an antenna plugged into your computer, so take precautions when electrical storms are about.

    Look forward to hearing what you discover.

    I'm Onno VK6FLAB

    Más Menos
    5 m
  • Decoding distant signals over the web?
    Aug 9 2025
    Foundations of Amateur Radio One of the many challenges associated with being a radio amateur is actually being able to listen to weak signals. If you're like me and more than half the planet, you live in an urban area, which comes with the benefits and pitfalls of having neighbours. From a radio perspective, there's plenty of noise that drowns out weak signals, so more and more amateurs are finding new and interesting ways to deal with this. Over the years I've talked plenty about so-called web-sdr, or internet accessible software defined radios. Essentially a radio receiver, preferably in a radio quiet area, hooked up to some software that allows you to listen in using a web browser. There's thousands of internet based services across the globe, the most popular of those are websdr.org and kiwisdr.com. As a new amateur you might have visited one or more of these and tuned around to listen to various radio stations and QSOs or contacts between amateurs, on bands that you can't access because you don't have the gear, or frequencies that are drowned out locally by your neighbour's pool pump, air conditioner, LED lighting, solar power inverter, television, motor home, cycle, or whatever else they seem to have an endless supply of behind closed doors. As a crusty amateur, and after about 15 years, I'm probably one of those, you might have started experimenting with building your own, or you might be blissfully unaware of these internet marvels. Either way, one restriction you run into is the ability to do anything other than listen. You might get the option to pick between Upper and Lower Side Band, or AM, sometimes even FM, but generally that's your lot. This means that trying to use such a tool to decode WSPR, or FT8, or RTTY, CW, PSK31, or whatever else takes your fancy becomes a challenge. It occurred to me that if you're able to capture the raw signal from a web browser, you could feed that into your decoder of choice. It would also mean that you wouldn't need any local hardware to start playing. Before you get all hot and bothered like I did. This is a non-trivial process that several others have attempted to wade through with varying levels of success. Much of the documentation I've discovered revolves around virtual audio cables and loop back software, and even the idea that you physically plug your computer's speaker output into your line input, or even hold a microphone up to your speakers. Aside from the lack of elegance associated with such contraptions, they require that you install all manner of weird software, and in many cases deal with permissions, since microphones are generally locked for good privacy reasons. Prompted by the webserial tool by Phil VK7JJ, it occurred to me that if we can talk to actual physical hardware within a web browser, then we can probably use a web browser as an audio source for local decoding software. Before you start hunting for the source code, there is none. I've spent the past few days playing around and although I made a waterfall display inside GNU Radio that used the audio from websdr.org, the results were not amazing, and I created a proof of concept by using a tool called BlackHole on the Macintosh I was using at the time. It's essentially doing shenanigans with audio mapping, not something which I really want to do, but it gives me a pretty picture, or not, as the case may be. More interesting is the progress being made over in the KiwiSDR community, where there is already an I/Q button, in other words, the raw data needed for processing further down the line. I came across projects that link the KiwiSDR to other tools, but it's unclear if that's the hardware, or the web client, I suspect it's the hardware, but I might be mistaken. If you're not sure what this might mean, think about listening to the same frequency at the same time across the globe using multiple web browser tabs, and comparing the signals in real time, or decoding them, or using them for comparing signal strengths, or propagation, or any number of things that are currently only possible with a vast network of radios under your own control. If you need to nerd out on the technicalities, the idea is that if you can access an SDR via a web browser, it would be cool if we could decode the stream coming back without needing to install software on the computer. There appear to be tools that do this kind of thing to get the audio into "ffmpeg". If that's gobbledegook to you, ffmpeg is a tool that allows you to do all kinds of cool stuff with audio and video. Using something called WASM, or webassembly, it's possible to link web browser audio to ffmpeg. I suspect it's possible to use the same mechanism to send audio to GNU Radio, or any other decoder, for processing. There also appears to be a thing called a Web Audio API AudioBuffer where the raw audio gets sent to, so perhaps that's accessible in some way. The point being, that I think this is doable, so much so, that I ...
    Más Menos
    6 m
  • What can we activate today?
    Aug 2 2025
    Foundations of Amateur Radio

    Every single radio amateur has come to this hobby with an itch to scratch. Time and again I've seen amateurs around me pursue that particular purpose, only to come out the other end with a look of bewilderment writ large across their face. For some amateurs it means the end of their involvement in the hobby, for others it starts a new journey into the unknown.

    One of the ways we explore our community is by travelling out of our shack into the big outdoors in whatever form that takes. Popular activities include setting up a radio in a location and talking to others, known colloquially as an "activation". We do this all over the planet. Perhaps the most recognisable of these is IOTA, or Islands On The Air, where a station is erected on an island and contacts are made. As amateurs we cannot help ourselves and seem to have an insatiable need to measure our prowess. We do this by counting how many contacts, callsigns, countries, grid-squares, or in this case, islands, we've managed to put in the log.

    If an island represents a new callsign, a new country, and a new grid-square, the contact making will turn into a feeding frenzy that can last for days, especially if the station offers multiple bands and modes, making the effort all the more tempting.

    We don't stop with islands. Summits, with Summits On The Air or SOTA are popular, as are Parks, POTA, and even over a weekend, the International Lighthouse and Lightship Weekend, or ILLW.

    Some of these activations follow rules set out by amateurs like you and I, who thought it would be fun to track such activations and encourage others to participate. For example IOTA World publishes a four page document outlining what's required for those on the island, activators, and those trying to make contact, or chasers. This raises an important point. Rules require documentation, which leads to discussion and disagreement, and versions. I can show you two versions of the IOTA World rules, neither is dated, of course both are different, so if you're going to publish rules, make sure you add a date or version, preferably both, to the rules document.

    Disagreements aside, sometimes there are multiple programs with the same name or aims. Two groups came up with the same idea and didn't know about each other, or, a group in a different country wanted to run the show in a different way and a new group was formed.

    I'm mentioning this because sometimes these groups are antagonistic towards each other and have forgotten that the whole point of this is to have fun.

    So, what else can we activate?

    Well, there's Castles and Stately Homes, Bunkers, Beaches, Museums, Walmart Parking Lots and even Toilets On The Air, mind you, Slow Scan Television, or SSTV is discouraged as a mode.

    The other day the power was off for maintenance in my street and I planned on escaping to the local library, which caused me to search for libraries across Perth. It seems there's pretty much one in every suburb and I considered the notion of activating a library or three, comes with easy access to public transport, a car park, and even toilet facilities, what's not to like? I wondered what might be a suitable exchange so it could incorporate the library itself, promoting amateur radio and libraries, two birds and all.

    I made a comment on mastodon.radio and it turns out that Frank K4FMH beat me to it, several years ago. Libraries On The Air, or LiOTA. I've been hunting for a dataset of libraries in Australia to give to Frank, but it's been slim pickings, despite there being over 10,000 of them, apparently around 10% of those public.

    It raises another question, is there a directory of activation types anywhere? I couldn't find one, so I started a list on my GitHub repository. Feel free to add any I missed.

    Toilet jokes aside, consider that TOTA is being held during the annual Hackers On Planet Earth conference and it will introduce new people to our amateur community, which ultimately might be the best reason to have fun, get on-air and make noise.

    I'm Onno VK6FLAB

    Más Menos
    4 m
  • Using Amateur Bands for other purposes
    Jul 26 2025
    Foundations of Amateur Radio Recently I came across a series of strident posts about the injustice associated with a non-amateur service using the 70cm band. Complete with links to discussions, spectrum plots, angst and even incoherent outrage, all related to the notion that whomever "allowed" this user to transmit on this band was clearly incompetent. Except, that this is probably not the case, or the full story. So, what's going on and why are people incensed? This all started at least six years ago. Since then AST SpaceMobile has deployed seven low Earth orbit satellites and used the 70cm band to communicate with them. Although in the trial phase, there's plans for an additional 243 satellites, and there's at least one other company playing in the same space, Atmos Space Cargo. The outcry from amateurs is around the commercial use of "their" 70cm amateur band. It's an emotional statement, but what is the reality? Before I dig in, let's set some terms. Radio frequencies are globally coordinated because electromagnetism doesn't care about sovereign borders. This coordination is conducted at the United Nations by a body called the ITU, the International Telecommunications Union. Within that body, amateur radio gets a seat at the table from an organisation called the IARU, the International Amateur Radio Union. For the purposes of the ITU, the world is divided into three, Region 1, or essentially Europe, Russia and Africa, Region 2, the Americas and Greenland, and Region 3, the rest of the world. There's more to it, for example, Antarctica is split across all three, but for the moment, that really doesn't matter. Of interest is that the band plan, the agreements that outline which frequencies are set aside for what service, might be defined differently across each of those three regions. To add complexity, each country can be granted exceptions. I don't know the exact mechanics of how this is achieved, but I can guarantee that there's lots of haggling and foot stomping, diplomatically of course. If you're curious how I come to that observation, just look at the absurd list of exceptions associated with each band plan allocation. Further complexity is added by the fact that not all allocations occupy the same frequency range. For example, in Region 1, the 2m band for Amateurs exists between 144 and 146 MHz, in Region 2 and 3 it's between 144 and 148 MHz. Within an allocation there is the concept of shared and exclusive priorities. These determine who "wins" if two stations with a different service are transmitting on the same frequency. Essentially, a secondary user may not interfere with a primary user and a tertiary user may not interfere with either a secondary or a primary user and so on. A primary user can pretty much do what they want, as long as they stay within the allocation and don't interfere with other primary users. As a result, the order in which services are listed, matters. An exclusive allocation doesn't have to be shared at all. Between regions these service priorities might not be the same. For example, in Region 1 between 430 and 432 MHz is allocated to Amateurs and Radio Location, but in Region 2 and 3 it's between Radio Location and Amateurs. So an amateur using that frequency whilst in Region 1 would be a primary user, but in Region 2 or 3 they wouldn't. As an added wrinkle, for example in Australia, that slice is "primarily for the purposes of defence and national security", even though Radio Location is the primary service and Amateurs the secondary one. As a bonus, amateurs in Australia have access to 420.8 to 421.2 MHz as a secondary service, even though the ITU designates this as Fixed, then Mobile, except Aeronautical Mobile, and then Radio Location. Although amateurs are a secondary service, they come after the Department of Defence who are the primary users for those frequencies in Australia. Between 420 and 430 MHz, and from 440 to 450 MHz in several countries, Australia included, the Amateur Service is explicitly designated as a secondary service even though the band plan doesn't actually show this. If you're confused, you're in good company, since this tapestry of regulation isn't as straightforward as the "70cm band is an amateur band", in fact, I'd go so far as to say that it's not an amateur band at all, except perhaps in Region 1 between 430 and 440 MHz where Amateur is designated as the non-exclusive primary service. Back to the blow up. AST was at one time authorised to use 430 to 440 MHz for trial purposes by a regulator in Region 2, the FCC, the United States Federal Communications Commission. I suspect that at the time, the Blue Walker 1 nano satellite was experimental and the approval made sense. You can argue that whomever initially allowed this made a mistake, but, reality is whatever the regulator says it is, unless someone at the ITU objects. It appears that the FCC has since been attempting to make AST comply, instead with billions of ...
    Más Menos
    11 m
  • There's promotion .. and then there's Amateur Radio
    Jul 19 2025
    Foundations of Amateur Radio In the community of radio amateurs scattered around the planet we have a habit of getting together with others to have fun in whatever shape that takes. The obvious ones are HAMfests, car boot sales, raffles and other amateur adjacent pursuits, but we also do things like licence training, weekly on-air nets, contesting, portable activations, climbing mountains, or hills, setting-up in parks, or lighthouses, we set-up on a field day, just for fun, and find excuses, sorry, reasons, for any number of other activities. Some of these are solitary affairs, but many are best enjoyed shared with multiple friends, both old and new ones. Having been a member of this community since 2010 I've come to observe an aspect of this community that is odd, to say the least. We organise all these events, but rarely promote it beyond a single email to three people, if that. It's almost as-if the average organiser thinks that their event permeates the community by magic osmosis. Even if there is any form of promotion, there's sometimes a date and time, but hardly ever does it show that time in UTC, even if it's a radio event, it's like we've forgotten that radio waves pass through time zones, or there is a misconception that everyone on the planet knows what your local timezone is, let alone if it's summer or winter time at the time of the event. So, what does promoting your event look like if you actually want people to know about it? For starters, you should consider who you want to have as a participant. A local HAMfest is unlikely to attract people from around the globe, but Friedrichshafen and Dayton are examples that contradict that notion. A VHF-only event might be intended for local amateurs, but what if it allows for satellite or digital contacts, like say via Allstar, IRLP or Echolink? Similarly, you might run a weekly on-air net, but have visitors from around the planet. The point being, that your audience might not be exactly what you initially think. In other words, there might be people playing from further afield. Consider that when you announce what time the event starts, and finishes. Speaking of finishing, adding an expected closing time is helpful for participants where only one member of the family lives and breathes amateur radio and the rest just want to get on with their respective lives, so consideration is welcome. Aside from telling your audience when and for how long the event goes, adding a location is not optional. You'd be surprised how many events say things like: "it's again in the usual location", or "we're at the community hall" without ever publishing an address. I can tell you, it's fun discovering that the name of the hall isn't unique. Now, for the big one. After putting the information together about the event itself, where and how do you announce it? For starters, on your own website, in whatever form that takes. It serves two purposes, announcing to the world what is happening, but it's also the definitive place where the right information is published. This is important because things change, get cancelled, moved, updated, whatever. Life isn't static, so you need to define a place where the official announcement lives. At this point I'd like to mention that this is often where promotion stops. It's easy to think that in your universe everyone you know is aware of your website, but that's just not true. A single place to publish is not the end of the process, it's the start. Then you need to use things like the local news broadcast, the national news broadcast, the international news broadcasts, contesting websites and calendars, social media, fediverse and whatever else you can get your hands on. You need to include it in your own club news, in club newsletters from other clubs, on the local amateur notice board, you need to talk about the event on-air, share it during on-air nets and if it's recurring, tell the world that it's going to happen again next year. Nothing here is revolutionary, it's not like launching a rocket into space, this is basic common sense and you too can do this. If you need help, ask. So, if you have an event that you want to have participants for, you need to make noise. Publishing the announcement at the local planning department in Alpha Centauri 50 years before the event is going to cause issues, as will defining the date for an annual event as: When the June solstice is on a weekday (Monday through Friday), the weekend following shall be the weekend of the event. When the June solstice falls on a Saturday or Sunday, that weekend shall be the weekend of the event, but only for the Winter field day, the Summer one requires you to count back four weekends, or forward, depending on if you're talking about the Spring or Summer event, and add one if it falls on the weekend. In case you're wondering. No, I didn't make that up. It's real. I'll leave you to ponder how you'd add such an event to your family calendar. ...
    Más Menos
    6 m