If a database was used, then it could easily handle unique sequential
serial
numbers with any number of workstations, since the serial number would not
be committed until the log transaction was written. There is probably an
easy way to implement this with the current "logging technology" and not
even use a database.
This is too simplistic and doesn't reflect what the real issues are. If
you've ever done SS as a competitive multi-single effort you will soon
realize why the numbering gets screwed up. TR does a slightly better
job than WriteLog currently because it increments serial numbers on
networked computers as QSOs get logged. If WriteLog also did this
it would solve 90% of the problem. I think this is equivalent to the
database suggestion quoted above.
A typical competitive multi-single effort in SS will have two to three
(or more) networked computers/radios. One arrangement has a run
operator and a spotter. The run operator may have two radios,
operating SO2R, while the spotter(s) finds unworked stations and
adds them to the bandmap. A second arrangement is for two
operators to each have one radio, one a run operator and the
other doing S&P. Another arrangement is to have a 3rd operator
who is the "pounce" operator, waiting on a spot, trying to sync a
call into a gap in the run operator's transmissions. Late in the contest
this radio is likely to be used in a duelling CQ mode as a second
run station. Note that the two stations never simultaneously
transmit.
The first problem that occurs is when the pounce operator chooses
a spot. He clicks on the spot and immediately a number is assigned
by WriteLog when the callsign goes into its field. He may camp on
the frequency while the run station makes several QSOs, waiting for
the opportunity to call. This is a good time to copy the parts of the
exchange that don't change, and also to anticipate the next serial
number sent. Finally, the pounce operator has a chance to transmit
and sends the callsign. For the sent number to be in the correct
sequence he must clear out all the carefully entered fields to get
WriteLog to assign a new number.
It is possible for QSOs to be interleaved between the two stations.
As long as both stations don't simultaneously transmit this is
permitted under the rules. If this happens then the first operator
sending a number must send the next available number and the
other operator must send the following number. It's possible to
do this in TR, but WriteLog either has the same number on
both computers or the pounce number will lag for the reason
mentioned in the previous paragraph. If repeats are required on
one or the other station then things can get very messy. If
you have to abort a Q because a station disappears in QSB then
you may have to resend that number out of sequence or give
a revised number to the other station (if she's still around).
I understand why Chad, WE9V, said that he just sends whatever
number WriteLog provides. It is much easier, even though this
number will almost always duplicate a number already sent and
it may often be several numbers out of sequence.
-Mike, N7MH
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|