Sounds like a grab interval problem. What processor/speed/SMARTDRV was
being used in each case? A faster machine, or one running with a
different cache size/option in SMARTDRV, might slip by the problem.
On Mon, 8 Nov 1999 10:07:00 -0800 , you wrote:
>
>We had it happen once too. We did not read the new rules soon enough to see
>the unlimited band change rule for Multi-Single, so we used a beat on wall
>signal and only did it for 1 hour on 40M run and 80M S&P (I am too young to
>have an octupus laying around). Well, I had remembered people suggesting
>that serial numbers be 'reserved' because this can happen and I was watching
>out for it on the very few Q's we made in the second radio. Here is how it
>went:
>
>station a=cq radio, b=s&p radio (need to look at log to get all the specific
>details)
>
>A: CQ on 40M
>B: Finding a new one on 80M
>A: gets called by N6BF (something like that)
>A: give N6BF exchange with #518 (I seem to remember)
>B: beats on wall and calls K7RAT (that I remember)
>A: type in exchange from N6BF and pause while....
>B: gives K7RAT #518 in exchange by hitting enter
>A: hits enter to QSL and number is now #519 but gave #518
>
>We stopped trying this. Only looking for mults on second station. With one
>op this would be tough to do, doing 2 exchanges at a time.
>
>Dan KI6X (@K6NX)
>> ----------
>> From: George Fremin III[SMTP:geoiii@kkn.net]
>> Reply To: geoiii@kkn.net
>> Sent: Monday, November 08, 1999 9:13 AM
>> To: dawley@execpc.com
>> Cc: trlog@contesting.com
>> Subject: Re: [TRLog] Serial #, Pathological behavior in a network
>>
>>
>> Scott Dawley writes:
>> >
>> >
>> > I was playing around last night after the contest
>> > to simulate two radios in the SS, each radio
>> > pausing when/if the other is finishing a QSO.
>> >
>> > What I found is that EVEN IF you keep only one
>> > transmitter on the air at a time, you can get
>> > both radios to send the SAME SERIAL # to two
>> > different stations. This occurs if one station
>> > is in the middle of a QSO (say, copying the
>> > exchange) and the other station is sending
>> > an exchange.
>> >
>>
>> Maybe you should explain the steps you used to
>> cause this to happen. I do not know anyway to do this.
>>
>> I watched N5KO make 322 2nd radio QSOs this past weekend
>> and I dont think he was able to make the program do what
>> you describe.
>>
>> > The obvious one is to not jump back and forth between
>> > radios mid-QSO, but that makes for less efficient
>> > use of time.
>> >
>> > Thoughts?
>> >
>>
>> How are you making two radio QSOs.
>>
>>
>>
>>
>> --
>>
>> George Fremin III "I'm talkin' 'bout that outlaw X
>> Johnson City, TX It's cuttin' through the air.... "
>> K5TR (ex.WB5VZL)
>> 830/868-2510 -- "Heard it on the X"
>> geoiii@kkn.net -- ZZ Top
>> http://www.kkn.net/~k5tr
>>
>> --
>> FAQ on WWW: http://www.contesting.com/trlogfaq.html
>> Submissions: trlog@contesting.com
>> Administrative requests: trlog-REQUEST@contesting.com
>> Problems: owner-trlog@contesting.com
>> Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
>>
--. .-..
73, Guy
Guy Olinger, K2AV
k2av@contesting.com
Apex, NC, USA
--
FAQ on WWW: http://www.contesting.com/trlogfaq.html
Submissions: trlog@contesting.com
Administrative requests: trlog-REQUEST@contesting.com
Problems: owner-trlog@contesting.com
Feature Wishlist: http://web.jzap.com/n6tr/trwish.html
|