Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+SS\s+On\/Off\s+Times\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[TRLog\]\s+SS\s+On\/Off\s+Times\s*$/: 10 ]

Total 10 documents matching your query.

1. [TRLog] SS On/Off Times (score: 1): Author: Lfelker@aol.com (Lfelker@aol.com); Date: Tue, 26 Oct 1999 10:20:44 EDT; I dont recall seeing this is addressed on the reflector. In reviewing the Cabrillo format in the Nov QST, I didnt see any fields reserved for on/off times. How is everyone planning on dealing with th; /archives//html/TRLog/1999-10/msg00082.html (7,477 bytes)
2. [TRLog] SS On/Off Times (score: 1): Author: geoiii@kkn.net (George Fremin III); Date: Tue, 26 Oct 1999 07:32:41 -0700 (PDT); The way most have done this in the past is to list the offtimes on the summary sheet. -- George Fremin III "I'm talkin' 'bout that outlaw X Johnson City, TX It's cuttin' through the air.... " K5TR (e; /archives//html/TRLog/1999-10/msg00083.html (8,074 bytes)
3. [TRLog] SS On/Off Times (score: 1): Author: k6ll@juno.com (k6ll@juno.com); Date: Tue, 26 Oct 1999 07:52:50 -0600; I always put it on the summary sheet. No contest sponsor has ever complained to me about that. e.g: op time: 2100 - 0400 = 07:00 1000 - 0300 = 17:00 total = 24:00 Dave Hachadorian, K6LL Yuma, AZ K6LL; /archives//html/TRLog/1999-10/msg00084.html (8,130 bytes)
4. [TRLog] SS On/Off Times (score: 1): Author: Lfelker@aol.com (Lfelker@aol.com); Date: Tue, 26 Oct 1999 11:15:25 EDT; Thanks to all for comments. The few times I have submitted electronic logs, I have put on/off times in the summary sheet. But the official SS announcement requires (as it has for some time, I think); /archives//html/TRLog/1999-10/msg00085.html (7,637 bytes)
5. [TRLog] SS On/Off Times (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 26 Oct 1999 15:32:05 -0000; I think the plan was for the log checking software to determine the operating time based upon the log itself. However, since listening time counts as operating time, I don't see how this can be done; /archives//html/TRLog/1999-10/msg00086.html (8,201 bytes)
6. [TRLog] SS On/Off Times (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 26 Oct 1999 15:33:48 -0000; There is a problem with this with Cabrillo - as it is more than a log format... it is a complete entry format - including the summary sheet. Currently - there is no provision for including op time e; /archives//html/TRLog/1999-10/msg00087.html (7,719 bytes)
7. [TRLog] SS On/Off Times (score: 1): Author: kg5u@hal-pc.org (Dale L. Martin); Date: Tue, 26 Oct 1999 18:32:35 -0500; fields with that Seems straightforward to me, Tree. The rules say "periods may not be less than 30 minutes in length." Any 30 minute or more time gap is an off-time. Anything less is on-time and the; /archives//html/TRLog/1999-10/msg00090.html (8,490 bytes)
8. [TRLog] SS On/Off Times (score: 1): Author: aa0cy@nwrain.com (Bob Wanderer); Date: Wed, 27 Oct 1999 10:21:32 -0700; I humbly disagree. Because of my station (and operator capabilities, I can easily go 30 minutes or more without a QSO (e.g. unsuccessfully calling a station I still need or everything I hear is a dup; /archives//html/TRLog/1999-10/msg00096.html (9,237 bytes)
9. [TRLog] SS On/Off Times (score: 1): Author: n6tr@teleport.com (n6tr@teleport.com); Date: 27 Oct 1999 18:41:07 -0000; Yup - I understand the problem. Even I, myself, world class contester extraordinare, have gone 30 minutes without a QSO in the SS - sitting in front of the rig trying. (How is that for the opposite; /archives//html/TRLog/1999-10/msg00097.html (8,118 bytes)
10. [TRLog] SS On/Off Times (score: 1): Author: kg5u@hal-pc.org (Dale L. Martin); Date: Wed, 27 Oct 1999 23:33:31 -0500; contester Wow! Whodathunk!? Somewhere around here I have a list of the number of 4-, 5-, 6-, 7-, 8- and 9-minute Between-QSOs-times that I experienced during the CW SS, 10m and WW CW contests. I pos; /archives//html/TRLog/1999-10/msg00102.html (8,565 bytes)

Current List: 1 - 10
Page: [1]