Bob,
I too experienced the stuttering halting FSK you have described. What
solved the issue for me was to select None under Port in RttyRite and set
the FSK port in MMTTY itself. From earlier posts by Ed W0YK, Don AA5AU and
Joe W4TV it seems the only way around this buffer error is to prohibit
RittyRite from controlling the FSK function and leave that task up to MMTTY.
I now let MMTTY control the FSK keying on my main RttyRite window and let
the RittyRite clone windows, one with MMTTY with a different profile and the
other with 2Tone, just decode and never transmit anything. This has worked
out so well for me after numerous tests that I have now uninstalled the
MMTTY plug in and am going exclusively with the XMMT.ocx interface. We'll
see for sure how this works in the EA RTTY contest this weekend. Should be
a good proving ground.
BTW, after uninstalling the plug in, the first time I started RttyRite I got
an error message about an item in my list of TU types that had only been
partially uninstalled and it asked if I wanted to complete the uninstall. I
answered Yes and WL went immediately opened RttyRite. Clicking on TU type
showed MMTTY, the plug in, had been removed from the list of options.
73,
Gary AL9A
----- Original Message -----
From: "WB2COY" <wb2coy@hvc.rr.com>
To: <writelog@contesting.com>
Sent: April 03, 2013 5:31 PM
Subject: Re: [WriteLog] MMTTY/2Tone
Some more information......
Further experimentation has confirmed to me that XMMT.ocx or 2Tone has
nothing to do with the stuttering or halting FSK output that I am seeing.
I started with a clean writelog.ini (No Rttyrite entries) and chose Sound
Card FSK as the TU type. I selected my FSK COM port in Ports, and Hardware
FSK. When transmitting a Macro, several characters go out, there is a
second or so delay, and then the rest of the macro goes out. It can be
easily heard in the radio monitor function while transmitting into a dummy
load. So this tells me that Joe, W4TV is absolutely right in his
assessment that this is a timing issue unrelated to 2Tone or XMMT.ocx, as
this anomaly (to me anyway) also appears using the native Writelog RTTY
capabilities, with neither XMMT, MMTTY or 2Tone as part of the
configuration.
My working configuration using MMTTY and COM port FSK does not have
Hardware FSK checked in Rttyrite Ports. It seems that I have to start with
a clean writelog.ini and configure Rttyrite and MMTTY in some proper
order, otherwise Hardware FSK is checked and greyed out, and MMTTY has
COM-TxD(FSK) greyed out as well. If I do things in the correct order, I
can get only my COM port checked in Rttyrite Ports, and go to MMTTY
Options-Setup and COM-TxD(FSK) can be selected and all is good. This is
where I have to be sure to NOT Click on Rttyrite TU type, otherwise
Rttyrite locks up.
We’ll see how this performs under real world conditions during the EA-RTTY
contest this weekend.
Bob WB2COY
_______________________________________________
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/
|