KM9G Reports On New Phonetic Alphabet

Amateur radio has a long tradition of innovation concerning technology and radio operating practices. This includes innovating with the use of phonetic (or fonetic) alphabets, as previously reported here: Twisted Phonetic Alphabet

Today, April 1st, Steve/KM9G reports on the latest set of fonetics from the AFRL:

The post KM9G Reports On New Phonetic Alphabet appeared first on The KØNR Radio Site.

VHF Range From SOTA Summits

When doing VHF activations for Summits On The Air (SOTA), the radio range is dependent on the height of the summit and the surrounding terrain. The Radio Mobile website from Roger/VE2DBE is a great tool that can be used to estimate the radio range from a particular site. Repeater system owners often use tools like this to predict the coverage of their repeaters. I don’t normally do this type of analysis for SOTA…I just look at a topo map and get a rough idea of how far my signal will go. Then, I decided to spend a little time analyzing a few summits in Colorado to see what I could learn.

Pikes Peak (W0C/FR-004)

Pikes is a 14,115-foot summit that towers over the eastern plains of Colorado, making it an ideal radio site. The Radio Mobile plot shown below shows the solid radio coverage in blue and the fringe area in yellow. I won’t go into how to use Radio Mobile on this post. As you’d expect, you enter the location of the radio site (summit) along with various parameters such as frequency, minimum detectable signal level, transmit power, and antenna gain. I entered some nominal parameters consistent with typical SOTA stations on 146 MHz (2 meters).

VHF coverage prediction for Pikes Peak (W0C/FR-004)

Pikes covers about half of the state of Colorado, reaching out to the Kansas state line. To the west, the coverage does not go as far because the radio signals are blocked by other mountain ranges. In particular, the signal tends to drop off at the Sawatch Range, west of Buena Vista. I’ve activated Pikes many times and this plot lines up well with my general experience. The blue area can be worked quite reliably with a decent station on both ends. By “decent” I mean a 20-watt transmitter on the summit with a small Yagi antenna and a 40-watt radio with an omnidirectional antenna at the chaser station. Working stations near the Kansas state line is usually easy on 2m FM. The highest spot in Kansas (Mount Sunflower, not a SOTA summit) can usually be worked without much trouble. However, longer distance contacts are possible, especially using SSB or CW. I’ve written before about the Myth of VHF Line-Of-Sight.

When using VHF for SOTA activations, It is important to consider the potential stations that will be within range and on the air for you to work. Besides being a high summit, Pikes overlooks the major cities in Colorado, from Fort Collins to Pueblo, so finding someone to work on 146.52 MHz is usually easy. It is common to have a pile up of stations calling you.

Colorado has over fifty 14,000-foot mountains and all those are workable from Pikes Peak on 2m FM.

Mt Herman (W0C/FR-063)

Mt Herman is another popular SOTA summit, with an elevation of 9063 feet, not nearly as high as Pikes Peak. This summit also looks out over the eastern plains of Colorado, as shown in the coverage plot below. Although the range is not as good as Pikes, it still covers the major cities, so again it is easy to do a 2m FM activation from Mt Herman. It is more difficult to work stations to the west. I can usually work stations in Woodland Park and Divide from Mt Herman, but reaching Buena Vista is a challenge.

VHF coverage prediction for Mount Herman (W0C/FR-063)

Threemile Mountain (W0C/SP-107)

VHF activations can be much more challenging when the summit is further away from populated areas. Let’s consider Threemile Mountain, which is 10,020 feet in elevation, located about 20 miles south of Hartsel, CO. This summit tends to get blocked to the east by the Front Range and to the west by the Sawatch Range. Even though the summit is higher than Mt Herman, its radio range is not as good.

VHF coverage prediction for Threemile Mountain (W0C/SP-107)

In particular, it does not cover Denver, Colorado Springs, and Pueblo very well, so the number of available stations to work drops dramatically. There are a number of stations that monitor 146.52 MHz up in the mountains, so if you are patient you can usually make some VHF contacts. This can be a source of frustration for VHF activators, or you can take it on as a challenge.  I have activated Threemile five times and I don’t think I’ve ever worked a Denver station on 2m FM. I have worked some Denver stations from there using 2m SSB, during a VHF contest. Oh, I did manage to work Larry/N0LL in Smith Center, KS on 2m SSB for a distance of 372 miles. See Radio Fun on Threemile Mountain (W0C/SP-107). So you never know what you’re going to get on VHF/UHF.

Conclusions

