WQ6X runs BARTG RTTY & Russian DX contests remotely

Lately, business traveling has demanded that for contest operations I largely operate NX6T remotely from the bay area.  Some of the contest gigs I've operated remotely this year include:  RTTY RU, the CQ 160 contest, ARRL DX CW and NAQP RTTY.

This past weekend left me with no client commitments.  Instead of running my usual portable operation from W7AYT's QTH in Concord Ca. (East Bay section) requiring extensive equipment and antenna setups, I decided to book a room with a view for the weekend at the Clarion Hotel near the Concord airport and run this weekend's contest events remotely from NX6T (Fallbrook); otherwise known as "Nashville".
Listed on the contest calendar were the BARTG RTTY and Russian DX contests,
along with the LA & VA state QSO parties; in that priority order.

Unlike CQP, it is typical of many state QSO parties that they last only 12 hours.
By the time 40 & 80 meters finally come alive those QSO parties are over; as happened with this year's LA QSO party.  Although the VA QSO party had a 2nd run on Sunday, while working the final portion of the BARTG contest I never heard any VA stations - so much for the weekend's QSO parties.

Running remote, CW contests are the easiest to operate.
While I largely prefer to sit on run frequencies, attracting stations to my signal, it also pays to search and pounce from time to time; either by tuning the radio "manually" or - if I am running assisted - by clicking callsigns on the bandmap.

Because tuning RTTY stations remotely is tricky (even with negligible internet latency), for contests like BARTG & the RTTY RU, I prefer to run a frequency to reduce the operating complexity.
The 5% (or so) S&P contacts made in these contests largely happen "by accident".



One of the many desirable aspects of the BARTG is the contest length (48 hours) starting @ 02:00z; just after dinner PDT time.

An order of takeout sushi set the stage for a somewhat productive Friday evening on 20 meters and later, on 40.
Hamachi (Yellow tail tuna) is one of my favorite sushi rolls.

Using LogMeIn Hamachi on the Toshiba laptop gave me access to the NX6T VPN allowing remote access to station 1's Toshiba laptop and control of the K3 radio and KPA-500 amplifier.

At NX6T, STN's #1 & #2 are now both remote capable so this weekend I got to share the Nashville antenna farm with other operators who wanted to run the BARTG gig along side the Russian DX contest, but on SSB instead.

For STN#1 my configuration was relegated to running BARTG @ 65 watts onto a 2-el yagi on 40 meters and via the KPA-500 amp (at about 360 watts) into a 3-El Stepp-IR yagi for 20 & 15 meters (both antennas 15mh high).

While I was able to turn the rotor remotely, switching between 20 & 15 meters on the Stepp-IR required the next door neighbor walk into the ham shack and manually turn the bandswitch on the WX0B SIX Pack antenna switch box.

For the Russian DX contest I ran the K3 @ 100 watts on 40 and 360 watts on the high bands.  Unfortunately I was unable to run 80 or 10 meters for those contests.

A problem I increasingly encounter when running RTTY contests  remotely is an increasing number of stations increasingly off frequency when responding to my CQ test calls.   If I were running my FT-1000mp, I would simply turn on the RIT and tune them in; rewarding poor operating procedure.  These stations either have THEIR Rit on or they found me via a DX spot entry on the internet that listed my MARK frequency incorrectly.  Rather than check to see if they could decode my data correctly BEFORE transmitting, they just blindly press F4, sending their callsign off frequency.

My solution to this was to define N1MM's F-10 key to send "UR OFF FREQUENCY - PLEASE TUNE ME IN", followed by the F9 Key ("CALLSIGN?").  After a short pause, most stations tune me in and a proper QSO is made.  Unfortunately, some stations don't get it and eventually disappear; probably cursing me for not working them.

Although the Russian DX Contest started at 12:00z (5am PDT) because the BARTG contest was my weekend priority I didn't begin until after 22:00z.

Running the DX contest on CW became my priority, with brief segments of BARTG activity in between until it was finally over at 12:00z on Sunday.

As you can see, I managed 139 QSOs on 40 & 20 meters, enough for a 6th place in the USA and 7th place for North America; although not enough to take any awards.


Nevertheless it was a LoT of fun.
I look forward to next year with a more focused effort.

Did you play in the BARTG and Russian DX contests?

