Close only counts in horse shoes and hand .... How about " 599 QWR 123" Bet most would still click on the 123. As I was testing MMTTY, ST-8000, and 2Tone on receive on a number of stations during the
I SHOULD know this. But. I. Don't. The space character is in both "character sets", i.e. LTRS and FIGS. It shouldn't be necessary to send a FIGS character after a space (or LTRS before) when sending
Speaking totally non-technically, I prefer spaces. I have some tremor in my mouse hand. When a sequence is hyphen-delimited I sometimes mouse up the hyphen along with the desired characters. In the h
Susan, I believe you can change the font size in the RTTY window. It has been a while since I used WL, and I don't remember exactly how to do it. But I do remember changing the font size to a larger
On 02/11/2013 09:26 AM, Susan King wrote: Speaking totally non-technically, I prefer spaces. I have some tremor in my mouse hand. When a sequence is hyphen-delimited I sometimes mouse up the hyphen a
REPLY: If reception was perfect, i.e. no garbled characters, then USOS would not be necessary. In fact, with wired TTY it isn't used at all. Only with radio TTY is it needed. The idea behind it is th
The font in most WriteLog windows can be changed (type, size, etc). The Log Window and Entry Window font settings are available on the Settings drop-down menu. The other windows have the font setting
I think the key concept I was missing is that it requires enabling by the sender. The way I was interpreting this thread was that UOS provided value even if the originator did not send extra shift ch
Susan, In the RTTY window, click FILE / FONT. However, you will probably have to do that every time you start WriteLog. 73, Jim N6VH On 2/11/2013 7:26 AM, Susan King wrote: Speaking totally non-techn
I think that this is incorrect. As I remember, USOS is enabled on the receiver's end and adds the extra LTRS on space. I don't believe that the transmitting station sends a LTRS character along with
ok, so for the guys hunting for milliseconds a solution could be to have 2 sets of exchanges available.. one additional for the strong stations returning - with USOS temporarily switched off.. on the
That is correct. From the transmitter's viewpoint, each SPACE is simply an "implicit LTRS." The transmitter's only responsibility when using USOS, is to change its own state to LTRS right after sendi
I think you are overcounting, Andy. It should be just 3xFIGS. No additional LTRS are sent by the transmitter. But yes, it still does adds up to a lot for the people looking to save milliseconds, but
Which means that those who want to save the 330 ms to 500 ms per report (2 x FIGS or 3 x FIGS) can use dashes if they wish even if they enable USOS. There is more time saving from eliminating the th
Hi to all , just for info - http://dwestbrook.net/projects/ham/rtty-length/ nice message length calculator . USOS on/off and so on and with one familiar call signal ;-) allready filled in..... Tnx &
I think that this is incorrect. As I remember, USOS is enabled on the receiver's end and adds the extra LTRS on space. I don't believe that the transmitting station sends a LTRS character along with
REPLY: I think you're right. If I recall correctly, when a space is detected by either the transmitter or receiver, they each reset themselves back to FIGS case, but no actual FIGS character is sent.
REPLY: The biggest time saver of all would be to eliminate the signal report. How about it, contest sponsors? Bill, W6WRT _______________________________________________ RTTY mailing list RTTY@contes
No, just the opposite! :-) :-). When a Space is sent and received, both ends set their state to LTRS, not to FIGS. You are right that no shift character is sent. When all else fails, check the ARRL H
I think you're right. If I recall correctly, when a space is detected by either the transmitter or receiver, they each reset themselves back to FIGS case, but no actual FIGS character is sent. The s