So what conclusions can we draw from this analysis?

  1. Radio Mobile does a good job of predicting typical 2m FM coverage. My experience on these summits aligns well with the Radio Mobile predictions.
  2. But much longer distance contacts are still possible. VHF is not limited to line of sight. Radio Mobile is intended to predict reliable radio coverage, not the exceptional radio contact.
  3. Be aware of the population density of the coverage area because that is a huge factor for making radio contacts. New VHF activators should start on summits that overlook the major Colorado cities.
  4. Improve your VHF activator station. Every additional dB of signal improves your ability to make those weak-signal contacts on the edge of the coverage area.

As always, get off the couch, gather your radio gear, and head for a summit.

73 Bob K0NR

The post VHF Range From SOTA Summits appeared first on The KØNR Radio Site.

Combined Logging for SOTA and POTA

Doing a simultaneous activation of a Summits On The Air (SOTA) summit and a Parks On The Air (POTA) park is becoming more common. There is a lot of crossover between the two programs. Here in Colorado, many of the SOTA peaks are in national forests or national parks, making them an ideal double activation.

Creating one file for logging both programs can be a challenge but I’ve settled in on an approach that works for me. I’ve decided to use HAMRS for this, whether it is real-time logging or transcribing a paper log after the event. HAMRS provides useful templates for both SOTA and POTA, but not both simultaneously. HAMRS still has a few quirks on entering callsigns and timestamps, but I am hopeful those things will get addressed in the fullness of time. If you are using a different logging program, you can probably still benefit from this post.

I wrote about the different ADIF fields that POTA and SOTA use here:

More Logging Tips for SOTA & POTA

Simplest Case: No P2P or S2S

For an activation that does not involve making contact with other parks or summits, the logging requirements are simple. POTA refers to these contacts as Park-to-Park or P2P, while SOTA refers to them as Summit-to-Summit or S2S. Same basic idea.

The ADIF file for POTA needs to have the usual logging information but the special POTA fields (MY_SIG_INFO, SIG_INFO) can be left blank. The filename will indicate the park you are operating from and must meet the standard POTA format. (Example: K0NR-K-4404-20211017.adi for K0NR operating from K-4404 on 17 Oct 2021). If you do have some simple P2P QSOs in there (one park contacting another single park, no double activations), the POTA database will attempt to identify these contacts by comparing the logs of the two POTA activators. I believe this works pretty well but I have not tested it extensively.

For the SOTA log, you must provide your SOTA summit using the MY_SOTA_REF field. If you use the HAMRS SOTA template, it will take care of this for you. Then you can use the same ADIF file for POTA by setting the filename to the right format. If you need to add the MY_SOTA_REF manually, ADIF Master is a good tool to use.

With P2P or S2S

When there are P2P or S2S contacts, things get a bit more complicated. The ADIF log needs to have MY_SIG_INFO for each QSO set to your POTA number and SIG_INFO set to the other station’s POTA number. If the other POTA station is activating more than one park, this can be handled by entering multiple QSOs in the file. (I think this is the cleanest way of handling it, but let me know if you have other methods.)

The SOTA logfile requires something similar, with MY_SOTA_REF set to your SOTA summit and SOTA_REF set to the other station’s SOTA summit.

One ADIF can be created that has all four SOTA/POTA fields set correctly but you’ll probably have to use ADIF Master or a text editor to get this all entered. HAMRS can help you with either SOTA or POTA, using the corresponding template. Normally, I try to determine if I have more P2P or S2S contacts and choose the template (POTA or SOTA) with that in mind. Then, I use ADIF Master to add in the other -OTA program logging info.

POTA does allow for simultaneous activations of more than one park. For example, the Continental Divide Trail is considered a park and it often runs through a national forest, so both can be activated together.) If you are activating more than one POTA park, you will need to create a log file for each park and submit them individually. A SOTA activation can only be from a single summit.

Wrap Up

I treat my SOTA/POTA logs as separate files but I also import them into my master logging program, which is currently Log4OM2. I also upload the file to Logbook of The World (LoTW). It is important to set up a new LoTW location with the grid locator, state and county set correctly. This may create a long list of locations in your LoTW account but provides proper confirmation for stations chasing grids, states, and counties.

These are some things I’ve learned along the way and I hope you find them useful.

73 Bob K0NR

The post Combined Logging for SOTA and POTA appeared first on The KØNR Radio Site.

Where is the RF Digital Multimeter?

