Thursday, October 31, 2019

WQ6X Teams Up w/NX6T for Triple Team Training

N N 6 X --- N 6 K I --- K N 6 D L G
From a "serious" competition standpoint, while the operators @ NX6T are GooD, in the CQ WW
Ssb contest we don't stand a chance of a 1st-place (worldwide) finish.  Instead, while we give it our
best shot, more important is to use this event as an opportunity to Elmer up-and-coming radiosport operators and give me "time in the chair" with the recently perfected Elecraft K3/0 installation @W7AYT.

This was another start-in-Alameda and end-in-Concord remote operating weekend. 
Although everything was well in place to operate WQ6X from W7AYT, Space WX conditions were
not in our favor.  Propagation was so poor that in the end only KL7RA made it to the WQ6X Log.

While we were plagued by solar storms all weekend, @ NX6T a surprising number of DX openings occurred; especially to Central/South America.  On Sunday 10-meters put two dozen QSOs in the NX6T Log.  Switching to the Stepp-IR antenna allowed me to simultaneously run South America and Asia, with a plethora of 0-Point QSOs from stations who happened to be in the signal path to SA.

W Q 6 X (Stn-1) & N 6 K I (Stn-2)
I began the remote operation from Alameda using VNC Viewer & RCForb.  N6KI loaded up Station #1's Voice Keyer memories allowing me to Search & Pounce (S&P) throughout the evening while watching the Houston Astros finally win a World Series game.  After midnight when 40 meters went long, I put a few QSOs into the log and turned it over to N6KI; usually I do the 2am shift but was so exhausted from a long week that sleep took priority.

Late Saturday morning when I fired-up on 15-meters I was surprised to find signals all over the place.  As it turns out, we made more QSOs on 15 meters than we did on 20 - HuH?  That NEVER happens.

Typically it is the CQ WPX contest that provides exotic prefixes/countries.  This year, the W.W. Dx contest brought us a bunch of juicy prefixes.  For this contest, some of my favorites include: 5K0, VP6, 8P5, V47, ZF9, ZP6, FS4, 7A2, 3G1, TG9, CB8, HR9, PY0, BW2, E2, 6W1, V3, V26, ZS6,
CD2, EF8, FY5, VP2, CS5, 5J5, TI7, JR6 & J69.

I often bitch about 0-Point QSOs.  The one thing they are GooD for is propagation determination.  While using the Stepp-IR purposely allows running BI-Directional, on 40-meters in the morning when the Shorty-40 is pointed to Asia, the 20-db F/B-ratio is hardly enough to much attenuate the Kw signal to the Southeast, all but encouraging 0-pointers interspersed with the 3-point Asian QSOs.

Typical for most operations from W7AYT, cobbling divergent technologies is what makes it all work.  For example, while I normally use the Electro Voice 664 microphone, the excellent frequency response while desirable for ragchewing is actually a detriment to contest work.  Instead, I used the 664 as a support stand for turning the Heil PRO-set into a contest mic, allowing me to wear wireless headphones for receiving.

Despite not making  many QSOs as WQ6X, at least there was an opportunity to create updated WQ6X contest .Wav files; many also usable for the upcoming Sweepstakes contest in November. 

