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

Results:

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

Total 68 documents matching your query.

41. Re: [RTTY] SO2R (score: 1): Author: Michael Schulz <mschulz@creative-chaos.com>; Date: Mon, 28 Sep 2015 12:49:08 -0700; One thing I'd like to add would be the suggestion to *not* use 59914 but rather 599 14 in the exchange. That why one can just click on it in MMTTY for example and N1MM+ populates it. The string toget; /archives//html/RTTY/2015-09/msg00094.html (10,697 bytes)
42. Re: [RTTY] SO2R (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Mon, 28 Sep 2015 13:13:54 -0700; What Ed said 100%. There are myriad reasons for delays. And one of the things you learn doing SO2R is how to kill a CQ when you need to send a response on another radio. I have experimented with sing; /archives//html/RTTY/2015-09/msg00096.html (15,521 bytes)
43. Re: [RTTY] SO2R (score: 1): Author: Ken K6MR <k6mr@outlook.com>; Date: Mon, 28 Sep 2015 13:17:53 -0700; Im still relatively new at this so the answer to this question may be weve always done it this way After GM3XXX sends his exchange, why do you send his call again (GM3XXX TU M7T QRZ) ? You sent his c; /archives//html/RTTY/2015-09/msg00097.html (10,333 bytes)
44. Re: [RTTY] SO2R (score: 1): Author: Al Kozakiewicz <akozak@hourglass.com>; Date: Mon, 28 Sep 2015 20:17:52 +0000; Agreed, but N1MM fills out the zone based on the call sign for this contest so there no need to click anything at all. WW is the lazy man's contest with respect to the exchange. Only need to click on; /archives//html/RTTY/2015-09/msg00098.html (12,268 bytes)
45. Re: [RTTY] SO2R (score: 1): Author: Michael Schulz <mschulz@creative-chaos.com>; Date: Mon, 28 Sep 2015 13:21:30 -0700; Yes, by default it does it, I had several occasions this weekend where the zone sent was not the same as the one pre-filled (all US based calls). Mike K5TRI contest so the time waited for OK. _______; /archives//html/RTTY/2015-09/msg00099.html (13,827 bytes)
46. Re: [RTTY] SO2R (score: 1): Author: Al Kozakiewicz <akozak@hourglass.com>; Date: Mon, 28 Sep 2015 20:26:25 +0000; Hmmm. I believe the zone will change once you enter the state. There were a few 2 area call signs from CA and I was careful to check the zone before logging and I recall that all were zone 3 and not; /archives//html/RTTY/2015-09/msg00100.html (14,155 bytes)
47. Re: [RTTY] SO2R (score: 1): Author: Michael Schulz <mschulz@creative-chaos.com>; Date: Mon, 28 Sep 2015 13:28:00 -0700; There are multiple reasons why the zone might mismatch with the sent exchange. 99.9999% of the cases are correct. There are always outliers. It was a mere suggestion. Mike K5TRI were probably all ___; /archives//html/RTTY/2015-09/msg00101.html (15,866 bytes)
48. Re: [RTTY] SO2R (score: 1): Author: "David G3YYD" <g3yyd@btinternet.com>; Date: Mon, 28 Sep 2015 16:29:18 -0500; Simple it is the last opportunity that he has to ensure I have his call correct (I lose points for incorrect call) and for that station if he has QRM to know I have successfully worked him. In a busy; /archives//html/RTTY/2015-09/msg00102.html (11,408 bytes)
49. Re: [RTTY] SO2R (score: 1): Author: "Jeff AC0C" <keepwalking188@ac0c.com>; Date: Mon, 28 Sep 2015 15:30:33 -0500; The number of time sent really depends on a lot of things. If you have a big signal and are running high power, then it's easier to get away with a single instance of sending the guy's call sign beca; /archives//html/RTTY/2015-09/msg00103.html (11,689 bytes)
50. Re: [RTTY] SO2R (score: 1): Author: Ken K6MR <k6mr@outlook.com>; Date: Mon, 28 Sep 2015 13:44:23 -0700; I only wonder why we dont do that on cw. Same problem, but I rarely hear anyone do it on cw. I guess whatever works for you is the way to go. Tnx, Ken K6MR Simple it is the last opportunity that he h; /archives//html/RTTY/2015-09/msg00104.html (11,615 bytes)
51. Re: [RTTY] SO2R (score: 1): Author: Ed Muns <ed@w0yk.com>; Date: Mon, 28 Sep 2015 16:52:24 -0400; Of course. The more times you send each other's call sign, the more certain that you have it correct. Where do you draw the line on how many times you verify the other station's call? Almost no one d; /archives//html/RTTY/2015-09/msg00105.html (13,377 bytes)
52. Re: [RTTY] SO2R (score: 1): Author: Jeff Stai <wk6i.jeff@gmail.com>; Date: Mon, 28 Sep 2015 14:13:19 -0700; The main reason to resend their call in the TU is if they corrected you (or you corrected yourself) and you want to acknowledge the correction (and per the CQWW rules, you actually are required to!); /archives//html/RTTY/2015-09/msg00108.html (14,385 bytes)
53. Re: [RTTY] SO2R (score: 1): Author: Michael Schulz <mschulz@creative-chaos.com>; Date: Mon, 28 Sep 2015 14:19:26 -0700; I actually also correct the call before the TU in CW as well in case of a correction. Mike K5TRI _______________________________________________ RTTY mailing list RTTY@contesting.com http://lists.con; /archives//html/RTTY/2015-09/msg00109.html (16,153 bytes)
54. Re: [RTTY] SO2R (score: 1): Author: "Jim W7RY" <w7ry@centurytel.net>; Date: Mon, 28 Sep 2015 15:08:52 -0700; Agreed Ed! I usually run SO2R but had some issues (mine) with software. I didnt run long but had a great time in the hours I did work. 73 Jim W7RY --Original Message-- From: Ed Muns Sent: Monday, Sep; /archives//html/RTTY/2015-09/msg00112.html (13,504 bytes)
55. Re: [RTTY] SO2R (score: 1): Author: "Don Hill AA5AU" <aa5au@bellsouth.net>; Date: Mon, 28 Sep 2015 17:31:13 -0500; As a measure, I normally do around 2k Q's in the ARRL RTTY Roundup and I'm low power. I send the station's callsign only once when running and none if I'm S&P and my total score reduction usually run; /archives//html/RTTY/2015-09/msg00113.html (14,999 bytes)
56. Re: [RTTY] SO2R (score: 1): Author: Ed Muns <ed@w0yk.com>; Date: Mon, 28 Sep 2015 19:21:32 -0400; This is so obvious and ingrained, its out of my consciousness. And, yes, the CQ WW Committee added it to the rules a couple years ago. Our reason was that some "errant" stations were cleansing thei; /archives//html/RTTY/2015-09/msg00115.html (15,763 bytes)
57. Re: [RTTY] SO2R (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Mon, 28 Sep 2015 19:08:25 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: With N1MM Logger, you can click anywhere in 59914 and it will capture only the zone. It has had this capability for years. However, I do put a space in t; /archives//html/RTTY/2015-09/msg00117.html (9,385 bytes)
58. Re: [RTTY] SO2R (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Mon, 28 Sep 2015 19:24:57 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: Not necessarily. Often it happens that there are two or more stations each of whom thinks they are the one the CQ station is working and both of them wil; /archives//html/RTTY/2015-09/msg00119.html (9,095 bytes)
59. Re: [RTTY] SO2R (score: 1): Author: Bill Turner <dezrat@outlook.com>; Date: Mon, 28 Sep 2015 19:30:34 -0700; -- ORIGINAL MESSAGE --(may be snipped) REPLY: Because on CW you can pretty much trust your ears to decode properly or to be fairly sure that they did not. Not so with RTTY. The machine can make a mis; /archives//html/RTTY/2015-09/msg00120.html (8,320 bytes)
60. Re: [RTTY] SO2R (score: 1): Author: Ken K6MR <k6mr@outlook.com>; Date: Mon, 28 Sep 2015 19:43:59 -0700; True enough. The problem I see is if the station decides you have the call wrong at the TU message its too late. Once you send TU the other stations are now calling and you may not hear/see the previ; /archives//html/RTTY/2015-09/msg00121.html (9,307 bytes)

Current List: 41 - 60
Page: [1] [2] [3] [4]