[ct-user] SS + 9.46.002

Robert S Morris Robert S Morris" <rsmorris@worldnet.att.net
Mon, 8 Nov 1999 15:20:45 -0500


Had the same problem here with a short trial at 2 radio 2 band 2 computer
operation in the 15M position.. Only way I saw to get the number unlocked
was to
turn that computer off and back on again..
Had 10 computers on during SS hooked thru a LAN. Not all of the numbers
got corrected before sending..
73/Bob
W4MYA

----- Original Message -----
From: Dallas Carter <ludal@dmv.com>
To: <N2NU@aol.com>
Cc: 'CT-USER' <ct-user@contesting.com>
Sent: Monday, November 08, 1999 9:46 AM
Subject: RE: [ct-user] SS + 9.46.002


>
> Yes, It was a terrible problem.  Another one was that once a call was
entered, the number
> was locked in, and if erased, the number was set.  If that radio did't
make a QSO for some
> period, the number sent was significantly out of whack.  The ones we
noticed were
> corrected and sent manually.  The log will have to be edited to get them
back in sequence
> though.  After a bit we noticed that the problem was going to occur when
the serial number
> became offset by one character space before transmission.  My appologies
to those who
> inadvertantly got the wrong number.  I will send a note to the UBN folks
in hopes that
> those stations won't be penalized for our S/W errors.  73  Dallas W3PP
> M/S, ct946.004, five computers at 9600, no collisions.
>
> ----------
> From: N2NU@aol.com[SMTP:N2NU@aol.com]
> Sent: Monday, November 08, 1999 9:07 AM
> To: ct-user@contesting.com
> Subject: [ct-user] SS + 9.46.002
>
>
> Used CT this weekend 2 computers/2 radios - anyone else out there have
> problems with sequence numbers in multi computer setup?
>
> My symptom was that CT occasionally wanted to send the same number
> (the same number appeared in the next contact field) after it had
> already been used once.  Had to be observant and fix the problem
> manually to keep from using serial numbers twice.  This happened maybe
> 15 times in 24 hours.
>
> Computers hooked together comport to comport at 9600.  Didn't observe
> any communication error messages (ala received bad checksum).
>
> -john
>
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.k1ea.com/
> Questions:                owner-ct-user@contesting.com
>
>
>
>
>
> --
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> WWW:                      http://www.k1ea.com/
> Questions:                owner-ct-user@contesting.com
>


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