AmateurRadio.com

Summits On The Air (SOTA) operating events are a great way to promote activity and create opportunities for summit-to-summit radio contacts. Here’s the 2016 calendar, an update of the 2015 list suggested by Guy N7UN. Many of these dates are aligned with VHF events but there will be HF activity as well.

• Jan 30-Feb 1: ARRL Jan VHF Contest + NA SOTA Winter Activity Weekend
• Apr 16-17: North America SOTA Spring Activity Weekend
• Jun 11-13: ARRL June VHF Contest + NA SOTA Summer Activity Weekend
• Jul 16-17: CQ WW VHF Contest + optional for SOTA
• Aug 6-7: Colorado 14er Event + NA SOTA Rocky Mtn Rendezvous + W7 SOTA Activity Weekend + ARRL UHF Contest
• Sept 10-12: ARRL Sept VHF Contest + NA SOTA Fall Activity Weekend

Of course, any day is a good day for SOTA activity.  The August 6-7 weekend looks to be the alignment of the planets with four events happening around that weekend. Early August usually offers excellent conditions for hiking the highest peaks in Colorado, so come on out and play.

For more info on VHF SOTA, see How To Do a VHF SOTA Activation.

Get off the couch, put on your hiking boots, grab your backpack, grab your radio but most important: get on the air!

73, Bob K0NR

The post 2016 SOTA Activity Days appeared first on The KØNR Radio Site.

Bob Witte, KØNR, is a regular contributor to AmateurRadio.com and writes from Colorado, USA. Contact him at [email protected].

My new UTC clock on the PC desktop

I have Friday off today and got my running around out of the way this morning, so I decided to flip the radio switch and see what was happening. I was going from band to band around 1600 UTC and there was just stations here and there most U.S stations. Then at 1700 UTC I was listening on 20m and on the Elecraft P3 the lower end of 20m came alive! From only hearing U.S stations to hearing LOTS of  European stations and at first I could not tell if it was a contest or not but it had to be.  I went to WA7BNM contest site and looked things over to see what contest it was while at the same time listening to the contest to see what the exchange was. To be honest I did not have to much luck with either, I really could not make out the exchanges and the web site was not really clear what contest this could had been. As I was attempting to ferret out the contest an old issue came back to me....UTC time! I have an app on my Iphone that gives local and UTC time but more often than not the Iphone is not close by when I need to reference UTC time. The same issue comes up when logging a contact on paper temporally until logging it on the PC. I was going to purchase the MFJ 108B dual LED clock but it was good I held off. It occurred to me to get online and search for something that was a free download on the internet!! I found a neat little program that sits on your desktop. You can resize it, move it around, when you restart your PC it comes alive in the last place it was left when you turned your PC off and best of all it's free!  Have a look at it and see what you think and by all means if you are using another program let me know what it is and I will check it out.
Mike Weir, VE9KK, is a regular contributor to AmateurRadio.com and writes from New Brunswick, Canada. Contact him at [email protected].

I need your help!

Come meet me on the shortwave (HF) ham bands for the Morse code (CW mode) special event, the Straight Key Century Club (SKCC) celebration, with special callsign, K3Y. During the shifts (time slots) listed below, I am the control operator as K3Y/0.

I need you to make a contact with me.

This special event takes place every year during January. We celebrate the legacy of Morse code, and promote Morse code and manual creation of the code by any non-electronic (digital) device and method. Which means that we love mechanical bugs, straight keys, two ends of a wire, or any other manual device, if Morse code is generated. The Straight Key Century Club is a free membership group. The link to their website is below.

I need you to make a contact with me, during my scheduled times, listed below.

NOTE: YOU DO NOT NEED TO BE A MEMBER OF THE (free) SKCC GROUP. To get into my logbook, you meet me on my frequency, and use Morse code to communicate with me. It is painless. If you must, you can use computer-generated Morse code. Or, you can tap it out on any Morse code signalling device, like a bug, a set of paddles, or a straight key; whatever you choose to make Morse code emanate from your HF transmitter.

HOWEVER: For those of you who want to get fully immersed in the spirit of this event, you are invited to use a straight key. And, as a bonus, you may and can join the SKCC group for FREE. Then, you would have your own SKCC number. That’d be cool; we SKCC members use that number in our exchange during our QSO information exchange. But, you don’t need that. Since it is free, why not?

What is needed is simply you, getting on the shortwave band, finding me, hearing me, and responding to me with Morse code. In other words, we need to have a QSO using Morse code. I am not a fast operator, so no problem if you are not very fast. I’ll meet your speed.

In any case, here are some of the times I will be on the air as K3Y/0… please dust off your straight key, bug, paddles, whatever, and make a QSO with me. Thanks!

My current schedule:

UTC Start/End (remember, these are NOT your local times, but are the UTC (GMT) times!)

(revised times, as of edit date)