Is WQ6X in YOUR Log?

WQ6X & N6KI team up as NX6T for 1st S-A 10-meter Contest.

Over the years, team NX6T has put together operations for an array of different radiosport events.

This year for the 1st time we decided to participate in the South American 10 meter (SA10) contest.  Considering that Sunspot Cycle 24 is well on its way out, the more 10 meter GiGs we can operate the better.  Next year may clearly find us in the SFI basement; we're already getting close to that point as it is. 


For a 24 hour (only) contest it was not cost/time effective to make a drive to the NX6T site in Fallbrook.  Instead, we perfected the remote access to NX6T.  Overall the internet latency was hardly noticeable.  Because the contest started at 12:00z 10-meters was not yet open in Southern California.
I started CQ'ing for the contest at 15:15z, making my 1st QSO at 15:44z.



As it turns out only WQ6X and N6KI were available to run this gig.  While Dennis slept, I fired up the contest on CW running NX6T remotely from a "secret location" in the bay area, with the objective to run mostly CW with a little SSB.  

Without full SSB control remotely, I had to limit voice
operation to searching and pouncing, allowing me to "talk" using pre-programmed N1MM  macro keys to play .WAV files.  As it turns out, the SSB to CW ratio was exactly equal;
39 QSOs in each mode.

Like the ARRL 10-meter contest, the SA-10 contest is a multi-mode affair (CW & SSB).

Essentially, stations worldwide can work each other, however we make MORE points working South American stations.



Equipment-wise we ran the usual Elecraft K3 radio into an ACOM 2000 amplifier. 
The antenna was a 3-element Stepp-IR running BI-Directional, allowing us to work
Japan as well as South America.



As contests go, this gig was a bit of a ho hummer.
Additionally, because this is a 24-hour contest, for us left coasters we get one shot at 10 meters - when its gone,
it's GONE; there is no redo on this one.

Being a single band contest, ten meters is either open or
it isn't.  At the Fallbrook location, once the band was open and stable (around 15:30z) it remained intact up to the time
I turned it over to N6KI to finish the event - 22:15z.

Despite Dennis' best efforts he could only manage 5 more QSOs for the contest; evidently, I worked all there was to work otherwise - go figure.  By 00:30z the band was gone and so was the contest for us.

Our 78 QSOs netted over 20k points, which while a pittance (by other contest standards) may be just enough for NX6T to take 1st place worldwide (outside of South America).



As you can see from the 3830 Scores website (CLICK HERE), our closest competitor (W3HAC from the PVRC) made only 29 QSOs for 3,300 points.  Theoretically, we should get a 1st place certificate as compensation for all the effort we expended operating this South American GiG.

 

Did YOU work the SA-10 contest?
Is NX6T in YOUR Log?

WQ6X runs NAQP RTTY Remotely from Laughlin

