Rob,
While I don't know how this relates to your specific problem, I have
learned that MMTTY uses two .ini files that establish the behavior of
your instance of the program. These are plain text files, and it's well
worth the effort to study them in a simple editor. One is mmtty.ini and
the other is userpara.ini. The settings that I ran into are those that
set the Mark and Shift frequencies, and they are present for all of the
dozen or so decoding parameter settings. I like to work with low tones
(915 Hz, 1085 Hz), while MMTTY defaults to high tones (2125, 2295 Hz),
and these defaults are stored in the .ini files. mmtty.ini is your
current (last) settings for the program, while userpara.ini contains all
of the programmable decoder settings, like Standard RTTY, Fluttered, and
so on. Each of those sets of settings includes the Mark and Shift
frequencies.
The way this can bite you is that you may set MMTTY for 915 Hz, then
toggle from one decoding algorithm to another with the TYPE button and
MMTTY switches to 2125 Hz as set in those sets of decoder settings.
These decoder settings also include AFC on/off (default is ON) and NET
on/off (default is ON).
Once I discovered this, I went into those .ini files and edited them so
they always come up the way I like to operate.
73, Jim K9YC
On Sun,2/14/2016 11:36 AM, Rob K6RB wrote:
Last night I made sure that all MMTTY instances on this computer were deleted
and a new 1.68 full version installed. I then used the .icx to join it to
WriteLog. I went through and set up MMTTY in AFSK, using 915 mark frequency,
170 Hz, etc. I made sure ATC, AFC were unchecked. All looked good until the
first time I logged a new QSO. The AFC button depressed (like magic) and the
Mark frequency began floating. I never had this with version 11.
I looked at keyboard shortcuts menu to see if there was anything related to the “enter” key.
As an after thought, I hit “set default.” No joy.
I looked at the MMTTY setup window on MMTTY and saw nothing related to the interaction between
“enter” and AFC. I’m at a loss. The .ini file was inherited from version 11 and
I had no such problem before. Something is weird. Any ideas?
Rig is K3/Alpha 87A; computer uses Windows 7; everything works great on CW modes. If there is no data in the entry window
and I hit “enter,” it does not invoke AFC. But, if there is data, and I log it by hitting
“enter” it will “push” the AFC button every time. It is as if the log function and AFC
invocation function are conjoined.
Rob K6RB
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
_______________________________________________
WriteLog mailing list
WriteLog@contesting.com
http://lists.contesting.com/mailman/listinfo/writelog
WriteLog on the web: http://www.writelog.com/
|