One of the most useful electronic test tools available to us is the digital multimeter (DMM). There are many different models to choose from but for less than $50, you can get a decent quality meter that measures DC and low-frequency AC voltage, current, and resistance. Using such a meter, with auto-range capability, is pretty much a matter of selecting the desired measurement function and connecting up the test leads. It is a really simple, but effective measurement device.

So where is the radio frequency (RF) equivalent of the DMM? There are some excellent multifunction RF/microwave instruments such as the Keysight FieldFox analyzer. But these professional instruments are much more expensive than a DMM and much more complicated. I am thinking of something that has the same Select-and-Connect usability of a DMM.

Low-Cost RF Instruments

In recent years, low-cost RF instruments have emerged that can make some impressive measurements. The first one that comes to mind is the nanoVNA, a compact vector network analyzer. There are several different models available but a typical configuration covers two-port measurements from 10 kHz to 1.5 GHz, at a price of around $70. The nanoVNA is quite capable, able to measure two-port s-parameters (reflection and transmission), return loss, standing wave ratio (SWR), etc.

More recently introduced, the tinySA spectrum analyzer offers basic spectrum analyzer measurements from 0.1MHz to 960 MHz. The cost is ~$60 and the SA includes a basic signal generator feature.

I own both of these devices and I think they are excellent instruments for the price. But they aren’t what I am looking for in an RF DMM. They do provide a proof point that simple and affordable RF instruments are possible.

Another device that has caught my attention is the Surecom SW-33 SWR / Power meter. This tiny meter is great for tossing into my SOTA backpack or radio Go Kit, to have some basic RF measuring capability in the field. It covers 125-525 MHz, up to 100 watts (with an appropriate dummy load or antenna), for less than $50.

But it only measures SWR and power. Not bad but not quite everything I’d like in my RF DMM.

Antenna analyzers are another category of affordable RF test equipment. As the name implies, they are focused on making measurements on antenna systems. Again, there are many different models to choose from, ranging in price from about $100 to $500. Shown below is the RigExpert Stick 230-K with a bit of a simple DMM look to it. The primary antenna measurement is SWR, but the antenna analyzers often include complex impedance, return loss, reflection coefficient, etc.

The RF DMM

OK, Bob, what is it that you do want in an RF DMM? Good question. Thank you for asking.

The device I have in mind should cover the common RF measurements that a typical radio amateur needs to perform. In terms of the use model, consider what is needed to check out a new radio installation, from the transceiver to the antenna. I want to be able to check the transmit power, the impedance looking into the coaxial cable, the SWR (and return loss) of the antenna system across the typical ham bands (160m through 70 cm).

So here is the wish list:

  • Frequency Range: 1 to 450 MHz
  • RF power meter (directional, inline measurement)
  • RF power meter (with internal dummy load)
  • Antenna measurements (SWR, Return Loss, complex impedance, other derived values)
  • Frequency counter
  • Basic signal generator (produce a sine wave at a particular frequency)
  • Probably an N connector for ruggedness and good match at UHF frequencies. However, an SMA connector would have the advantage of small size and might be more appropriate.
  • Price: <$50

I initially left out the signal generator but the antenna measurements will generate a test signal, so having a simple signal generator is not a big stretch and can be very handy. A couple of bonus features could be the measurement of FM deviation and decoding of CTCSS frequencies. I think these can be added at minimal cost but they are a nice to have feature, not mandatory.

I included an internal dummy load for simple RF power measurements. It is really handy to be able to check power level independent of the antenna system. This raises the issue of what power level it will support and for how long. It would be great to be able to measure 100-watt transmitters for a short period of time but that may be inconsistent with a low-cost, handheld device. A 5-watt dummy load should be easy and maybe a bit more…perhaps 25 watts? Of course, external attenuators can be used for measuring higher power.

It will be tempting to include frequency sweeps of the various parameters but simplicity should be the top priority, so the RF DMM probably only measures one frequency at a time. Leave out the fancy display, analogous to how a typical DMM does not provide an oscilloscope display.

It is also tempting to include standard DMM features in this device, so you’d have one meter that covers all of the basic ham measurements. Given the availability of inexpensive DMM integrated circuits, this would not be a big stretch. This would require separate DMM inputs (banana jacks). Perhaps skip the current measurement capability and just have DC/AC voltage and resistance? But everyone already has a normal DMM, so I see these features as optional.

The price point may be aggressive but the idea is to make it cheap enough that most radio amateurs own one, or several. Keep one in your Go Kit, one at home, and one in the car (similar to a DMM).

So that is my idea for an RF DMM. What do you think?

