Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mg03.r1000.mx.aol.com (Internet Inbound) with ESMTP id 60C9D38000083; Sat, 17 Mar 2012 08:08:29 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1S8sPM-0003Kv-CF for rs_out_1@blacksheep.org; Sat, 17 Mar 2012 12:06:52 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1S8sPL-0003Km-Tu for rsgb_lf_group@blacksheep.org; Sat, 17 Mar 2012 12:06:51 +0000 Received: from out1.ip09ir2.opaltelecom.net ([62.24.128.245]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1S8sPJ-0001Zx-Hl for rsgb_lf_group@blacksheep.org; Sat, 17 Mar 2012 12:06:51 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ap4BAM99ZE9cGSfQ/2dsb2JhbAAMNrM4hhkBAQEBAzg8BBELCQ8JFg8JAwIBAgFFEwgBAcIFkHwEjgCYEIJm X-IronPort-AV: E=Sophos;i="4.73,602,1325462400"; d="scan'208";a="509180378" Received: from host-92-25-39-208.as13285.net (HELO [192.168.2.4]) ([92.25.39.208]) by out1.ip09ir2.opaltelecom.net with ESMTP; 17 Mar 2012 12:06:43 +0000 Message-ID: <4F647E53.8010903@talktalk.net> Date: Sat, 17 Mar 2012 12:06:43 +0000 From: qrss User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: rsgb_lf_group@blacksheep.org References: <4F647735.3372.5358BB@mike.dennison.ntlworld.com> In-Reply-To: <4F647735.3372.5358BB@mike.dennison.ntlworld.com> X-Spam-Score: 1.4 (+) X-Spam-Report: autolearn=disabled,RATWARE_GECKO_BUILD=1.426 Subject: Re: LF: Opera will QRM 137k QRSS Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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=none 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:513278912:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d60cb4f647ebd0255 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Hi Mike I think your subject is necessary. Not everyone is aware of the gentleman's band plans on LF. I think your last post was noted and responded to by the 'team'. Being in Beta test hopefully more can be done to satisfy all. Like yourself I regard Opera as a useful tool. There was not much response to your last post, I believe some have not too sensibly marked all subject lines with Opera as Spam. PS I miss your 136kHz Opera signal. 73 Eddie G3ZJO On 17/03/2012 11:36, Mike Dennison wrote: > Some of you may have missed my last post on this subject because it > had 'Opera' in the title and you thought it didn't concern you. But > it does. > > The Opera data mode evolves almost daily and is still in its Beta > stage. It recommends operating frequencies, and indeed won't work > outside these frequencies without mis-using it. The early versions > recommended 137.3 to 137.5kHz for Opera 8 and 137.5 to 137.6kHz for > the slower Opera 32, both beacon only. So far, so good. > > Just over a week ago, version 1.3.3 introduced a new 'QSO mode' and > recommended 137.4 to 137.6 for this activity. It then moved Op8 > beacons to 137.6-137.8kHz. My last post on this subject protested in > strong terms at this flagrant disregard for long-standing > bandplanning. In particular it would have caused interference to the > 137.777kHz America-Europe DX watering hole. > > I have been away for a week and have downloaded Opera version 1.3.9 > (I did say it evolved daily) and this has improved the bandplanning, > probably thanks to some members of this group who are closer to the > Opera team than I am.The threat to the DX wateringhole has gone but > the encroachment on the QRSS window is still there. > > The new frequencies are: 137.5 to 137.6kHz for Op32 and 137.6 to > 137.7kHz for Op8. The 'QSO mode' seems to have been dropped on this > band. > > This still means that Opera 8 beacons will occupy the area between > 137.65 and 137.70 which has for many years been used for QRSS 3 and > 10 QSOs, including the centre frequency (137.70) itself. > > Whilst Opera may be regarded as machine generated/read QRSS and > therefore a good bedfellow for QRSS, it uses a different (non-Morse) > coding. Therefore an Opera user will not be able to read QRSS (and > won't even know it is there it if he turns off the resource-hungry > waterfall display) and the QRSS user will struggle to read what he > thinks is a weak QRSS station, but will in fact be Opera. > > It could be argued that QRSS operators could use 137.70 to 136.75kHz, > but this disregards the substantial QRM from DCF39 sidebands which > affect all of western Europe, especially Germany. In any case, why > should they have to halve the available slot? > > However, much more to the point, bandplanning on this band has been > the subject of considerable discussion on this group right from the > very start, and has evolved to suit all concerned. By contrast, the > Opera team appear to have made arbitrary decisions based perhaps on a > poll of a handful of keen Opera fans without any consultation with > users of other, long-standing modes. > > When Opera first came out, I was accused of old-fashioned thinking > when I referrred to local adjacent channel QRM. If Opera is so > frequency-efficient, why does it need 200Hz when QRSS3/10 has got by > with 80-100Hz for years? > > Lastly, I am not anti-Opera. Until a week ago I used it every day, on > both modes and regard it as a useful tool. But it must be compatible > with users of other, well-established, modes. > > Does anyone else feel as angry I do about a software writer dictating > our bandplans? > > Mike, G3XDV > ========== > > >