The Role of Respect in Radiosport - Part 4

This is the 4th installment of the WQ6X contest BEEFs BLOG.
You may recall:

1. Part 1 was a potpourri of BEEFs; a Beefy Potpourri.
2. Part 2 brought us a look at the technology side of 40-meter QRM. 
   This included an encounter with an Indonesian Witch Doctor.  I KiD you NoT.
3. Part 3 was another potpourri opening with a look at CW on steroids
   and ending with a look at stations who GIVE UP.

Part 4 is largely about the world of SO2-R operators who haven't a clue.
However first, let's begin Part 4 with a look at operators who waste everybody's
time by sending large amounts of unnecessary exchange data.

BEEF #16 - CW STATIONS WHO SEND 599+ EXCHANGE EVERYTIME I ASK FOR ONLY A SPECIFIC PIECE OF INFORMATION
One of the BiGGesT wastes of time in radiosport contests is sending unnecessary information.
A not insignificant number of contests have us send "599" followed by an additional piece of information; typically, a Serial #. To be in compliance with contest rules, I send a "599" for
every contact (but only once per QSO).

Under N1MM+ I define Function Key F6 to send "UR NR?" and F7 to send "NR 1234".
Sending a minimal amount of information is very important when the receiving end is
experiencing medium-fading.

When I send "NR?" and you send "599 1234", what usually happens is I hear the 599 VERY LOUD just in time for the signal to fade when you send me the number. This causes me to ask for a repeat AGAIN and AGAIN; whereas, if you JUST sent "1234", I would get it the first time and we can then BOTH move on. Is that so difficult for people to understand? It MUST be because most people
make this most fundamental of radiosport mistakes. WAKE UP PEOPLE!


 
























BEEF #17 - STATIONS WHO DON'T WAIT AT LEAST 1.5 SECONDS BETWEEN RUN QSOS LISTENING FOR CALLERS BEFORE MAKING ANOTHER CALL
When I run a frequency during a contest, after EACH QSO I take a 2 second pause, listening
for other callers. Doing this prevents me from having to make a lengthy CQ call when there are stations ready and waiting to make a QSO.

When I am calling a run station, IMMEDIATELY after he concludes his QSO I press F4 to send my call. Often when the rig is back in receive, he is in the middle of calling CQ (we both transmitted at
the same time). I call him the second time and comes right back to me.

