TopPodcast.com
Menu
  • Home
  • Top Charts
  • Top Networks
  • Top Apps
  • Top Independents
  • Top Podfluencers
  • Top Picks
    • Top Business Podcasts
    • Top True Crime Podcasts
    • Top Finance Podcasts
    • Top Comedy Podcasts
    • Top Music Podcasts
    • Top Womens Podcasts
    • Top Kids Podcasts
    • Top Sports Podcasts
    • Top News Podcasts
    • Top Tech Podcasts
    • Top Crypto Podcasts
    • Top Entrepreneurial Podcasts
    • Top Fantasy Sports Podcasts
    • Top Political Podcasts
    • Top Science Podcasts
    • Top Self Help Podcasts
    • Top Sports Betting Podcasts
    • Top Stocks Podcasts
  • Podcast News
  • About Us
  • Podcast Advertising
  • Contact
Not in our directory?
Add Show Here
Podcast Equipment
Center

toppodcastlogoOur TOPPODCAST Picks

  • Comedy
  • Crypto
  • Sports
  • News
  • Politics
  • True Crime
  • Business
  • Finance

Follow Us

toppodcastlogoStay Connected

    View Top 200 Chart
    Back to Rankings Page
    Hobbies

    Foundations of Amateur Radio

    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?“.

    Advertise

    Copyright: ℗ & © 2015 - 2020 Onno Benschop

    • Apple Podcasts
    • Google Play
    • Spotify

    Latest Episodes:
    Bringing an upconverter into your life Jan 23, 2022
    Show notes

    Foundations of Amateur Radio

    A couple of days ago, after months of anticipation, an unassuming little box arrived on my doorstep. Inside the box was a nondescript electronic device with two SMA connectors and a USB socket. Other than the branding, there were no markings on the device and it came without any instructions.

    It did come with a couple of SMA adaptors, which came in handy.

    A little research later determined which of the two SMA adaptors connected to an antenna and which connected to a radio.

    The gadget itself is called an upconverter.

    It's an interesting little device that essentially mixes two frequencies together, creating two new ones, start with say 720 kHz and mix it with 120 MHz and you end up with 120.720 MHz and 119.28 MHz. In other words, if you mix two frequencies together, you end up with both the sum and the difference of those frequencies.

    If you have a radio that can listen to 120 MHz, but cannot listen to 720 kHz, then using an upconverter, you can, as it were, expand the frequency range of your radio to hear different signals.

    I purchased the upconverter with the intent of connecting it to my PlutoSDR, since the lowest frequency it can do is 70 MHz. Combine the two and I should be able to listen to all of the amateur HF frequencies at once.

    Given that my PlutoSDR is currently doing something else, I had a look at using the upconverter with my WSPR beacon monitor that uses an RTL-SDR dongle. Technically it's not required, since my particular dongle can be used to tune to HF frequencies, but as an experiment, it works well enough.

    So, I connected the antenna to the upconverter, the upconverter to the dongle and the dongle to a Raspberry Pi, a single board computer that runs Linux. Essentially the exact same setup I've been running for years, except that I inserted the upconverter between the dongle and the antenna.

    That and some power took care of the hardware.

    The software initially gave me some challenges. After discovering that the tool I'm using, rtlsdr_wsprd, has an option for an upconverter, I was up and running in minutes.

    So, at the moment, and for the next foreseeable little while, my WSPR monitor is using an upconverter to scan HF. Technically this should increase the sensitivity by a significant amount, since the dongle is better suited to tuning to higher frequencies than it is to lower ones, but only time will tell.

    I updated my monitoring scripts to take into account if the frequency I was monitoring was out of range, so it currently won't report on anything above 60 MHz, but then that's fine for what I'm working on.

    I've updated the script on github if you want to have a look. It's nothing fancy, it essentially checks to see if there's a file called upconverter and if so, it calls a slightly different monitoring script.

    Given that I have existing logging data associated with this monitor, I should be able to discover if there's any significant difference between what I've been monitoring to date and what's coming in now that an upconverter is in the listening chain. Theoretically, I should be able to hear weaker signals, but time will tell.

    One thing that was interesting whilst I was discovering how this all works and hangs together is that it wasn't immediately obvious how to set it all up in software. I tried several tools to make sense of the data. In the end the combination of gqrx, setting the local oscillator offset to a negative frequency, in my case 120 MHz, got me to the point where I could set the frequency to 720 kHz and hear my local broadcast station, whilst the software actually, secretly behind the scenes, added 120 MHz to that and tuned the radio to 120.720 MHz.

    Once I got my head around that, things started falling into place.

    The same is true for rtlsdr_wsprd, adding the upconverter flag with the value of 120MHz, got my monitoring station up and running.

    This is a pretty user friendly way of getting started with frequency mixers. You might recall my exploration into components apparently made from unobtainium. The intent is to use a variable frequency to achieve a similar thing, but that's a project still on the drawing board, for now, I have a fixed frequency, 120 MHz, which is plenty to get started.

    If you're curious why I'd want a stable variable frequency, consider for example, what might happen if you transmit from a HF frequency into an upconverter. Perhaps you could use your HF capable WSPR beacon to make a signal on 2m or 70cm. 120 MHz won't cut it, but perhaps you can work out what's needed to get from the 10m WSPR band to the 2m WSPR band, or the 70cm WSPR band.

    I'm Onno VK6FLAB


    When I said Parrot Repeater ... I likely had a different picture in mind. Jan 16, 2022
    Show notes

    Foundations of Amateur Radio

    A little while ago I mentioned in passing that I was considering implementing a parrot repeater to help determine how your radio is performing. Discussion afterwards revealed that not everyone had the same picture in mind, so I thought I'd share with you some of what I'm considering and why.

    Most of the modern radio landscape revolves around hooking a computer up to some type of radio frequency capable device. Commonly it's the audio and control signals that travel between computer and radio, but there are plenty of examples where raw data makes the journey, like in the case of an RTL-SDR dongle.

    That journey is increasingly made using USB, the cable, not the sideband, and limits are based around the maximum speed that a Universal Serial Bus has. Essentially the amount of data that you can process is limited by how fast your computer can talk to the radio.

    For my parrot repeater, I'm imagining a device that can receive RF from any radio and process that signal to determine what the centre frequency is, the deviation, stability, the mode, what ever parameters I end up being able to determine, a whole other discussion on its own. In response, the idea is that the device generates a report and either presents that using text to speech, or as a web-page, or both.

    Using traditional methods, this would involve a radio, a computer, some software, connections between the radio and the computer, not to mention power for both the computer and the radio, an antenna and perhaps an amplifier. The picture I have in mind is not anything like that. I'm imagining a single device that takes power and does all I've described inside the one device. No external computer, no audio cables, no control cables, no hard drives, not anything, just a PlutoSDR and a power source connected to an antenna or two.

    You might think that's fanciful. As it happens, we already have some of that today. When I run dump1090 on my PlutoSDR, it presents itself to the world as a website that I can visit to see which aeroplanes are within range, where they are exactly on a map, what messages they're sending and where they're going. All of the processing is done inside the PlutoSDR. All I have to do is give it power and an internet connection.

    This is possible because the PlutoSDR is essentially a computer with RF. It runs Linux and you can write software for it. Unlike my Yaesu FT-857d, which also has a computer on board, rudimentary to be sure, but a computer none the less, it cannot be altered. I cannot load my own piece of software, launch a web browser and point it at my Yaesu, not without connecting an external computer that in turn needs to be connected to the radio. I might add, that this is is how many repeaters work and how devices that implement AllStar and Echolink manage to make the jump between the Internet and the world of RF.

    If your eyes are not lighting up right now, let me see if I can put it in different terms.

    The PlutoSDR has the ability to access signals between 70 MHz and 6 GHz. It can do so in chunks of 56 MHz. Said differently, if you were able to consider all of the amateur HF spectrum, from zero to 54 MHz, you could fit all of it inside one chunk of 56 MHz that the PlutoSDR is capable of. You couldn't send it anywhere, since you're limited to how fast a USB cable is, but you could technically process that inside the PlutoSDR itself.

    To get the PlutoSDR to see the amateur HF bands you could connect it to a transverter, in much the same way that today many 2m handheld radio owners use a transverter to get to 23cm, except in this case, we're going the other way.

    In order to actually use this massive amount of information, you're going to need to do some serious signal processing. Accessing 56 MHz of raw data is hard work, even if you don't have to get it across a serial connection. As it happens, the PlutoSDR also comes with an FPGA. As I've mentioned previously, it's like having a programmable circuit board, which can be programmed to do that signal processing for you. It has the capability to massage that massive chunk of data into something more reasonable. For example, you might be able to use it to extract each of the amateur bands individually and represent them as an image that you might show to the world as a waterfall on a web browser.

    Now to be clear, I'm not saying that any of this exists just yet, or fits within the existing hardware constraints. I'm only starting on this journey. I'll be learning much along the way. No doubt I'll be using existing examples, tweaking them to the point that I understand what they do and how they work. I've already been talking about some of this for years. As you might have discovered, this adventure is long with many different side quests and at the rate I'm going I'm confident that this represents the breadth and depth of what amateur radio means to me.

    So, if you're wondering why I'm excited, it's because the amateur radio world of opportunity is getting bigger, not smaller.

    I'm Onno VK6FLAB


    Products made from unobtainium Jan 09, 2022
    Show notes

    Foundations of Amateur Radio

    The other day I received an email from a fellow amateur, Elwood WB0OEW. We've been exchanging email for a little while and having been in the hobby since before I learnt to ride a bicycle, he's always got some interesting insight into something I've said and an encouraging word to share.

    This time he introduced me to a project he built and published a couple of years ago. It's a variable frequency standard, built from parts and, at the time, costing all of about $150, more on that shortly. Compared to the microwave oven sized HP-606A signal generator sitting on my bench in bits, with some diligent layout, this project could fit inside one of the valves that drives that massive hunk of equipment.

    As an aside, truth be told, I'm a little afraid of the HP. It managed to pop the RCD, a residual current device, or safety switch, in my house and in doing so, took out the UPS that powers my main workstation, so, not unexpectedly, I'm reluctant to repeat the experience. Once I understand precisely what happened, I'll pick up the restoration efforts and based on what I learnt today, it might get me where I want to go faster.

    Elwood's frequency standard is a very interesting project that delivers a very precise Variable Frequency Oscillator or VFO with an accuracy approaching 1 part per billion. His project uses an Arduino to control a touch sensitive display, read a knob and set and correct the frequency using a GPS as an accurate external time source. It's all very compact, easy to follow and I immediately thought that this would be an excellent project to build with a little twist.

    I'm thinking that it would be really great to have this device sit on your local network and make it remote controllable.

    The heart of this frequency standard project is a chip called an Si5351. The Silicon Labs Si5351, to use its full name, was first sold by Mouser in 2010 and has been popular since. You'll find it in all manner of places, including the Linux kernel source tree, the QRPlabs QCX and BITX to name two, the Elecraft KX2, scores of Arduino projects and countless frequency source products and projects used in amateur radio.

    The Si5351 is a configurable clock generator. Think of it as a programmable crystal that can be configured on the fly, as often as you like. For configuration, it uses an I2C bus, or Inter-Integrated Circuit communications protocol, a special serial bus intended for chip to chip communications, invented by Philips Semiconductors in 1982. That's the same Philips from the light bulbs and audio cassettes, CD, DVD and Blu-ray, also the Philishave. To complete the picture, Philips Semiconductors became NXP in September 2006.

    Back to our frequency standard project.

    I wondered if I could cut out the Arduino from the actual correction process, since I didn't need a display or a knob and discovered that the Si5351 comes in several flavours. Elwood's design uses the A-version, but there's also a C-version that has the ability to take in an external clock, like say that from a GPS, and correct within the chip itself.

    With that information in hand, I figured that I could use a simple Wi-Fi capable system on a chip, something like say an ESP8266, to configure the clock and take care of communications with the outside world. In the process I'd learn how to do a bunch of new things, including my first foray into generating RF, first time writing actual firmware, first time designing circuits and no double many more firsts.

    Then I hit a snag.

    It seems that the Si5351 has gone from commonplace to zero in stock. Not just zero in stock in Australia, or the US, no, zero in stock anywhere. There are a few A-version breakout boards, that is, the chip on a circuit board, available from one supplier. There is also a new compatible chip, an MS5351M, available from China, but that's a drop-in for the A-version, not the C-version.

    So, where it stands is that I can almost taste the design, essentially three chips, an almost trivial circuit board, some SMA connectors, a power source and an external GPS antenna, something that would represent the very first circuit I actually designed, which is a long way from reading the circuit diagram for my Commodore VIC-20 back in the days before I owned a soldering iron.

    It did bring me face to face with an odd realisation.

    There are components that we use in day-to-day use, ones that are common, used across many different industries, that come from a single source. I should also mention that this particular manufacturer just got sold to another company, which doesn't help matters.

    Nobody seems to know how long this shortage might last with forecasts varying wildly, but I'm beginning to wonder how many of these kinds of components exist and how we might reduce our dependence on single supplier hardware.

    I'm also starting to look at using an FPGA to do all of this in software, but that's going to take some time, of course we could start using valves again. My 1960's era HP signal generator is starting to look much less intimidating.

    I'm Onno VK6FLAB


    Leaving the hobby ... Jan 02, 2022
    Show notes

    Foundations of Amateur Radio

    The other day I came across a how to video on becoming a radio amateur. It's a recurring kind of publication, the kind that I've contributed to in the past.

    I wondered what it would take to leave the hobby.

    First of all, I'd have to let my callsign lapse. That's easy enough, but I paid for five years, so it's going to take a while. When it has finally ceased being mine, have I stopped being an amateur?

    For one, my qualifications would still be in the regulator's database, likely well beyond my breathing years. I wonder if they implement the right to be forgotten?

    Another thing I'd have to do is stop knowing about how antennas work in day-to-day situations. I'd have to stop noticing the location of free to air television antennas, mobile phone towers, Wi-Fi antennas throughout the community and even the network in my home.

    I'd also have to say goodbye to all the friends I've made around the place. There's hundreds of people scattered around the globe who with a single word might lure me back into their world, and with that the risk of being sucked back into the community once again.

    At a minimum I'd have to stop using computers, or radios, or electronics really. I'd have to stop wanting gadgets and measuring equipment, not to mention having to mothball my soldering irons and give away all my heat shrink.

    I'd have to give back the space I've eked out in the house and return it to the general living space it once was. I'd also have to sell all my radio gear and antennas. I'd have to rip out the coax, fix up any holes, cancel pending orders for new antennas and donate my books and magazines to the local library.

    I'd have to stop looking at electronics magazines, cut up my loyalty cards for the local electronics and hardware stores and start an online store to sell all the connectors and adaptors I've amassed over the time I've been part of the community.

    I'd have to forget the phonetic alphabet that I use almost daily and start using crazy words to spell things over the phone like a normal person does.

    Experimentation would be a thing of the past and would be frowned upon as a fringe activity, one only suited to madmen and amateurs, and I'd have to stop investing my time in software and projects that might one day be used in amateur radio.

    One of the hardest things to give away would be my curiosity, the one thing that's innate to my wellness. I'd have to stop asking Why? and How? all the time. I'd have to plead ignorance when someone asks how coax works and what's inside a blob of goop on a random circuit board they found on the side of the road.

    Then there's the other things like physics and general science. I'd have to disavow all knowledge of these activities. I'd have to stop looking at the stars and stop wondering which radio frequencies were being emitted from all over the night sky.

    I'd have to become ignorant of emergency services and communication, of event management and club life. I'd have to feign interest in anything that wasn't science or technology and I'd have to keep a straight face and my mouth shut when someone extolled the virtues of an irrational belief system.

    I would likely have to give up my job as an IT consultant and start on a more manual job. Perhaps I'd take up gardening, though I'm not sure how I'd do in the weather at my age.

    Even if I achieved all that, and kept it up for the rest of my life, I'd still be an amateur, just one hiding from the hordes of humanity striving to live on this ball of dirt, hurtling through the heavens on a journey through the stars.

    I'm not sure I could do that.

    So, for better or worse, as I see it, once an amateur, always an amateur and if you're curious and believe in science and technology, I'm here to say that you're well over halfway towards being an amateur! Welcome to the club!

    I'm Onno VK6FLAB


    What testing equipment is essential? Dec 26, 2021
    Show notes

    Foundations of Amateur Radio

    After discussing the notion that it's not really possible to determine how your gear is performing without measuring, several people commented that in the good old days an amateur was expected to have sufficient equipment to test performance of their gear.

    I flippantly pointed out that once upon a time, computers ran on punch cards too. That's not to dismiss the notion of testing, but rather that times have changed. Testing equipment that was suitable in the 1980's is still available around the place, but expect to pay for it. Some of it is still relevant, some less so.

    Even if you do acquire suitable equipment, how do you know if what you're measuring is real? How do you know if the frequency counter that you have is accurate, how do you know if 1 Volt is 1 Volt, or 1 second is 1 second? As I've said before, measurement is the act of comparing two things.

    If you think that's ludicrous, consider the rulers and tape measures in your home. They all indicate the same measurement, right? Just for a laugh, pull out all the ones you can find and see what you discover. If you've not done this, you're in for a surprise.

    I don't want to dissuade you from getting testing equipment, far from it, but don't expect to fork out to get the equipment and call the job done. The point being that spending lots of money on gear isn't the end of the story, it's just the beginning and in my opinion it's not the place you should start.

    Based on community responses, ninety recommendations in all, so hardly scientific or representative, but still a good feel for the space we're playing in, the single most important piece of equipment you should get after sorting out your radio, antenna, coax, power supply, computer, software and other fun things we fill our shacks with is the Digital Multi Meter. You can spend anywhere from $10 to $500 on one, but it should be high on your list. As with the rulers, your results will vary, so be mindful of that when you go shopping.

    While the SWR meter and the Watt or Power meter appear regularly, they're not the next highest ranked testing gear. Mind you, most current radios have those built-in to some extent, so perhaps the numbers are somewhat distorted here.

    The next essential piece of equipment is some form of monitoring. Either active, passive, programmable, automated, manual, what ever. Hardware like the NanoVNA, the TinySA, even using a Software Defined Radio feature high on the list. Most of these devices either generate a signal to test against, or they rely on your radio to do the heavy lifting, depending entirely on what you're testing. An antenna analyser is among these kinds of tools.

    As an aside, the dummy load, either a high power one, or a more modest one, come recommended by many different people.

    Together with this list of monitoring equipment comes associated accessories, adaptors, patch leads, attenuators and filters.

    After that comes equipment such as variable power supplies, Watt meters, grid dip meters, oscilloscopes and frequency counters.

    I will observe that from the responses I received there was a distinct flavour to the recommendations.

    On the one hand there was the combination of recommending something like a station monitor, or a signal generator, an oscilloscope and a frequency counter, including things like a Bird 43 RF Watt meter. On the other hand were recommendations for spectrum analysers, NanoVNAs, SDRs and the like. It's not quite across the analogue to digital divide, but it's close.

    Note at this point that I'm a software guy in the process of restoring an analogue HP 606A Signal Generator from the early 1960's, so I'm not pointing the finger anywhere.

    There were other tools recommended too, an LCR meter, a tool that allows you to measure Inductance, Capacitance and Resistance, something you can buy in kit form if you want to get started, or similarly, can be purchased for varying amounts of money online. Speaking of money, varying amounts that is, the service monitor was on the wish list for several people. Prices between that of a new radio or a new car with varying amounts of warranty.

    I will make mention of a bi-directional coupler which was marked as essential by one amateur. It's a tool that allows you to sample a signal in the forward and the reflected path which comes in handy when you're trying to test and build equipment.

    As mentioned before, your transceiver has some of this equipment built in, or can be set-up to do some of this, so there's no need to go out and spend thousands of dollars to set-up your testing bench on day one, but the day after, I'd add it to my birthday list.

    No doubt that there's many and varied opinion on this. What is your essential testing equipment?

    I'm Onno VK6FLAB


    How does your gear measure up? Dec 19, 2021
    Show notes

    Foundations of Amateur Radio

    When you spend some time in this hobby you're likely to find equipment with similar performance for vastly different pricing. At one end of the spectrum you might compare a cheap $25 hand-held radio to a $450 one. At the other end, a $1,500 SDR or Software Defined Radio against a $4,500 one.

    Those examples are for brand name devices, which generally speaking have published specifications, come with regulatory approvals, a wide user base, reviews and a distribution network. If equipment is found to be operating out of specification, a regulator might seek a remedy or ban the sale of the equipment.

    Those various sources and processes make it possible to compare those devices in a structured way to discover just how deep into your pockets you need to reach in order to acquire a shiny new gadget.

    If you buy any of these devices in the used market, you have no way to determine just how far from the factory specifications the device you're contemplating has deviated. Is that waterproof radio still waterproof, or did the previous owner open up the case and put it together incorrectly? Was it dropped and did a component get damaged? Did the static electricity from a local thunderstorm leak through the circuit via the antenna, or did the previous owner not use anti-static precautions when they looked inside?

    If it actually failed, it's easy to know. If it's still working, absent a laboratory, you're essentially on your own.

    If that's not challenging enough, consider hardware that's released as open source, that is, the original designer released their project, shared the design, a circuit board with component list and specifications. Another person can pick up the documentation and legally build a copy of the hardware.

    How do you know how the two compare?

    Aside from considering how well any design might actually match the real world, how do you know if the original design can be improved upon or not? Did the second builder use the same components, substitute with better ones, or economise on parts they thought were too expensive?

    What happens if the two designers argue with each other about the performance of their respective designs? What if the second design becomes vastly more popular than the original and what if you throw in outright intellectual property theft over the top of all this?

    Now consider the same physical hardware, from the same factory, but using different software. How do you know what impact the software has on the performance of the equipment? For example, one component seen more and more is a chip called an FPGA, a Field Programmable Gate Array. Think of it as a programmable circuit board where updating the software creates a different circuit.

    An FPGA might be used to filter radio signals. With just a software update, you can program different filters and change the actual performance of the entire device. How do you know if the new version of the software has improved or worsened performance?

    What all this lacks is a standard way of describing performance. Not only the kind of standard that's achievable in a laboratory, but one that we can test at home. There's no documentation that I've been able to find that shows how to measure some of this objectively, or even compare your own kit against itself.

    It would be great if I could measure my gear against a standard and you could too and we could compare our respective equipment against each other.

    Even using the laboratory standard measurements, for example the Sherwood Engineering Receiver Test Data, which allows you to compare other tested equipment in the same list, is hard, if not impossible to compare at home by the likes of you and I. Not to mention that Rob NC0B has finally retired after 45 years, so having been licensed in 1961 age 14, there is a good chance that updates are going to become a thing of the past when Rob stops volunteering his time.

    I will mention that this isn't a new thing. Many years ago I spent some time as a broadcaster. One of the very first things I was taught is that you need to set levels to trigger the VU Meter just so. When you make a recording to tape, you're required to generate a 1 kHz tone at a specific level so when it's played back to air, the voice levels will be correct.

    When I became licensed in 2010 I almost immediately discovered that there isn't even a standard way to test if the signal that my radio is putting into the local repeater is the same as that of other amateurs. You'll notice this because you're forever twiddling the volume on your radio when you speak with others on-air because their voice levels vary widely.

    One idea I've been toying with is using a parrot repeater that can measure a signal, allowing anyone who uses the same parrot to compare their equipment.

    How would you approach this increasingly complex problem in such a way that the amateur community can share their results in a way that makes comparison meaningful and useful?

    I'm Onno VK6FLAB


    Getting Amateur Radio propagation data at home Dec 12, 2021
    Show notes

    Foundations of Amateur Radio

    For some time now I've been discussing the potential of weak signal propagation and its ability to create a live map from the data that your own station transmits. There are several systems in place that show a map of where and when your station was heard in the past little while. Using 200 milliwatts, I've been transmitting a WSPR or Weak Signal Propagation Reporter beacon on 10m for the past few weeks.

    At the moment, the furthest away my beacon has been heard is 13.612 km away. That's an 0.2 Watt signal heard on the other side of the planet, on 10m. As distance goes, it's a third of the way around the globe. I must point out that there's no way of knowing if this signal travelled the short path or the long path.

    If you've heard those terms, short and long path but were wondering what they mean, here's how it works. If I get on my bike at my QTH in Perth in VK6 and peddle East until I hit Sydney, I'll have crossed Australia, taken about 184 hours and travelled about 3.746 km. That's the short path. If I head West instead and start swimming, visit Cape Town, Buenos Aires and Auckland along the way, I'll have travelled much further, still made it to Sydney, but taken the long path.

    Radio waves can do the same. Depending on propagation, a signal might take either the shortest route, or go in the opposite direction and take the longest route along the great circle between two stations.

    I'm mentioning this because WSPR doesn't tell you if it's one or the other and if you're using a vertical, it could be either. Even directional antennas might receive a signal from unexpected directions.

    Using one of the mapping tools, wspr.live, I extracted all the sightings of my callsign and all the reports that I'd made from my receiver. It shows that my newest transmitter has now been heard by 11 stations across three continents.

    Those numbers are just the beginning. I wanted to see on the map where these stations were, so, during the week I built a proof of concept world map that I used to visually show the four character Maidenhead grid squares that my station was heard in. I also had a look to see which stations I'd heard over the years and where they were. In all, 771 different stations are in my log, either as a receiver or a transmitter.

    N4WQH heard me on 40m, 18.832 km away when I was using 5 Watts. My station has heard, or has been heard across 331 different grid squares. There's reports across some remote parts of Australia, Japan, India, South Africa, Europe, the United States, several across the Pacific and even a few in Antarctica.

    I wondered how many of the world's grid squares have actually been activated and which station was heard the furthest and how much power was used. Those numbers will have to wait for another day. I initially started using wspr.live which has a neat way of allowing you to embed an SQL query as part of the URL to download the output.

    I was getting some interesting results, so I thought, rather than hammer this lovely resource with my questions, I should download the raw data instead. So I did. Well, I am. Still. It's big.

    As of today, there's 166 files, taking up 60 GB of compressed data, with over 3.5 billion reports.

    The first spot in that data goes to N8FQ who heard WB3ANQ on Monday, the 17th of March, 2008 across 911 km on the 30m band transmitting with 28 dBm, or about 630 mW, reporting a signal to noise ratio of 1 dB.

    Using preliminary data to get started I mapped all the activated squares, each shown as a red box and saw that my entire map was red. At that point I figured that either I've got a bug in my code, or something else is going on.

    To give some context before I share what I found, a Maidenhead locator consists of a combination of letters and numbers. For four letter grid squares, there's a grand total of 32.400 different combinations, running from AA00 to RR99. They're 2 degrees wide and 1 degree high and their width depends on where on the planet they are. At the equator it's about 222 km wide and 111 km tall, at the North and South pole, it's 0 km wide. If you travel between two squares, you might have to move a meter, or the entire width of a grid square.

    Among the report, I found stations who had activated more than one square. That's fair enough, you can move your station and start making noise where ever you like. I found stations with activations across more than a thousand different squares. Before I start pointing the finger, I will mention that if you attach a WSPR beacon to an aircraft, or a balloon, you can legitimately activate plenty of squares.

    When you set-up a WSPR transmitter, you're required to manually enter the locator and mistakes happen. There's plenty of records with invalid Maidenhead locators, typically shown instead is a callsign. Then there are stations that pick desirable locators. This manual entry is also true for the power level and even the callsign, so I'm not outing these stations here, since it's entirely possible that the callsign shown doesn't actually relate to the transmitter or the licensed amateur.

    What does all this mean?

    It means that the information in the WSPR database cannot be trusted. I suspect it also means that the data used to lodge FT8 contacts across the planet can probably also not be trusted. It means that any propagation data you're deriving is likely contaminated by misreporting, deliberately or not.

    As a community, if we want to use this for actual measurements, we'll have to figure out how to make this a trusted resource, because the information that WSPR can bring to propagation is in my opinion extremely valuable.

    I would love to hear your thoughts on how we might fix it.

    I'm Onno VK6FLAB


    Amateur Radio and the art of getting started ... Dec 05, 2021
    Show notes

    Foundations of Amateur Radio

    One of the regular topics of conversation in amateur radio, especially for those new to the community, is where to start? The sheer volume of available options is often overwhelming. If you've never encountered the complexity associated with this amazing hobby the experience can be disheartening and even demoralising.

    In my early years I was results driven. Getting on air, making noise, logging a contact, adding a country, winning a contest, rinse and repeat, get better, do more. There have been numerous occasions when I came home from one of my adventures disappointed, sometimes bitterly so.

    That happened for quite some time, until one day I realised that the journey in and of itself is the reward.

    That might sound disingenuous, so let me illustrate.

    This week I set-up an automatic beacon in my shack that can be heard by stations around the planet, letting me know just how far my signal can travel at any particular moment, using my own station antenna and local propagation. As projects go, it continues to be an adventure.

    As you might recall, I like low power operation, truth be told, I love low power. The smaller, the better. Less is more and all that. I recently completed the first leg of a journey to set-up a permanent beacon. For years I'd been dabbling around the edges. On the weekend, whilst I was in my shack, I'd regularly set-up my computer and radio, set it to WSPR beacon and see what stations heard me. I couldn't turn my radio below 5 Watts, so that's what I used. Before you start, yes, I could turn down the volume, but that involves math and I wanted a result, now.

    It filled a gap using WSPR, Weak Signal Propagation Reporter, like that. For a while, I improved on things by having a receiver set-up that monitored the bands all day every day and recently I turned it back on, with limited success, more on that shortly.

    What I really wanted was to see where my signal was going, not what I could hear. I received a few emails suggesting that a ZachTek WSPR Desktop transmitter, built and sold by Harry, SM7PNV, would be just the ticket. It's a little metal box with USB and SMA connectors. One SMA for the supplied GPS antenna, used for location and time, the other for a transmit antenna. USB provides serial for configuration and power if it's operating in stand-alone mode. Yes, you can operate it without needing a computer and if you want it does band-hopping. After configuring it with things like your callsign and bands, you can plug-in the GPS, your antenna and power it via USB and it will run as an automatic 200 milliwatt WSPR beacon.

    That device in turn prompted a journey to discover a more appropriate antenna, since my current station antenna uses an automatic tuner that won't get triggered by this tiny transmitter. That caused an exploration in how and where to mount any new antenna, with a side-trip into finding a specific anti-seize compound locally. To pick the mounting hardware, I had to get into wind loading, how strong my satellite dish mount might be, how to install and tune a multi-band antenna. The list just keeps growing and that voyage continues.

    I'm tracking the requirements with a project specific check-list, just to make sure that I don't miss any steps and have a place to document new discoveries when they invariably hit me in the face. So-far, so-good.

    The WSPR monitor receiver is currently connected to a generic telescopic dipole, mounted indoors, which in the past gave me a much better result than my station vertical, so I should be able to keep both running.

    Next on the list is to construct a live propagation map for my station, then a way to switch modes on that map, so I can tell if it's worth calling CQ without going blue in the face. I'm also working on a WSPR transmitter for 2m and 70cm, because they are under served in my neck of the woods.

    The takeaway from all this is that whilst there are many steps, and truth be told, that list is growing as I learn, each step is tiny and doable. The only thing that separates me from someone who doesn't know where to start, is this.

    I started. You can too. Anywhere. Doesn't matter. Pick anything that tickles your fancy. Start digging. It's a hobby, not a profession. What ever floats your boat, what ever makes you excited, what ever you're interested in, pick it and do something, anything.

    That's how you get anywhere in Amateur Radio, and Open Source, and life for that matter, just start.

    I'm Onno VK6FLAB


    One Timezone To Rule Them All Nov 28, 2021
    Show notes

    Foundations of Amateur Radio

    Right now it's 10:45.

    That piece of information is unhelpful without any context. I could just as easily have told you that it's 2:45 and it would be just as accurate, helpful and meaningless. The point being that without context, you don't know if I'm an insomniac, drinking morning tea, recovering from a late lunch or putting on my PJs.

    If I'm talking to people in the same room, supplying the time happens within the context of that room, but if the world is our oyster, our room is a little larger and dawn for one person is dusk for another, at the same time.

    Before we could communicate at the speed of light and travel faster than a bullet, time was a relative thing related to the location of the Sun and considered mainly by mariners and astronomers. Even with the advent of increasingly accurate clocks, for most people, noon was when the Sun was at its highest point and the local clock was set to that.

    When our world got smaller, because communication and travel got faster, people started noticing that noon in one place wasn't the same as noon in another place. It became a real problem when people travelled hundreds of kilometres by train in a day. Imagine coming up with a train time-table that takes into account each local version of noon.

    In an attempt to deal with this, railroad managers in the United States established 100 railroad time zones. This malarkey continued until the 18th of November 1883 when four standard time zones were established for the continental United States.

    Of course, being human and all, that was a local solution. Great Britain had already established its own standards for time for England, Scotland and Wales.

    In October 1884, the International Meridian Conference, held in Washington DC, adopted a proposal that designated the Prime Meridian for longitude and timekeeping should be the one that passes through the centre of the transit instrument at the Greenwich Observatory in the United Kingdom and established Greenwich Mean Time, or GMT as the world's time standard.

    Why Greenwich? At the time the United Kingdom had more ships and shipping using Greenwich as their reference than the rest of the world put together and the observatory at Greenwich had produced the highest quality data for a long time. As an aside, on a French map before 1911, 0 degrees was centred over Paris. There are other wrinkles, like the fact that Earth isn't round and as a result the Greenwich Prime Meridian is not quite in the right spot because measurements didn't take into account local variations in gravity.

    In 1972, Coordinated Universal Time, or UTC replaced GMT as the standard for time in the world. It now references the International Reference Meridian, currently about a 102.5m east of the original Prime Meridian passing through Greenwich. It's on the move with reference to land because tectonic plates shift and where it is today is not where it's going to be tomorrow, so don't go looking for a marker to indicate the IRM.

    Meanwhile in the rest of the world people needed to come to terms with how to standardise on what to call time zones. The USA establishing four time zones was just for one country. Depending on who's counting, there's over 200 countries and each has its own set of time zones. Which each might include daylight saving, or not. For some, like VK6, daylight saving was voted on several times. Trials were had and time changes during summer were implemented, then reversed, then reversed again, and again, in total, VK6 did this dance six times and we currently don't observe daylight saving, neither does VK4 or VK8.

    So, not only does 10:45 require location context, it also requires that you know if there's daylight saving happening at that time in that location, which to add insult to injury, doesn't actually happen on the same date each year. It gets better if you consider time in another location. Do they have daylight saving, is it on at the time, do we have daylight saving at that time, how many hours are we apart, when is this actual event and what if we're coordinating efforts between people in multiple locations? Did I mention that summer in Europe is in July and in Australia it's in January?

    In case you're wondering, tracking all this is a massive job currently under the purview of the Internet Assigned Numbers Authority. The person coordinating this, whilst wrangling the politics of naming things, including dealing with warring countries who take umbrage at having their time zone named after "the enemy" is computer scientist Paul Eggert, the project lead of the time zone database.

    War aside, time zones are political. For example, Dublin Time was stamped out by the British as punishment for the Easter Rising.

    If that wasn't exciting enough, to provide local context, we use abbreviations to indicate which location we're talking about. In VK6 that abbreviation is WST, simple enough, Western Standard Time. What if your abbreviation was CST? Is that Central Standard Time in North America, China Standard Time, Cuba Standard Time, or even Australian Central Standard Time. If your local time zone is IST, you could be referring to Indian Standard Time, Israel Standard time, Irish Standard Time or even Irish Summer Time.

    As radio amateurs we hold global contests and we advertise our online club meetings and events. Often, we refer to times and dates that might be understood by an audience of one, but utterly confusing to the rest of the world.

    So, what do you do with this?

    Simple, use UTC. My timezone, called WST, or AWST, is UTC+8. F-troop, a weekly net for new and returning amateurs runs every Saturday morning at midnight UTC, that's 0:00 UTC. No confusion, no daylight saving, everyone can figure out if it's worth being awake for and I must applaud the amateurs from G-land and PA with their contributions in the very, very early hours of their morning.

    So, next time you make some noise about a contest, or any amateur activity that goes beyond the people in your suburb, specify the time in UTC. Who knows, perhaps one day, even the likes of SpaceX, Apple and Google will start using UTC to announce their events ...

    As Goldie Hawn put it: "Well, in my time zone that's all the time I have, but maybe in your time zone I haven't finished yet. So stay tuned!"

    I'm Onno VK6FLAB


    The Rebirth of Homebrew Nov 21, 2021
    Show notes

    Foundations of Amateur Radio

    On the 12th of December 1961, before I was born, before my parents met, the first amateur radio satellite was launched by Project OSCAR. It was a 10 kilo box, launched as the first private non-government spacecraft. OSCAR 1 was the first piggyback satellite, launched as a secondary payload taking the space of a ballast weight and managed to be heard by over 570 amateurs across 28 countries during the 22 days it was in orbit. It was launched just over four years after Sputnik 1 and was built entirely by amateurs for radio amateurs.

    In the sixty years since we've come a long way. Today high school students are building and launching CubeSats and several groups have built satellites for less than a $1,000. OSCAR 76, the so-called "$50SAT" cost $250 in parts. It operated in orbit for 20 months. Fees for launching a 10cm cubed satellite are around $60,000 and reducing by the year.

    If that sounds like a lot of money for the amateur community, consider that the budget for operating VK0EK, the DXpedition to Heard Island in 2016 was $550,000. Operation lasted 21 days.

    I'm mentioning all this in the context of homebrew. Not the alcoholic version of homebrew, the radio amateur version, where you build stuff for your personal enjoyment and education.

    For some amateurs that itch is scratched by designing and building a valve based power amplifier, for others it means building a wooden Morse key. For the members of OSCAR it's satellites. For me the itch has always been software.

    Sitting in my bedroom in the early 1980's, eyeballs glued to the black and white TV that was connected to my very own Commodore VIC-20 was how I got properly bitten by that bug, after having been introduced to the Apple II at my high school.

    I'm a curios person. Have always been. In my work I generally go after the new and novel and then discover six months down the track that my clients benefit from my weird sideways excursion into something or other.

    Right now my latest diversion is the FPGA, a Field Programmable Gate Array. Started watching a new series by Digi-Key about how to use them and the experience is exhilarating.

    One way to simply describe an FPGA is to think of it as a way to create a virtual circuit board that can be reprogrammed in the field. You don't have to go out and design a chip for a specific purpose and deal with errors, upgrades and supply chain issues, instead you use a virtual circuit and reprogram as needed. If you're not sure how powerful this is, you can program an FPGA to behave like a Motorola 65C02 microprocessor, or as a RISC CPU, or well over 200 other open source processor designs, including the 64-bit UltraSPARC T1 microprocessor.

    I'm mentioning this because while I have a vintage HP606A valve based signal generator that I'm working on restoring to fully working. Homebrew for me involves all that the world has to offer. I don't get excited about solder and my hands and eyes are really not steady enough to manage small circuit designs, but tapping keys on a keyboard, that's something I've been doing for a long time.

    Another thing I like about this whole upgraded view of homebrew is that we as radio amateurs are already familiar with building blocks. We likely don't design a power supply from scratch, or an amplifier, or the VFO circuit. Why improve something that has stood the test of time? In my virtual world, I too can use those building blocks. In FPGA land I can select any number of implementations of a Fourier Transform and test them all to see which one suits my purpose best.

    In case you're wondering. My Pluto SDR is looking great as a 2m and 70cm beacon, transmitting on both bands simultaneously. It too has an FPGA on board and I'm not afraid to get my keyboard dirty trying to tease out how to best make use of that.

    What homebrew adventures have you been up to?

    I'm Onno VK6FLAB


    Previous 1 24 25 26 27 28 61 Next

    Related Podcasts

    Ham Nation

    1

    Ham Nation Games & Hobbies
    The Brülosophy Podcast

    2

    The Brülosophy Podcast Games & Hobbies
    Good Job, Brain!

    3

    Good Job, Brain! Games & Hobbies
    Making It With Jimmy Diresta, Bob Clagett and David Picciuto

    4

    Making It With Jimmy Diresta, Bob Clagett and David Picciuto Arts
    Waypoint Radio

    5

    Waypoint Radio Arts
    BeerSmith Home and Beer Brewing Podcast

    6

    BeerSmith Home and Beer Brewing Podcast Games & Hobbies
    footer-logo

    Contact Us

    Toll Free: 844-670-7747

    Links

    • Home
    • Top Charts
    • Networks
    • Apps
    • Independents Podcasts
    • Podcast Advertising
    • Podcast News
    • Contact Us
    • About Us
    • Analytics & Insights

    Stay Connected

      Privacy, Terms of Use & Our Code of Ethics Protecting Content Creators Copyrights