Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Zone\s+sent\s+as\s+letters\?\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+Zone\s+sent\s+as\s+letters\?\s*$/: 31 ]

Total 31 documents matching your query.

1. [RTTY] Zone sent as letters? (score: 1): Author: Jim Reisert AD1C <jjreisert@alum.mit.edu>; Date: Sat, 26 Sep 2009 22:54:08 -0600; I copied two stations today whose report was received the same way: 599 PR AL The zone (04) is ALWAYS being sent (received) as "PR" instead of "04". It's 100% consistent, I never see the numerical zo; /archives//html/RTTY/2009-09/msg00097.html (6,708 bytes)
2. Re: [RTTY] Zone sent as letters? (score: 1): Author: Phil Sussman <psussman@pactor.com>; Date: Sun, 27 Sep 2009 01:25:05 -0400; Jim, It's the dreaded USOS (Unshift on Space) rearing it's ugly head. In the "who's fault is it" sense the answer is most likely both. For things to work correctly USOS must be in sync, and things li; /archives//html/RTTY/2009-09/msg00098.html (7,857 bytes)
3. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Bill, W6WRT" <dezrat1242@yahoo.com>; Date: Sat, 26 Sep 2009 23:08:35 -0700; ORIGINAL MESSAGE: REPLY: This has truly been beat to death over the years, but it really is best to NOT use the hyphen because that defeats USOS. USOS is a great feature, but both TX and RX stations; /archives//html/RTTY/2009-09/msg00099.html (7,471 bytes)
4. Re: [RTTY] Zone sent as letters? (score: 1): Author: Kok Chen <chen@mac.com>; Date: Sun, 27 Sep 2009 00:19:27 -0700; That is an incorrect analysis of the original poster's (AD1C) problem. The "599 PR AL" is due the fact that the receiver was using USOS while the transmitter was not. I.e., Jim *was* using USOS on h; /archives//html/RTTY/2009-09/msg00100.html (8,415 bytes)
5. Re: [RTTY] Zone sent as letters? (score: 1): Author: Phil Sussman <psussman@pactor.com>; Date: Sun, 27 Sep 2009 04:12:51 -0400; Chen, Your explanation, as usual, is concise and far better than I could have ever expressed it. Thank you, 73, de N8PS PS. I was sure that I was correct with the - sign. -- _________________________; /archives//html/RTTY/2009-09/msg00101.html (9,542 bytes)
6. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Jim W7RY" <w7ry@arrl.net>; Date: Sun, 27 Sep 2009 08:50:22 -0700; I think USOS is a receive setting only. USOS does not effect transmitting? 73 Jim W7RY -- _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.contesting; /archives//html/RTTY/2009-09/msg00102.html (9,378 bytes)
7. Re: [RTTY] Zone sent as letters? (score: 1): Author: Phil Sussman <psussman@pactor.com>; Date: Sun, 27 Sep 2009 12:42:19 -0400; If the USOS 'feature' is set to ON: (as I understand it) ON TRANSMIT: If there is a space after a numeric character, the sending software inserts a 'shift FIGS' character into the transmitted data st; /archives//html/RTTY/2009-09/msg00103.html (11,693 bytes)
8. Re: [RTTY] Zone sent as letters? (score: 1): Author: Peter Laws <plaws0@gmail.com>; Date: Sun, 27 Sep 2009 11:53:55 -0500; Me too! I'm poking at CQWW and immediately went and changed my EXCH macro! :-) -- Peter Laws | N5UWY | plaws plaws net | Travel by Train! _______________________________________________ RTTY mailing; /archives//html/RTTY/2009-09/msg00104.html (7,593 bytes)
9. Re: [RTTY] Zone sent as letters? (score: 1): Author: Kok Chen <chen@mac.com>; Date: Sun, 27 Sep 2009 10:15:18 -0700; Unfortunately, it does. The transmitter has to check if a character with a numerical shift is being send right after sending a space character. When USOS is used at the receiving end, the transmitter; /archives//html/RTTY/2009-09/msg00105.html (8,331 bytes)
10. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Bill, W6WRT" <dezrat1242@yahoo.com>; Date: Sun, 27 Sep 2009 15:18:56 -0700; ORIGINAL MESSAGE: REPLY: Well, yes and no. The problem happens when the figs shift BEFORE the 599-3 gets garbled. Then you get TOOAE. If USOS was on in that example and there was no hyphen, you would; /archives//html/RTTY/2009-09/msg00111.html (9,014 bytes)
11. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Bill, W6WRT" <dezrat1242@yahoo.com>; Date: Sun, 27 Sep 2009 15:19:59 -0700; ORIGINAL MESSAGE: REPLY: Right you are, my error. I knew it was one or the other. :-) 73, Bill W6WRT _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists; /archives//html/RTTY/2009-09/msg00112.html (9,019 bytes)
12. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Bill, W6WRT" <dezrat1242@yahoo.com>; Date: Sun, 27 Sep 2009 15:28:14 -0700; ORIGINAL MESSAGE: REPLY: No, no, no.... please don't do this. USOS exists for a reason. If you fill your exchange with hyphens you will soon start seeing TOOAWT and other mysterious exchanges. Let US; /archives//html/RTTY/2009-09/msg00113.html (8,634 bytes)
13. Re: [RTTY] Zone sent as letters? (score: 1): Author: Kok Chen <chen@mac.com>; Date: Sun, 27 Sep 2009 16:20:08 -0700; Lets use rational dialog instead of scare tactics. You seem to think that a FIGS before the 599 can get wipe out by noise and thus cause an "TOOAWT." And yet a FIGS after a space character in a USOS; /archives//html/RTTY/2009-09/msg00114.html (10,084 bytes)
14. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Paul Playford" <paul@w8aef.com>; Date: Sun, 27 Sep 2009 18:01:25 -0700; FWIW, I just finished racking up 1284 qso's in the CQWW RTTY contest and not once did I see TOO. But I did see a few unshifted zones. Never a problem when a hyphen was present. de Paul, W8AEF ZF2JI/Z; /archives//html/RTTY/2009-09/msg00115.html (9,305 bytes)
15. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Bill, W6WRT" <dezrat1242@yahoo.com>; Date: Mon, 28 Sep 2009 06:50:37 -0700; ORIGINAL MESSAGE: REPLY: Paul, your two statements above contradict themselves. The most likely reason you saw unshifted zones was BECAUSE hyphens were present. An unshifted hyphen prints as the lett; /archives//html/RTTY/2009-09/msg00118.html (9,740 bytes)
16. Re: [RTTY] Zone sent as letters? (score: 1): Author: "Bill, W6WRT" <dezrat1242@yahoo.com>; Date: Mon, 28 Sep 2009 06:50:43 -0700; ORIGINAL MESSAGE: REPLY: I'm all in favor of rational dialog. Here is some: My objection is the use of hyphens or slashes or periods to separate the elements of an exchange, such as 599-25-25 or 599/; /archives//html/RTTY/2009-09/msg00119.html (10,598 bytes)
17. Re: [RTTY] Zone sent as letters? (score: 1): Author: "WS7I" <ws7i@ewarg.org>; Date: Mon, 28 Sep 2009 07:07:18 -0700; What I really don't understand is why you don't just make this easy. 5993 WA de ws7i And don't tell me its 03 its just Three! -- ws7i@ewarg.org [This E-mail scanned for viruses by ClamAV] ___________; /archives//html/RTTY/2009-09/msg00120.html (10,878 bytes)
18. Re: [RTTY] Zone sent as letters? (score: 1): Author: Peter Laws <plaws0@gmail.com>; Date: Mon, 28 Sep 2009 09:47:11 -0500; I thought about this on the weekend (when I made a whopping 44 Qs ... but C3 and FO8 for new ones :-). I have always used a leading 0 but now am having second thoughts. I did insert a - in my macro -; /archives//html/RTTY/2009-09/msg00122.html (8,673 bytes)
19. Re: [RTTY] Zone sent as letters? (score: 1): Author: Hank Garretson <w6sx@arrl.net>; Date: Mon, 28 Sep 2009 08:06:17 -0700; I did insert a - in my macro -- Instead of using {EXCH} in your macro, just type what you want it to send. In my case: ... 599 3 CA ... 73, Hank, W6SX _______________________________________________; /archives//html/RTTY/2009-09/msg00123.html (8,443 bytes)
20. Re: [RTTY] Zone sent as letters? (score: 1): Author: Peter Laws <plaws0@gmail.com>; Date: Mon, 28 Sep 2009 11:21:55 -0500; That would defeat the point of using the variable. In N1MM, you determine the exchange when you start the log for a new contest. Because it's a variable in the macro, you usually don't have to change; /archives//html/RTTY/2009-09/msg00129.html (8,911 bytes)

Current List: 1 - 20
Page: [1] [2]