[WriteLog] Re: Serial Numbers in Multi Operations

[bruce]

I had to check this myself but what he is doing is OK by the rules. For 
SS there is no band change restriction. There is also no reason why both 
transcievers couldn't be on the same band as long as they don't transmit 
at the same time. This does seem like a very agressive setup and 
probably isn't what anybody had in mind when they made up the category 
"Multi-Single" but it seems OK.

Now, why can't Writelog handle this? It's networked and certainly knows 
that there was another Q with the number it's using. It certainly should 
be possible to handle this although it might not be easy.

BTW, I have no intention of every operating this way.


Bob Naumann wrote:

> Hi Chad,
> 
> Regardless, multi-single contest rules do not allow for that to happen - except for CQWW which does not use serial #'s.  
> 
> In a multi-single you should not be operating on two bands at once under any circumstances.  
> 
> Multi-single rules are the most restrictive (10 minute rule or # of band changes) in order to prevent this sort of practice, where you're really multi-2 or multi-multi.
> 
> 73,
> N5NJ
> 
> 
> ============================================================
> From: Kurszewski Chad-WCK005 <chad at motorola.com>
> Date: 2004/11/29 Mon PM 02:49:10 CST
> To: n5nj at gte.net,  writelog at contesting.com
> Subject: RE: [WriteLog] Re: Serial Numbers in Multi Operations
> 
> He said he "started to enter a Q".  He didn't say anything about
> working (trasmitting) two stations at once.  WL assigns a number
> as soon as you start typing in a call.  You will also see
> this behavior as SO2R in WL and you enter a call in each call
> entry area, you will get numbers assigned, and if you wipe the
> first one, that number is skipped and never reassigned.
> 
> I've given up on totally sequential numbers, and as others
> have said, it doesn't matter as long as you log what was sent.
> I proved this to myself last year during SS CW where I submitted
> a M/S log with funky numbers and ARRL had zero problems with
> that.
> 
> Chad WE9V
> 
> 
>>-----Original Message-----
>>From: writelog-bounces at contesting.com 
>>[mailto:writelog-bounces at contesting.com] On Behalf Of Bob Naumann
>>Sent: Monday, November 29, 2004 2:38 PM
>>To: writelog at contesting.com
>>Subject: Re: [WriteLog] Re: Serial Numbers in Multi Operations
>>
>>
>>Al,
>>
>>You are not supposed to work two stations at once as a multi-single.
>>
>>This is a rule violation.
>>
>>There is no reason for WL to allow you to do this.
>>
>>73,
>>Bob N5NJ
>>
>>============================================================
>>From: Aldewey at aol.com
>>Date: 2004/11/29 Mon PM 12:07:13 CST
>>To: writelog at contesting.com
>>Subject: [WriteLog] Re: Serial Numbers in Multi Operations
>>
>>In a message dated 11/25/2004 10:31:04 PM Central Standard 
>>Time, Aldewey 
>>writes:
>>
>>
>>>
>>>I know this has probably been discussed before but I just 
>>
>>wanted to see if 
>>
>>>there is a simple answer.
>>>
>>>In our Multi-Single SS Operation, we were running two 
>>
>>networked stations.  
>>
>>>If we started to enter a Q in the entry window on Station 
>>
>>#1, a Serial Number 
>>
>>>was automatically assigned.  If the op on Station #2 starts 
>>
>>to enter a Q at 
>>
>>>the same time, the same serial number is assigned. Once 
>>
>>these numbers are 
>>
>>>assigned, there doesn't seem to be a way to change it.  If 
>>
>>the Qs are both 
>>
>>>completed, they both go in the log with the same QSO 
>>
>>Number.  Does anyone know a 
>>
>>>simple way around this dielemma?
>>>
>>>TR seems to handle this a little better.  In the scenario 
>>
>>described above, 
>>
>>>the same Serial Number is initially assigned (just like 
>>
>>WL).  However, once 
>>
>>>someone enters the first Q, the serial number of the second 
>>
>>radio is 
>>
>>>incremented automatically.  It does take some coordination 
>>
>>between the two ops to make 
>>
>>>sure who has which number, but TR does make sure that 
>>
>>duplicate serial 
>>
>>>numbers do not go into the log.
>>>
>>>Any suggestions on how to accomplish this with WL?  
>>>
>>>73,
>>>
>>>Al, K0AD
>>>
>>>
>>
>>Before reverting back to TR for Multi-Op contests with Serial 
>>Numbers (i.e 
>>SS, WPX, etc), I just wondered if anyone could point me to a 
>>solution to this 
>>problem  when using Writelog.  I didn't get any response to 
>>my original post.
>>
>>73,
>>
>>Al, K0AD
>>_______________________________________________
>>WriteLog mailing list
>>WriteLog at contesting.com
>>http://lists.contesting.com/mailman/listinfo/writelog
>>WriteLog on the web:  http://www.writelog.com/
>>============================================================
>>
>>
>>_______________________________________________
>>WriteLog mailing list
>>WriteLog at contesting.com
>>http://lists.contesting.com/mailman/listinfo/writelog
>>WriteLog on the web:  http://www.writelog.com/
>>
> 
> ============================================================
> 
> 
> _______________________________________________
> WriteLog mailing list
> WriteLog at contesting.com
> http://lists.contesting.com/mailman/listinfo/writelog
> WriteLog on the web:  http://www.writelog.com/
> 
> 
>