[WriteLog] MMTTY/2Tone

[Don AA5AU]

Thanks for the nice write-up Bob. I testing last night and most of the day today and confirm everything you say except the slow or stuttering FSK problem.

Before getting to the first two major issues at hand, I did want to mention that AFC being on all the time with 2Tone is not as big of a factor as you think because with the two vertical Mark and Space lines you can tune any RTTY signal in properly as if AFC was not off (we can debate this later). On with the issues.

In my testing, I have found two major issues with version 11.10G.

1. If the MMTTY plug-in is installed and invoked in the main RTTY window, any attempt to access the TU Type menu will lock up Rttyrite. As Bob has mentioned, Rttyrite can be closed via the Task Manager without having to shut WriteLog down all the way.
2. Running MMTTY via XMMT.ocx causes AFC to automatically come on when a callsign is cleared from the Entry Window whether is by using ALT-W, logging a contact, backspacing until it's clear, etc.

Some background info:

Several of us beta tested several versions of this new XMMT.ocx support with the first one being 11.10B. Last night I reverted back 11.10B and the AFC problem did not exist in that version. I then upgraded to C, D and E only looking at the AFC problem. When I got to E, the problem started. I believe this can be fixed. Wayne has been informed.

Unfortunately I did not have time to go back through the versions a second time looking only at the Rttyrite lock-up problem and I don't have all those versions on this machine at this location and home PC is shut down due to weather. I do know that it probably did not exist in the original 11.10B. I base this on the fact that my writelog.ini file was set to bring up the MMTTY plug-in in the main Rttyrite window originally before XMMT.ocx with WriteLog existed. So the fact that I was able to change from MMTTY to XMMT.ocx the first time I tried 11.10B tells me the problem probably did not exist in that first version. Tonight (if I have time), I will again go back in versions to help Wayne determine where this first started. Again, I believe it can and will be fixed.

The slow or stuttering FSK situation is something I cannot address because it's not happened to me. I use Hardware Generated FSK with 2Tone in the main Rttyrite window with no problem (using a legacy COM port) on main PC/radio. On a second PC/radio, I use Software generated FSK with a USB-to-serial adapter with 2Tone in the main Rttyrite window and this works fine as well. I used version 11.10F set up for SO2R in the March NA RTTY Sprint and had no problems whatsoever - hardware and software generated FSK. Last night I tested Software-generated FSK with 11.10G on the second radio and it worked.

I think that's where we stand right now. Sit tight. It will all work out.

73, Don AA5AU



>________________________________
> From: WB2COY <wb2coy at hvc.rr.com>
>To: writelog at contesting.com 
>Sent: Wednesday, April 3, 2013 2:45 PM
>Subject: Re: [WriteLog] MMTTY/2Tone
> 
>This is an update to my previous posting where I believed I had everything working to my satisfaction using XMMT.ocx for all Rttyrite wiindows. My main Rttyrite window is set up with MMTTY using FSK on a COM port, and Clones are set up using 2Tone and MMTTY with a different profile. I have separate folders for all instances of MMTTY and 2Tone. Everything seemed fine until I realized that AFC would turn on in MMTTY after clearing a callsign in the log Entry field, either by right clicking in the Rttyrite window and selecting Clear Entry Window, hitting Alt-W, or just logging a call. This requires clicking on AFC and HAM to get back to no AFC action. This was unacceptable to me as a casual S&P operator, because I never want AFC on in the decoder that I am using for my Transmit function. Don, AA5AU confirmed this AFC behavior after we conversed offline on my experiences. This does not happen with the Plugin.
>
>Some background: My computer/radio setup is Windows 7-64bit, Dual Core 2.2 Ghz processor, 3 GB RAM, U.S. Interface Navigator, ICOM 756ProIII. The Navigator presents me with serial ports for PTT, FSK, CAT and other functions not related to this issue. The Navigator provides a USB Audio Codec for receive audio, and I am using FSK to send RTTY.
>
>I found that I can set up my Main (primary) Rttyrite Window using the old Plugin to avoid the AFC issue, but once it is up and running, any clicking on TU Type in the Rttyrite Window will lock up that window and any other mouse clicks in any windows are frozen. Task Manager can be used to shut down the locked Rttyrite Window and the MMTTY Window, then clicking “Window” and “RTTY Window” from the Entry Window will bring it back up without having to completely shut down Writelog. Again, as long as I don’t touch the TU Type menu item in Rttyrite, all is well. Any changes to MMTTY settings can be made via MMTTY’s  Options-Setup feature. The COM port for FSK is set in the Rttyrite window under Ports, and COM-TxD(FSK) is selected in MMTTY. 
>
>To summarize, for now my working configuration uses the Plugin for the primary MMTTY window for Tx/Rx and both clones use XMMT.ocx. I do not want to use 2Tone as my primary Tx/Rx as it has AFC on all the time, plus my testing showed the stuttering transmit anomaly that Gary, AL9A described in an earlier post.
>
>The bottom line is that if the AFC bug can be corrected using MMTTY and XMMT.ocx, then I will use XMMT.ocx for all functions and drop the Plugin and be a Happy Camper!
>
>Hope this is helpful to others who are trying to sort this out.
>
>73, Bob WB2COY
>
>_______________________________________________
>WriteLog mailing list
>WriteLog at contesting.com
>http://lists.contesting.com/mailman/listinfo/writelog
>WriteLog on the web:  http://www.writelog.com/
>
>
>