[RTTY] MMTTY AFC Bug

[Joe Subich, W4TV]

Don,

> With the MMTTY plug-in for WriteLog, there is an option to turn AFC
 > OFF while there is a callsign in the Entry Window. I checked to make
 > sure this option was not checked and it was not. I even enabled it
 > thinking it might help when using the 512 profile, but it didn't
 > work. AFC stayed on even if there was a call in the Entry Window.

Are you using the "Profile Panel?"  It also has the option to turn
AFC ON/OFF based on CQ mode or S&P mode ... it is possible there is
some "false triggering" of AFC in that code as well.

73,

    ... Joe, W4TV


On 1/9/2011 11:16 PM, Don AA5AU wrote:
> I'm wondering what profile people were using when the AFC was turning off.  I
> didn't notice this until Sunday when I switched from FIR to the AA6YQ 512
> profile and found that it works wonderfully for copying weak signals while
> running 15 meters to EU.  I decided to run it on both radios for most of the day
> and on several occasions heard a signal, but got got no print because AFC was
> off (I think).  At the times it happened, I chalked it up to the new profile.  I
> was "thinking" that it was the nature of the 512 profile that if you aren't
> tuned right on the signal or if the signal is too far off that AFC couldn't tune
> it fast enough that it won't print.  I was working so hard at making contacts
> that I didn't actually put 2 and 2 together that AFC was turning itself off.
>
> On Saturday, using FIR profile, I did not have this problem.  I did eventually
> go back to the FIR profile later Sunday and didn't have the problem.
>
> With the MMTTY plug-in for WriteLog, there is an option to turn AFC OFF while
> there is a callsign in the Entry Window.  I checked to make sure this option was
> not checked and it was not.  I even enabled it thinking it might help when using
> the 512 profile, but it didn't work.  AFC stayed on even if there was a call in
> the Entry Window.
>
> There's plenty of RTTY contests in the two months where we try to determine
> what's going on.
>
> The AA6YQ 512 profile is really awesome!
>
> Thanks Dave!
>
> 73, Don AA5AU
>
>
>
> ----- Original Message ----
> From: Dave AA6YQ<aa6yq at ambersoft.com>
> To: Rick Ellison<rellison at twcny.rr.com>; rtty at contesting.com
> Sent: Sun, January 9, 2011 4:56:09 PM
> Subject: Re: [RTTY] MMTTY AFC Bug
>
>>>> AA6YQ comments below
>
> -----Original Message-----
> From: rtty-bounces at contesting.com [mailto:rtty-bounces at contesting.com]On
> Behalf Of Rick Ellison
> Sent: Sunday, January 09, 2011 5:44 PM
> To: rtty at contesting.com
> Subject: Re: [RTTY] MMTTY AFC Bug
>
>
> This is one of the things I was going to point out Bob..
> There are a few different settings in N1MM that will cause the AFC to turn
> off or on depending on what setting you have off or on.. One of them being
> send Ham Default on S&P/Run Change. If the AFC is turned on in the Default
> profile and this setting is turned on then the AFC could be turned off or on
> depending..
>
>>>> That's why I've asked if anyone running MMTTY standalone had experienced
> this behavior. So far, the only two reports have come from ops using
> WriteLog and N1MM; those applications could be directing MMTTY to disable
> AFC.
>
>      73,
>
>          Dave, AA6YQ
>
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>
> _______________________________________________
> RTTY mailing list
> RTTY at contesting.com
> http://lists.contesting.com/mailman/listinfo/rtty
>