Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-md05.r1000.mx.aol.com (Internet Inbound) with ESMTP id CB890380000B6; Thu, 11 Aug 2011 05:38:08 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1QrRgu-0007on-3C for rs_out_1@blacksheep.org; Thu, 11 Aug 2011 10:36:40 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1QrRgt-0007oe-Fz for rsgb_lf_group@blacksheep.org; Thu, 11 Aug 2011 10:36:39 +0100 Received: from rhcavuit01.kulnet.kuleuven.be ([134.58.240.129] helo=cavuit01.kulnet.kuleuven.be) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1QrRgr-0005R1-2D for rsgb_lf_group@blacksheep.org; Thu, 11 Aug 2011 10:36:39 +0100 X-KULeuven-Envelope-From: rik.strobbe@fys.kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 84E661382F7.A434C X-KULeuven-Information: Katholieke Universiteit Leuven Received: from smtps02.kuleuven.be (smtpshost02.kulnet.kuleuven.be [134.58.240.75]) by cavuit01.kulnet.kuleuven.be (Postfix) with ESMTP id 84E661382F7 for ; Thu, 11 Aug 2011 11:36:22 +0200 (CEST) Received: from ICTS-S-HUB-N3.luna.kuleuven.be (icts-s-hub-n3.luna.kuleuven.be [10.112.9.13]) by smtps02.kuleuven.be (Postfix) with ESMTP id 35846F3865 for ; Thu, 11 Aug 2011 11:36:22 +0200 (CEST) Received: from ICTS-S-EXC2-CA.luna.kuleuven.be ([10.112.11.13]) by ICTS-S-HUB-N3.luna.kuleuven.be ([10.112.9.13]) with mapi; Thu, 11 Aug 2011 11:36:22 +0200 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" Date: Thu, 11 Aug 2011 11:36:22 +0200 Thread-Topic: QRS / QRSS QSO How long ? Thread-Index: AcxXspFGMIFTmlIFRfWAlwMGCMarXwAVZDvX Message-ID: References: <2EC3B8AE82EF4F788FDB59D135233BB9@AGB> In-Reply-To: <2EC3B8AE82EF4F788FDB59D135233BB9@AGB> Accept-Language: nl-NL, nl-BE Content-Language: nl-BE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: nl-NL, nl-BE MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,HTML_MESSAGE=0.001 Subject: LF: RE: QRS / QRSS QSO How long ? Content-Type: multipart/alternative; boundary="_000_BF4A524700075746A6467658DFC7102CB0B27CF205ICTSSEXC2CAlu_" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.5 required=5.0 tests=HTML_40_50,HTML_MESSAGE, TO_ADDRESS_EQ_REAL autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:319349984:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d60594e43a30008af X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none --_000_BF4A524700075746A6467658DFC7102CB0B27CF205ICTSSEXC2CAlu_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Graham, if you restrict the QSO to the exchange of calls and reports a QRSS3 QSO ta= kes about 30 minutes. In QRSS10 this will be about 100 minutes, in QRSS30 3= 00 minutes etc... Using DFCW will reduce the time to about 1/3 so DFCW3 =3D 10 minutes, DFCW1= 0 =3D 33 minutes, DFCW30 =3D 100 minutes etc... If you want top exchange names and QTH's it will takes much longer, and mai= nly depend on the length of your name and QTH. Living in Llanfairpwllgwyngy= llgogerychwyrndrobwllllantysiliogogogoch will increase the QSO length by 30= minutes in QRSS3. ;-) But in my humble opinion there is no need to exchange names, QTH's etc... i= n such slow modes. 73, Rik ON7YD - OR7T ________________________________ Van: owner-rsgb_lf_group@blacksheep.org [owner-rsgb_lf_group@blacksheep.org= ] namens Graham [g8fzk@g8fzk.fsnet.co.uk] Verzonden: donderdag 11 augustus 2011 1:06 Aan: rsgb_lf_group@blacksheep.org Onderwerp: LF: QRS / QRSS QSO How long ? QRS / QRSS QSO How long ? May be the how long is a piece of string question .. but .. As a rough guide What speed and how long would a qso take using = qrs/qrss ? What would be used for a 'DX' qso as opposed to a beacon on 136 & = 500 ? NB: (not the audio band) By qso I mean call / name / qth , eg, the exchange of a couple = of words Tnx - G.. --_000_BF4A524700075746A6467658DFC7102CB0B27CF205ICTSSEXC2CAlu_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Graham,
 
if you restrict the QSO to the exchange of calls and reports a QRSS3 Q= SO takes about 30 minutes. In QRSS10 this will be about 100 minutes, i= n QRSS30 300 minutes etc...
Using DFCW will reduce the time to about 1/3 so DFCW3 =3D 10 minutes, = DFCW10 =3D 33 minutes, DFCW30 =3D 100 minutes etc...
If you want top exchange names and QTH's it will takes much longer, an= d mainly depend on the length of your name and QTH. Living in Llanfair= pwllgwyngyllgogerychwyrndrobwllllantysiliogogogoch will increase the QSO le= ngth by 30 minutes in QRSS3.  ;-)
But in my humble opinion there is no need to exchange names, QTH's etc= ... in such slow modes.
 
73, Rik  ON7YD - OR7T
=  
Van: owner-rsgb_l= f_group@blacksheep.org [owner-rsgb_lf_group@blacksheep.org] namens Graham [= g8fzk@g8fzk.fsnet.co.uk]
Verzonden: donderdag 11 augustus 2011 1:06
Aan: rsgb_lf_group@blacksheep.org
Onderwerp: LF: QRS / QRSS QSO How long ?

QRS  / QRSS    QSO= How long ?
 
May  be the  how long  = is a  piece  of  string   question .. but  ..
 
As a  rough   guide&nbs= p; What  speed  and  = how long  would a  qs= o  take using  qrs/qrss ?
 
What  would be  used  for a 'DX'  qso  = as  opposed  to  a beacon on 136 &  500  ?
 
NB: (not  the  audio  b= and)
 
By  qso  I mean  call /= name /  qth   , eg, the    exchange  of=   a couple  of  words
 
 
Tnx - G..


--_000_BF4A524700075746A6467658DFC7102CB0B27CF205ICTSSEXC2CAlu_--