00:00 - 02:59 19-Jan-16
00:00 - 02:59 20-Jan-16
00:00 - 02:59 21-Jan-16
00:00 - 02:59 22-Jan-16
00:00 - 05:59 23-Jan-16
14:00 - 18:59 23-Jan-16
20:00 - 21:59 23-Jan-16
00:00 - 02:59 24-Jan-16
14:00 - 18:59 24-Jan-16
21:00 - 21:59 24-Jan-16
00:00 - 02:59 25-Jan-16
00:00 - 02:59 26-Jan-16
00:00 - 02:59 27-Jan-16
00:00 - 02:59 28-Jan-16
00:00 - 02:59 29-Jan-16
00:00 - 05:59 30-Jan-16
13:00 - 18:59 30-Jan-16
20:00 - 21:59 30-Jan-16
00:00 - 03:59 31-Jan-16
13:00 - 23:59 31-Jan-16

Now, what frequency will I be on?

To find out what frequency I am on:

Visit http://g.nw7us.us/sched4SKCC and look on the right side for my callsign, NW7US. I usually post my frequency of operation right after my call sign.

Typically, evening operation is 30m, then 40m, and then possibly 80m.

If you are trying to alert me to your presence, you may message me on my personal Facebook profile, under my “Tomas David Hood” profile messages, but I may not see that right away.

Here is the detail covering the K3Y operation and the SKCC group: http://skccgroup.com/k3y

73 de NW7US
dit dit

This was last year:

https://www.youtube.com/watch?v=UfRvITFpTb4

..

..

Visit, subscribe: NW7US Radio Communications and Propagation YouTube Channel

As much as I love CW and try and promote its use on 630m, one cannot deny the growing interest and use of the WSPR mode on our newest ham band.



Its ability to dig deep into the noise and successfully decode signals as weak as -30db makes it an attractive method of watching the night-to-night and hour-to-hour propagation magic.

One only needs to check the number of stations logged into the WSPRnet Activity-page, uploading 630m spots each night ... a typical evening will see 60-80 calls listed.

The main problem with WSPR is that it's a one-way, beacon-only mode and it's not possible to utilize it for a valid two-way contact. It's nice to know that station 'A' is able to hear station 'B', and vice-versa, but the only way for both stations to know this is for them to both be monitoring the internet uploads ... if both stations were able to confirm their respective receptions all via radio, then a two-way contact could be claimed. Thankfully, there is another mode that solves this dilemma, without internet intervention and that's JT9.

JT9, developed by K1JT, is a spin off from his JT65 weak signal QSO-mode software developed for EME. JT9 has been tailored for the noisier HF and MF bands and is apparently, about 2db more sensitive than JT65. In the past, I have made several single-yagi EME contacts on 2m using JT65, with many of these QSO's being in the -27 to -29 db range. This would suggest that 630m JT9 contacts could be made at signal levels as weak as -30db!

A recent "630m Activity Weekend" in Europe turned out be a "630m JT9 QSO Party" with dozens of Europeans working each other throughout the event using this weak signal mode with great success. It looks very much as if JT9 may now be the go-to mode for two-way work on 630m when, as is often the case, signals can be easily seen on a visual waterfall display, but are too weak to be heard on CW.

DC1RJJ's 630m JT9 action courtesy: KB5NJD

On this side of the Atlantic, recent JT9 contacts have been made between several of the U.S. experimental stations. WH2XCR in Hawaii (K9FD/KH6) and WG2XIQ in Texas (KB5NJD) worked on Dec 9th, while WH2XGP (W7IUV), WG2XSV (W0YSE/7) and others have been exploiting the power of JT9 to work around the country.

Such has been the case for me recently, with the arrival of VE3OT on 630m. Since beginning his nightly slow speed CW, QRSS6 beaconing, his signals have been easily visible here every night but only strong enough to hear aurally, on two occasions.  It is likely that we could work each other fairly routinely on JT9 but will need to wait for very good conditions to work on CW.

The good thing about modes such as WSPR and JT9 is that they can be used without the need for linear amplifiers in the PA ... class D or E amplifiers, fairly universal in the LF/MF world, can be employed. The most popular route at present seems to be via a homebrew  transverter that will allow the use of the station's main HF transceiver (using the tone-generating JT9 / WSPR software) to generate the required 630m RF.

I've been looking for a new radio workbench project to catch my interest and building a 630m transmitting converter is beginning to look more attractive, now that we have another DX target in VE3 land ... of course, if and when the U.S.A. gets the band, there will be an entire new crew of stations spread across the continent to keep the transverter busy!


Steve McDonald, VE7SL, is a regular contributor to AmateurRadio.com and writes from British Columbia, Canada. Contact him at [email protected].

It looks like my tri-band Par antenna, which should be a good match on 10m, 20m and 40m is faulty.  It is a good match on 10m, but only on 20m and 40m via the ATU. Tomorrow I shall try loading it up as a long wire tuned against ground via the ATU. Somewhere I have a Sandpiper Poliakov vertical that I should erect. As I recall  this has a 9:1 unun so it matches well on most HF bands via an ATU.

