Thanks to Bill, K3SV, for jogging my memory with a question he
asked to me.
You can setup the profile buttons at the bottom of the MMTTY control
panel to do different things with AFC and NET depending on how you
desire them to react.
If you go to the Rttyrite window, under the 'TU type' menu, and choose
TNC Setup, another window will open where you can select various
parameters. This window is called "Rttyrite MMTTY Settings".
When I remembered about this, I also remembered how I set it so AFC
would never come on. I redefined the Standard profile. How I did this
was to take the default Standard profile (Profile #1) and un-check AFC
in the AFC/ATC/PLL tab in Setup and also un-check AFC Connection
on the Demodulator tab page. I then went to the Profiles(S) menu on the
MMTTY control panel to 'Assign Menu' and chose 'Standard RTTY'.
A dialog box will open asking for a Profile Name. I left it as Standard RTTY.
This redefined the Standard RTTY profile so that AFC was always off.
However, in the 'Rttyrite MMTTY Settings' window (the one you get from
TNC Setup in the Rttyrite window), I un-checked all boxes under "Profile
Panel Settings" and checked "AFC is automatically turned OFF while there
are call letters in the CALL field".
This way, AFC NEVER comes on.
If you want AFC to come on when using the different profiles, you would
setup this way in "Profile Panel Settings".
MMTTY comes with 4 Profiles for RTTY. #1 is Standard RTTY, #2 is for
Fluttered signals, #3 is for Fluttered signals (FIR) and #4 is for Multi-path.
These 4 profiles are pre-defined by the author. I would not recommend messing
around with the actual settings for these unless you feel comfortable
re-defining
the characteristics of the profile itself.
Just some more thoughts I had about the MMTTY plug-in.
73, Don AA5AU
http://www.aa5au.com
http://www.geocities.com/writelog
|