Brian, Thanks for the reply. But I defy you to know when I am on radio 2 by
listening to my run frequency. I can answer a CQ response and interleave a
second radio 2 Q and you would not know the difference. The magic of doing
that is “the art”. And when I can’t do it, I don’t call the Radio 2 Q.
The only time I would be “coming back to my frequency” and hoping to get back
on is if I took a bio break. And if I lost it, I lost it.
I am sure many other SO2R operators feel the same as I do.
73
Ed N1UR
From: brian coyne [mailto:g4odv@yahoo.co.uk]
Sent: Tuesday, March 14, 2017 1:57 PM
To: sawyered@earthlink.net
Cc: CQ-Contest Reflector
Subject: Re: [CQ-Contest] PJ4G ARRL DX SSB Recording by N2IC
>>>I am not "using more bandwidth" on the same band.
That is debatable ED and is only really true where an op returning to the first
radio following a cq,call,or contact,on the second radio cedes that first
frequency when finding another stn has moved in. How many do that without
starting a frequency fight? - I don't come across many.
73 Brian 5B4AIZ.
_____
From: Ed Sawyer <sawyered@earthlink.net>
To: cq-contest@contesting.com
Sent: Tuesday, 14 March 2017, 15:53
Subject: Re: [CQ-Contest] PJ4G ARRL DX SSB Recording by N2IC
For the record, I often SO2R on the same band. However I am not dual CQing
on the same band. So - I am not "using more bandwidth" on the same band.
I agree with KK9A that if 2 or more bands are wide open, dual CQing on 2
bands is no different use of space than dual CQing on one band. But in the
bottom half of the sunspot cycle, there is a difference because for good
chunks of time, there might be only one optimum band for a circuit (ie - NA
to EU). I think ARRL should make it against the rules like CQ has.
Ed N1UR
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
_______________________________________________
CQ-Contest mailing list
CQ-Contest@contesting.com
http://lists.contesting.com/mailman/listinfo/cq-contest
|