To turn out a major contest package with functionality like CT, N6TR and
the like would be a Major Undertaking.
Besides, serious contest logging packages are not really suitable for 'normal'
log book keeping. They won't let you log: name, QTH, power, antenna etc
etc. They have a lot of stuff you may not need: network/multi op functionality,
running totals, band maps, pop-up windows...
However, it would be nice if the logging software offered basic CW features.
The reason is, that a lot of CW ops use a computer to both send CW and
also log with it. The CW 'keyer' needs to know the call of the guy being
worked, in order to fire it back at him, and also the RST report you have
decided to give him (as typed into the RST-sent field).
It makes good sense to combine 'logging' and 'CW keyer' functions.
Therefore, logging software without basic CW functionality would be pretty
much useless to people who do: (casual) CW contesting, CW field day
operating, CW pile-up busting & DX chasing, putting a special callsign
station on the air DXpedition-style, low band (LF) or 6 m ops wanting to
'beacon' CW messages
Things that spring to mind are:
1. A CW keyer on the parallel port with programmable speed.
2. Programmable messages under the function keys (CQ, exchange, tu,
QRZ?, agn?, cl? etc)
3. The ability to bring logbook fields into 2. E.g. The exchange message will
grab the callsign field contents and sends "AA1BC 5nn".
4. An incrementing number field for contests: "AA1BC 5nn 001"
5. The ability to put the CQ message into a loop (repetitive CQ with breaks to
take calls)
Other (non CW related) Desirable Functions:
Rig (CAT) control for the major radio interfaces (you'll need a lot of beta-
testers :-(
DX Cluster support (putting up spots worked from the log, plonking spots into
the log)
There are zillions of other features: beam headings, awards info,
country/prefix check etc etc.
Wilbert, ZL2BSJ
