This last weekend began with the 24-hour FOC QSO Party event. The "CQ BW" is an operating event, not a contest, which is why it is listed on the WA7BNM Contest Calendar ([X]), yet not listed
on 3830Scores.Com ([X]).
The above WQ6X 3830 submission (close-up below) says it all, altho I have some details to add.
On Saturday while there was allegedly an Alabama QSO Party (ALQP) in progress, I never heard anything - daytime band conditions SUCKED, so I took time to de-thread the morass of audio-filters cables/wires that have accumulated at this constantly evolving portable operation and start over.
As improvements are made to integrate numerously different audio filters into one operational configuration, even with initially organized intention, wires and cables can become hopelessly confused. By the 00:00z SPRINT start time, still no Alabama was heard in the SF East Bay - the ALQP and SPRINT both ended at the same time (04:00z), leaving the QSO Party an unfulfilled dream.
As improvements are made to integrate numerously different audio filters into one operational configuration, even with initially organized intention, wires and cables can become hopelessly confused. By the 00:00z SPRINT start time, still no Alabama was heard in the SF East Bay - the ALQP and SPRINT both ended at the same time (04:00z), leaving the QSO Party an unfulfilled dream.
Most FOC on the air activities are between members only. With this GiG, non-members can not only work FOC members, but they can also work non-members as well. Because the FOC QSO Party ([X]) is NoT a contest, I took a more casual attitude towards making FOC QSOs, saving the excess adrenaline for surviving the SPRINT GiG - it turns out I would need it.
In general, the NA Sprint contest opens on 20-meters, drops to 40 when we run out of new contacts and (for me) ends with a combination of 40 & 80; altho, 80-meters was nearly not worth the effort for only 5-points.
Within 2-minutes on 20-meters, shack-RFI took out the RigExpert PLUS CAT control unit.
I could paddle-send Cw thru the unit, altho the N1MM software lost the serial ports. The ability
to run the contest with function keys on 20-meters was a BiG ZERO. Fortunately, during a previous SPRINT contest, the FT-2000's onboard Cw keyer memories were already loaded to send most of
the needed info, requiring only the callsign and the QSO# to be sent manually. Using 2-handed gymnastics, I would send the caller's callsign, press F4 to send MY callsign, manually send the QSO # (sometimes twice) and then press F2 to send "RON CA". Once I deemed 20-meters a done-deal, the move was made down to 40, without looking back.
I could paddle-send Cw thru the unit, altho the N1MM software lost the serial ports. The ability
to run the contest with function keys on 20-meters was a BiG ZERO. Fortunately, during a previous SPRINT contest, the FT-2000's onboard Cw keyer memories were already loaded to send most of
the needed info, requiring only the callsign and the QSO# to be sent manually. Using 2-handed gymnastics, I would send the caller's callsign, press F4 to send MY callsign, manually send the QSO # (sometimes twice) and then press F2 to send "RON CA". Once I deemed 20-meters a done-deal, the move was made down to 40, without looking back.
Restarting the RiGExpert PLUS brought back the serial ports which allowed me to run 40 & 80 under complete computer control, like the "BiG BoYs". Saturday's spurious Space-WX didn't help matters, with all manner of flare-ups and BELCHES until well past midnight. By the time the storms were over, so were all of the events. 80-meters produced only 5-QSOs, hardly worth the time spent - at LEAST,
I could say I was there.
I could say I was there.
The only thing left of significance was hearing the Russian "K" propagation beacon (on 7038.8) reasonably loud at 06:30z; altho this time the beacon exchange was "K K K K K", whereas, a couple of weeks ago it was "K K K". Someone is OBVIOUSLY attending to these Russian beacons - the Mystery DEEPENS.
DiD YOU work the FOC QSO Party and the NA Sprint Cw contest?
Is WQ6X in one of YOUR LoGs?
No comments:
Post a Comment