73 Bob K0NR

The post Where is the RF Digital Multimeter? appeared first on The KØNR Radio Site.

Get Your Ham Radio License, Colorado

The Technician license is your gateway to the world-wide excitement of Amateur Radio, and the very best emergency communications capability available!

We are once again offering our highly-successful Technician License Class in Monument, Colorado.

 

  • Earn your ham radio Technician class radio privileges
  • Pass your FCC amateur radio license exam right in class on the last day
  • Multiple-choice exam, No Morse Code Required
  • Learn to operate on the ham bands, 10 meters and higher
  • Learn to use the many VHF/UHF FM repeaters in Colorado
  • Find out how to participate in emergency communications

Schedule

Online + In-Person in Monument, Colorado

Sat   April 2    1 – 5 PM In Person

Sun  April 3    1 – 4 PM Online

Tue  April 5    6 – 8:30 PM Online

Sat   April 9    1 – 5 PM In Person (includes Exam)

 

Online sessions will be held using Zoom.

The in-person sessions will be at Woodmoor Community Center (Woodmoor Barn) in Monument, CO.

Registration fee: $30 adults, $20 under age 18
Advance registration is required.

 

Students must have the required study guide:

HamRadioSchool.com Technician License Course

Third Edition, 2018 – 2022

Register

To register for the class, go to:

http://w0tlm.com/radio-classes/tech-registration

Any questions, contact Bob Witte KØNR [email protected]

Sponsored by the Tri-Lakes Monument Radio Association www.w0tlm.com

For more information on amateur (ham) radio visit www.arrl.org

The post Get Your Ham Radio License, Colorado appeared first on The KØNR Radio Site.

How’s That North America Adventure Frequency Working?

In January 2021, I wrote about the North America Adventure Frequency (NAAF) which originated in the North America SOTA community. About a year later, how is this working out? Is anyone actually using it?

 

 

A few key points to remember:

  • The NAAF is 146.58 MHz.
  • This frequency is in addition to, not a replacement for, the National Simplex Calling Frequency 146.52 MHz.
  • Local usage will likely vary depending on needs.
  • Program 146.58 MHz as The Other Simplex Frequency in your radio.

I’ve noticed that quite a few SOTA activators are posting Alerts and Spots with 146.58 MHz. For example, K2CZH and KN6OUU posted these SOTA Alerts:

Here N8FN and WJ7WJ are spotted on 146.58:

Of course, the National 2m FM Calling Frequency (146.52 MHz) still gets a lot of use. I tend to use Five Two when I am activating in rural areas, some distance from the major cities. The frequency is usually quiet AND there are a number of folks that tend to monitor it. I use the NAAF when I’m near the big cities (Denver, Colorado Springs, Boulder, …). Putting out a Spot is usually important, to get the attention of the more dedicated SOTA chasers watching SOTAwatch. That is, I don’t think there are a lot of people monitoring the frequency (compared to 146.52), so a spot on SOTAwatch gets them on frequency.

Some of the Parks On The Air (POTA) activators are also using NAAF. Here’s an activation alert by KD7DTS from the POTA website:

So I think the NAAF is working as intended. It is not a replacement for 146.52 MHz but a standard choice for portable operating when you want to stay off the calling frequency. Thanks to everyone that has given it a try.

73 Bob K0NR

The post How’s That North America Adventure Frequency Working? appeared first on The KØNR Radio Site.

More Logging Tips for SOTA & POTA

I previously wrote about some of the tools I use for managing SOTA and POTA logs. See Tips and Tools for Managing Logs. I continue to learn about the file formats and various tricks for generating the logs. Some of this is not well-documented…at least I haven’t found it…so I am sharing what I’ve figured out. My apologies in advance if I get any of this wrong. Reader Beware!

Lately, I’ve been trying to figure out how to do one log file for both SOTA and POTA. I am not aware of a logging program that will handle both simultaneously. (Let me know if you do.)  The ADIF file format can handle this and is the way to go for such a log file. Also, an ADIF file can be imported into other logging programs and Logbook of The World. The complete documentation for ADIF can be found here: https://www.adif.org/

SOTA Logs

Our combination SOTA + POTA activations usually start out as a SOTA activation. Then, if the SOTA summit is inside a POTA-designated park, we may try to do both simultaneously.

