Friday, March 16, 2018

WQ6X reminisces about RTTY

While I LOVE formulating WQ6X Contest BLOG entries, it is easy to get caught up in writing about WHAT happened, in lieu of making the NEXT event happen. This evening (March 9th) while planning the next two contest weekends, I looked at this year's BLOG work and noticed that February slipped by with nary a BLOG entry from WQ6X.  HORRORS!  Let's Fix that.

It's no secret that I am falling in love with RTTY contests.
It's now 4+ years ago that with N6GEO, WP2/WQ6X took 1st place (worldwide) for the 2014 ARRL RTTY RU GiG. Here are the write-ups
for that event:

I SO much enjoy the RTTY RU contest that WQ6X Software will once again sponsor an award plaque for the 2018 RTTY RU contest. If the plaques are as cool looking as 2014, the recipient will be as pleased as I was when the surprise box one day appeared at my P.O. Box.

For RTTY RU 2018, my 654 QSOs
most likely earned a 1st place win for San Diego section.

The preliminary results are out and WQ6X is not listed for any major category wins; altho the section results will be published in a few weeks.

With the RTTY RU ancient history, the next RTTY GiG for WQ6X to dabble in was the Mexican RTTY contest (in early February), along with the WPX RTTY contest the following weekend.

Because N6KI & WQ6X were hyper-focused on the CQ 160 contest, I never found time for the NAQP RTTY GiG the end of the month - look for WQ6X next year.

Even though audio filters on the remote end are not useful for RTTY contests (altho they are AWEsome for CW work), I used this weekend as an opportunity to test-drive cascading an MFJ 752-B and JPS NIR-12 for the left ear and another MFJ 752-C for the right ear.
The NIR-12 sports a decent DSP-notch filter which helps knockout annoying tuner-uppers without affecting the actual RTTY decoding
on the NX6T end.

For the Feb 3rd weekend, I began operations with the F.O.C. CW contest allowing me to test-drive the NX6T STN-1 remote operation. Then, after some DEEP sleep I managed to start the XE-RTTY contest right at 12:00z working a couple hours here and an hour there.

For heat reasons when I ran a frequency, the ACOM 2000 amplifier was dialed back to 550-650 watts, while S&P contacts were made running approx. 1350 watts - into a C-31 Yagi, a 2-element "shorty
40" and 80-meter inverted vee all up only 13mh; altho the station is 900' above sea level. Because the SFI was so low, 40 and then 80 opened way earlier than I am used to. That made up for NO signals heard on 15 & 10 meters. It was nice to see many XE states on the
air, altho I was hoping for more.

An advantage of the SFI being so low is that 40 meters currently opens to the east most days by mid-afternoon; with EA5HYJ calling in @23:58z Saturday afternoon - NICE! That evening a huge CHUNK of spectrum was occupied by a CW PILEUP for the recently activated Z60 station in Kosovo. Luckily 80 meters was available as a refuge. Later, on 7.039 mhz the M & K Russian military beacons were heard, about the same time an opening to JA materialized - at least those intrusive beacons are good for SOMETHING.

Saturday morning, at 18:26z I received a STRANGE transmission (w/o callsign ID) saying "TEST is OVER". Every time I called CQ XE RTTY he would repeat that message; I guess the IDIOT didn't realize the XE RTTY is a 36 HOUR affair, not 30 hours like the RTTY RU in January. When I pointed this out to him he Quietly disappeared.

From 18:00z to 18:22z I had 23 stations call on my run frequency, before it all of a sudden became real quiet. I must admit, for a brief moment I visualized this BOGUS station sending "contest over" message all over the band, effectively convincing unaware
operators to shut it all down. 

By 18:34 stations were again calling; I guess, like me, they checked the contest rules on the website rediscovering the fact that we had 6 more hours of frustrating fun. Client commitments co-opted two hours of OP time, with WQ6X returning to 20 meters at 21:15z, eventually moving down to 40 meters (@23:00z) for the last hour of the contest.

After submitting the score to the 3830 Scores website it would seem that WQ6X took 21st place worldwide, 18th-place for NA, 17th-place for USA and 1st-place for W6.  Not BaD for just screwing around, learning new remote operation techniques.

Did YOU work the 2018 Mexican RTTY Contest?

Is WQ6X in YOUR Log?

Wednesday, January 31, 2018

NX6T Showcases California in CQ-160 Contest

