Actually, I believe both Hardware and Software generated FSK have always had
this delay. I have been using both for a long time and
never really noticed it (reason why in next paragraph).
Unlike Ed, I do not rely on what's on the screen when transmitting for timing.
Instead, I use what I hear in my ears for timing
between the two radios and only look at the Rttyrite screen during a
transmission just to make sure the correct message is being
sent. The reason I never noticed the delay is because I turn MONITOR off on my
radios during contests. I do not want to hear to my
tones going out because I use my ears to tell me what's going on. If I hear
silence in my left ear, it means I'm transmitting on the
left radio. I then concentrate solely on the other radio that is receiving (the
ear I hear noise or RTTY on). I know Ed does this
differently as well. It wasn't until I did a couple of single band RTTY efforts
this year that I turned MONITOR on and noticed the
delay. With 2Tone in the main Rttyrite window, you are limited to only Hardware
or Software generated FSK (or AFSK).
HOWEVER, if you use MMTTY via XMMT.ocx and set up MMTTY to transmit FSK via the
TX and Misc tab screens in MMTTY setup, the delay is
only about one character. I just tested this a few minutes ago.
AND, if you use MMTTY via XMMT.ocx and set up MMTTY to use EXTFSK to transmit
FSK, it appears that what goes to the Rttyrite screen
is in perfect timing with what is being sent. Just tested this too.
I haven't tested AFSK yet. But I will do so as I continue to work on new web
pages documenting things like transmitting FSK and AFSK
options when using the various sound card modems.
73, Don AA5AU
-----Original Message-----
From: WriteLog [mailto:writelog-bounces@contesting.com] On Behalf Of Ed Muns
Sent: Sunday, April 21, 2013 12:19 AM
To: 'Writelog'
Subject: Re: [WriteLog] 11.11C & XMMT
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 information to
time my transmissions on other radios. MMTTY with the
MMTTY Plug-in had exellent correlation between printed transmitted characters
(blue Italic text in the Rttyrite window) and the
actually transmitted characters.
However, I've come to learn that some other ops pay no attention to the
transmission printing and instead rely on the monitor audio
to tell them when the transmission is finished. Nonetheless, I have made the
request for this to be fixed in WriteLog but I don't
know how feasible that is.
Ed W0YK
Anthony N2KI wrote:
> I did my upgrade to v 11.11C and followed the procedure outlined on
> Don's page. Initially I had trouble when starting WL and traced it to
> a bad comm port number in the ini file. Once this was fixed and I
> tested WL using XMMT and found there to be a timing problem with what
> is being sent in relation to how it appears on the transmit window in
> Rittyrite. The transmit window prints what is being transmitted but
> the actual transmission is still ongoing well after the TX window
> displays what is being transmitted.
> Anyone else seeing this? Is there a fix? Thanks
_______________________________________________
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/
|