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

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[RTTY\]\s+RTTY\s+Best\s+Practices\s*$/: 21 ]

Total 21 documents matching your query.

1. [RTTY] RTTY Best Practices (score: 1): Author: Ed Steeble <esteeble@sc.rr.com>; Date: Mon, 09 Jan 2006 15:56:06 -0500; After reading the comments and discussions after the RU here are some of my observations, thoughts: 1) I will add CQ after my call when CQing. However with 90w to 100w and a vertical, I will keep the; /archives//html/RTTY/2006-01/msg00171.html (8,589 bytes)
2. Re: [RTTY] RTTY Best Practices (score: 1): Author: "Terry Gerdes" <terry@ab5k.net>; Date: Mon, 9 Jan 2006 19:13:43 -0600; hi Ed, Good stuff. One other thing to add is: I will never send a QSO B4 message. If someone calls me and I show him to be a dupe, I will work him anyway. The better op's know to do this. 73 Terry -; /archives//html/RTTY/2006-01/msg00175.html (9,964 bytes)
3. Re: [RTTY] RTTY Best Practices (score: 1): Author: "Tom Osborne" <w7why@verizon.net>; Date: Mon, 09 Jan 2006 20:06:05 -0800; and teach the new RTTY operator?" Hi Ed Best place to send them is www.aa5au.com. Don has a great tutorial there to help them get started in the right direction. 73 Tom W7WHY _______________________; /archives//html/RTTY/2006-01/msg00187.html (7,072 bytes)
4. Re: [RTTY] RTTY Best Practices (score: 1): Author: "A.J.C." <n2ki@amsat.org>; Date: Tue, 10 Jan 2006 07:12:28 -0500; All, Agreed; updating the CQ macro is a plus. Adding the CQ to the end does make it easier to differentiate the caller from the call-ee. "CQ Test N2KI N2KI CQ" as an example. No need to spell out the; /archives//html/RTTY/2006-01/msg00194.html (11,008 bytes)
5. Re: [RTTY] RTTY Best Practices (score: 1): Author: "Bill Turner" <dezrat1242@ispwest.com>; Date: Tue, 10 Jan 2006 07:05:59 -0800; ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A CR at the end doesn't accomplish anything positive and has one detrimental effect, IMO. When you are receiving, all you need is a; /archives//html/RTTY/2006-01/msg00195.html (8,691 bytes)
6. Re: [RTTY] RTTY Best Practices (score: 1): Author: "Andreas Rehberg" <arehberg@gmx.de>; Date: Tue, 10 Jan 2006 16:43:56 +0100 (MET); have to chase it with the mouse. this is only true for people 50yrs and older ;-) -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie _____________; /archives//html/RTTY/2006-01/msg00198.html (7,803 bytes)
7. Re: [RTTY] RTTY Best Practices (score: 1): Author: Bill Coleman <aa4lr@arrl.net>; Date: Fri, 13 Jan 2006 20:44:37 -0500; I never liked this practice in CW. Seems I would always copy the CQ and miss the guy's call. I also don't like the "CQ NA AA4LR NA" for the same reason. Space? Why not a CR/LF? I had a couple of guys; /archives//html/RTTY/2006-01/msg00298.html (8,738 bytes)
8. Re: [RTTY] RTTY Best Practices (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Fri, 13 Jan 2006 17:56:29 -0800; I don't like it on CW either, since TEST has fewer elements than CQ. Not so on RTTY, of course. CR/LF makes the line jump at the receiver end, unless using WriteLog. Space accomplishes the same purpo; /archives//html/RTTY/2006-01/msg00299.html (10,259 bytes)
9. Re: [RTTY] RTTY Best Practices (score: 1): Author: Kok Chen <chen@mac.com>; Date: Fri, 13 Jan 2006 18:39:21 -0800; It is not just a good idea, it is plain courtesy to the S&P guys like me. Otherwise I would have to wait until you CQ again, or more likely, I will just keep tuning to find the next station up the ba; /archives//html/RTTY/2006-01/msg00305.html (10,595 bytes)
10. Re: [RTTY] RTTY Best Practices (score: 1): Author: "VSH-RW4WZ" <vsh@udm.net>; Date: Sat, 14 Jan 2006 13:30:35 +0400; I'm not WriteLog user and really couldn't understand what is the difference with CR/LF readings by WL and other programs ? 73! Larry RW4WZ _______________________________________________ RTTY mailin; /archives//html/RTTY/2006-01/msg00316.html (8,070 bytes)
11. Re: [RTTY] RTTY Best Practices (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Sat, 14 Jan 2006 09:32:07 -0800; ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When printing, most RTTY programs insert a new line at the bottom of the screen and the previous line "jumps" up. Each new line cau; /archives//html/RTTY/2006-01/msg00319.html (9,651 bytes)
12. Re: [RTTY] RTTY Best Practices (score: 1): Author: Peter Laws <plaws0@gmail.com>; Date: Sun, 15 Jan 2006 12:24:31 -0600; Thank you for validating my use of odd numbers of critical elements, i.e. "IL IL IL". -- Peter Laws | N5UWY/9 | plaws0 gmail | Travel by Train! "They that can give up essential Liberty to obtain a li; /archives//html/RTTY/2006-01/msg00341.html (9,160 bytes)
13. Re: [RTTY] RTTY Best Practices (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Sun, 15 Jan 2006 11:18:57 -0800; ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ That statement caught my attention. What is desirable about odd numbers? Bill, W6WRT ______________________________________________; /archives//html/RTTY/2006-01/msg00348.html (9,187 bytes)
14. Re: [RTTY] RTTY Best Practices (score: 1): Author: Peter Laws <plaws0@gmail.com>; Date: Sun, 15 Jan 2006 13:27:01 -0600; If you copy "IL IN", you can't be certain where I am. If, OTOH, you copy "IL IN IL", you can be *reasonably*, but not 100%, certain that I'm in Illinois. -- Peter Laws | N5UWY/9 | plaws0 gmail | Trav; /archives//html/RTTY/2006-01/msg00349.html (9,596 bytes)
15. Re: [RTTY] RTTY Best Practices (score: 1): Author: Jeff Stai WK6I <wk6i@twistedoak.com>; Date: Sun, 15 Jan 2006 11:28:23 -0800; odd numbers break ties, this is why we have a vice president ;-) - j -- Jeff Stai jds@twistedoak.com Twisted Oak Winery http://www.twistedoak.com/ Rocketry Org. of CA http://www.rocstock.org/ Amateur; /archives//html/RTTY/2006-01/msg00350.html (9,506 bytes)
16. Re: [RTTY] RTTY Best Practices (score: 1): Author: Douglas Hall <doughall@pobox.com>; Date: Sun, 15 Jan 2006 14:33:56 -0500; From my perspective, it's not so much odd numbers as (in this case) 3 of them. Sending "IL" 3 times provides a way to do a 2/3 majority vote. If it comes out on my side as "IL IN IL" I can say with; /archives//html/RTTY/2006-01/msg00352.html (9,365 bytes)
17. Re: [RTTY] RTTY Best Practices (score: 1): Author: Bill Turner <dezrat1242@ispwest.com>; Date: Sun, 15 Jan 2006 11:36:11 -0800; ORIGINAL MESSAGE: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I use three myself, but that wasn't the question. The question was why odd numbers? 5, 7, 9? 101? Bill, W6WRT _____________________; /archives//html/RTTY/2006-01/msg00354.html (9,243 bytes)
18. Re: [RTTY] RTTY Best Practices (score: 1): Author: Kok Chen <chen@mac.com>; Date: Sun, 15 Jan 2006 13:01:38 -0800; In the early days of spacecrafts, Avizienis at JPL had introduced the concept of "Triple Modular Redundancy" into their hardware. Critical hardware were replicated in three, together with a voting me; /archives//html/RTTY/2006-01/msg00361.html (10,020 bytes)
19. Re: [RTTY] RTTY Best Practices (score: 1): Author: Bill Coleman <aa4lr@arrl.net>; Date: Sun, 15 Jan 2006 22:42:19 -0500; Chen, Cabrillo is just a data format for sending in logs -- it doesn't do the checking. However, the contest judges use several layers of checking to adjudicate a contact. Say W7AY and AA4LR make a c; /archives//html/RTTY/2006-01/msg00377.html (9,579 bytes)
20. Re: [RTTY] RTTY Best Practices (score: 1): Author: GM3SEK <gm3sek@ifwtech.co.uk>; Date: Mon, 16 Jan 2006 08:16:19 +0000; That first statement isn't the whole story, because "the Cabrillo format for sending in logs" was part of a larger package of changes in the rules about duplicate and other non-scoring contacts - and; /archives//html/RTTY/2006-01/msg00380.html (9,599 bytes)

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