『Foundations of Amateur Radio』のカバーアート

Foundations of Amateur Radio

Foundations of Amateur Radio

著者: Onno (VK6FLAB)
無料で聴く

このコンテンツについて

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?".℗ & © 2015 - 2025 Onno Benschop 物理学 科学
エピソード
  • The ARRL incident of May 2024, a year later
    2025/06/28
    Foundations of Amateur Radio Just over a year ago, the ARRL, the American Radio Relay League, the peak body for amateur radio in the United States and one of the oldest of such organisations, experienced an incident. During the weeks following, the ARRL was tight-lipped about the extent of the incident and most amateurs only really noticed that services were off-line or slow to respond. After months of delay and disinformation, the ARRL finally revealed that it was the subject of a ransomware attack and that it had paid a million dollar ransom. It went on to blame the authorities for its silence. Mind you, it didn't tell me personally, it made public statements on its website. Similarly when I specifically contacted the ARRL to discover what information of mine it held, and what the status of that information was, the ARRL responded that I should refer to its public statements. It continued to state that my information was not compromised, since it only lived in LoTW, the Logbook of The World, the system it uses to coordinate the verification of amateur radio contacts, which are used to distribute awards like the DXCC and Worked All whatever. Imagine my surprise when I received an email this week, sent from "memberlist@arrl.org" to my non-amateur radio email address. I confirmed with several amateurs that they too received this email. Informative, to a point, but likely well beyond anything intended by its author, it stated that LoTW was being updated with associated down time, incidentally, inexplicably, coinciding with the 2025 ARRL Field day, and it "will be fully migrated to the cloud". It went on to solicit donations. It made no reference whatsoever to the ransomware attack. There's a lot hidden in that email. Although the attack last year was linked to the outage associated with LoTW, the ARRL has continued to claim that the LoTW data was not impacted by the ransomware attack, but the email reveals that the system is being migrated to the cloud, in other words, right now, it's not in the cloud. Which begs the question, where is the server infrastructure for LoTW today, and more importantly, where was it a year ago when its systems were compromised? From a public post by Dave AA6YQ, dated the 2nd of February 2021, in response to a message about a January LoTW committee meeting, we know that the LoTW server "now employs the current version of an SAP database engine". A month before that, Dave wrote another informative email that indicated that 105 thousand callsigns submitted logs to LoTW in the last 1,826 days or the five years between 2016 and 2021. There were logs from 21 thousand callsigns in the week prior to that January post. In all, according to Dave, there were 153,246 callsigns who submitted contacts to LoTW. The LoTW committee meeting minutes are no longer available from the ARRL website, but I have a copy. The document states that there were 1.2 billion contacts entered into LoTW, big number right? The next line tells us that this resulted in 262 million QSO records. I wonder what happened to the other billion records? This activity was generated by 139 thousand users using 200 thousand certificates. For context, every VK callsign automatically comes with an AX callsign, but LoTW requires that you separately register each with its own certificate. As someone who has been playing with databases since the 1980's I can tell you that LoTW is a tiny database. For comparison, the WSPR database is an order of magnitude larger, not to mention, more active. I have no insight into the business rules within the LoTW database, but the fact that updates are being processed in batches and that it regularly has delays indicates a level of complexity that I cannot account for. As an aside, the LoTW committee document lists 10 members. Dave is not one of those listed. It makes me wonder who else has access to this database. Note that I have no reason to believe that Dave's information is questionable, nor that he has access that he shouldn't, he was after all a member of the LoTW committee from 2013 until 2017 when the ARRL removed all development resources from the LoTW. I'm asking who else has access and why? While we're here, who has been doing maintenance and updates on this system over the past seven years? Moving on. The database for LoTW contains information from amateurs all over the planet, including those in Europe where the GDPR, the General Data Protection Regulation, enacted in 2016, is extremely strict on the security and disclosure of personal data with very heavy penalties for breaches. The GDPR requires notifications be sent within 72 hours of a breach, and that an organisation must designate a data protection officer. I wonder who has that role at the ARRL and I wonder if they told anyone? Did any European amateurs receive personal notification from the ARRL about their data, I know I didn't. My first activation of LoTW was in 2013, now twelve years ago. I received ...
    続きを読む 一部表示
    12 分
  • The Art of decoding a signal.
    2025/06/21
    Foundations of Amateur Radio

    The other day Randall, VK6WR, encouraged me to get on-air. He described it like this:

    "There is a mystery signal on 40m that you can try your new Universal Radio Hacker skills on. It appears to be a FSK signal separated by 7kHz with the two signals at 7.0615 and 7.0685 MHz. Each of them on their own sounds a bit like a Morse signal, but my CW decoder decodes junk. But if you can see it on a spectrum scope, it is clearly FSK because either one of them is on at any time."

    He went on to say: "You'll need an SDR to receive the signal given the separation, but could be a fun investigation!"

    Having just discovered "Universal Radio Hacker", a tool that can help you decode radio signals, that sounded like something I'd love to have a go at. Unfortunately, after the demise of my main workstation last year, my current set-up doesn't allow me to do such recordings, but Randall, ever the gentleman, provided a recording of the signal.

    He writes: "This was captured with gqrx demodulating the signal as SSB audio with the VFO tuned to 7.060, so both "signals" are there, one very low freq and one very high freq."

    If you're curious, I've uploaded the file as it was shared with me to my VK6FLAB GitHub repository under "signals".

    Over the next two days I spent my time attempting to decode this signal. I opened up Universal Radio Hacker and spent delightful hours getting precisely .. nowhere. Some of that is absolutely my unfamiliarity with the tool, but this is a great exercise in learning on the fly, where truth be told, I tend to live most of my life.

    It wasn't until several hours later that I decided I should at least listen to the audio. To my ear it sounded like 25 WPM Morse Code, but being still in the learning phases, while my brain was triggering on the sequences, decoding wasn't happening. Of course I could cheat and forward the audio to one of my fellow amateurs, but the actual message wasn't really the point of the exercise, at least not at this stage.

    Instead I fired up "multimon-ng" which has an in-built Morse decoder. I spent some hours doing more Yak Shaving than I was expecting, but even then, I still didn't get more than gobbledegook out of the process. I used "Audacity" to shift one of the signals by one wavelength and mixed them together. This allowed me to reduce the noise significantly, but still none of my tools did anything useful. In case you're wondering why, if you have a tone and noise and shift one signal by the wavelength of the tone, then mix them, the tone adds to itself, but the noise, random in nature, is just as likely to add as it is to subtract, so in effect, you're increased the signal to noise ratio.

    After multimon-ng failed, I tried an online Morse decoder, which gave me all manner of text, but none of it made sense to me. Of course it's possible that this is someone rag chewing in a different language, but I couldn't make any sense of the thing.

    I did come up with some issues that prompted me to create the signal repository. I realised that I didn't have any known "good" signals. Previously I'd tried decoding a sample FT4 signal, but that went nowhere, mainly because the signal was noisy.

    So, what I'm going to do over the next couple of weeks is create some clean, as-in, computer generated, known signals, and add them to the repository. The aim is to have a known good starting point to learn from. In software development this technique is often used to limit the number of unconstrained variables. In our case, if I generate a known good Morse Code signal, then I can learn how to use Universal Radio Hacker to decode it, so when I come across an unknown signal, I can use the techniques I learnt to attempt to decode it.

    Feel free to make pull requests with known good signals yourself. RTTY, PSK31, WSPR, FT8, etc. Feel free to include non-amateur modes.

    One thing, I'm not looking for off-air recordings of signals, yet, that can come later, right now I need signals that are pure, as-in, as I said, computer generated. Of course at some point, perhaps sooner rather than later, I'll discover that generated signals are no easier to decode than off-air recordings, but that's for another day.

    Meanwhile, you too can play. Download one or more sample files and decode them. Let me know what you learn.

    I'm Onno VK6FLAB

    続きを読む 一部表示
    5 分
  • Random Serendipity
    2025/06/14
    Foundations of Amateur Radio

    The other day I was discussing with a fellow amateur the increased frustration my mobile phone provider was inflicting. We hit on the idea of figuring out if other providers would fit the bill and how we could determine if their coverage would suit our needs. Aside from using an old mobile phone, I suggested that using a $25 RTL-SDR dongle would provide a way to record mobile phone cell site beacons from the various mobile networks to map what signal levels we might find.

    To that end, I discovered a tool called LTE-Cell-Scanner by Xianjun BH1RXH. Forked from the original project by James Peroulas, it allows you to use simple hardware to scan for LTE Cells used by mobile phone networks. James points out on his site that this tool can also be used to calibrate an RTL-SDR receiver's oscillator, since an LTE downlink centre frequency is stable to within 50 Parts Per Billion, that's 10 times more stable than my Yaesu FT-857d using a TCXO.

    If this doesn't mean much, think of it as a local frequency reference standard that you can use in your shack with minimal effort and cost.

    The story gets better.

    I started building LTE-Cell-Scanner from source and in doing so discovered a directory on my computer named "uhrr". I didn't remember what it was for, so I looked online. The first search result, when I looked for "uhrr radio" was a repository by Oliver F4HTB, more on that in a bit.

    The second search result was something called "Universal Radio Hacker". I clicked on the link and discovered a mind boggling tool. There are times in your life when something flips, this was one of those times. It happened when I discovered "csdr" by Andras HA7ILM and again when I discovered "GNU Radio".

    Diving into "Universal Radio Hacker", by Dr. Johannes Pohl and Dr. Andreas Noack I was introduced to the art of decoding and generating digital radio signals. In 2018 it was presented for the first time during the USENIX Workshop on Offensive Technologies, or WOOT, as a tool to discover, decode and identify exploits of proprietary IoT devices scattered all over the planet. As an aside, USENIX, Users Of Unix, since 1975.

    Back to radio. Universal Radio Hacker allows you to dissect recorded radio signals using all manner of interactive processes. When you go looking for it, and you should, I recommend that you start by watching some videos. You'll find an introductory play list on my YouTube channel. By the time you've seen those, you'll likely share my excitement.

    To encourage you further, the Universal Radio Hacker is open source, written in Python, and runs on Linux, MacOS and Windows. So far there have been 94 releases of the software, so it's seen significant development in the years since it was released into the wild.

    When installing it I was surprised to discover that its acronym was "uhr", not "uhrr". This was a relief since I still didn't remember what "uhrr" was all about and I couldn't imagine having forgotten Universal Radio Hacker. It turns out that the last time I looked at "uhrr" was apparently in 2021 when I shared my experience in an article titled "The remote edge..."; "uhrr" or "Universal Ham Radio Remote" is a tool that allows you to use a web browser to access a radio remotely.

    My little journey into unexpected diversions, distractions and discovery has led me into a path where several puzzle pieces have come together. For example, Universal Radio Hacker and GNU Radio can talk to each other, they're both written in Python, they're both open source, have a history of development and have a community of users. The LTE-Cell-Scanner, also open source, will allow me to calibrate most if not all of my radio gear and I'm once again inspired to keep digging into yet another aspect of this wonderful hobby. I'm sure that there are more than a thousand different hobbies under this roof.

    Go forth, explore, discover, be amazed, and stay curious!

    I'm Onno VK6FLAB

    続きを読む 一部表示
    5 分

Foundations of Amateur Radioに寄せられたリスナーの声

カスタマーレビュー:以下のタブを選択することで、他のサイトのレビューをご覧になれます。