To me, it sounds like some rigs (like the TS-940s) do not send correct
updated data to CT fast enough (especially after switching from transmit to
receive). It is a problem with the rig NOT CT.
If you are experiencing problems, you may want to check with the
manufacturer of the rig to see if there is an updated EPROM available for
the rig. New rig firmware may solve the problem. The TS-940 was sold for
many years. I would be very surprised if Kenwood did not update the
firmware at least once.
If updated firmware is not available (or if updated firmware does not solve
the problem), it sounds like you must wait a bit after switching to receive
before sending a SPOT. (Or just buy another rig - hi)
73's
Rob
>From: "Gilmer, Mike" <mgilmer@gnlp.com>
>Reply-To: "Gilmer, Mike" <mgilmer@gnlp.com>
>To: "'CT-USER'" <ct-user@contesting.com>
>Subject: RE: [ct-user] QSX Reversed
To: <ct-user@contesting.com>
>Date: Mon, 27 Mar 2000 10:05:18 -0500
>
>
> > Is this a case where CT isn't "smart enough" to figure out a backwards
> > spot ?
> >
> > For example:
> >
> > normal: DX de N5NJ: 7088.4 RW2F QSX 7188.4
> > backwards: DX de N5NJ: 7188.4 RW2F QSX 7088.4
> >
>
>Well, "backwards" is relative. If, say, a European station spotted:
>
>DX 7188.4 N5NJ QSX 7088
>
>it might be correct! CT would then have to apply "out-of-band" rules to
the
>spotted callsign - which, of course, are different in different countries.
>Even then, if both of the frequencies were in-band (say DX 28045 ZA1AAA
>28065), but were spotted "backwards", CT would be helpless.
>
>The data really needs to be correct as originated.
>
>73
>Mike
>
>--
>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
|