Just for clarity, I think it's important to point out that #1 applies to
lockout over a network, not when using Writelog's SO2R features with two
transmitters connected to the same computer. In the latter case, you can't
transmit on a radio without moving the transmit focus to it (manually or via
SO2R switching features), and that will automatically terminate any
transmission that may be in progress on the other radio. Since you can't
transmit with the paddle or mic without moving the transmit focus, this
works whether you use function key messages or manual transmission.
Lockout over a network can be done, but it's a pain to implement. There are
all sorts of timing bugs that can occur, and "what to do" issues (like, What
do you do when another radio is transmitting? Queue up or make the op try
again?) In the case of multiple radios on the same band, it's better to use
a smart hardware lockout mechanism.
73, Dick WC1M
-----Original Message-----
From: Ed Muns [mailto:w0yk@msn.com]
Sent: Sunday, September 04, 2011 1:58 AM
To: writelog@contesting.com
Cc: 'RA'
Subject: Re: [WriteLog] New CQ WW rule on lockout
SSB and CW do work the same as RTTY with regard to the lockout in WriteLog.
What is different, though, is that CW may be sent by paddle (or, SSB by
microphone) and WriteLog has no way of knowing and cannot invoke its
lockout. Therefore, the WriteLog lockout is bypassed when CW and SSB is
sent "outside of WriteLog". RTTY is different than CW and SSB in that 100%
of all text is sent through WriteLog (via messages or keyboard typing) so
that WriteLog can always invoke its software lockout.
In summary, there are two ways in which the WriteLog lockout doesn't really
meet the CQ WW lockout rule completely:
1. There are a few milliseconds of overlap, i.e., simultaneous transmission
of two transmitters, when the LAST ONE WINS option is triggered. This was
Randy's point (I believe) and due to timing delay between shutting the
active transmitter down before the inactive one starts up. Perhaps some
coding enhancement could fix this, but Wayne would have to comment about
such viability.
2. Per the explanation above, both CW and SSB operation in the majority of
setups has commonly used ways that WriteLog cannot know to invoke the
lockout.
I don't consider #1 a major infraction because my belief is that operators
should not utilize the lockout to prevent simultaneous transmission.
Rather, the operator should never initiate a second transmission until the
first has completed. Thus, the lockout is like a fuse in hardware and is
only a failsafe for those rare occasions where the operator inadvertently
triggers a second transmission before the first is complete. Moreover, a
few milliseconds overlap is irrelevant (my opinion) and the first
transmission is effectively interrupted from a communication standpoint.
Therefore, only a properly designed HARDWARE lockout will completely meet
the CQ WW lockout device rule. This is not a shortcoming of WriteLog or any
other software logger, but simply a recognition that software loggers cannot
provide the level of lockout required for CW and SSB. RTTY mode uniquely
can be adequately locked out, if point 1. above is acceptable to the CQ WW
committee.
Ed - W0YK
Don, AA5AU, replied:
> Good question Randy but I would think SSB and CW should work
> similar to RTTY.
Randy, K5ZD, commented:
> I can see where this would work for RTTY where the computer
> is always doing the sending. How does it handle CW or voice?
> Again, probably ok when the computer is doing the sending,
> but what if one of the ops presses the footswitch and starts talking?
>
> Is the network interlock really fast enough to insure there
> are not too signals on the air at the same time?
Don, AA5AU, answered:
> > When using more than one computer, either as SO2R or Multi-Op, they
> > must be networked and connected to each other via WriteLog.
> Use "Link
> > to Network" command which I think is on the WL Setup menu.
> >
> > When this is accomplished, both "First one wins" and "Last one wins"
> > become available in the Setup menu on each PC. Select the
> same option
> > on each PC. Either set all PCs to "First one wins" or all PCs to
> > "Last one wins". The lockout is performed over the network. Works
> > well. I've been doing this for SO2R on 2 PCs for years. Use "Last
> > one wins" for SO2R and I am guessing "First one wins" for Multi-Op.
Mark, K6UFO, asked:
> > >How do I setup my Multi-op network of computers to meet
> the new CQ WW
> > rule on lockout?
> > >
> > >The new CQ WW rule:
> > >
> > >> 12. When two or more transmitters are present on a band,
> either a
> > >> software or hardware device MUST be used to prevent more
> > >
> > >> than one signal at any one time;interlocking two or more
> > >> transmitters
> > >
> > >> on a band with alternating CQs (soliciting contacts) is
> not allowed.
> > >
> > >I understand how to set this up when the two radios are
> connected to
> > >one
> > >
> > >computer, using "Radio: Number of radios" and "Setup: RTTY
> Single Tx
> > Lockout".
> > >This is how I do SO2R operation.
> > >
> > >
> > >But how does this work for radios connected to different
> computers on
> > >a network? Assume I plan to have four radios, connected to four
> > >different computers for
> > >
> > >four operators in a Multi-2 category. During some of the time, an
> > >operator may
> > >
> > >want to go looking on the same band as another radio. Will
> > >
> > >"RTTY Single Tx Lockout--First one wins" prevent him from
> > >transmitting over the
> > >
> > >other radio?
> > >
> > >It's time consuming to set all this up and test it, so I'd
> like your
> > >guidance and
> > >
> > >suggestions in advance, Thanks,
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|