[Top] [All Lists]

Re: [CQ-Contest] SO2R technique

To: <cq-contest@contesting.com>
Subject: Re: [CQ-Contest] SO2R technique
From: "Robert Naumann" <w5ov@w5ov.com>
Date: Mon, 7 Aug 2006 07:19:59 -0500
List-post: <mailto:cq-contest@contesting.com>

Thank you for posting your message.

Your observation is correct. It's not easy to do SO2R, and you have hit on
one of the main reasons why it does not double your capacity simply by
adding the second radio.

Being able to blend the two together is one of the skills you will need to

Try setting a longer delay between CQs to start with along with trying to
use the second radio when you know the rate will be lower.

GL & 73!

Bob W5OV

-----Original Message-----
From: Guy Molinari [mailto:guy_molinari@hotmail.com] 
Sent: Sunday, August 06, 2006 7:08 PM
To: cq-contest@contesting.com
Subject: [CQ-Contest] SO2R technique

I'm an SO2R newbie.   Now that I have a basic CW SO2R setup off the ground 
(one DX contest and one domestic contest so far) the first problem that I 
have encountered revolves around operating technique.

The problem.

How do I time and synchronize my callls on the second radio without 
interrupting the CQ'ing on the run radio.   It seems to me that the highest 
priority is effectively soliciting Q's on that radio while quickly working 
good stuff on the second.   I'm finding that it is NOT EASY (like any good 
skill that must be acquired).   I find that whenever the station I'm trying 
to call pauses to listen for an answer, my run radio is still transmitting.

The most obvious solution is to turn auto cq off when I find a new station 
to work on the second radio and turn it back on when searching for another 
one.   This leaves my run frequency vulnerable.  Especially to the guys to 
tune to a QRG (mine) wait a half second.  Send QRL?.  Wait another half 
second.  And then proceed to tell me that I should QSY.

There must be a better way.   Thoughts?

73 - Guy, N7ZG

CQ-Contest mailing list

CQ-Contest mailing list

<Prev in Thread] Current Thread [Next in Thread>