RTTY
[Top] [All Lists]

Re: [RTTY] AA5AU Contest Notes now multi computer n1mm SO#R

To: <rtty@contesting.com>
Subject: Re: [RTTY] AA5AU Contest Notes now multi computer n1mm SO#R
From: <john@kk9a.com>
Date: Sat, 16 Feb 2013 15:59:58 -0000
List-post: <rtty@contesting.com">mailto:rtty@contesting.com>
The single op category is only one operator and one transmitted signal at a 
time, regardless of how many radios, computers and amps that he has.  This 
is clearly a single op effort and not a multi. Try doing SO2R sometime 
before you criticize, it is not that easy. I certainly could have done 
better and had a more accurate log last weekend if I had a second operator 
running the second station. A good efficient operator using a good antenna 
system can still do quite well using only one radio.

John KK9A



To:rtty@contesting.com
Subject:Re: [RTTY] AA5AU Contest Notes now multi computer n1mm SO#R
From:Ed <w3nr@comcast.net>
Date:Fri, 15 Feb 2013 20:39:03 -0500

On Feb 15, Mark wrote:
> I've run n1mm with two networked pcs, one controlling an so2r pair and the
> other computer
> running a single rig.  You will need to set the log up for a multi 
> something
> category to get
> the computers talking.  In a serial number contest you'll have to verify 
> they
> are done
> correctly for your single op category.

What is wrong with this picture. Where do single-ops fit into this. I'm 
saying
those of us that do not have 3 radios, 3 antenna systems, 3 amps and all the
misc items needed to run "multi something". If you need to setup the 
software
for "multi something", then you need to send in your log as "multi 
something".

And you wonder why the non "multi something" place so low in single-op 
category.

Guess you all need to just keep patting each other on the back......don't 
think
about all of the real single-ops that gave you all those Q's and mults.

Ed W3NR 

_______________________________________________
RTTY mailing list
RTTY@contesting.com
http://lists.contesting.com/mailman/listinfo/rtty

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