Since installing a new fiber-optic microwave access tower @ NX6T (in Fallbrook), "NashVille" has become more reliably accessible for remote operators (such as WQ6X & N6CY). This last weekend gave us the opportunity to thoroughly test the remote access configuration. Otherwise, we ran a standard configuration of K3 radios into either an ACOM 2000a amplifier (STN-1) or an Expert
2-KL amplifier (STN-2), both into a 160 meter inverted vee with a 70' apex.

NIR-12 + 752 filters

For this contest event it was a radio swap @ STN-1 that was initially our critical issue, delaying N6KI's initial
start until 02:00z.  (Dennis quickly made up for lost time with a couple
of 70+ QSO hours.)

On my remote end of the operation, I got to play around with a JPS NIR-12 "Noise and Interference Reducer" along with a pair of MFJ-752 audio filters, all to process the laptop's
IP-sound audio.

Once properly adjusted, the 752's gave me a partial stereo-CW effect; higher pitched signals appeared in the left ear and lower pitched signals ended up on the right. The NIR-12 introduced tighter audio bandwidth for the left ear.

NX6T remotely during dinner

Friday evening, by the time I took
over the "dinner shift" (@04:00z) Dennis had put over 200 QSOs
into the 160 log.

My 1st QSO of the evening was with none other than N6GEO; someone I have run numerous multi-OP events with over the last 9 years.

I was literally putting on the headphones while sending George
the exchange for QSO #211.

While QRN was a mild annoyance for this 160 weekend, the more difficult phenomenon was quick fading; specif-ically with weak signals. Altho the contest requires we
send "599", we ONLY need to send it once. I set up
FKey-6 to ask for ONLY the QTH, yet stations

robotically send 599+QTH.

Unfortunately, with quick fading, signals often dropped out after the "599" obliterating the 2-or-3 charter abbreviation.
I remind people of this EVERY contest and yet they STILL send me unnecessary information and are perplexed why
I keep asking for a QTH repeat . The solution is simple: send ONLY the QTH (w/o 599); even with quick-fading
I will get it the first time and we can BOTH move on.

Propagation-wise, on Saturday, 160 meters opened in
San Diego at 23:00z, but only to California. At 00:50z,
the Southeast quickly flooded in followed by W8 & VE3.
By 01:40, NP2J was in the log. Openings this early to
the Left Coast are usually unheard of, making this 160
contest a delightful surprise.

As I usually do, for this weekend, most of my op-time was during the "dinner" hour (04:00z - 06:00z) and then the "wee hours" of the morning (usually after 09:00z - 10:00z). Luckily, a Christmas present of Popcornopolis caramel corn kept me fueled in the operator's chair during these sleepy hours, along with some super strength KONA coffee.

This weekend was another manifestation of my oft-repeated complaint regarding operators who score a QSO on my run frequency and then shift down barely 200hz to call "CQ Test". Has it ever occurred to them that most stations are running 500hz filters at best; even with a
250hz filter, their 200hz shift is STILL within filter skirts
and annoyingly audible.

My solution is to shift the VFO down 200hz and send "QRL QSY" several times working back up to the run frequency during the final QRL/QSY. In most cases, operators get the message and put more "distance" between themselves and "thou".

One station was so annoyed that I asked him to move
that he zero-beat my run frequency and sent patches of random dits/dahs atop of weak stations calling in, requiring numerous repeats; eventually he got bored with this and moved on.

Considering that the inverted vee at Nashville is hardly favoring Asia, I was delighted to work several JA stations both Saturday & Sunday morning. While BG7 & BG5 stations appeared in the bandmap, they unfortunately were not audible @ NX6T.

It was amazing how many DUP callers there were, indicating that nearly everyone was running out of new QSOs to make. After the contest, in looking at the 3830 Scores website I noticed that most of the top scores were all European stations. We were overjoyed to work 14 DXCC entities while they were bummed that their DX count was only 85 (just missing DXCC) - it certainly is all relative.

When it was all over we entered 834 legitimate QSOs (460 remotely) into the log for 145k contest points; not bad for an inverted VEE @ 70'. While we were at the bottom of the North American heap (E. Coast stations have a definite advantage over the Left Coast) it would seem that we did take a
1st place for W6 (California).

Did YOU work the CQ 160 meter CW contest?

Is NX6T in YOUR log?


Tuesday, January 30, 2018

WQ6X Parties with North America during January NAQP Contests

