Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-md05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 9859838000090; Wed, 1 Feb 2012 05:53:35 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1RsXny-00081Y-J1 for rs_out_1@blacksheep.org; Wed, 01 Feb 2012 10:52:46 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1RsXny-00081P-5A for rsgb_lf_group@blacksheep.org; Wed, 01 Feb 2012 10:52:46 +0000 Received: from rhcavuit02.kulnet.kuleuven.be ([134.58.240.130] helo=cavuit02.kulnet.kuleuven.be) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1RsXnw-0000Wi-Kl for rsgb_lf_group@blacksheep.org; Wed, 01 Feb 2012 10:52:46 +0000 X-KULeuven-Envelope-From: rik.strobbe@fys.kuleuven.be X-KULeuven-Scanned: Found to be clean X-KULeuven-ID: 63B32128089.A8FCA X-KULeuven-Information: Katholieke Universiteit Leuven Received: from smtps02.kuleuven.be (smtpshost02.kulnet.kuleuven.be [134.58.240.75]) by cavuit02.kulnet.kuleuven.be (Postfix) with ESMTP id 63B32128089 for ; Wed, 1 Feb 2012 11:52:31 +0100 (CET) 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 2F518F3862 for ; Wed, 1 Feb 2012 11:52:31 +0100 (CET) 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; Wed, 1 Feb 2012 11:52:31 +0100 X-Kuleuven: This mail passed the K.U.Leuven mailcluster From: Rik Strobbe To: "rsgb_lf_group@blacksheep.org" Date: Wed, 1 Feb 2012 11:52:30 +0100 Thread-Topic: OPERA and QRS Thread-Index: Aczgy4KK1BbmdydUTni+rTyfbGJtJwAACvPQ Message-ID: References: <4F2911FC.3020709@talktalk.net> In-Reply-To: <4F2911FC.3020709@talktalk.net> 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,none Subject: LF: RE: OPERA and QRS Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=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:440785152:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d60594f2919af788e X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Hello Eddy, comparing Opera and QRSS with identical bit lengths seems not correct to me= as Opera uses "ticks" (such as Forward Error Correction) to improve SNR. Assuming a simple 8 bit character set it takes only 48 bits to transmit a 6= character call. With clever coding (as used in WSPR) it is even possible t= o fit a 6 character call into 28 bits. But each Opera transmission contains= 240 bits. So if Opera is allowed to use FEC in order to improve, QRSS should be allow= ed to increase dotlength for the same reason. Same transmission duration seems far more fair than same bit/dot length.=20 But then the dot length would have to differ for every call, so maybe we sh= ould agree on an "average call" to determine the QRSS dot length. A traditi= onal method to determine CW speed is the PARIS method (PARIS includes exact= ly 50 dots, including the word spacing), inserting an average length number= (7) would give us the nice call PA7RIS, that contains 66 dots, including t= he word spacing. As Opera transmits only a single word (call) the word spac= ing is not used, so it can be ommted also in QRSS what leads to a (convenie= nt) number of 60 dots. Opera4 takes 246 seconds, so the QRSS speed to compare with should be 246/6= 0 =3D 4(.096) seconds dot lenght. 73, Rik ON7YD - OR7T=20 ________________________________________ Van: owner-rsgb_lf_group@blacksheep.org [owner-rsgb_lf_group@blacksheep.org= ] namens qrss [qrss@talktalk.net] Verzonden: woensdag 1 februari 2012 11:20 Aan: rsgb_lf_group@blacksheep.org Onderwerp: LF: OPERA and QRS We all seem to have agreed to compare OPERA with a QRS speed which takes the same time to send a call sign, correct or not? A QRS beacon can send the call continuously all day and successive periods are often used to establish the information. How about comparing like for like in the timing of Data Bits, OPERA uses digital techniques and no doubt repeats the data in the 4 minute period of OP4. In this case we would need to be comparing it with QRS1 or QRS1.025 if you like. I feed a coding session coming on. 73 Eddie G3ZJO=