[ct-user] CT sending a wrong QSO number

[Gerald Caouette]

Yes we had  several PC,s  set up and were operating MS using one tranceiver
to run while several receiving  stations entered information into the band
maps then we would transfer the transmiting operation to a different
tranceiver and the first station then became a receiving location during
one of these transfers the numerical sequence got out of step by 18 QSO,s 
we believe it was related to an opon window being left open for about 10
minuits.. the screen showed one serial 3 but the keyboard keyer sent the
serial # - 18  we only picked up on the error when one of our other
receiving stations noticed that the serail # displayed was not the one sent
by the keyer we resolved the issue by bringing all the stations off line
and and replacing the log with the log from the machine with the fewest
QSO.s we sacrificed the 18 QSo,s and about 1/2 hr operating time but 
were able to bet back in sync.with the keyer messages and exchanges... 
we are hoping to fix the damaged portion of the log and the 100 or so QSO
that were affected by the problem ...

I made us aware that what CT showed and what it sent were not always the
same in regards to the exchange. so we had to check our selves a lot more
often.

But in spite of this we all had a great weekend.
73 de ve6nap@oanet.com



----------
> From: Lehtimaki, Kari <Kari.Lehtimaki@wang.com>
> To: 'CT-USER@CONTESTING.COM' <CT-USER@contesting.com>
> Subject: [ct-user] CT sending a wrong QSO number
> Date: Monday, May 31, 1999 3:46 AM
> 
> 
> 
> We are happy that CT is able to update QSO numbers correctly in our
> networked PCs. Unfortunately last weekend something went wrong in sending
> them out... We were running M/S and had 3 PCs for logging. The QSO
numbers
> were corrected every time a QSO did not reach one of the PCs in the LAN.
But
> then after some 24 hours of operating one of the PCs started to send out
QSO
> numbers that were equal to the QSO number shown minus 1... Did not find
any
> fix to that from CT commands or setup. We rebooted the PC - no help. Then
we
> saved and renamed the file in this PC and put there a properly working
file
> from one of the other two PCs. That helped for a while until wrong
numbers
> were coming out after a few minutes later from our pileup PC. Decided to
> give up fixing the problem with saving and loading files and continued
> running QSOs only with the pileup PC. The number sent stayed 1 QSO behind
> till the end.
>  
> Today after merging the files there appeared a new as QSO #1. The first
two
> lines look like this:
> 
> 4898  80 0824 RU4HH         -96 +$@(
>     1  15 0000 VE3OI         599 1    VE3
> 
> Could this be related to the problem? Maybe the file was corrupted at
some
> point. In the three original files this line does not show. It appears
only
> in the merged file.
> 
> Any others with the number problem last weekend?
> 
> And we had also the logging problem K0HB reported. That was with our
other
> multiplier PC. CT turned the band of the logged QSO to 20m after pressing
> enter.
> 
> 73 de Kari, OH2XX @OH2U
> 
> vaihde (09) 476 100			exchange +358 9 476 100
> suora (09) 4761 0492			direct tel. +358 9 4761 0492
> fax (09) 4761 0302			fax +358 9 4761 0302
> gsm 040 504 5939			gsm +358 40 504 5939
> kari.lehtimaki@wang.com <mailto:kari.lehtimaki@wang.com> 
> www.wang.com <http://www.wang.com> 
> 
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.contesting.com/ct/
> Questions:                owner-ct-user@contesting.com
> 

--
Submissions:              ct-user@contesting.com
Administrative requests:  ct-user-REQUEST@contesting.com
WWW:                      http://www.contesting.com/ct/
Questions:                owner-ct-user@contesting.com