The SOTA database supports uploading ADIF files, including support for Summit-to-Summit (S2S) contacts. The figure below shows a recent SOTA log, in ADIF format, displayed by ADIFMaster. The 6th column is MY_SOTA_REF, which is the SOTA reference for the summit I was activating. In this case, it was W0C/SP-084 and is the same for all of the QSOs. The 9th column is SOTA_REF, which is the SOTA reference of the other station’s summit, if any. Most of the rows are blank, because the other station was not on a summit. However, N0TZW and N3ALT were on W0C/PR-031 that day resulting in a pair of S2S contacts. If you get these fields set correctly in the ADIF file, the SOTA database will log the activation and the S2S contacts correctly.

POTA Logs

For simple POTA activations, you just need to get the QSO information correct and the file name indicates the park you were operating from. For example, the file name K0NR-K-4404-20211017.adi indicates the station callsign (K0NR), operating from park K-4404 on 17 Oct 2021. The POTA system will try to identify Park-to-Park (P2P) radio contacts in the file, by comparing activator logs. My understanding is that this works only for the simple case of two activators, each operating from only one park.

The figure below shows a POTA log using ADIFMaster. The 7th column is MY_SIG_INFO, which is the POTA designator (K-8295) for the park I was activating. This is the same for all of the rows. The eleventh column is SIG_INFO, which is the POTA designator for the other station. Most of these are blank because the other station was not in a park. However, there are six QSOs shown that were Park-to-Park. Note that the QSO with N7OOS was entered twice, with two different park numbers. This is because he was doing a double activation that day…putting two parks on the air at the same time. Yes, activating multiple parks at once is possible, even common, in POTA. A good example is when a national scenic trail runs through a national forest. One operating location is in both parks simultaneously.

It might be possible to have two POTA designators tagged to one QSO, I am not sure. But I think it is cleaner to just enter it as two separate QSOs. I know the POTA database will interpret it correctly. When I imported the file into Logbook of The World, it complained there were duplicate QSOs, which were easily ignored.

The 6th column in the figure is MY_SIG, which indicates a special interest activity or event (e.g., POTA). In the general case, the logging program would use this field to interpret the meaning of SIG_INFO and MY_SIG_INFO. It appears that the POTA system does not require MY_SIG to be set to POTA and will just go ahead and interpret SIG_INFO and MY_SIG_INFO for POTA use. Not shown is another field called SIG, which is the special interest activity or event of the other station.

Creating a SOTA/POTA Log

When doing a combination activation, I’ll set up the logging program for SOTA or POTA based on whether I expect to have more S2S or P2P radio contacts. For example, if I just expect to work a few summits and many parks, I’ll use HAMRS with the POTA template. That way, all of the parks get entered correctly from the start. I will note any S2S contacts in the comment field and come back later to fix them.

The easiest way to manage ADIF files is via ADIF Master. You can also edit the files manually using a basic text editor but that can be error-prone. To add a new field in ADIF Master, you insert a new column (right-click on a column, then left-click insert column). Then create a label for the column by right-clicking the top of the column, followed by Custom, entering the name of the new ADIF field.

Here’s the short list of ADIF fields that may need to be used:

MY_SOTA_REF is your SOTA reference, the summit you are activating

SOTA_REF is the SOTA reference for the other station, assuming its an S2S radio contact. If you submitting a Chaser log, this is the SOTA reference for the summit you are chasing. Your MY_SOTA_REF would be left blank.

SIG is the name of the contacted station’s special activity or interest group (e.g., POTA)

MY_SIG is your special interest activity or event (e.g., POTA)

MY_SIG_INFO is your park number that is being activated.

SIG_INFO is the park number for the park you are working (P2P).

By editing my log files using ADIFMaster, I’ve been able to create log files that can be submitted to SOTA, POTA and LoTW without errors. It takes a little bit of work to get the file right. Before you submit a log file, it is always a good idea to view it using ADIFMaster, to try and spot any obvious errors. This is especially useful for POTA logs, when the turnaround time can take up to two weeks.

This is what I’ve learned. How about you?

73 Bob K0NR

The post More Logging Tips for SOTA & POTA appeared first on The KØNR Radio Site.


Subscribe FREE to AmateurRadio.com's
Amateur Radio Newsletter

 
We never share your e-mail address.


Do you like to write?
Interesting project to share?
Helpful tips and ideas for other hams?

Submit an article and we will review it for publication on AmateurRadio.com!

Have a ham radio product or service?
Consider advertising on our site.

Are you a reporter covering ham radio?
Find ham radio experts for your story.

How to Set Up a Ham Radio Blog
Get started in less than 15 minutes!


  • Matt W1MST, Managing Editor