WQ6X Remotely - w/ MFJ-752c and NIR-12 audio filters
After the RTTY RU contest is over, to open the new year, the CW & SSB NAQP GiGs are the first contest events of each new year (the NAQP RTTY contest doesn't happen until late in February).
The NAQP contest is unique amongst contests of its type in that there is no high power category
(only LP and QRP); run over 100 watts and your entry becomes classified as a "check log".

NX6T STN-1 & STN-2 Night-Remote
Additionally, unlike so many contests, there is no 59/599 report, nor is there a serial # in the exchange, just name
and QTH; which tends
to makes things a bit more personal, even tho we make up names like "Dude" and "Loco" (often heard from XE2MX).

A unique aspect to NAQP is that each of the 3 contest events (Cw, Ssb & Rtty) are run TWICE every year (in
the winter and again in August) offering a 2nd opportunity to improve on our original scores from earlier that year.

Antenna Towers @ NX6T

Because of the low power restriction there is a greater reliance on antenna directionality and gain
as well as operator skill. While there is no Multi-multi category in NAQP, there ARE Multi-single and Multi-2 classifications. Additionally, because much of the NX6T operations are run remotely, installing a new microwave dish to the fiber-optic internet connection across the hill has made all the difference towards reduced internet latency.

N6KI Running 20-m CW
In years past I have often run single-OP from NX6T in Fallbrook (either from the shack in "Nashville" or remotely) when N6KI operates from elsewhere. For 2018, NX6T ran as a Multi-2 operation in both events; cw (run completely remotely) and ssb run with operators in the chair as well as remotely (thanks to Ron WQ6X and Rick N6CY).

For the CW event, I opened on 15 meters (making occasional CQ calls on 10 meters) while K6AM & N6KI put 20-meters on the air.

For the Ssb event I opened on 15 meters (again 10 meters never materialized) while KK6NON ran
a continuous pile up on 20 meters. For both events, 15 shutdown by around 22:00z, relegating me
to take early refuge on 40 meters.

KK6NON on 20 meters
One of the few advantages of being in the depths of the solar cycle 24 is that 40, then 80 and 160 meters open up considerably earlier in the afternoon than during the upper reaches of the solar cycle. For the Cw event I was receiving calls from Western Europe
by 01:30z - UNHEARD of normally.

Another "advantage" of NAQP GiGs over other contests is that they are over by 06:00z. On 40-meters, the so-called intentional-QRM (that occurs in most contests) does not usually occur until well after 07:30z.

During the 2018 NAQP SSB I encountered intentional RTTY QRM on 7232.32 at 23:56z.
Usually there are foreign broadcasts carriers on 7.230.  This year, instead of broadcast QRM I get RTTY.  Luckily, the K3's auto-notch filter can take out most RTTY signals and carriers. Unfortunately, in Cw contests, the auto-notch filter also takes out the code, so we take what we get at those times.

Another indication of incredible low band propagation was hearing the M - D - K Russian military beacons on 7.039 @ 06:15z - shortly after the NAQP was over. Unfortunately, propagation to Japan (Zone 25) doesn't occur on 40 meters before the NAQP is over with - by 08:00z their signals approach S-9.

Score-wise, while we made more QSOs for the NAQP SSB event than for CW, WQ6X logging
an additional 49 multipliers made a difference of 58k points. This is why multipliers are often considerably more important than "raw" QSOs. It is for that reason that I go to the
trouble of working 80 & 160 meters - those are what I call "Free" multipliers.

NX6T NAQP CW Results


Did you play in the January NAQP contests?

Is NX6T in YOUR Log?


Wednesday, January 24, 2018

WQ6X runs RTTY RU Routinely but Remotely

T'was the night BE-4 RTTY
Ever since taking 1st place worldwide as WP2/WQ6X in 2014 and Pacific Division in 2015
(both with N6GEO), WQ6X's RTTY RU operations have been more-or-less ho-hum affairs.
The GiGs in 2016 and 2017 run remotely from NX6T in Fallbrook BOTH produced paltry
14k point scores.   With some advance preparation in December, my goal was to at least
submit a 1st place log from the San Diego (SDG) section.

Because the RTTY Roundup (RU) contest begins
at 18:00z (10am Pacific time), this gave me the opportunity to setup N1MM+ and MMTTY macros
for NX6T Station #1 on Friday evening and get more-or-less 8 hours of sleep before the event started. 
I rarely start a contest right at the 18:00z beginning,
so this year was a unique exception.

Shack heat was a concern during the contest weekend, so the K3 was run into an ACOM 2000a amplifier dialed back to about 550 watts; more than enough to do the job as a high power entry.

Having access to the usual bevvy of antennas at "NashVille" added a few extra DB gain to the 550

Making QSO 600 near the end of the contest
While overall I like the MMTTY demodulator, I have been tempted to run TWO demodulators: MMTTY+FLDIGI or MMTTY+TinyFSK; doing so allowing each program to be configured for the demodulation algorithm it utilizes most effectively. Then again, running remotely I have enough variables to contend with. For now, I will postpone running two demod programs until the next portable operation @ W7AYT. 

Something that recently occurred to me is that a clever trick when running remote would be to configure a 2nd copy of MMTTY (with different demod settings). or run FLDIGI, on the laptop
end of the connection, routing the IP-Sound audio to the locally-run demodulator as a backup
for deciphering callsigns and QSO #'s.

Unfortunately, software-wise N1MM+ was somewhat of a disappointment this year, resulting in probably 50 CRASH messages throughout the weekend when callsign changes were made before logging a contact. Overall, N1MM+ has been very stable in the last year, so these crash messages were quite surprising.

Propagation-wise, while there were no solar disturbances, with the SFI down to 69, 10 meters never materialized, despite a number of CQ calls while rotating the yagis looking desperately for any 10-meter action. The Reverse Beacon Network reported my callsign on 10 meters but it does no good if everyone is convinced (in advance) that the band is dead so they don't go there.

15 meters produced very little log activity on Saturday, however on Sunday 131 stations were coaxed into the log. 20 meters produced 164 contacts altho I felt more should have been possible. Unfortunately at the bottom of the sunspot cycle, when
20 dies, it dies QUICKLY.

Fortunately, 40 meters came alive
both days "early" in the afternoon. I
was overjoyed to receive calls from EU stations on 40 by 01:00z. On the "Left" coast, we get excited about things like this. Even 80 meters produced a handful of DXCC entries, including SN7 & EA1. Lack of OC and AF continent countries was disappointingly noticeable.

Because there is a maximum of 24 hours OP time allowed out of the 30 contest hours, I managed to fit two sleep periods in (09:00z-12:45z & 14:50z-19:00z), qualifying as OFF time; then again, my total OP time was only 19 hours, leaving me to wonder what I was doing that squandered 5 precious OP hours. In between naps, I managed to add QSOs to the 40 meter log section.

The BiG surprise was NO intentional QRM on 40 meters (which happens nearly every contest). Instead, I encountered what I will call a "BEEPER" on 21090.90 @ 21:08z on Sunday. This
annoying idiot moved around my run frequency +/- making it difficult to put a notch filter on him.
The upside of the 15 meter run was the "pipeline" I experienced to the VE6 world, making up for
the lack of VE6 in most of the 2017 RTTY contests.

The 2018 RTTY RU contest seemed to be lacking in adequate DX activity; not
to mention the RARE states like NE, ME, RI, VT & DC, and of course all the "exotic" eastern Canadian provinces.

Even the 2014 RTTY RU had more DX activity; then again being a DX station myself at that time I guess I shouldn't
be surprised.

When it was all over, a 49k point score was not all that great, but unless I have miscalculated, it is enough to take a 1st place for the San Diego (SDG) section.

Did YOU work the 2018 RTTY RU contest?

Is WQ6X in YOUR log?


Tuesday, January 23, 2018

WQ6X Radiosport for 2017: What I've Learned

It was just over a year ago when I made up my mind to participate
in more radiosport events than ever before; not an easy target considering the 40 events I participated in during 2016. I wrote up
the 2016 contest season around this time last year. ([CLICK] Here
to read that write up)

For the most part, in 2017 WQ6X participated in the "bigger" events such as the major DX contests, WPX, Field Day and Sweepstakes. However what propelled WQ6X over the 40+ mark were the numerous state QSO parties and oddball DX contests and unique RTTY events. 

Additionally, since my Honda automobile was stolen a year ago, only
2 physical trips to NX6T in Fallbrook were actually made in 2017.
Most WQ6X operations from NX6T were accomplished remotely (via the internet) using VNC Viewer and the RCForb rig control software. Having access to the fabulous ACOM 2000-a amplifier feeding into Stepp-IR, C-31 and 2-el 40-meter yagis make it easier for my signals to be heard.

While NX6T is equipped only with a pair of inverted VEE's for 80
& 160, they gave incredible performance. Having a station location (Fallbrook) over 900' above sea-level certainly helps bounce
strong signals off the F-Layer.

Numerous times in 2017 I was informed that my signal was heard
in EU or OC (often off the back of the antenna) yet there was no reciprocal return path; frustrating for me because I hear no one calling back; frustrating for them because I'm not responding to their calls. This problem is a reminder that no matter how well we do, there are always additional ways to improve a contest score.

In recent years WQ6X has set high score records for various California counties during the California QSO party (CQP) and several ARRL sections in contests like Sweepstakes, the 10 meter contest and the RTTY Roundup (RU) contest. In upcoming radiosport events, I look forward to beating my original records.

As I write this on You Near's eve day, it would seem that the ending contest event count stands at 82. A fitting end to the 2017 contest season is the Canadian RAC contest the last weekend of December. Because I ran remotely, running CW only made the most sense and probably earned a 1st place finish for W6 (California).

While each of the 82 radiosport events are unique amongst themselves, they often share a number of frustrating situations:

  1. In every CW contest there are always idiots who muscle their way thru a pileup on my run frequency and then IMMEDIATELY move down 200 hz to call CQ - HuH? WTF is THAT all about?
    In a recent contest, XE2S didn't even bother to move;
    he made the QSO with me and then w/o changing frequency IMMEDIATELY called CQ on my run frequency (I had been there for nearly an hour).
    For 18 minutes I alternated between function key F-1 ("CQ Test") and F-11 ("QRL QSY"). He SO didn't get it that I modified F-11 to "QRL QSY LID".  Finally, after making only 2 QSOs while I made 15, XE2S found an actual clear frequency 1.5kc below me - the band was hardly crowded - and finally moved.
    HuH? Am I MISSING something?
  2. Intentional QRM has become an increasingly frustrating problem. While I don't like it, I am used to illegal SSB operations in the lower segment of 40 meters (below 7.025) and the "data cranker" RTTY stations.
    However, during the JIDX SSB contest in November we encountered one of the 3.840 (garbage dump frequency) idiots playing a recording shouting "F - U!", over and over again, along with another 3.840 IDIOT sending "T-E-S-T" (on CW) after every CQ call.
    Amazingly, the station never jammed us while actually making the QSOs, only after each CQ call. I guess some people get REALLY BORED @ 3:30 am - ever heard of SLEEP? (Can you say "time to go to sleep"? - I KNEW ya' could.)
  3. SO2-R stations who (in violation of radiosport ethics) call CQ on
    2 frequencies or get so caught up with S&P'ing they end up ABANDONING callers on their run frequency. Remember this:
    if I answer your CQ 3 times and you don't come back to me or anyone else, then I will send "QRL?" 3 times. If there is STILL
    no response, then the frequency is NOW MINE and I start calling CQ. If you now start calling CQ (w/o 1st asking "QRL?") then you are NOW QRM'ing me.
    Bottom-line: if you can't keep two frequencies going FLAWLESSLY, then you have no business running SO2-R".
  4. I don't mind if you RUDELY tune up for 5 minutes on my run frequency as long as you have the courtesy to give me a QSO before moving on afterwards. I am used to JA stations tuning up on me and then immediately calling me - at LEAST they end up
    in my log. Luckily. the FT-1000mp and K3 radios are equipped with a DSP auto notch which immediately obliterates their tune-up carrier. Then after I log the QSO I can choose to turnoff the DSP auto-notch if I so desire,
While the above issues are indeed frustrating, overall in 2017
I learned a number of useful things that I would like to pass on:

  1. Find an excuse to "play" in every contest event you can. Experience gained in one contest event can improve operations
    in other contests. Experiment with different station configurations to improve operating efficiency. During the latter portion of 2017
    I used a number of different external audio filters. While the MFJ-752 Autek QF-1a and JPS NIR-12 filter work well with my Yaesu FT-1000mp, they ALSO do a reasonable job of cleaning up the laptop receive audio when I run remotely using RCForb and IP-Sound PC software.
  2. Always submit a  LOG. Sometimes log entries get disqualified for
    all number of reasons, or, sometimes people forget to submit a log for that contest. Case in point: a 24-point log submission
    score earned WQ6X a 1st place for North America in the
    Russian [CQ-M] Contest.

  3. ALWAYS Fill-in Soapbox Comments. Doing this gives you
    "free" public exposure when your comments are quoted in
    the magazine(s) by the contest sponsors.
  4. BTW, when you post your score to the 3830Scores website,
    ALWAYS fill-in the comments section on the reporting form.
    I often use the 3830 comments in the SOAPBOX section of
    the log I am submitting - saving a LoT of time.
  5. Don't Give Up! In radio sport contests operators give up way
    too easily. For example:

    -A- Often when I run a frequency I will have 5 stations calling
    me.  I pick one of the callsigns and make the 10-second QSO.
    Then when I send QRZ? no other stations come back to me. HuH? Where did all you GO? You mean you can't wait 10-SECONDS to be my 2nd contact and 20-seconds to be my
    3rd contact, etc.?  I promise you will spend WAY MORE than
    10 - 30 seconds tuning the band looking for someone else.
    The most effective thing to do is to invest up to 30 seconds
    to make the contact with me first before spending upwards
    of a minute or more to find someone else.

    -B- Sometimes for whatever reason, when I work a station I am not able to get the information so I keep asking for a repeat until
    I am confident I can press the [ENTER] key to log the contact. Frequently after 2 or 3 requests for a repeat, the other station
    just DISSAPPEARS. Understand that when you do that I DO
    NOT log the contact.  I am either confident the information is correct and LOG the contact or use CTRL-W (WIPE QSO)
    and continue calling CQ. Therefore, if I ask for a repeat

    -C- Often one of the reasons I am unable to copy a station's exchange is that they send me unnecessary information (such
    as 59/599 in the NAQP contests). If QRN/QRM/QSB is present, by the time they finally get around to sending the required information (Name and QTH in the NAQP contests) their
    signal either fades out or gets tromped by the QRM/QRN.
    When I ask you to repeat ONLY your name, I do NOT want
    you to send me a signal report and I do NOT want to know
    your QTH; I ONLY want your name.
    For CW & RTTY contests, I have function keys pre-programmed to send ONLY a specific piece of information. When I use N1MM+ in NAQP, I define the F7-key to send ONLY my name and the
    F9-key to send ONLY my state. When asked to repeat a specific piece of information I use one of those keys. 
    If asked for the ENTIRE exchange then I just press the F2-key.
  6. Before EVERY contest I take a look at what entry classifications are available to me; such as: Single-OP, Single-OP Assisted, Single-OP CW/SSB/Mixed, or even Single-OP Single-Band. Additionally, whenever possible, I view the contest result statistics for the last 3 years to determine which operating category I stand a chance at winning. Case in point: For the 2017 CQP contest I noticed that the county high score for Contra Costa county was easily within my reach, so I setup a special operation from W7AYT's QTH in Concord. I was not disappointed.

Virtually every weekend of the year there are radio sport contests
to be had; from CW & SSB to RTTY, 10 & 160 meter contests, VHF contests, State QSO parties and all manner of DX contests, to special GiGs like last year's SEQP event during the 2017 solar eclipse.

While Radiosport is LoTs of fun, it is not JUST for "kicks". Contest operation makes it possible to learn and improve my operating skills, paving the way for emergency preparedness should earthquakes and hurricanes appear out of nowhere; as happened in the Carribbean during the latter part of 2017. In Puerto Rico and the Virgin islands, local ham radio operators (in conjunction wit a LoT of amateur radio assistance from the mainland) made the difference in bringing those islands "back online". Many of those mainland operators were seasoned contesters, such as Valerie NV9L.

Do YOU engage in radiosport events?

If not, WHY NOT?

If so, is WQ6X in one of YOUR contest logs?

Wednesday, December 13, 2017

WQ6X Survives 2017 ARRL 10-Meter Contest

WQ6X after dark
What can I say about the
2017 ARRL 10-Meter Contest?
Considering that we are currently
 at the bottom of solar cycle 24,
I wasn't expecting a lot, however
I CERTAINLY didn't see THIS coming. While the A & K indexes were low,
so was the solar flux (SFI) - around
70 - Bummer Dewd.
(In retrospect, we should have conducted an emergency run of the
10-Meter contest during that false-hope 150+ spike in the SFI back in Sept.)

Operating portable from W7AYT's QTH, I gave the newly installed (October) Hy-Gain 3-element 10-meter yagi a good workout. The antenna had such a "narrow beam-width" that when I happened onto the "Colorado corridor) (around 06:10z) 4 Colorado stations hit the log almost immediately; however without the peak capabilities of
the outboard QF-1A filters, they would have been lost
to the noise.

This year's 10-meter event was largely a CW affair; my condolences to the SSB only operations. Throughout
the weekend I put out lengthy CQ calls on 28484.84 & 28434.34, with only a handful of takers. It seems to
me that people gave up too quickly.

Normally I would not work 10-meters past about 03:30z. Continuing another 4 hours made a big difference as that
is when several northeast multipliers made it into the log.

Altho I technically ran as an SO2-V (2 Vfo's) operation, there was so little SSB activity that SO2-V for cross-mode work was virtually unnecessary". However for CW, I could run a frequency using RX-A while S&P'ing bandmap spots with RX-B.

FT-1000mp with dual outboard QF-1A filters
Running SO2-V was much easier with an Autek QF-1A audio filter for each ear, which allowed me to simulate what is known as stereo-CW. Properly wired, with stereo-CW a signal will shift from one ear to the other while tuning "THRU" the signal (either up OR down).

While the actual QSO count in this weekend's GiG was noticeably lacking, the FT-1000mp's outboard wiring was given a a through shake-down. Simplifying audio cable clusters made the audio filter trial/error proceed more smoothly.

Because of the strange noise characteristics during the contest, the FT-1000mp's eDSP Contour/NR knobs we constantly being juggled, looking for that EXACT combination with the QF-1A filters to bring a marginal signal through. Despite all that, no states east of Colorado & Arizona made it to the log; they were simply not even HEARD.

While WQ6X CW QSOs were occasionally spotted, I think most stations either heard my call randomly, or by slowly and patiently tuning the bands. While I ran assisted, spots often disappeared as quickly as they appeared. Typing in manual spots for those frequencies kept them around longer. Unfortunately, because of weak signals there were numerous partial callsigns positioned luckily next to a callsign correction; but not always - hence the frustration.

As disappointed as I was with the QSO totals in this GiG, reading score submission reports from all call areas it is clear that my experience was hardly unique. While the 10-meter contest seemed more like the California QSO Party, in the midst of it all, CW5W and PT3T made it into the log Saturday afternoon. Spots were seen for KH6 and several VE6's & VE-4's stations, but you can't work'em if you can't hear'em.

Typical of most 48 hour contests, on Sunday, paint was drying faster than I could make QSOs. The real accomplishment was to hear my good friend N6GEO calling me on SSB. A QSX to 14.032 picked him up on CW as well. He was 1 of only 2 other stations that worked WQ6X multi-mode. Pointing the yagi towards Twain Harte made the CW QSO possible. Were we communicating via skip, or (more likely) ground wave?

That evening I worked W7AYT as he ran his FT-450D into the CHA-250 vertical, also at the QTH. This was technically his FIRST contest QSO - how cool is that?!

RF susceptible cable equipment

During a recent contest, I received
a visit by the local cable guy to check their pole-based equipment.  For the ARRL 10-meter contest he was back again.

A few questions and answers between us pinpointed that their equipment is susceptible to 2nd harmonic interference from 28mhz
(i.e.. 10 meters). 

What Dingle Dork came up with the brilliance to park a system critical component on a frequency which is the 2nd harmonic of a potentially signal-riddled amateur band; amateurs can run up to
1.5kw, which can envelope cable equipment. Pointing the antenna towards the Southeast and
South America positioned the yagi; in an end-fire null-position of the cable unit.

However point the antenna to the Southwest (Oceana) or Northeast USA,
the antenna
is then BROADSIDE to the cable equipment; over-powering it and disrupting it.
While the yagi's F/B is 24db, that close, -24dbm means nothing.
My next operation @W7AYT is not for a few weeks; there's time for
them to get their act together. Can you say "Faraday" shielding?
We shall soon know the answer.


When I think back on it, the poor 10-meter propagation kept me CQ'ing more which kept the cable equipment offline longer; until nearly 07:00z (10pm) on Friday AND Saturday evening; primetime cable viewing time.

You have heard me say "When in Doubt CHEAT, but within the rules".  I even wrote a BLOG entry about this.  [CLICK] here to read that BLOG Entry.  Along this line, I saw fit to employ an EASY button bringing humor into this deplorably dismal 10-meter contest.

The 2017 ARRL 10-meter contest is now "ancient history". It would seem that my complaints (other than the cable problem) were shared by most amateurs around North America; altho to varying degrees. From the East Bay (EB) section, evening propagation to the North Northeast direction
was a noticeable reality Friday evening; whereas as Saturday evening, no such path was evident.

Based on score submissions to the 3830 Scores website, it would seem that WQ6X took a 1st place for East Bay section and a 2nd place for W6 (California). That is based on the assumption that
the Log Checking Robot (LCR) doesn't ding my submitted score too much.

Do YOU work the ARRL 10-meter contest.

Did YOU survive the horrible condx?

Is WQ6X in YOUR log?

P.S. The wildfires which threatened NX6T died out just a mile from the hilltop. 
N6KI operated from home until Sunday when Dennis and K6AM (John) put NX6T
on the air for a few hours.

Monday, December 11, 2017

WQ6X joins N6KI for ARRL 160 Contest

WQ6X running remotely
The 2017 ARRL 160 contest was a mixture of different significances. While the contest begins @ 22:00z (14:00PT, 17:00ET), on the left coast that is a bit early (altho on Saturday the first signals wafted through the ether into the headphones at 22:36z).

Similar to last year, I dual-OP'd remotely with N6KI (Dennis) while he manned the OP chair live @ NX6T in Fallbrook (aka "NashVille"). Because Dennis was the lone operator atop the mountain, motor-raising tower #2 to 70' (23mh) was a one-man CHORE - Thanks Dennis.

Using WinTest to run the K3 into an ACOM 2000a,
NX6T started running a frequency @ 01:30z, immediately
hitting the 100/hr QSO rate for the first couple of hours.
At 04:00z when I took over (remotely) for the dinner shift there were already 247 QSOs in the log. S&P'ing and then running frequencies, I managed another 133 QSOs in the log by the time N6KI took over @06:30z.

N6KI running Station #2
With barely 2.5 hours sleep
I "stumbled" out of bed (08:45z), chugged a mug of Kona coffee
and picked up where Dennis left off,
adding another 133 QSOs to the log.
By 13:30z with no one new to work, I went back to bed. By 22:00z I fired-up STN-1 remotely tuning the band.

While an SFI of 70 is good for 160 meter contests, a K-Index of 3 resulted in S5 - S7 noise levels, which is not so fun.

What stood out in this 160 meter contest (to put it bluntly) were the numerous ASSHOLE operators.

While I don't normally name callsigns, for this GiG, the RUDENESS of N6ZFO, W1SRT and XE2S notably stood out and were completely uncalled for.

JUMPing on a frequency (already in use for over an hour) with 3KW and BELLERing "CQ CONTEST", without listening FIRST and sending "QRL?" second is completely LID behavior, prompting me to send "QRL QSY"; and when he didn't get it, I sent "QRL QSY LID" - eventually slinking away down 1.2kc to "remind" me he was still around. Turns out I was louder than XE2S;
it took him 18+ minutes of no QSOs to get the message and move on.

MFJ 752-C for laptop audio
During this fiasco, diverting the laptop audio thru an MFJ-752C notch filter I was able to reduce his barrage enough to copy stations who were smart enough to call me PRECISELY on frequency. (In the end. being ON Frequency reaps BiG dividends - ME).
Making only 12 QSOs in 18 minutes is not great, however it certainly is > 0.

Saturday afternoon, by 23:00z 160 meters began
to flutter open. After haphazard S&P'ing at 00:55z I parked NX6T on 1.820 and literally heard the signal levels emerge further and further eastward.
N6KI took the helm at 02:00z.

Because we had worked so many stations, Dennis went on a multiplier feeding frenzy, which was good
for the log. Thanks to his section skeet-shooting we managed 81 out of the 83 ARRL sections; missing
only NL & PR - Go Figure.

Stations #1 (remote) & #2 (live)
When I came back at 09:15z I continued the S&P and then settled in for 2 hours of intermittent frequency running. It was around this time some internet latency crept in. When that occurs, I make sure the auto-repeat CQ option of N1MM+ is turned OFF; I don't want to be knocked out (yes it HAS happened) while the remote station CQ's endlessly. Luckily, I can usually reconnect within a minute
or two to press the [Esc] key - Errrrk!

For NX6T, there were not a lot of DX stations in our ARRL-160 log, however
I was tipped off by N6GEO that V31 was on 160 (he saw the spot but couldn't hear him).

Evidently our slouchy inverted VEE managed to skip a signal across the east-coast "pond" - how nice is that?!

DX-wise, only the usual bevy of regulars made it to the log; such as: NP2J, PJ2T,JE1CKA ,JA3YBK, JH2FXK & RW0CR

10-meter RTTY - all 4 QSOs!!
After the 160 contest was over I had hoped to find some time for the 10-meter RTTY contest
(a sort of pre-cursor to the ARRL 10-meter contest the following weekend (altho the 10-meter contest
doesn't support RTTY). Nevertheless, I found JUST enough time to call CQ, eventually putting
4 QSOs into the log.  In case you're wondering, yes, I DiD send in a WQ6X log and added the
score to my WQ6X submissions list on 3830Scores website.

NX6T ARRL-160 Ending Score

Based on the 3830 Scores website, it would seem that NX6T's 154k point score has taken a 1st place for San Diego section and 2nd place for the Southwest Division. Not bad for a couple of Old Pharts.

Lights out after the 160 contest

Who would have guessed just 3-4 days later the raging Fallbrook fires would come within
1 mile of the "NashVille" operation. Is this a LAST BREATH for NX6T on the mountain?
Stay tuned for the upcoming ARRL 10-meter contest BLOG entry to find out.

Did YOU work the 2017 ARRL 160 meter contest?

Is NX6T in YOUR Log?