HuH? If you had waited JUST 2 seconds you would have heard me calling you and there would
be no need to call another CQ until AFTER we make our QSO. The bottom line is PATIENCE.
Getting ANXIOUS actually slows things down rather than improving operating efficiency.

  
BEEF #18 - SO2-R OPERATORS WHO DO SUCH A POOR JOB RUNNING THINGS THAT "BOTH" FREQUENCIES END UP WAITING
While I have mixed feelings about running SO2-R in contests (as long they are in their own separate category I don't mind them), my BIGGEST problem with SO2-R are the operators who THINK they are SO2R-Aces, when in fact, they are just beginners.
 
Nothing is MORE annoying than hearing an S-9 "CQ contest" call and not only does he not come back to me, he responds to no one else either. After sending "WQ6X" 3 separate times, if there is
no response, I send "QRL?" 3 separate times. If there is STILL no response, I press F1 to call CQ
and the frequency is mine; unless of course NOW the Idiot wakes up and blindly calls CQ without
first listening to see whether or not the frequency is in use (a violation of FCC rules which require
we listen BEFORE transmitting).

When that happens I intersperse [F1] CQ calls with [F9] QRL QSY messages. 

What if the reason they were delayed was because of an equipment glitch? TOO BAD.
If you're having equipment problems, then fix them off the air; not at our expense.

BEEF #19 - SO2-I - SINGLE-OP TOO IDIOTIC
A variation of the above complaint is the Dingle-Dork (usually during his state's QSO party)
running a CW frequency (VFO-A) and an SSB frequency (VFO-B) - (in many contest events
this is forbidden).

I remember one day waiting "in line" to work a QSO party station on CW. After each QSO he would ask: "SSB? QSX 14222.22". Next thing WE discover he was now using VFO-B to make a ragchew-style QSO party contact, leaving US stranded on the Cw frequency with the line getting longer.
(I was listening to the SSB frequency with the FT-1000mp's Sub-RX).

After no replies to my 3 "QRL?" queries, I started calling CQ for HIS QSO party signing as "WQ6X/CA". When he blindly came back on frequency I pressed the [F9] key, letting him know the frequency was now in use. The amazing thing is, he actually yielded the frequency over to me - I can at LEAST credit him for that.  Nevertheless, I registered a complaint with the QSO party sponsor.

What is even MORE amazing is that I managed 5 QSOs from his state in that original pileup which included some of his state-buddies; ALL of which he could have worked for QSO point credit had he JUST stuck to running CW (Cw QSOs are worth more points than Ssb).
 
 

BEEF #20 SO2R-NL - SINGLE-OP 2-RADIOS - NOT LISTENING
Similar to BEEF #17 is the SO2-R IDIOT with an S9+ signal who calls CQ TEST with
a 1-second pause in between each call.

Realize it takes me at least TWO seconds to press the [F4] key sending my callsign. It's clear
that this operator is simply keeping this frequency busy (which is against most contest rules).
My solution?: QRLx3 and then I just "MUSCLE" in on the frequency and call CQ. When he complains the frequency is in use, I say "no it isn't - I called you 5 times and you didn't respond. If my signal is so loud that I am QRM'ing you then why did you NoT respond to my call?"

 
SOME LAST MINUTE THOUGHTS
wOw!  What began as a single Top-10 contest beef BLOG entry has become a 4-part Top-20 BLOG series.  Instinct tells me that before the summer is behind us I will have enough material for a 5th
(and possibly 6th) BLOG entry in this series.

What are YOUR Beefs in Radio sport? 
e-Mail your ideas to me and I can include them in Part 5 or 6.

 

The Role of Respect in Radiosport - Part 3

This is the 3rd installment of the WQ6X contest BEEFs BLOG.
You may recall:

1. Part 1 was a potpourri of BEEFs; a Beefy Potpourri.
2. Part 2 brought us a look at the technology side of 40-meter QRM. 
   This included an encounter with an Indonesian Witch Doctor.
   I KiD you NoT.

Part 3 is another potpourri, but of a radically different kind.
Let's begin Part 3 with a look at CW on STEROIDS.

BEEF #11 - CW STATIONS WHO RUN CONTESTS AT 35+ WPM
Sending code so FAST that no one can understand it is NoT (I repeat, NoT) CooL. 
Every CW contest there are a handful of stations who like to call CQ contest at 35+ WPM;
one guy was clocked at least 38 WPM! This is complete NONSENSE. The guy at 38+ called
and called and no one came back to him; probably because they could not decipher his callsign.
I put QRSPSE in the callsign field and pressed F5 after every call he made until he got the
message. Eventually he slowed down to about 30 WPM allowing me to give him a QSO,
followed by 8 more contacts.

Remember this: your CALLSIGN advertises that you are "open for business". If we can't copy your call then we can't work you; or, we will enter your callsign incorrectly in the log.  Either way, you don't get the QSO. I NEVER run faster than 25WPM and immediately slow down when a significantly slower station calls. What about you?


  

BEEF #12 - STATIONS WHO SEND WQ6? AND THEN WORK SOMEONE COMPLETELY DIFFERENT; EX: KB1XYZ
HuH? Why did you give up on me and work someone else?
When I get a partial callsign I keep with that station until a QSO is made.
I will keep sending "WQ6?" again and again until all the other IDIOTS shut up and let me
finish the current QSO.  It's really THAT simple.
When I send "WQ6?", if you don't have a WQ6 in your call then SHUT UP!!! OK? 
It's really as simple as that.

 

BEEF #13 - STATIONS WITH CHOPPY ENGLISH
This is another variation of the previous BEEF. Your callsign is your trademark.
If we can't understand you, your call will never make it to the log correctly. Now, I AM impressed by
non-English speaking operators who make an attempt at using English during Radiosport contests. However, saying your callsign correctly and intelligibly is SO important that you should practice
it OVER-and-OVER again BEFORE the contest. 
Recording your rehearsed-voice in a .WAV or .MP3 file allows you to play it  through your transmit audio over and over again.  If necessary, have someone ELSE (whose voice is similar to yours) say your callsign and YOU record him/her.

In years past I have made .WAV files such as "November Xray SIX Tango - SIX Tango"
or "Whiskey Quebec SIX Xray - SIX X-ray".


 

BEEF #14 - STATIONS WHO GIVE UP
When stations are weak or fade out in the middle of sending a number, I am forced to ask for a repeat. When I ask: "NR?" I want ONLY your number, NOT "599 + Number".   If signal fading is significantly choppy, when you ALSO send the signal report again (which I did NOT ask for),
then what we get is this: "5 9 9 - 1 2 @ & 4". Is that 1234? or 124? or?
I will continue to send "NR?" until I get your number. I am a patient operator and you should be too.
Don't give up on me after 3 INCORRECT responses to my "NR?" request; learn to do it the right way and I will get everything on the FIRST repeat. To make things easier on my end, when running N1MM+ I define function key [F6] to send "NR?" and [F7] to send "NR 1234" when sending
YOU my number.


 

BEEF #15- MULTIPLE STATIONS WHO GIVE UP
Consider the following scenario.  I call CQ contest on a run frequency and have 7 stations all respond to the CQ call.  I select one of those stations to work and spend about 10 seconds making contact with this station as we both send our exchanges.  At the end of the QSO, I press F3 to send "TU WQ6X" waiting for the next caller, only to be met with SILENCE.

HuH?  WTF?  Where did EVERYBODY go?  Why would you call me and then disappear? 
Do you mean to tell me you can't wait 10 - 15 seconds to make a QSO with me.
I make another CQ call and this time 5 stations call me.  I spend 10 - 15 seconds making that
contact and press F3 ("TU WQ6X") and AGAIN everybody disappears.  Are there REALLY that
many unworked stations that you can't wait your turn for the next QSO?  Am I missing something?


SOME FINAL THOUGHTS
What all the above BEEFs have in common is that the people I described were all not paying
attention and/or have no clue about what to do in a radiosport event.  This is why the first step towards  participation in any competition is to read the rules THOROUGHLY - find out specifically what the rules allow and what they don't; otherwise not only do you waste YOUR time, you waste
the time of the stations you incorrectly attempt to contact, as well as other stations legitimately
waiting their turn.

What is the first step you take before a radiosport event?
There is a 4th Part to this series.  [CLICK HERE] to read that.

For WQ6X - All Asian is All Over the Place

One of the things I like about radiosport is its seeming predictability.
Every event has some sort of repeating time-frame; usually the same weekend of a given month.

WQ6X equipment configuration @ W7AYT

In years passed, I have consistently run some contests (such as JIDX & WPX) from NX6T's station
in Fallbrook; other GiGs (like the November Sweepstakes) from W7AYT's QTH in the ARRL East
Bay section.  Other contests (such as the ARRL Dx GiG) have been run mostly remotely. 
Where I called in remotely from has varied widely; from Las Vegas and Laughlin
Nevada to hotel stops along Highway 101in California.

While all different, these events at least have a semblance of repeatable, predictability. 
Then, 2018 made the scene.  Thus far this year, contest GiGs I shoulda run onsite (@NX6T)
ended up being run remotely while other GiGs normally run elsewhere ended up as ad-HOC operations from W7AYT.

WQ6X remotely running the dinner shift @ NX6T

For the 2018 All Asian Cw GiG, the original plan was to join the NX6T crew LIVE from Fallbrook,
while taking time out to attend a wedding, also in Fallbrook.  Last minute client changes in Alameda sidelined the trip to Fallbrook.  Instead, I spent the weekend @W7AYT's QTH in Concord; the idea being to help put Asian QSOs in NX6T's log (WQ6X made nearly 300 QSOs out of the 900+ total).
In the [so-called] off hours look for Asian signals arriving in Concord.

One of the biggest frustrations in this Asian event was the dozens of non-Asian calling stations to
my CQ calls.  Because the F/B-ratio on a 2-element 40-meter yagi is not all that spectacular, NX6T was quite loud in the Southeast.

Surprisingly however, I received numerous calls on 20-meters from stations all over Europe,
even though Europe is geographically to the Northeast while Asia is to the Northwest.  Sending "ASIAONLY" usually sent most non-Asian callers on their way.  For those stations that persisted
I sent "599 55", ignoring whatever they sent in return.  Pressing Ctrl-W wiped any remnants from
the log.

N6CY (Rick) & N6KI (Dennis)

Due to a shortage of available Cw operators, Rick (N6CY), Dennis (N6KI) and WQ6X all did double (and even triple) duty.  Our dedicated cooperative effort made all the difference.

While running extra duty shortened
my operating time as WQ6X, it was well worth it.

Sometimes we seem to make even more contacts when under the pressure of an operator shortage.

Antennas @ W7AYT

As it turns out, a number of GooD openings to Asia made their way to Fallbrook.  Unfortunately, less than a dozen Asian signals made it too the made it to the FT-1000mp front-end.

Using the upgraded WQ6X Lazy 8JK Sloper and a Comet CH-250 vertical; sometimes individually and sometimes
in parallel.

There were so few Asian stations heard that I am beginning to think that W7AYT's QTH has a charged RF barrier-shield blocking signals from the northwest.

In the past, attempts to run All Asian and JIDX contests from this location have been frustrating operations, at best.  Then again, openings to the southeast (even tho blocked by trees) seem quite good from this location.





While this year's All Asian
GiG was full of frustrations, there
were a number positive surprises.
Because signals from the middle east are so rare in Fallbrook, for this contest
I pointed the Yagi's due North during greyline periods.

At one point, manually tuning around
20-meters I happened onto a Very
LOUD station tuning up.  Once finished the station identified as: 4X70A. 


An immediate call to him put 4X70A into the log.  Within 30 seconds there were 50+ North American stations calling.  I got lucky on that one.

When it was all over, it looks as if NX6T took 1st place worldwide for the high power Multi-OP
Single-Transmitter category; at least according to the 3830 Scores website it would seem that way.
[CLICK HERE] to see the 3830 results.

JUNE 9th 2018 Follow-UP:
I received an e-mail from N6KI (Dennis) with the following certificate attached:

 

 

I guess the Three Stooges aren't so stoogie after all!



The Role of Respect in Radiosport - Part 2

I opened the first installment of this contesting series with the following quote:

"In radiosport, indeed during ALL on-the-air activities, in my mind, it goes w/o saying that respect for others should be an over-arching trait representing our on-air decorum."

Unfortunately, because ham radio operators are people too, they sometimes say/do some rather WEIRD things on the air; especially during radiosport contest events.  This 4-part BLOG entry series gives me an opportunity to air out the dirty laundry often lurking at the depths of [often] worldwide competitions.

In the first BLOG of this series we had BEEFS #1 --> #5.
[CLICK HERE] to read Part I of this series.

In this issue we will continue with BEEFS #6 --> #10, beginning with a pesky little
"creature" known as the WooDPecker.

BEEF #6 -  OVER THE HORIZON (OTH) RADAR - WOODPECKER 2.0
In the EARLY 1980's the shortwave spectrum was PLAGUED by the Russian Over-the-Horizon radar. It's FAVORITE operating frequency was 13.856 mhz (or thereabouts) - right below the 20-meter CW allocation; although the radar pulses could be heard WELL-ABOVE 14.350. This radar was dubbed "the Woodpecker" because of its pulses which had a woodpecker-like sound.

A.E.A. Corporation immediately released what they called the "Moscow Muffler"; in an attempt to combat this menace. Since then, virtually every amateur transceiver is equipped with an NB-1 noise blanker, and sometimes an NB-2; although depending on who you ask, those blankers are effective only 1/2 the time and sometimes introduce their own artifact, in the form of circuit/audio distortion.

With the demise of the Soviet Union, the Woodpecker all but disappeared. However now, in the last 2-years, a new Woodpecker has built a nest on 6.995 mhz or thereabouts. WTF is THAT all about? What Dingle Dorks decided that it is a GooD Thing to park a megawatt radar transmission right next door to the 40-meter CW band? If you're going to INTERFERE with broadcasts, I would think the illegal PIRATE Radio stations (clustered around 6.555 Mhz) would be fair game; not amateur CW.
Am I missing something?

 

BEEF #7 -  DATA CRANKERS IN CW CONTESTS & RTTY QRM IN SSB CONTESTS

Because I operate the night shift during most radiosport GiGs, that puts me on 40 meters
much of the time. The 40-meter amateur band is shared with a number of different radio services. Unfortunately, I have gotten used to data cranking on my CW run frequencies and RTTY during SSB contests. I NEVER hear the data crankers or RTTY in the SSB segments EXCEPT during radiosport contests - wassup with that?

 

BEEF #8 - STATIONS WHO WON'T ID ON A REGULAR BASIS

Many stations (whether simply DX or running a contest frequency) simply REFUSE to ID.
When I run a frequency, I program Function Key [F3] to send "TU WQ6X", opening it up for
the next caller. Sending "QRZ?" (w/o a callsign takes just as long to send as a callsign.
What is so difficult to understand about that?

BEEF #9 - CALLING CQ TEST ON CW WITH A SINGLE CALLSIGN ID FOR EACH CALL

When running a frequency, sending your callsign advertises yourself as being open for communication. If we log your callsign incorrectly, then YOU get Dinged for the QSO.

Imagine the following: "CQ TEST WQ6X". If there is quick fading or the noise-level is significant,

one or more letters of the WQ6X call can be obliterated. Sending the call TWICE (or maybe even

3 times) "CQ TEST WQ6X WQ6X" gives us a chance to catch it on the repeat. Otherwise, we have

to wait around for another "CQ TEST WQ6X" call, only to have it obliterated as well.

Bottom-line?  Keep your CQ calls Informative, yet Quick.

 

 

BEEF #10 - OTHER FORMS OF INTENTIONAL QRM

As I said above intentional QRM on the 40 meter band happens nearly all 40-meter CW contests; everything from someone playing a voice recording repeating "F - U" over and over again, to this happening during the 2017 WPX-CW contest:

 

Stations were dutifully lining up to put WQ6X in their log until 10:47z when a Loud HOWLING noise appeared, followed by an Ssb-audio CW calling "CQ WPX de YC9WSQ". 

This went on intermittently yet continuously. The QRM got so loud that I moved to 7027.27 to escape the cacophony.

Then at 12:53z YC9WSQ was now at it again on 7.027 with that HOWL seeming LOUDER than ever. This station never worked anybody so it was clearly nothing
more than harassment; or, the guy was under the influence of one of the doctor's concoctions.

After the contest, I looked up his callsign on QRZ.Com and found this WEIRD picture. Which one is the operator? The guy on the right or the witch doctor on the left? 
(Note: As of November 2020, the YC9WSQ callsign can no longer be found using QRZ.Com.  However doing an internet search on the call, I was directed to YB9URM wherein use of this call was more-or-less explained, altho I STILL don't understand it.)

As you can see, a lot WEIRD things happen during radiosport GiGs; especially during the Weird Prefix Contest.   My BEEFS get even beefier in the 3rd installment of this BLOG series coming soon to the WQ6X.BlogSpot.Com.  [CLICK HERE] to read Part 3.

The Role of Respect in Radiosport - Part 1

In radiosport, indeed during ALL on-the-air activities,
in my mind, it goes w/o saying that respect for others should be an over-arching trait representing our on-air decorum.   Unfortunately, the desire for a "perfect whirrrrl'd" is FAR from perfect.

This Blog entry began as a Top-10 list of BEEFS
I have with radiosport operations and operators.

The list quickly grew way beyond the 10, relegating
this BLOG to become a 4 part BLOG series; this entry being part 1. 

Normally with Blog entries I go to great lengths ensuring there is some sort of aesthetic beauty in what is written.


Because this is a blatant list of beefs, I am just going to list them without fanfare and share my thoughts about each one, as well as a few relevant pictures as well. 
To make things more meaningful, I used poetic license
in the choice of visual images.

BTW, the opening picture is a PERFECT example of one of my radiosport BEEFs. 
([CLICK HERE] to read the BLOG entry this picture 1st appeared in.)

 

 

BEEF #1 - STATIONS CALLING ME WAY OFF FREQUENCY
On CW, operators running radios with 2.0+ Khz I-F's often tune WAY OFF my run frequency. 
They seem to think because they can hear me, I should also be able to hear their 20 - 50 watt
signal into a mis-matched dipole.

When I run the FT-1000mp I can immediately switch-in the clarifier knob and tune them in.
However, if I am running remote, I have NO ACCESS to an R-i-T control; the RCForb software
cannot invoke that Elecraft K3 feature.

A work-around to this problem is to synch VFO-A & VFO-B and put the radio in SPLIT mode; listening on VFO-A and transmitting on VFO-B.  The CORRECT answer is for calling stations
to call with no more than a 1000hz offset. Do you think you can do that?

 

 

 

 

 

 

 

 

 

 

BEEF #2 - STATIONS THAT SHOW UP OUT OF NOWHERE,
ZERO-BEAT THE RUN FREQUENCY AND CALL CQ
This is ESPECIALLY noticeable when running RTTY contests.
Out of NOWHERE an S-9+ station opens up with "CQ TEST"
with PERFECT RTTY copy, meaning the station is EXACTLY
on the run frequency; it was NO accident.

A special N1MM+ Function Key (FKey-9) allows me to repeatedly
send "QRL / QSY" until they get the message and move on.
Amazingly some don't; XE2 stations in particular.  I-F notch filters
are the RTTY operator's answer to IDIOTS like this.

Now you know why I purposely choose frequencies like 14084.84.

 

 

 

 

 

 

 

 

 

 

 

 

 

BEEF #3 - STATIONS WORKING ME IN A CONTEST WHO
CALL ME AGAIN 7 MINUTES LATER

HuH? He JUST worked me? Did he log the previous contact incorrectly?
Should I work him again to be sure he's in the log?
I have done that only to have them call me a THIRD time 20
minutes later. I guess they don't hear too many contest stations.

Then again, I guess their attitude is that making DUP QSOs is
better than falling asleep at the radio.

BEEF #4 - STATIONS WHO WORK ME AND THEN ATTEMPT QSOS WITH MY CALLING STATIONS ON MY RUN FREQUENCY
HuH?  WTF is THIS all about?  Go find your OWN run frequency, or S&P (Search and Pounce) elsewhere.  What are these operators NoT thinking?  When a station does this, I press function
key [F5] (their callsign) followed by [F9] ("QRL QSY") followed IMMEDIATELY by the [F1] key
("CQ Contest").  After that they usually LEAVE.

BEEF #5 -  STATIONS WHO WORK ME THEN MOVE DOWN 200HZ AND CALL CQ CONTEST
A variation on the BRUTE operator (described above) is the IDIOT who makes sure to work me FIRST, then moves down 200hz (but still within the reaches of the Yaesu's 500 & 250 hz filters)
to call their OWN CQ Contest.  HuH?  WTF is THAT all about?

I have consistently noticed that they usually don't make any QSOs from those calls
(because my signal is drowning them out).  Eventually, they find a new frequency.

The solution to THESE Idiots is SIMPLE - I move down 200hz and press [F9] again and
again until they MOVE.   Then it's back to the run frequency and back to the contest.

That's it for this 1st installment, Radiosport fans.
[CLICK HERE] to read Part II of this series.

 

 

 

 

Beacon Tracking saves WQ6X from drowning in 2018 SEA NET

Radiosport-wise, the 1st weekend
in June is usually very quiet.
Thinking I may have missed something,
I took a gander thru WA7BNM's Contest Calendar for June.

All I came across was
the SEA net contest.
([CLICK HERE] to read the
rules for this contest GiG.)

Altho the event started at 12:00z,
there was NO WAY I was ready to
get up THAT early; in fact, the WQ6X starting time was more like 23:00z
(mid afternoon PDT).

Originally, the contest was not a part of WQ6X's N1MM installation, I downloaded the SEAnet.UDC (User Defined Contest) file and imported it into the N1MM+ software on the WQ6X laptop, as well as Station #1 @ NX6T. It lists itself as the SEAnet RTTY contest and yet sets the operating modes as CW+SSB - GO Figure.

To make a BORing long story short, bottom line: the 2018 SEAnet contest was - from the WQ6X perspective - a NO SHOW. Devising custom CQ macros for this contest, I auto-CQ'd from the NX6T station for what seemed like hours. The only comebacks were stateside idiots who sent me 5NN and their state CODE (ex: AL & NM), to which I pressed the F3 key (TU QRZ?) and then used Ctrl-W to WIPE the QSO rather than log it.

What is frustrating about this weekend is that there were JA's & VK's (amongst others) who QUALIFIED to be in the contest but in fact were not. HuH?! This is the beef I have with stateside contests - operators don't play in their own contests. Somehow I thought this weekend would be different; and, it wasn't.

Now I coulda moped around about how I got screwed, however instead, I used this weekend to learn
a LoT MoRe about the radio beacons which populate the amateur bands; some you may know about, and some you may have never heard of before.

To open this discussion, I invite you to consider a set of beacon stations that have been around
(in one form or other) since the 1930's; none other than WWV, WWVH & CHU Canada.

When I purchase a transceiver (such as
my Yaesu FT-1000mp or its FT-920 & FT-900 predecessors) or a shortwave receiver (such as the current Tecsun PL-600), one of the immediate things
I do is to load up the 1st 10 frequency memories with the WWV/WWVH/CHU frequencies (leaving #10 available). 

A couple of weeks ago at W7AYT's QTH during a non solar storm weekend, in the evening I was able to copy ALL of the WWV/WWVH frequencies: 2.5, 5.0, 10.0, 15.0, 20.0 & 25.0 Mhz., as well as CHU
on 7.850. Scrolling thru the time stations gives me a sense of what
the LUF & MUF frequencies are at that time of day.

As a backup reference, several more memory allocations allow listening to various commercial
RTTY stations in the 7.5 and 8.5 Mhz frequency ranges as well as the Pirate Radio Spectrum
(6.500 - 7.000 Mhz) giving an indication of the propagation on those frequency segments.

Manually scrolling or invoking a channel scan gives me a good overview of the shortwave spectrum.
At W7AYT I use the CH-250 vertical to check band openings, BECAUSE it is a vertical, and because the FT-1000mp has a dozen+ auto tuner memories set to match the vertical.  Within 5 minutes I can get a quick look at overall propagation.   In addition to 100+ frequency memories, the thing I like most about the 1000mp is it's antenna tuner and dual receive capability.

Russian "Letter" Beacons

I often bitch about military incursions into our amateur bands  (such as the Chinese military M8JF calling the Russian RIS9 on 3772.84 @13:00z).

Then again, an upside to their activities is that inadvertently they give us LoTs of propagation information from North
and North-Central Asia.

I often hear the 40-meter letter
beacons (7.039 Mhz) nearly every
day after around 07:00z. Depending
on where I am listening from (NX6T, W7AYT or N6GEO) one or more beacons will drift through.
 

 

This weekend, only the "M" beacon (Magadan) was heard at NX6T.
I've covered the lower frequency beacon offerings first because they are not well known
to amateurs and shortwave listeners. More familiar are the 18 NCDXF beacons stationed
strategically around the globe.

I devised the WQ6X Beacon Tracker to help determine which beacon
I am hearing at any given moment. While this is not necessarily a new idea, combining
it with a Space WX sub-window and the ability to capture screen pictures IS unique.

3-EL Stepp-IR + 2-el Shorty-40

 

One of the useful functions of the NCDXF beacons is that they can give us an indication of whether or not a band is actually open and to where.

 

Throughout this weekend
I set the Stepp-IR yagi (atop Tower #2) to BI-Directional, pointing it in various directions to listen for several 3 minute periods as each beacon went through its 20 meter transmissions.

Considering that this weekend seemed to have a dearth of Oceania/Asia stations, I was surprised
to hear the W6WX, KH6RS, VK6RBP, JA2IGY & VR2B beacons, altho ZL6B never made it to Fallbrook. While it didn't count for the SEAnet contest, signals from YV5B (Venezuela) were heard throughout the night and even on 15 meters Sunday afternoon along with LU4AA in Argentina
(altho the rest of the band seemed dead).

It is BECAUSE I could copy KH6RS, VK6RBP & JA2IGY that I spent as much time calling
"CQ SEA Test" as I did. While it effectively accomplished nothing, it DiD get me into listen
and evaluation mode; something I sometimes don't do enough of.

Do YOU ever make use of the various propagation beacons on the shortwave bands?

How many beacons have YOU heard?

WQ6X Double-OPs CQ WPX Contest



WQ6X running the "dinner shift"

I am continuously amazed by how fast time flies.  It seems like only yesterday
I was in Fallbrook multi-OP'ing the 2017 WPX
Cw contest.

In fact, it has been over
2 1/2 months since the 2018 WPX SSB contest
in March. Many contests have come and gone since then, including the NX6T multi-op 1st-place finish
in 7QP 3 weeks ago.

As I did with the Cinco De Contest weekend ([CLICK Here] to read about that) for this year's WPX Cw GiG I double-OP'ed the contest, joining the NX6T crew remotely while putting 139 QSOs in the WQ6X log throughout the weekend, operating from W7AYT's QTH in Concord. Although probably neither operation won any major awards, the weekend was a LoT of fun and gave me the opportunity to "take care of business" (WQ6X business) at the Concord QTH.

Friday evening client commitments prevented me from getting started until 03:00z when I took over station #1 remotely during the dinner shift as usual for the NX6T crew. An operator shortage kept me in the chair until midnight (07:00z).

With barely 90 minutes sleep, N6KI rousted me from sleep back into the chair at 09:00z to keep 40 meters hopping. For this contest I began each operating shift by searching and pouncing (unless an operator slipped me into an already busy run frequency).

During a lull period on Saturday, I took the time to remove the top cover on the FT-1000mp to squirt some newly acquired DE-OX-ID into the memory/channel rotary encoding switch inside the front panel.

That DE-OX-ID stuff certainly does what others say it will do - the 1000mp is as good as new.


The WQ6X antenna switch was also brought back into operation out of desperation to improve signal levels
for WQ6X during the few periods I
ran solo from W7AYT's QTH.

The last operation @ W7AYT I devised an
audio cable configuration that runs each receiver (Main-RX and Sub-RX)
in the Yaesu transceiver, each through a separate Autek QF-1A filter;
one for each ear.


Using a pair of Radio Shaft audio-isolation transformers allowed patching the laptop's remote audio into those Autek filters as well. 
I've always been disappointed in the Elecraft K3's DSP filters
(when run remotely). Running the receive audio thru a QF-1A
allowed peaking weak signals over the noise and other junk sounds.
Luckily the 40 meter intentional QRM never materialized during
this contest.  W/o the Autek filtering several dozen QSOs would
never have made it to BOTH the NX6T and WQ6X logs. 
An Autek QF-1A should be a part of EVERY remote
operator's "Run Kit".

For running WQ6X locally I utilized W7AYT's Comet CH-250 vertical (Antenna B) along with the newly reconfigured WQ6X Lazy 8JK
Sloper (Antenna A) .

Each antenna had it's advantages, altho in general the CH-250 (being a vertical) was much more noise prone; yet sometimes signals were louder
than on the 8JK.

Using the WQ6X parallel antenna switch the antennas can be run separately
or run in parallel.  I have no doubt the radiation pattern is weird running two different antennas in parallel.

In many cases parallel antennas created an effect similar to "diversity reception" allowing receive signals to occasionally combine, yielding
a stronger signal.

In the last year I've had nothing but bitches when it comes to Space WX.

This weekend, not only was the SFI up to a whopping 77, the A & K indices were OK. 40 meters experienced a lot of noise in Fallbrook, but not in Concord.

Again, this is where the QF-1A filters made all the difference - peaking CW signals over that noise by as much as 20db. 

It is probably due to the 10% increase in SFI that I experienced a 10-meter opening at NX6T (at W7AYT exactly one QSO was made on each of 15 & 10 meters).

Running the 20mh Stepp-IR yagi on tower #2 allowed me to point the antenna, make a few QSOs, point the antenna +45 degrees and make more QSOs, etc. Thanks to the BI-directional capability of the Stepp-IR I was able to work South Carolina and Alaska, or New England and Hawaii, or VE7 and PY7.  In 90 minutes over 60 10 meter QSOs
made it into the log.

Another amazing occurrence was 20 meters. Many operators
said Friday night was great but Saturday was a disappointment.
During my OP time, Friday evening was so-so and Saturday evening was AWEsome. I've not heard Europe that strong, that deep into the evening, in many years. Maybe there IS propagation hope just ahead. We ran out of stations to work around midnight so N6KI made a run on 80 meters and I resumed solo-OP'ing as WQ6X on 20 and then 40.



KB7V - N6KI - AI6O

The original plan for the weekend was to have 10 operators running overlapping shifts. Of course it never works out anywhere near the original plan; the same thing occurring during the Cinco De Contest weekend. Because of the operator shortage I ended up spending somewhere around a dozen extra hours remotely that I had designated for operating WQ6X in Concord. 

Now there is an old saying "be careful what you wish for". In THIS case, at 21:45z on Sunday that wish resulted in an internet router outage across the hill in Fallbrook; not only locking out remote access completely but also disrupting access to internet spots for the band map. The AWEsomely wonderful WPX run on 10 meters abruptly came to an end.

N1MM+ Ending screen @W7AYT

Having no further access to NX6T (until 35 minutes after end of the contest) gave me complete license to finish the WPX contest as
WQ6X and not feel guilty about it.

Not knowing whether to run on 40 or 20 meters kept me bouncing back and forth between bands. While the 1000mp dual-receive is intended for in-band operation, because I run the radio as SO2-V
I can be running a frequency on 20 meters with the sub-RX on 40. While I can't "HEAR" anything on 40, the bandmap spots keep me informed as to whether or not I should switch bands.

Then, while running on 40 I can be bandmap checking on 20 meters.
Everything ran rather smoothly.

When it was all over, WQ6X had 139 QSOs in the log for 26K points, while NX6T turned 2465 QSOs into 5.4 million points. When you consider what we had to work with, both operations were an
amazing success.

Did YOU work the 2018 WPX Cw contest?

Is NX6T or WQ6X in YOUR Log?

WQ6X hosts a solo antenna party during King of Spain CW Contest

Current audio filter configuration

This weekend showed a dearth of contest activity as most of the BiG GuN OPs were hanging out at the HamVention in Dayton.  

E-mail notification of the 2018 King of Spain CW contest gave me another reason to run NX6T remotely as well as an excuse to experiment with various feedline configurations for the WQ6X Lazy 8JK Sloper antenna I have been
using @ W7AYT's QTH.

The King of Spain contest actually began at 12:00z (5am) on Saturday altho SWL'ing with the FT-1000mp until 09:30z argued against a timely K-o-S contest start. As a compromise, the 1st QSO didn't make it into the NX6T log until 18:11z - 11am Pdt.

Running NX6T remotely at dusk

 

A goal for this operation was to check out the new and improved UHF Wi-Fi router connection.

While the router was indeed faster, online video games played on the
other end of the router caused
"blip" interruptions to the connection nearly every 5 seconds, chopping Cw Dits/Dahs.

Current antennas @W7AYT

As it turns out, the K-o-S contest (run remotely as NX6T) and the
8JK antenna evaluations were separate (yet related) events. 

I ran remote as NX6T leaving open the possibility of making
K-o-S contacts as WQ6X from the Concord QTH; which in
the end never happened.

Instead, the Saturday evening 8JK configuration (I made a final change Sunday morning) was used as a receiving antenna for monitoring NX6T's signals from Fallbrook (some 400 miles away).

It's a weird experience to press a function key on the laptop in Concord which initiates an internet data transfer causing station #1 to send a 1300 watt signal into the 2-element yagi, which is immediately received on the FT-1000mp sitting next to the laptop.  The K3's sidetone (received via the internet) actually took longer to reach Concord than the actual transmitted signal itself (travelling at nearly 186,000 mph) - GO Figure.

 

 

Thanks to the MFJ-259b antenna analyzer I discovered the resonance and (false-resonance) points of each 8JK feedline configuration under evaluation. 

The MFJ-259 allows me to perform a quick survey of the 1.8 to 30 mhz spectrum noting all the resonance points.  As it turns out the Cobra dipoles are also resonant at 5.7mhz (49-M) and 15.5 mhz (19-M), offering GREAT shortwave broadcast reception.

The WQ6X sloper came about by phasing a pair of sloped Cobra dipoles together using a 4:1 balun, converting the 450 ohm ladder line into a coax feed. It's actually easier to feed coax thru the window than ladder line.

During this contest weekend, because
of the 12:00z to 12:00z operation time frame the usual 40-meter intentional QRM was not a problem. 
By 09:00z on Sunday, the K-o-S
was largely over, and again, no QRM. 


During this time I usually hear the Russian military beacons on/around 7.039.  From the SF bay area
I heard the "T" beacon quite loud and the "M" beacon about S-6.  Because it's not on the list I thought I was mis-copying the "T" beacon it until I realized a "DaH" is JUST THAT.

 As Saturday evening droned on, K-o-S QSO candidates diminished into silence. At 09:00z out of desperation I turned the antenna towards JA calling CQ for 5+ minutes with no reply. In retrospect, I should have kept turning the yagi CCW looking
for VK/ZL K-o-S players; maybe next year.


Did YOU play in the King of Spain Contest?

Is NX6T in YOUR LoG?

WQ6X runs another Cinco DE Contest as WQ6X & NX6T

The begining of MaY opens with two important things: Cinco de Mayo and Cinceo DE Contest.

For 2018, we had the RARE occurance of BOTH events happening on the SAME Day.

How cool is THAT? As with years past, this weekend brought us: 7QP, NEQP, INQP, DEQP & the ARI Dx contest.

Similar to 2016-2017, the principle QSO parties for the Cinco de weekend are the 7QP and NEQP, altho last year, WQ6X squeaked in a 1st-place for CA in the INQP GiG - Go Figure.


In years past I have joined up with the NX6T gang onsite.
In 2016 WQ6X won the 7QP 1st-place plaque from W7AYT's
QTH, followed by a 3rd-place finish in 2017. For 2018 I did something completely different: WQ6X remoted in to NX6T for several operating sessions at station #1, interspersed with running WQ6X/6 at W7AYT's QTH in Concord, Ca.

Prior to the May 5th contest weekend I spent time with the FT-1000mp tuning the bands and noting signal conditions.

 Unfortunately, while the
A & K Indices were low,
so was the solar flux
(SFI) - Bummer Dewd.


Amazingly, Friday evening using the onsite CH-250 vertical, it was possible to copy WWV signals on ALL of their frequencies: 2.5, 5,
10, 15, 20 & 25 mhz - not BaD considering we are at the bottom
of the sunspot cycle.

Antennas @ W7AYT's QTH

Running either the Comet CH-250 vertical or the WQ6X Lazy 8JK Sloper allowed for Horiz/Vertical propagation comparisons.

Amazingly, sometimes
the vertical was quieter than the sloper. 
In some cases, the sloper produced stronger signals, some w/increased noise.


To resolve this seeming conflict, on my next trip to W7AYT the MFJ-1026 noise canceller (languishing on the closet shelf) will be placed inline as I re-learn the art of antenna noise reduction.

Due to a lack of operators, the morning QSO Party shifts were
poorly manned. WQ6X fired up STN#1 @10 am, working mostly 20 with a brief stint on 15. 10 meters produced no openings, up on the hill, or in Concord, altho KK6NON alerted me to a 10-meter opening
in Oceanside (approx. 6 miles away). That opening never made it inland and never materialized in the SF bay area.

Eventually live operators trickled into the shack @NX6T,
allowing me to run as WQ6X via the FT-1000mp in Concord.

AI6O - NN6X - W6ZAR

The afternoon / evening shifts brought in a handful of operators,
some new to the NX6T operation: AI60 and W6ZAR. They helped expand the 20-m stats and put some SSB QSOs in the log as well,
I was temped to patch in the Electro Voice 664 into the laptop's mic jack for running some SSB remotely from NX6T, but eventually decided against it; too many variables to deal with I did NoT need.

Had I not been so Lazy, it could have been tested the 664 on Friday evening and be all ready to go. OH Well - one thing at a time.

7QP Ending Stats

ARI contest participation was never heard @ NX6T OR W7AYT. 

While I saw an occasional "9" spot, no INQP QSOs ended up in the WQ6X log either; likewise for DEQP.



From the Concord location, oddly enough, no SSB stations were heard in the State QSO Parties, only Cw. 

All complexities aside, 7QP and NEQP were the only contest events out of Cinco DE Contest that were actually worth spending any real time pursuing.

Because 7QP ended at midnight and NEQP was (per the rules) on hold until Sunday morning, neither of the operations (NX6T or WQ6X) had to contend with the obligatory intentional 40-meter QRM usually experienced after 07:30z - I guess, a blessing in disguise.

Filing a 3830Score for WQ6X AFTER N6KI submitted the NX6T
score exposed a design flaw in the WA7BNM contest calendar.

Shortly after I reported it to Bruce Horn the problem was resolved.

Now in the WQ6X 3830 Statistics BOTH score submissions appear
on the list; at this rate, WQ6X might even surpass last years contest submissions.

Did YOU participate in 7QP or NEQP?

Is WQ6X or NX6T (or Both) in YOUR Log?

　05-29-18: This JUST In - NX6T took another Multi-OP 1st place.