Even soldering on a coax is hard work these days! Oh to be fit.

At the moment I am on 630m WSPR using the earth-electrode “antenna”.

Roger Lapthorn, G3XBM, is a regular contributor to AmateurRadio.com and writes from Cambridge, England.

On 7. November 2015, several radio amateurs in northern California heard echoes in the 80 meter band. I was made aware of it by Jack, W6FB in Santa Clara, who recorded signals from K6YT some 25 miles away. According to W6FB, the echo effect was also heard north of Sonoma (several hundred miles north of him, reported by N6ZFO).

KM6I, Gordon, in Palo Alto also heard echoes of his own signals and recorded them. In his blog he analyzed the delay from the output of his transceiver and found 157 ms. He found that to be so close to the round-the-world time for signals of 138 ms, that he assumed that to be the cause.

I don’t agree, so I took the location of W6FB at locator CM97ah (Santa Clara) as a starting point for computing delay. This is latitude 37.31 and longitude -121.96 and gives a geomagnetic latitude of about 42.5 degrees. Then I put it into my program for computing path length along geomagnetic field lines assuming a height of the reflecting ionosphere on the opposite side of 100 km. The result is shown in the figure and predicts a delay time of 126 ms. My estimate of uncertainty is +/-5 ms.

The delay value is slightly less than 138 ms and easy to confuse with a round-the-world path. The challenge with estimating delays like this from the signal is that amateur transceivers may have an unspecified delay between start of transmission and start of sidetone. Measuring on the audio output as done here, measures the sidetone, not the actual RF.

I discussed this source of error in my 2009 QST article “Magnetospheric ducting as an explanation for delayed 3.5 MHz signals.” Therefore the measurement shown above may fit with 138 ms just as well as with 126 ms, it depends on the actual transceiver’s delay.

Other properties of the echo, such as the amplitude of the echo which according to W6FB at times was louder than the direct signal, also point to the duct theory as the explanation.

Others have heard such echoes also:

• 165-168 ms, K4MOG, February 2006, 80 m. Listen to the signal here. This event is also the object of the analysis in my QST article referenced above.
• 210-220 ms, G3PLX, November 2006, 160 m. Listen to the signal here.
• 214-219 ms, W2PA, February 2008, 80 m.
• 237 ms, OZ4UN, January 2009, 80m, Listen to audio file where also OZ7BQ very close by heard the echoes.
• About 200 ms, G3ZRJ, January 2012, 80m. Also heard by GW3OQK, 100 km apart.

Other posts on the theme: Magnetospherically Ducted Echoes or Medium Delayed Echoes

Sverre Holm, LA3ZA, is a regular contributor to AmateurRadio.com and writes from Norway. Contact him at [email protected].

On 7. November 2015, several radio amateurs in northern California heard echoes in the 80 meter band. I was made aware of it by Jack, W6FB in Santa Clara, who recorded signals from K6YT some 25 miles away. According to W6FB, the echo effect was also heard north of Sonoma (several hundred miles north of him, reported by N6ZFO).

KM6I, Gordon, in Palo Alto also heard echoes of his own signals and recorded them. In his blog he analyzed the delay from the output of his transceiver and found 157 ms. He found that to be so close to the round-the-world time for signals of 138 ms, that he assumed that to be the cause.

I don’t agree, so I took the location of W6FB at locator CM97ah (Santa Clara) as a starting point for computing delay. This is latitude 37.31 and longitude -121.96 and gives a geomagnetic latitude of about 42.5 degrees. Then I put it into my program for computing path length along geomagnetic field lines assuming a height of the reflecting ionosphere on the opposite side of 100 km. The result is shown in the figure and predicts a delay time of 126 ms. My estimate of uncertainty is +/-5 ms.

The delay value is slightly less than 138 ms and easy to confuse with a round-the-world path. The challenge with estimating delays like this from the signal is that amateur transceivers may have an unspecified delay between start of transmission and start of sidetone. Measuring on the audio output as done here, measures the sidetone, not the actual RF.

I discussed this source of error in my 2009 QST article “Magnetospheric ducting as an explanation for delayed 3.5 MHz signals.” Therefore the measurement shown above may fit with 138 ms just as well as with 126 ms, it depends on the actual transceiver’s delay.

Other properties of the echo such as the amplitude of the echo which according to W6FB at times was louder than the direct signal. This points to the duct theory as the explanation.

Others have heard such echoes also:

• 210-220 ms, G3PLX, November 2006, 160 m. Listen to the signal here.
• 165-168 ms, K4MOG, February 2006, 80 m. Listen to the signal here.
• 214-219 ms, W2PA, February 2008, 80 m.
• 237 ms, OZ4UN, January 2009, 80m, Listen to audio file where also OZ7BQ very close by heard the echoes.

Other posts on the theme: Magnetospherically Ducted Echoes or Medium Delayed Echoes

Sverre Holm, LA3ZA, is a regular contributor to AmateurRadio.com and writes from Norway. Contact him at [email protected].