Oops. Big oops.
Jim is absolutely correct. The problem comes in when people type "QSX UP" or
"QSX UP 5" instead of "QSX 7223" in the comment field.
I should know better...too early...
Anyway, if the QSX info is utilized, the data should be parsed well enough to
recognize whether the <TX FREQ> part is a valid frequency. If invalid, CT
seems to scan all the way to the timestamp (which follows the QSX info) and
jams that into VFO-B. Makes for interesting VFO-B settings.
Mike N2MG
On Mon, 29 October 2001, Jim Reisert wrote:
>
> There is no official format. But CT, being one of the first out there, set
> the defacto format to be:
>
> DX <callsign> <RX freq> QSX <TX freq>
>
> The word QSX is required, and <TX freq> must be in KHz. Note that "/" may
> work in place of "QSX".
>
> I wish Ken was a little more flexible, i.e. accept MHz instead of KHz
> (7.230) as well as recognize the QSX frequency without the word QSX if it
> "makes sense", i.e. the spot frequency is 40 meters and the comment is
> simply "7174" or "7.235". Ignore things like non-numeric strings and
> number out of bounds, i.e. "34".
>
> Trying to recognize all combinations of UP, DOWN, LSN etc. is too
> complicated.
>
> CT will make a properly-formatted spot for Kenwood and Yaesu radios, where
> it can read the "splitness" out of the radio. ICOM doesn't let you, so the
> user has to type in the word QSX and the transmit frequency. This is where
> some of the badly-formatted spots come from. There others? Probably some
> number of clueless users, or users who just don't care.
>
> 73 - Jim
> --
> Jim Reisert AD1C, 7 Charlemont Court, North Chelmsford, MA 01863
> USA +978-251-9933, <jjreisert@alum.mit.edu>, http://www.ad1c.com
________________________________________________
PeoplePC: It's for people. And it's just smart.
http://www.peoplepc.com
|