Altho the user-level documentation for the RigExpert PLUS is seriously lacking, thru trial-and-error
it was discovered that the output audio control (in proper balance with the FT-1000mp's mic gain/compression settings) can produce distortion-free, yet "punchy" contest audio.

While this year's CQ W.W. Ssb contest was hardly a spectacular affair, it DiD provide a training ground for new operators, new equipment configurations and new operating techniques to be examined and explored.

What about YOU? 

Did YOU work the CQ Worldwide Dx contest?

Is NX6T or WQ6X in YOUR LoG?

Monday, October 21, 2019

WQ6X runs Another 4-out-of-5 October contest GiGs

Similar to the 2nd October weekend, making this last weekend work radiosport-wise took some careful orchestration, interspersing what turned out to be
4 contest activities throughout the weekend.

In furtherance of my 2019 journey to participate in 100+ Contest GiGs, I have been running a bunch
of dual-OP operations from W7AYT and my Alameda location remote into the San Diego Contest Club's NX6T station in Fallbrook (North of San Diego). 

This weekend found me in Alameda the entire time.  While the K3/0 is "parked" @W7AYT, for RTTY contests I have found running RCForb + VNC
Viewer to be more than adequate.  Unlike running
Cw remotely, with RTTY, if there is a brief internet outage, when I get things reestablished, the demodulated RTTY is usually still waiting on the
screen for me when the connection is resolved.

On the "lets'givit-a-shot" list for this weekend were the following 5 radiosport events.
  • [x] - JARTS RTTY Contest
  • [x] - New York QSO Party
  • [x] - Illinois QSO Party
  • [x] - Worked All Germany Contest
  • [x] - Stew Perry 160-meter Contest
The JARTS (Japanese Amateur Radio Teleprinter Society) GiG is similar to the Japanese-sponsored All Asia contest in that operator AGE is the main exchange parameter to be exchanged.  (How about an All Asia RTTY contest?).  While I am used to 75% of the ages reported in the All Asia GiGs to be 62 - 85, in the JARTS GiG it seemed that easily  90% of the participants were 62 to 89 years old. 

Altho not my exact age, I sent "55" in order to stand out from the rest of the field.  When numbers are sent with a (useless) signal report in a RTTY exchange, this weekend I sent it as "5NN 55".  The most confusing exchanges I received were "599 59".  With poor RTTY demodulation the "59" could be seen as a chopped "599", yet it occurred to no one to send it as "5NN 59" - HuH.

N X 6 T  after  Dark
The goal for this weekend was to run the JARTS RTTY GiG for the 1st 12 hours, with some nap time during the slow periods.  Then, @ 14:00z (for NYQP) and 17:00z (for ILQP) I could go county hunting, switching back to RTTY when I can no longer find W2 or W9 stations. 

While the Stew Perry Gig began @15:00z, at 8am (Pdt), the LUF including 160 meters has moved up to 5-mhz and beyond.  The Worked All Germany (WAG) contest also started @15:00z but EU didn't make it to the headphones until much later in the day.  My first 160-meter QSO didn't happen until 03:03z, with the band already in full-swing.

The NYQP and ILQP QSO parties were a COMPLETE BUST, from the Fallbrook perspective.  ILQP was a complete no show, even tho there were NUMEROUS IL stations working the JARTS GiG. 
In the 3830 Score report for the NYQP contest, I made the following comment:
Because this is only a 12 hour contest, the GiG was over before 160 & 80 open in W6-Land here to NY; with pretty much the same problem on 40 meters. Either lengthen the contest or start it at 16:00z or 18:00z, like most other QSO parties.
Nearly every month of every year I complain that - California excepted - most states don't play in their own QSO parties.  It doesn't stop me from looking for counties, however it IS frustrating when the bands are dead because most amateurs in a given state don't even know what a QSO party is.

To check worldwide propagation we have the
NCDXF beacons on 14.100, 21.150 & 28.200. 
I have previously written about these beacons ([CLICK HERE] to read that).  Unlike the CQ W.W. RTTY contest, during the JARTS event there were
no contest stations (who should know better) calling CQ atop the NCDXF beacon on 14.100.

Additionally, for those who know where to look, we have the Russian military beacons on  ~7.039.39. 
I have also written about these beacons.  ([CLICK HERE] to about read that.)  This weekend only the
"F" beacon was heard.

Last weekend, horrible Space-WX condx. plagued the contest activities.  Altho the A & K indexes were low this weekend, because the SFI is a lowly 65, signals were often weak; altho, thanks to the low SFI, 160 - 80 - 40 meters produced some surprising DX runs. 

Running  160 using  R C F o r b
During my initial run on 1831.31 in the Stew Perry contest, out of nowhere came a call from CX6VM @03:30z; rather early for SA to the West Coast.  A surprise call from RT0F @06:55z added a nice sweet multiplier to the log.  Overall, out of laziness, most of my time on 160 time was spent Calling CQ SP and letting stations come to me. 

While there were a lot of "juicy" spots in the 160 bandmap, most of the DX stations could not be heard @ the NX6T location.  This is a continuing problem for us atop the hill in Fallbrook; DX stations often hear us and give a call only to be disappointed that we can't always "hear back".  We are heard, thanks to running high power.  No, we are not ignoring you, the Coaxial-Bazooka being at only 40' doesn't hear as good as it transmits.

Eventually, I ran out of new 160-stations to work, relegating one more stint in the JARTS GiG before taking a several hour nap.  At 12:23z I was back at it on 40 meters hoping for another JA run.  Unfortunately, there were virtually no new AS/OC stations. 

Because 2-point QSOs are better than 0-point QSOs, the Shorty-40 was turned back to N-E working Midwest stations before the band faded in that direction.  One last look at 160 meters produced 3 more QSOs with N5ULS closing out the Stew Perry 160 LoG.

After a few hours sleep, at 17:36 15 meters was given another chance.  Unfortunately, it was not the same as Saturday encouraging me back to 20-meters to run 14091.91 until non-listening stations took over my busy frequency @18:12z.  Moving to 14105.55 gave some "breathing room" until I ran out of new stations to work.  A trip to 21089.89 put 3 more QSOs in the log, including a surprise call from TI2OY - and then, NOTHING.

A last trip back to 20 meters found WQ6X calling CQ on 14088.88, 14091.91 & lastly 14113.13 where I enjoyed a pileup of JA stations.  Running out of non-dup 20-meter stations, at 23:00z I spent the last hour on 40 meters finding that E-Coast and Midwest stations were already working there way to the west coast.  The final JARTS QSO was from YV4ABR; a surprise considering that @23:49z we are lucky to work Texas, let alone Venezuela.

When it was all over, the final task was to produce the Cabrillo files, post the 3830 Scores and piece together the ending stats in preparation for this BLOG.  N1MM+ does a reasonable job of producing colorful stat screens.  With a little cut & paste by way of the old PC Paintbrush program, the stats can be put together in one view.

How did Your weekend Go?

Did You work the JARTS RTTY or Stew Perry 160 contest GiGs?

Is WQ6X in YOUR LoG?

WQ6X Runs 4-out-of-7 October Contest GiGs

Making this last weekend work radiosport-wise took some careful orchestration, beginning in Alameda and wrapping it all up in Concord; both QTH's at opposite ends of the EB (East Bay) ARRL section.
To further my 2019 journey to participate in 100+ Contest GiGs, I have run a bunch of dual-OP operations from W7AYT and my Alameda location remote into the San Diego Contest Club's
NX6T station in Fallbrook (North of San Diego).

On the "lets'givit-a-shot" list were the following 7 radiosport events.
  • [x] - Makrothen RTTY Contest
  • [x] - Nevada QSO Party
  • [x] - Oceania Dx Contest
  • [x] - Scandinavian Activity Contest
  • [x] - Arizona QSO Party
  • [x] - Pennsylvania QSO Party
  • [x] - South Dakota QSO Party
The Makrothen GiG is fast becoming one of my FAVorite RTTY contests.  According to the Makrothen website, the word "Makrothen" is Greek for "great distance" - we score more points for working stations further away from our operating location. 

This contest showcases the following uniquenesses:
  • There are no multipliers
  • QSO points are not fixed at 1, 2 or 3 points.
  • QSO points are computed by the Km (kilometer) distance between the two stations.
  • Contest operating periods are 3x 8-hours each, sandwiched around two
    8-hour off periods in between.
  1. - 00:00z to 08:00z on Saturday
      08:00z to 16:00z - Off Period
  2. - 16:00z to 24:00z on Saturday afternoon
      00:00z to 08:00z - Off Period
  3. - 08:00z to 16:00z on Sunday morning

As a result of the above, a Million point score is JUST getting started.
What makes this contest fun is that with every QSO I get immediate feedback on the distance between my California location(s) - the SF Bay Area and San Diego area - and each station worked.

Altho Space-WX condx were rather dismal, a 40-m QSO run to JA early Sunday morning followed by a 20-meter opening to EU during the final hour of the contest provided nearly 1/3 of the final score.

A major reason for this weekend's operation was to thoroughly test-run the Elecraft K3/0 for
remote operation to Fallbrook as NX6T, in conjunction with WQ6X operations from W7AYT. 
For this operation, nearly everything went extremely well - the new operating mantra being "IPCONFIG/Renew".

Interspersed with the Makrothen contest were several state/area QSO parties for AZ, PA & SD. 
I heard virtually NO SD stations other than the ONE I worked.  PA stations were more plentiful,
but where were the rover stations activating county lines. 

While there were no AZ rover stations that I am aware of, there were at least a reasonable number
of fixed stations that at least we had someone in Arizona to talk to.  I am so used to the 100's of Californians activating ALL 58 California counties that it surprises me when other states don't
play in their own GiGs.

For the AZQP, because there were so few Arizona stations calling CQ, I found a frequency and called: CQ AZ de NX6T, NX6T/Ca.  Instead of calls from AZ stations, I received calls from KY, GA, TN, TX, UT & W6.  HuH?  Per the Why You probably should not call me BLOG, if you don't know what "CQ AZ" or "NX6T/Ca" means, then you should not call me.  If I send "AZ stations only",
unless you are in AZ, you should not call me. 

In many state QSO parties this year many stations with call prefixes not reflecting the state were operating from were calling CQ, making it sound as if they were NoT in that state but looking for stations in that state.  When I asked "are you in AZ/PA/GA", they would say "Yes".  I shouldn't
have to ask - you should make it clear from the beginning.  For example, if you ARE in Arizona
and your callsign does not make that clear, then  add the county to your callsign, such as: WQ6X/MCP or NX6T/PNO.

After all the contest events are over I am then faced with all the administrative things to do such as: taking pictures and screenshots, posting 3830 scores and  submitting the .Log files for each contest event.  To make things a bit easier, I used the above checklist.

Did You play around in any of the above contests?

Is WQ6X or NX6T in Your LoG(s)?

Tuesday, October 8, 2019

WQ6X as K6C "Kicks-it" for another California QSO Party

For this 2019 CQP event, I decided to take the easy (trnsl. Lazy) way out by registering the K6C callsign and repeating last years dual-OP with NX6T from W7AYT's QTH in Contra Costa county.  Having registered the W6C callsign many times before, to alleviate the potential "boredom-factor", K6C (Kilowatt Six California) was used for state-recognition variety.

Using K6C required that a [new] set of N1MM .Wav files be recorded with the proper file-path assignments made to the SSB macro keys.  While there are many ways to make .Wav files,
I prefer the [freeware] Audacity program.  For my purposes, Audacity is WAY over complicated. 
Each time I use it, I stumble around and eventually produce the set of files that are needed.
Maybe one day I'll figure it out.  Until then, stumbling-thru works just fine.

The recently installed RigExpert PLUS, allowed the use of its built-in audio-codec to play the N1MM+ .Wav files directly to the transmit audio (no external cables needed); of course I didn't discover this trick until AFTER CQP was over.  RigExpert made an INCREDIBLE piece of hardware; unfortunately, there exists practically no user-level documentation for the unit, outside of how to hook it up to the various AFSK/Psk platforms that have emerged since the PLUS unit's debut in 2007.

The goal for this weekend was to run another dual-OP GiG, remoting into NX6T via the Elecraft K3/0 while running as K6C from Contra Costa county.  That more-or-less happened, altho not in
the order I was "expecting".  An unfortunate hardware conflict prevented using the K3/0 (for its intended purpose) until AFTER CQP was over - until then, it was RCForb to the rescue. 
Minus some pain-the-ass internet dropouts, I managed to stumble through and make
two frequency runs on Saturday afternoon and around 3am Sunday.

Before EVERY CQP Event I update the CQP.Org Admission Ticket
(they don't Doit anymore, so I Do).  This year I also posted a "Blast from the Past" BLOG, reminiscing about CQP expeditions I've been involved with during my 20 years of participating in the California QSO Party.
Amongst other things, CQP expeditions are about Emergency Preparedness. 
Even when I operate from a domestic QTH - as done in 2017 - 2019, there is
still the preparedness aspect of each unique operating configuration; either from the remoteness of the location, or the equipment configuration(s) required to make it all happen.
Nearly every operation from Concord finds me trying out new tweaks to the WQ6X Lazy 8JK Sloper, a new installation of the Elecraft K3/0 or some new audio-cabling arrangement in an attempt to leverage the dual-receive capabilities of the
FT-1000mp.  ([CLICK HERE] to read the original BLOG on that subject.)
For CQP 2019 no antenna modifications were needed. 
I simply leveraged the antenna farm to my advantage:
  • Comet CH-250 Vertical
  • WQ6X Lazy 8JK Sloper
  • WQ6X JA Sloper (that can never hear JA)
  • Hy-Gain 3-el. 10-m Long John yagi (just in case)
The remoting-IN to NX6T aspect of this trip was frustrating. 
Each GiG using the K3/0 turns up new operating configurations. 
This weekend I learned the importance of:  IPCONFIG/Renew, allowing
the Toshiba laptop to use the Mikrotik Ethernet hub as an internet HoT Spot.

I began CQP an hour late.  Recording .Wav files and tweaking CW macros at the last minute
always seems to take the first hour.  Oh wail - band conditions @ W7AYT were marginal anyway,
so I probably didn't miss much.  Contrast that with NX6T where there is a 70-ft tower sporting:
  • 3-el Stepp-IR
  • 2-el Shorty-40
  • 80-m Coaxial Bazooka Inv-VEE

  • 160-m Coaxial Bazooka Inv-VEE

There is also a new RX-Loop at NX6T, but I was so busy running a frequency that time was never found to give it a close listen.  Here is where operating onsite has it's advantages.  Onsite I can
more easily manipulate the Rx-Loop and/or have another operator (if one is present) to turn it
for me.  We certainly needed something; the 80/40 noise-levels in Fallbrook were horrendous. 
In contrast, the noise-level @ W7AYT was MUCH less; then again, so were the signal-levels.
All the effort that was made to create effective .Wav files was ALMOST not worth it.   Using the SO2-V approach, alternate CQ's were made on each band; first on Cw, then on Ssb, and finally,
back to Cw.  Despite all the efforts to make Ssb QSOs, no one came back to my CQ calls. 
The 3 Ssb QSOs made happened by S&P'ing - GO Figure!  Am I missing something?

When it was all over, it would seem that those 3 Ssb QSOs guaranteed K6C a mixed-mode (assisted) 1st-place from Contra Costa county; running as CW-only would probably have resulted
in a 3rd-place finish at best.
On the NX6T end of things, running the DX Log software (a WinTest spinoff), we turned in a reasonable score, considering who/what we had to work with.  While other W6 stations made a section sweep, for some reason, NT (Canada's Northern Territories) eluded us.  I picked up our 56th mult (MS) in the middle of the night as the Mississippians were waking up.  Our 1117 QSOs should be enough for a 1st-place from San Diego (SDIE).
We received the above e-mail from K2QU.  While I was on shift when that happened, I didn't recognize the call until, looking up that time in the log, I saw it was W2DXE.  I remember that
contact very well.  Being JUST above our HORRIBLE noise-level, his callsign seemed to sound different every time I heard it. 
If you have read my Role of Respect in Radiosport BLOG series, you know that I hate it when operators give up too easily.  Whenever possible I want to log the contact.  While the QSO itself is only worth 3 points, when you factor in the multiplier multiplication-factor, that one QSO was actually worth 171 points overall - think about that when you are tempted to blow-off a QSO (with no other stations calling).
Because I often run the "night shift" during radiosport events, I am used to being up at that hour at other times.

I am still an avid SWL'er, even tho the volume of SWBC stations has dropped considerably in the last 50 years. 

The 20-yrold Yaesu FT-1000mp makes an OUTSTANDING SW receiver; the CH-250 vertical makes an excellent SW listening antenna.  Of the transceiver's 100 memories 25 have been dedicated for listening to SWBC stations. 

I have taken a liking to Radio New Zealand [International] - RNZ.  Around 08:00z or 09:00z they come through nicely in the SF bay area on 5.945 mhz.  With the lower noise-level (compared to Fallbrook),
I would give RNZ a 55444 SINPO rating.  Also for fun, on Saturday I enjoyed an 8.5% Peanut Butter stout, thanks to W7AYT's belated birthday gift - Thanks Dennis.
That is all I have to say about CQP 2019 for now, altho I may well have more to say after the log submission deadline (the K6C log was submitted on Sunday).  While this was far from the most memorable CQP I've ever been a part of, it was an interesting challenge.  Contrary to my BITCH
about other QSO parties, in CQP, we Californians DO participate in our own QSO party.
What about YOU?
Did YOU work the California QSO Party?
Is NX6T or K6C in YOUR log?



Monday, October 7, 2019

Blast from the Past: California QSO Party (CQP)

Prior to the year 2000 I never paid attention to CQP - the California QSO Party.  Since then
I've not missed a GiG, altho some of my early solo events lacked a camera person.  The "Under Construction" sign is indicative that my CQP events are always in some way "under construction".
The WQ6X.Info CQP web section is loaded with documentation of all the events during the last 19 years.  Who would've imagined there would be such a variety of different CQP operations in those years; some new, some repeats.

My first exposure to CQP was with the W6ML crew (W6KC, W6SW, W6JTB, et. al) at Mammoth lake (in Mono county) during 2000 - 2003.  As you can see, we took 1st place for the Expedition category every year.

My first solo CQP events occurred from an under construction multi-million dollar house in the
Ojai valley in Ventura (VENT) county.  Initially, I operated from the spacious downstairs garage.  Later, operations moved a folding table to an upstairs bedroom where it was much warmer. 
Even back then, I insisted on using some form of wireless headphones.

Hooking up with N6GEO (George) we put Modoc county on the radio 3 times: 2010, 2012 & 2013.  While our 2012 trip was largely a disaster, we nevertheless took a 1st place for Modoc.  In 2013,
we not only took 1st place Modoc, but also for the entire low power M-M Expedition category.
  •  [CLICK HERE] to read the web section about our 2013 event.
  •  [CLICK HERE] to read the contest BLOG about our 2013 event.

Backing up to 2011, George suggested we take his cruiser out on the river, literally JUST
inside Sacramento county by several hundred yards.  Our 1st-place in SACR was certainly a break
from those LONG trips to Modoc (altho we would repeat that Modoc expedition in 2012 & 2013). 
  • [CLICK HERE] to read the web section about that event.

As we were deciding what kind of operation to put together for 2014, the CQP website that year showcased our 2013 event - how cool is that?  The way I look at it, they must've been DESPARATE for website copy in order to showcase our pictures for nearly 6 months - wOw!

The Downside, as I explained on the CQP 2014 webpage was that our planned trip to Tuolumne
was sidelined until 2015.  Instead, we setup an ad-Hoc operation from George's Brentwood QTH. 
The UPSIDE is that we set a county record for Contra Costa county from that operation.
  •  [CLICK HERE] to read the web section about the 2014 event.
  •  [CLICK HERE] to read the contest BLOG about our 2014 event.

In 2015, operating as W6E we put together a TUOL expedition in Twain Harte for CQP-50, devising
a 2-station portable operation from George's mountain cabin.  Our simple operation netted a 1st-place from Tuolumne county.
  •  [CLICK HERE] to read the web section about our 2015 event.
  •  [CLICK HERE] to read the contest BLOG about our 2015 event.

In 2016, the Twain Harte cabin was available, but N6GEO was on vacation with his XYL. 
Registering the W6K callsign I gave the newly acquired Yaesu FT-1000mp it's first contest run
(for WQ6X anyway - previously the radio had been part of N6VR's early SO2-R operation from Ojai).  Not only did W6K take 1st-place from TUOL, a county record was set, which has yet to be surpassed.
  •  [CLICK HERE] to read the web section about my 2016 event.
  •  [CLICK HERE] to read the contest BLOG about my 2016 event.

While I was making plans for CQP 2017, the CQP website showcased my W6K operation next to the K6M Modoc expedition from Bend Oregon  - Hey! they stole our K6M callsign.  As you can see, it is a GooD idea to take pictures at every event; you never know who might want to sneak a peak at a Blast from the Past.

For 2017, being in a lazy mood/mode, I decided to take "the easy way out" and run a CQP operation for the 1st time from W7AYT's Concord QTH in Contra Costa county.  When it was all over, I was shocked to discover that K6T (Kilowatt Six Tango) set a county record for CCOS.  Since then,
other expeditions have leveraged K6T to great success.
  •  [CLICK HERE] to read the web section about my 2017 event.
  •  [CLICK HERE] to read the contest BLOG about my 2017 event.

That leaves us with 2018.  Thanks to N6KI's efforts I took possession of an Elecraft K3/0 allowing
me to more easily run remote into NX6T in Fallbrook and also running as W6C from Contra Costa county (CCOS).  While W6C didn't set any records, at least a 1st-place for CCOS was made.
  •  [CLICK HERE] to read the web section about my 2018 event.
  •  [CLICK HERE] to read the pre-2018 CQP contest BLOG.
  •  [CLICK HERE] to read the contest BLOG about my 2018 event.

How did 2019 turn out?
Well.... you'll just have to read the upcoming BLOG entry on this last weekend's operation;
once I sort out all the pictures and web-links, there will be a LINK to it.

Do YOU ever play in the California QSO party (CQP)?

Is one of the above callsigns in YOUR Log?