WriteLog
[Top] [All Lists]

[WriteLog] AFC question

To: <writelog@contesting.com>
Subject: [WriteLog] AFC question
From: k1am@home.com (Jeff Bouvier)
Date: Mon, 15 Jan 2001 21:20:09 -0500
Bob,
        The program is setup to do that. I dont like that "feature"
either. During the Roundup I just turned off the AFC and kept it that
way for the whole contest. I used the RIT to tune stations in. 
        I think the AFC should remain on if we have it checked. I know
some people will forget it when they s&p but that's better than having
a station off qrg when you turn it back to them and having to ask for
repeats. 

        73, Jeff K1AM




On Tue, 16 Jan 2001 01:48:00 +0000, you wrote:

>
>Hello all,
>
>During the past RTTY Roundup I noticed a rather annoying thing happening
>to the AFC function.
>
>Let me start by saying when I call CQ I turn AFC on by checking the box
>in the tuning window.
>Here's the scenario that follows.
>
>I call CQ and someone answers.  I respond with the "Insert" key.  After
>my response is sent and the radio unkeys, the AFC is no longer checked.
>Now if the calling station is off frequency when they respond with their
>exchange (and I would assume if they were off freq with their initial
>response they'll be off freq with the exchange), I have to use my RIT to
>tune them in.  I then QSL their info, send QRZ and magically the AFC box
>is checked again and is active.  Am I doing something wrong to make the
>AFC become unchecked during the exchange?
>
>The only thing I could find in the documentation is relative to one of
>the release notes.  I believe it is Version 10.09 where the AFC was made
>to turn off if there is an entry in the exchange field.  Why?
>
>I'd appreciate any assistance in getting me "tuned back in".  This is a
>great product and I simply need to understand it better I'm sure.
>
>Thanks folks.
>
>Bob, N3FR  (ex N3IXR)


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


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