For the third weekend in a row I have run remote contest operations from NX6T in Fallbrook (aka "Nashville").  This last weekend found me going all out in the NAQP RTTY contest; a 12 hour event
(10am to 10pm PST) during which the rules allowed me to operate only 10 hours of the contest period.
Because the contest exchange is Name and QTH, the event has more of a personal feel to it.
Contact w/NE6I put me on one of the Southern California Contest Club (SCCC) contest teams
(Team #1).

In the past (the 2016 RTTY RU contest) to run full low power we set up STN#1
to run into a KPA500 amplifier allowing 100 or 150 watts full duty for RTTY.  Recently the KPA500 has been tripping out under marginal SWR issues.

After a call to Elecraft, N6KI and W6JBR devised a solution to this problem by running the K3 at near-full power (92 watts) with a huge cooling fan pointing head-on at the transceiver.

Operating from Harrah's hotel in Laughlin, I encountered virtually no latency problems during this contest.  Nevertheless, because tuning  RTTY signals remotely is tricky at best I chose to run frequencies 95% of the time.

The use of macros in N1MM make operations run smoothly.  Using Ctrl-K from time to time is the equivalent of sending manually with a key paddle in CW contests.


As I experience consistently in RTTY contests stations call me way off frequency.
While I can hear them, FLDIGI cannot decode their data.  If I was sitting in front of my FT-1000mp,
I would simply turn on the RIT and tune the signal in; something virtually impossible (in a timely fashion) when running RTTY remotely.  Instead, I would press Ctrl-K and type "You're off frequency - please tune me in", then send "QRZ?".  Most of the time they would shift frequency and we would establish contact.

My question is: how can you tune me in well enough to copy my "CQ NAQP" call and yet be OFF frequency when it comes time to transmit?  Most likely these stations found me through a spotting network with an incorrect frequency cited in the spot entry.  Rather than blindly call a station found
in a spot, LISTEN FIRST to make sure you have an ACTUAL copy on their data transmission.

In all NAQP contests single operators are allowed to operate 10 hours max out of the 12 hour contest period.  The gamble is, which 2 hours do I sacrifice?  If I run the 1st 10 hours consecutively then end of contest is 04:00z (8pm local time) missing out on 80/40 meter opportunities ending the contest. 
If I wait until noon to start, I miss out on any 10/15 meter exclusive morning openings.  Then, if I get called away from the radio at any time during the remaining 10 hours I will have wasted part of that obligatory off time.




For this event my  choice was to begin on time, take an hour
off mid day and end the contest at the start of the last hour.  Because off times must be 30+ minutes I took 40 minutes for lunch, requiring that I cease operations at 04:40z (8:40 local time); more or less in line with my original strategy.



My only regret for this NAQP GiG was that I did not give
10 meters any attention Saturday morning; instead I ran frequencies on 15 meters for 2+ hours.  By the time I took a look 10 meters was already gone.  I ended the contest moving from 40 down to 80 to wrap things up.  I was amazed to find a nice 80 meter opening across the U.S. to the Eastern seaboard.



True to infamous 40 meter contest fame, this year's NAQP RTTY experienced the typical 40 meter intentional QRM I have come to expect during contests.  Only this time while running a frequency (7.070.70) at 02:10z I was barraged with howling and rumbling noises, followed by what sounded
like the whine of a dropping bomb, again and again.  Go Figure.  At least the bomb drop noises showed some originality.  As with ALL intentional QRMers they soon get bored and either give
up entirely or find someone else to bother.  An hour later I am STILL on that same frequency
with another 40 QSOs in the log.

As it is, because 7.070 is in the middle of the international phone band (for Regions 1 & 3), QRM
from ssb stations allowed to share the spectrum is to be expected.  Then again, at 02:30z 7.070 became the National Tuneup Frequency as many stations began testing (saying "helllllllooooo  helllllllooooo").   If they ended up near my frequency I could understand that. 
However when they are EXACTLY zero beat with me, that is NO accident.

Now, to voice one of my main RTTY contest beefs: NCDXF beacon QRM on 14.100.
What?  You didn't know there is a propagation beacon on 14.100 24/7?  They been there for over 20 years.  (Co-relatively, are you aware of the beacon segment occupying the ENTIRE 28.200 to 28.300 segment of 10 meters?)  NCDXF beacons provide 24 hour propagation assistance for free; the least we can do is give them "room" to operate.  It's one thing to be on a nearby frequency and splatter onto 14.100; it's another thing entirely to have your center frequency EXACTLY at 14.100.

CLICK HERE to learn more about the NCDXF beacons and the service that these beacons provide.
There is no reason why we can't operate a RTTY contest and avoid the 14.097 to 14.103 corridor.
In fact, I did just that running a frequency for over an hour on 14.107 and later on 14.092.


Because I have been on the road for business the last 10 days, playing in the NAQP this last weekend was relaxing and fun, even tho I was inside all day on a sunny Saturday.
I had a nice view of the desert hills from my window while typing away.  In common with CW contests, running RTTY saves my voice (I had been teaching advanced therapy techniques all week).

Like last week's DX contest, I had no rotor control on the yagi's at NX6T, so essentially, the C-31 and 40-meter yagis were pointed 45-degrees (N-W), limiting who could hear me.  This becomes evident as I did not work a single
KH6 station and virtually none in S. America; altho
I was called by an AH2/W6 station - go figure.
As a result I was only able to work 47 out of the 58 multipliers, missing many of the Northwest states
and most of the crucial VE/VY sections.

Overall, I worked the high bands moving to
the lower bands as the contest progressed.
Mid afternoon, jumping between 15 & 20 meters allowed me fresh QSOs when I had worked all
a run frequency could provide.

Then, coming back to a band on a different frequency allowed other stations to encounter me "newly".


Did you play in the NAQP RTTY contest?

Is WQ6X in YOUR Log?

WQ6X runs ARRL DX Contest remotely from the Gold Strike casino hotel

This has been a busy February.  Last weekend my attempts at running the WPX RTTY contest remotely was a complete BUST due to horrible internet latency.
The last 1/2 hour of the event settled down enough for me to make 18 QSOs allowing me to submit a log with a WHOPPING 21 QSOs - at least I DiD submit a log,




Last week I had client work in Pasadena and am heading to Las Vegas to work with other clients this coming week.  In the middle of it all I managed to operate the ARRL Dx Cw contest from NX6T remotely; Friday evening from Southern California and the rest of the weekend from the Gold Strike casino hotel off I-15 en route to Las Vegas.

WQ6X's operating position

Friday evening, the issue of internet latency was quite a problem, limiting my success.

Saturday I drove to Jean Nevada hanging out at the Gold Strike hotel to participate in the ARRL DX contest and play a little Blackjack.

Because casino hotels want us to play in the casino not on the internet, they charge significantly for the online privilege.


As it turns out, a $12 investment in super-speed internet access all but eliminated the latency problem during contest operations.  Because the latency was so low I managed to run several frequencies until each one of them eventually QRM'd out.

STN#1 @ NX6T

Operationally I ran STN#1 (an Elecraft K3) barefoot into a C-31 yagi at 40' and a 40-meter yagi at 70' feet, with an 80-meter inverted Vee at its apex.  Unfortunately remote rotor operation was not possible so I dealt with fixed positioning of the yagi's.

Nevertheless, it was better than no operation at all.  As I have in the past, I used the LogMeIn Hamachi software and again for dinner enjoyed a hamachi (Yellowtail) sushi roll - go figure.


Staying up into the late night hours allowed me to sleep in, but probably caused me to miss 10/15 openings both mornings.  On both days, 10-meters seemed to "go long" early in the afternoon and close up early.
40 meters turned out to be THE band, allowing me to work 57 countries on that band alone.
Luckily, the bogus QRM I usually experience during 40 meter contest periods didn't materialize; all except the Russian "K" beacon on 7.030 mhz.  Why is it I only hear the 40-meter Russian beacons during contest weekends and never during the middle of the week?

Next to 40, 15 meters was my best operation.  Openings to Africa were certainly there on 15, altho so were the DX cluster fueled pileups, so no Africa in this year's log.

What was really strange is DX stations asking me for my NR (number).  While they send ME a number (their power level), the only NR I send is "599".  While I finally realized they wanted my QTH (state), beginning contesters may not understand this.  The correct request is: "SEC?"

While there were a surprising number of openings to South America because I was not able to point the antennas in that direction to work many of those stations, relying on back of beam access to South America and Oceania.  Then again, a north pointing C-31 yagi made working UA0 easy and afforded a late afternoon opening  into Northern Europe on 15 meters.

Overall, I managed about 18 hours of actual operating time making 364 QSOs in over 70 countries for a score of just slightly over 172k points.  While I won't win any awards for this one it was a LoT of fun to work so many countries from a casino hotel room.

That evening the one 6-deck Blackjack table in the casino gave me a run for my money.

Next weekend is the NAQP RTTY contest which I will probably run remotely,
so look for WQ6X ("Ron in CA") during that event.

Did you play in this weekend's ARRL DX contest?

Is WQ6X in YOUR Log?

WQ6X joins NX6T remotely for 2016 CQ 160 meter contest

The RCFORB radio control software

It's been several years since I last participated in the CQP 160 meter contest.  It doesn't make sense for me to make the 10 hour drive to Fallbrook to operate what is essentially  a night-time only contest, even though two nights are involved.  In order to participate, the OPs at NX6T enabled my remote access to STN #1 during the dinner hour and the post-midnight to sunrise periods.  While I was able to make this work, the internet latency (especially during the dinner hour) was HORRIBLE.

No antenna tuner needed here

The 160-m Inverted Vee @70'

Equipment wise we ran a bevy of Elecraft K3's into an ACOM 2000 amplifier out to a 160 meter inverted vee 70' high at the apex.  Remote facilities included Logmein-Hamachi, RCFORB & the VNC Viewer.

For the 2016 contest, the noise at the NX6T was an intrusive factor; largely S-8 on Friday evening.
While there are DNR noise filters in the Elecraft K-3 they are not easy to manipulate by way of the RCFORB remote radio software so I suffered through.
Then again, because this contest had no 40 meter operation, I was spared the usual belches, VFO sweeps Russian beacons and phantom RTTY signals I usually have to slog through during the 10:00z to 12:00z time frame on 40 meters during most CW contests.

STN#1 during the dinner hour

The idea was for me to takeover STN#1 at 10:00z (2am).  As I was about to settle into a 2 hour nap at midnite the call came in and I was soon running a frequency (1.807 mhz).  While the noise levels were high, running a frequency (as opposed to S&P'ing) worked out very well.

As sunrise made it's way I had made over 200 QSOs including a handful of countries thanks to a greyline-style opening to Asia Saturday morning just before the band faded into oblivion.


For Saturday evening, because the band opened "late" and the fact that we had worked a majority of stateside stations the pace started out slow.  When I took over at 04:00z for the dinner hour the internet latency was at its worst, altho eventually settled down affording a nice frequency run on 1.848 (mhz).
After the operator change-back I took to the world of sleep.
Because my cellphone was on the charger while I slept I didn't hear the 20+ attempts by N6KI to roust me from my slumber.  Eventually I rolled out of bed, fired up a middle-of-the-night Kona  coffee and hit the couch.  While the internet latency had settled down, there were not a lot of stations to work,
so at N6KI's recommendation I S&P'd for the 1st hour until I could find nothing left.
By 12:00z I was calling CQ on 1.802.76. 

Sunday morning the signal strength of W6's & W7's nearly burned out the cheap headphones I was using.  In retrospect I shoulda brought in my Heil headset from the trunk of my car, but I was too lazy to make the trip.  (I own the Heil PRO headset with the phase-switch on the left ear).
Sunday morning did not produce the desired repeat of Saturday morning's greyline, so by 14:30z
I shutdown the remote connection and went back to bed - effectively ending the contest for us.

Despite the frustrating internet latency problems, overall, this was a fun CQ 160 contest; all of which could be run via a laptop on the living room coffee table.  I recently upgraded my Toshiba laptop to a solid state disk drive, keeping Windows 7 rather than upgrade to Windoze 10.
As I have experienced recently, remote radio operations seem to run more smoothly with this configuration.  Looking at the contest results from the 3830 Scores website it looks as tho we took 23rd place worldwide and quite likely 1st place for California.

The view from NX6T's Fallbrook location

In the last 2 months I have been fortunate to join NX6T's Fallbrook operations remotely from a number of different locations on my part.

While the internet enables many amazing things in the 21st century I want to warn radio operators not to become overly reliant on an infrastructure that can be disrupted at any moment.
I still love sitting in front of a radio with knobs; tuning stations via a software screen is marginally effective, and, in the case of RTTY very tricky at best.

N6KI's formula for winning contests

For me, next up operation-wise is February's ARRL Dx CW contest, which will most likely include 160 meter operations.


DiD YOU join in this year's CQ 160 contest?

Is NX6T in YOUR log?

WQ6X runs NAQP SSB Solo portable

Being a part of NX6T's CW NAQP 2nd place last weekend was quite a thrill.
While I would have liked to join them for the NAQP SSB GiG, business demands made it impossible to make the trek to Fallbrook.  Even taking the train would have been too complicated for a contest that only lasts
12 hours, of which I probably would have had 4 hours of OP time available to me.

Instead, I decided to put together another infamous WQ6X ad-hoc operation; this time from the 3rd floor of a hotel.  Because my hotel room window there faced more or less east, I thought it would provide a decent possibility of working the contest.


While the solar flux index (SFI) was only 104, all the solar storms seemed to be behind us, as evidenced by an A-index of 6 and a K-Index of 0.


Unfortunately what sounds good in theory doesn't always turn out in the real world.

I tried three different antenna configurations before settling in on something that would actually work.

I ended up running the radio into a cobra dipole hung from the window curtain rods, with their wires hanging out the window.


The 1000mp's antenna tuner had little trouble tuning the radio on 80 thru 10 meters.
Unfortunately, signal levels were way down, altho I was able to work just about anyone I could hear.
To wrap 15 meters, I enjoyed a groundwave QSO on 15 meters with KG6LRI who was just learning the details of playing in the NAQP.

After a lunch break, I came back to discover 10-meters gone (it barely opened up) with 15-meters right behind it. Moving down to 20 meters I managed a whopping 16 QSOs before the band quickly disappeared.  No problem I figured, I'll just move down to 40 and then 80 - WRONG!

At 00:00z switching to 40-meters found an S-9 to +10 noise level, virtually obscuring any signals
that might have been there.  80 meters brought an S-7 noise level with the same problem.

Because of the noise, I was only able to manage 1 QSO on 40 meters (a W6 station) before getting real and realizing that NAQP was over for the  weekend.  Checking back throughout the evening found the S-9+ noise level continuing, until well after midnight.

Notice the S-7+ noise level on the S-Meter

 In essence, the highlight of this portable operation was being able to test the FT-1000mp features under adverse conditions.

I spent considerable time with the operators manual tweaking many of the numerous menu settings that are behind the scenes of the FT-1000mp transceiver.



This weekend also gave a thorough test to the recent addition of a solid-state disk drive to the laptop I use for running contests.  There is no doubt that faster disk I/O makes contest running (especially remote contest operations) perform more effectively.
The next operating goal for the Yaesu FT-1000mp will be CQ WPX RTTY contest next month.

Because of my dismal QSO total I almost did not submit a log but then remembered my own advice from an earlier BLOG entry I wrote this year on the subject of always submitting a log.
It isn't so important how MANY QSOs I make, but just showing up that really makes the difference.

The NX6T crew managed over 1200 QSOs altho complained of poor condx on 20 meters, a slow to open 40 meters and high noise on 80 & 160.  At least they heard signals on those bands.


While I was bummed by the small number of QSOs made, I nevertheless enjoyed what operating time I was able to manage.

Until N6GEO manages a new setup or at least a functional setup remotely from Twain Harte, I am going to have to come up with other ideas for bay area operations.

DiD YOU play in the NAQP SSB?

How did it turn out?

Is WQ6X one of the RARE QSOs in YOUR Log?

NX6T takes 2nd place in NAQP CW

H u H?

For serious contesters who did not play in the Jan 2nd/3rd RTTY RU, the NAQP CW GiG is the first "real" contest of the new year.  Having run RTTY RU remotely from Fallbrook the weekend before, it was time to sit down in front of a radio with knobs I can twiddle; even if it was a K3 (I prefer my FT-1000mp).


I used Friday evening as a time to settle in and scan the lower bands (160, 80 & 40), giving me an idea of what things will be like Saturday evening.  Luckily no space weather anomalies occurred during the weekend.


While I normally don't drive all the way to Fallbrook to participate in a 12 hour Multi-OP contest, this year  I was already in Burbank for the week; another 2.5 hour drive on Friday was no big deal.



We had a relatively small crew for this event; namely: N0DY, N6CY, N6KI, W6JBR and myself.  Nevertheless, we were all in top form.  Together we turned our Multi-2 operation into a 2nd place finish behind K7JR (manned remotely by KL9A & N5RZ).

N6CY w/N6KI looking for mults

At 10:00 am (local) I opened the contest for the 1st hour on 10 meters.  By 11:30 N6CY made the scene and put STN#2 on 15 meters.  Because we were both running a frequency NX6T ended up on many spotting networks.

By 12:30, N6KI joined us to S&P on 15 meters from STN#3 interspersed with Rick (N6CY) while I mopped up 10 meters via S&P before finally heading to 20 meters to run a frequency.  By 2:00 we lost N6CY, and added N0DY to spell me on 20 allowing N6KI to take over running 15 meters.

After a short nap I came in at 5 pm (01:00z) to see N0DY on STN#2 running a frequency on 40 meters.  Moving him to STN#1 to continue the pileup run allowed N6KI and I to dual-op 80 meters, which was wide open by 5:30 (local).
By 6pm we included a look at 160 into the game altho 160 wouldn't deliver until later in the evening.

N0DY & N6KI running frequencies

By 7:30 N6KI drove into town to bring back some Italian food while I worked 80 and eventually found a nice opening on 1.818.18 mhz to run the frequency.  Using the bandmap and 2nd VFO I was able to sneak in an occasional S&P QSO on 160 during lulls in frequency running.


An important note about 160 meters and NAQP: Just Do It!
I think of 160 meter QSOs as "free" QSOs and in the case of NAQP "free" multipliers; all just for showing up.
160 meters was worth 52k points to us.


Because the C-31 and Stepp-IR yagis are gain antennas and this was largely a North American contest, during the daytime we left the masts in their lower position.  As we moved down to 40 meters, the main tower was raised to 70', enabling the 80/160 inverted V's and taking the 2-el 40 meter yagi to the next level.

For the evening shift W6JBR joined us to wrap things up.  By the time 06:00z (10pm) arrived we were contested-out.  As you can see, our QSO total was quite an impressive 6-band score.

While I was not part of NX6T's NAQP GiGs last year, it is clear that our gang-of-5 operators easily surpassed last year's NX6T score.

DiD YOU play in this year's NAQP?
Is NX6T in YOUR Log?

WQ6X Ron runs RTTY RU Remotely and Robustly

It's hard to believe that it has been two years since N6GEO and myself engaged in a 1st place (worldwide) RTTY RU event as WP2/WQ6X.  Last year (2015) operating as N6GEO we took 1st place for East Bay (EB) section operating from George's Brentwood QTH.

Since last year the Brentwood QTH has been sold.  While George has been working on a remote operation setup from his cabin in Twain Harte, it was unfortunately not ready for this year's RTTY RU.
Client commitments made it impossible for me to make the trek to the NX6T site in Fallbrook so I looked into the possibility of operating remote from Fallbrook's Stn#1 altho actually setup at the W7AYT qth.

With incredible assistance from JR W6JBR we eventually made that happen; altho unfortunately, the 1st QSO didn't happen until 02:15z (8 hours into the contest) - meaning that I missed out on a days worth of access to the 20-15-10 meter bands.
 
On Sunday, either 10 meters opened up before I rolled out of bed at 10 am and then quickly closed or in fact the band never materialized into the San Diego area.  Either way, missing 10 certainly didn't help my score.  Surprisingly, 20 meters was the worst band of all - missing Saturday afternoon cost me a lot.

40 meters was more packed then I have seen in many a RTTY RU.  I felt sorry for the CW guys; especially that lone station on 7.045 blindly calling CQ at 15 WPM.  I don't know if he ever got a QSO, but he certainly was a brave man to attempt such a feat amidst the cacophony of RTTY signals surrounding him.

Remotely, this was my 4th experience (1st RTTY experience) operating "from" NX6T in Fallbrook.  Because internet latency is at the core of remote operations, for me personally, remote operating an SSB contest is NOT going to happen.  I get confused enough on CW and even more so running RTTY remote; attempting to run SSB would probably spin out my sanity.


One of the secrets to remote operation is PATIENCE, coupled with no negative self-labeling.  Running the 10-meter contest remote was tricky enough running only CW; I purposely chose NoT to run SSB.

Once I got into action, my biggest BEEF was the fact that most of the spots in the bandmap, while they yielded signals, the offset was wrong giving no decoding.  On my FT-1000mp I would just turn the tuning knob until the decoding starts.  Using a "tuning knob" over the internet is tricky enough on CW, however add to it a little internet latency and tuning RTTY becomes nearly impossible;
which is why some companies sell a remote operation tuning knob.

My solution to the tuning problem was to pick a "quiet" frequency and call CQ.  After awhile WQ6X was spotted by the skimmers.  (Because the WQ6X callsign is embedded in every lookup database, recognition of my callsign was automatic.)  Stations lined up and I would get an hour run here and there.
In the end, I probably made 15% of the QSOs by way of S&P; I let the rest come to me. The rest as they say is history.

Because I had to be in Burbank on business, I was originally going to make the drive at noon or 2:00.
Then the internet latency again set in.  To make up for lost QSOs I operated all the way to the 00:00z contest end and was on the 680 freeway at 4:40.

While the 273 QSOs is not all that impressive, research on 3830Scores.Com indicates that after all this I may actually sneak a 1st place win for the San Diego section - GO Figure.


 As I said in my previous blog entry, you never know when submitting a "marginal" log will win an award; so, just DO IT!


DiD YOU play in the 2016 RTTY RU?
Is WQ6X in YOUR Log?

The Importance of Submitting a Log for every contest

In May of 2013 I wrote a Blog entry about the importance of submitting a log for every contest you participate in, regardless of how few QSOs you actually make.  (Click here to read that Blog entry.)
Recent events have inspired me to revisit this point.

Submitting a log after every contest has its benefits.

1. It actually makes the log checking process EASIER and FASTER when everyone sends in a log.  Callsigns are less likely to be considered "unique" when they are from a station who also submitted a log.
   
2. Your callsign is more likely to be included in the callsign lookup database(s) for future contests making it easier for operators to conclude that your call is valid when they see it pop up on check-partial lists.
3.  You might actually win a certificate or plaque - which is what this blog entry is all about.

From a competitive contesters' point of view, #3 is the most important.
My attitude USED to be that I would not submit a log unless I thought it would be a clear winner, or at least a contender.  Because we used paper logs and dupe sheets in those days getting a log ready for submission was quite a chore.  Needless to say, I rarely submitted a log.

One year while checking the Sweepstakes results I discovered I would have won a certificate for East Bay (EB) section if only I had submitted a log - my competitor's log ended up being disqualified and became a "check log".  Oooops.  Had I submitted a log, my 2nd place score would have become a 1st place winner.

In the 2014 Sweepstakes phone contest while there were several school club stations on the air evidently none of them submitted a log - no plaques were issued for that category.  A school making 1 QSO could have submitted a log and received a piece of wood - go figure.

Today, thanks to the Cabrillo log format, submitting a log could not be easier.
As I said in the [original blog entry] on this topic, now I submit logs for EVERY contest I play in.
Because I like to piddle around in the numerous "mini" contests, in recent years I have submitted DOZENS of logs for those events.  From time to time I receive unexpected envelopes at my P.O. Box with certificates like this one.

The important thing to note about this contest entry is that I spent barely an hour making those 12 QSOs (9 on CW and 3 on SSB) while waiting for 10 & 15 meters to open up during the tail end of the All Asian SSB contest.  That evening I web-submitted the contest log and then moved on to other things.
100+ days later I am rewarded with the above 1st place certificate.

While we ran 1.3kw for the SSB contest, for TNQP I simply ran one of NX6T's auxiliary K3 radios barefoot into a sufficiently high C-31 yagi, offering lots of signal gain.

From the NX6T Fallbrook location there didn't seem to be a lot of TNQP activity.
In desperation I switched from CW to SSB to make 2 final SSB QSOs before hearing 15 meter Asian signals waft into the Station #2 speaker.   By the time the All Asian contest was over so was TNQP.
After wrapping up the All Asian log I made a Cabrillo file for the TNQP and web-submitted it before
leaving the mountain and heading back to the "real world".

Because QSO party hosts like those running TNQP make it so easy to submit a log, in my opinion there is no legitimate reason to not make a submission.  Wherever possible I submit logs on the same day a contest ends to get it out of my mind.  I also begin writing up the text for what will be the next entry to the WQ6X contest blog.  Before submission I write up a SOAPBOX entry for the log which can also be used for my contest summary submission to the 3830 Scores website.

Contrary to popular belief, contest organizers DO read soapbox entries and sometimes even use them in their results write up for the contest.  N6GEO and I discovered this to be true when we read the 2014 RTTY RU contest result - they printed a quote right from the soapbox comments I wrote for our WP2/WQ6X 1st place (worldwide) finish in that event.  You can see this write up at the WQ6X.Info/WP2 page.

The CQP organizers went one step further by putting operator pictures from our 2013 CQP event page on the CQP home page for nearly 6 months in 2014.  How cool is that?!

Another point should be noted about log submissions.  Some contests (like All Asian) allow you to work stations on multiple bands and then submit the entire log as a single band entry.  Because 20 meters was my best band, for the 2013 All Asian phone contest I ended up submitting the log as a single band 20 meter entry which gave me a 1st place win for USA.
I truly did not see that coming.

While the log submission was a single band entry, the remaining QSOs in the log become a "check log" (making the contest log checking duties easier for the contest organizers), and I ended up with an unexpected 1st place certificate.

The above points are all things to consider when you engage in contest activities.  The bottom line is - ALWAYS SUBMIT A LOG - you never know when it will turn out to be a winner.

Do you dabble in radio contest activities?
Do YOU submit a log for every event?
If not...... WHY NOT?!