CT-User
[Top] [All Lists]

[ct-user] CT9.63 beta needs user testing

To: <ct-user@contesting.com>
Subject: [ct-user] CT9.63 beta needs user testing
From: Jim Mullen" <jmullen@rockys.com (Jim Mullen)
Date: Sat, 9 Jun 2001 11:37:51 -0400
I second Dave's suggestion about preventing or limiting band changes during
FD operations. This has been a constant problem with every FD I have
participated in over the years. Sure would save a lot of post contest
changes when it's all over.

Jim, KK1W

-----Original Message-----
From: owner-ct-user@contesting.com
[mailto:owner-ct-user@contesting.com]On Behalf Of David Robbins
Sent: Saturday, June 09, 2001 10:12 AM
To: Ken Wolff
Cc: CT-User
Subject: Re: [ct-user] CT9.63 beta needs user testing



what might be nice is a way to define the bands for each station.  like here
i
don't want anyone accidently changing bands so i would set them only for one
band each.  at some fd sites it would also be nice to be able to do that so
only
specific bands could be used on each station.  m/s setups that put a couple
bands on each station would also benefit from this.  i would like the
alt-f1/f2
to only sequence through the specified bands for that station, so if one
station
is only for 10m and 40m it would alternate between them on alt-f1/f2 and
skip
over 15 and 20.  this wouldn't stop the operator from pushing the button on
the
radio for those bands, and i'm not sure what is best in that case, a warning
message, ignore it, or just let him operate as a way to override ct's band
list
if needed.

on a similar vein, for multi mode contests maybe ctrl-f1/f2 should be
limited to
specified modes for each station?  but that is probably not as useful.

Ken Wolff wrote:
>
> I have placed CT9.63.001 beta in the vault. I really needs testing on a
> variety of radios and setups, which I don't have. If you have an extra
half
> hour , please download and check it out for me. Let me know if funny
things
> happen with packet, or split operation, as well as all the bands.
>
> Thanks - Ken
>
> 9.63
>
> * FD requires RST and QTH from DX stations. CT now loads CTY.DAT and will
>   accept any exchange from DX. (tnx K2BA)
>
> * removed the microwave bands from the frequency display (ALT-J) because
> they
>   too large to fit in a 32 bit integer
>
> * added the concept of "supported bands" to radio code. CT will now
control
>   supported bands for particular radio. After a QSY to an  "unsupported
> band",
>   CT ignores the radio and act's like there is no radio. QSY to a
supported
>   band, and the radio comes alive again.
>
>   For the moment, all radios are set to the standard bands (160 through
10,
> no
>   WARC). I will be adding band sets for particular radios (VHF and WARC)
> soon.
>
> --
> WWW:                      http://www.k1ea.com/
> Submissions:              ct-user@contesting.com
> Administrative requests:  ct-user-REQUEST@contesting.com
> Problems:                 owner-ct-user@contesting.com

--
David Robbins K1TTT
e-mail: mailto://k1ttt@berkshire.net
web: http://www.k1ttt.net
AR-Cluster node: 145.69MHz or telnet://k1ttt.net

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



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


<Prev in Thread] Current Thread [Next in Thread>