If you use MMTTY as your main decoder and therefore your encoder for transmit, then simply select 'None' on the Rttyrite Port menu and then go to the MMTTY Options TX tab to set your FSK/PTT COM port
Yes, new capability with new a user interface and corner cases of incompatibilities are frustrating. Don is working on tutorials for all this on rttycontesting.com, so you may want to wait for that t
Do you have MMTTY's USB option set to "C: Limiting Speed" on the MMTTY Options Misc tab? That is necessary to pace the characters over USB with the microKEYER. All three of the Rttyrite hardware and
Absolutely! As far as I know you can ignore all this early adopter nonsense and use 11.10G just as you used previous versions. Just make sure you don't select the new TNC choice on the Rttyite TNC dr
Yes, you definitely want to have independent MMTTY folders for each MMTTY main and/or Clone windows you want to open. Same for 2tone. The way I do it is to install MMTTY in a MMTTY directory and then
Yes, this has been reported by several people here on the reflector. I also experience this once in a while when I'm stressing the software with my testing on various PCs. THE SOLUTION THAT HAS ALWAY
Thanks for the clarification, Jerry. That answers all my questions about your configuration and process. I see nothing wrong. I want to do some re-testing and see if I can reproduce what you and othe
Not you too! The problem installations are far outnumbering the working ones from what I see here on the reflector and in private communications. It's making me crazy! This morning I thought the prob
Thanks. That rules out one hypothesis. ;>) We'll get it figured out. My brain is overloaded with all the problem data that came in today! Ed W0YK _______________________________________________ Write
I suspect this tip has a similar effect as deleting [Rttyrite] ini sections in that it helps clean up any irregularities that somehow develop in the ini sections. It certainly can't hurt anything as
That's right. Known bug with MMTTY Plug-in and XMMT coexistence in WriteLog 11.10G. Work-around is to remove the MMTTY Plug-in. You can only set the COM port in either the Rttyrite Port menu or the M
Don is updating his tutorial on WriteLog and XMMT on www.rttycontesting.com with instruction on setting up Clone receive-only windows. Meanwhile, it is pretty straightforward once you have your first
The WriteLog rig driver for the Elecraft K3 does have more SO2V (and other) functionality compared to most of the other rig drivers. So, while the two receivers in the K3 can share the same COM port,
"Hardware generated FSK" and the MMTTY FSK are mutually exclusive. You choose one or the other as follows: 1. Hardware FSK uses Rttyrite's WinRitty FSK capability. When XMMT is selected on Rttyrite's
I second all of Joe's comments. Furthermore, the 2Tone AFC and NET "locked on feature" can be effectively disabled by simply zero-beating the station you are working. If CQing, then zero-beat with RI
Unfortunately this is the way it works now. I am disappointed because I have previously depended on the transmission printing to be closed sync'd with the actual transmission. I have used that inform
Good point, Don. This is another reason to use FSK. ;) (Reflector readers, please don't start another AFSK vs. FSK religious thread. I'm just being light-hearted here!) Ed W0YK ______________________
Clarification. I use the printed transmitted characters to know when to truncate an ongoing message or to gauge when a message is about complete so I can prepare to start a message on another radio.
[Configuration] ... CqFunctionKey=9 QrzFunctionKey=4 SendCallExchangeKey=5 ... (NOTE: Set each of these numbers to the Fn key number of your CQ, TU and Exchange message respectively.) [Entry] ... Sma
"Insert Sends the message corresponding to F10. (or you can change the "SendCallExchangeKey" entry in WRITELOG.INI to use a different function key.) Presumably you would have programmed this key to