I made a few at the beginning just like that. The Macros were left over from CQ WW RTTY and had something like "599-{EXCH}" in them. In N1MM, choosing the contest at the start defaults the value of {
4U1WB, which is the station mentioned, is in DC and does not count as a DXCC entity like 4U1UN and 4U1ITU. As noted, RTTY Roundup is States and Provinces, not ARRL/RAC sections. -- Peter Laws | N5UWY
Yes, very sad. Thirteen QSOs here since I got back on RTTY in 2004. -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ RTTY mailing list RTTY@c
Which OS? -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting.com/mailman/listinfo
Depends on the exchange. Remember that the dash is in FIGS set, not LTRS. (see, for example, http://www.dataip.co.uk/Reference/BaudotTable.php) 599 123 123 -- USOS causes an extra FIGS shift 599 123-
"But N is shorter than 9!" :-) (for the record, this is a joke - both are 5-bits long) -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ RTTY
The - character is in the FIGS case, not LTRS, so how would I end up with your example? -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ RTTY
Thanks for smacking my softball pitch into the left-field bleachers. :-) If the exchange is my state or my name, no dashes. If the exchange is a serial number, dashes. That's my plan and I'm sticking
If I understand USOS correctly (happy to be wrong!), then a USOS station would send the first example above as: <FIGS>599<SPACE><FIGS>123<SPACE><FIGS>123 and the second example as: <FIGS>599-123-123
Right click the text in bare MMTTY. Mouse-over and look on the top line when MMTTY engine is used with N1MM. Confident that other software has it. Assumed they all did. Seems like WF1B's RTTY had som
In the FIGS case or the LTRS case??? :-) -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.
I'm all for that. Doesn't one of the BARTG tests already ignore RST? More of that, please. -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ R
I don't see this. I need to add 17% (in the example given) to EVERY transmission because a bit *might* get stomped? When I first got back into RTTY I sent my exchange three times, every time based on
I have to agree. If you aren't interested in making your communications as robust and efficient as possible, you should definitely not read these messages! -- Peter Laws | N5UWY | plaws plaws net | T
First of all, I know nothing. Of substance, anyway. The issue is the shifts - they're overhead. To get more than 32 characters out of 5 bits, Baudot includes a FIGS shift and a LTRS shift. As Chen ju
I, too, think it would be fun to try 75-baud RTTY, perhaps in a 4-h sprint type of contest. How about the "BARTG High Speed Sprint"? :-) If enough people like it, surely someone will adopt it for a l
I have one of those little Brother label printers and try to mark both ends with both connections. The ink has faded, though, as N5UWY's window faces south and they are pretty much in the sun most of
I have a Panduit label-maker at work, too, but unfortunately, it's not the type that does the little wrap around the wire thing. If it *was*, I'd have to keep it at home. You know, so nothing happene
Got to agree. Interested in 75-baud Baudot. No ASCII, no 110-baud, etc. And yes, this started out as a speed vs robustness discussion, but all that STILL applies to 75-baud RTTY. Of course, if we all