Return-Path: Received: from mtain-db07.r1000.mx.aol.com (mtain-db07.r1000.mx.aol.com [172.29.64.91]) by air-df05.mail.aol.com (v129.4) with ESMTP id MAILINDF051-5ef24bdb43db345; Fri, 30 Apr 2010 16:55:55 -0400 Received: from post.thorcom.com (post.thorcom.com [193.82.116.20]) by mtain-db07.r1000.mx.aol.com (Internet Inbound) with ESMTP id B25E13800036A; Fri, 30 Apr 2010 16:55:52 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1O7xEw-0008Sd-Tq for rs_out_1@blacksheep.org; Fri, 30 Apr 2010 21:55:14 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1O7xEw-0008ST-FJ for rsgb_lf_group@blacksheep.org; Fri, 30 Apr 2010 21:55:14 +0100 Received: from smtp5.freeserve.com ([193.252.22.128]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1O7xEu-00071I-F4 for rsgb_lf_group@blacksheep.org; Fri, 30 Apr 2010 21:55:14 +0100 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3411.me.freeserve.com (SMTP Server) with ESMTP id 7A26A1C0021C for ; Fri, 30 Apr 2010 22:55:06 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf3411.me.freeserve.com (SMTP Server) with ESMTP id 6CC501C00224 for ; Fri, 30 Apr 2010 22:55:06 +0200 (CEST) Received: from AGB (unknown [91.110.80.156]) by mwinf3411.me.freeserve.com (SMTP Server) with SMTP id DE56E1C0021C for ; Fri, 30 Apr 2010 22:55:03 +0200 (CEST) X-ME-UUID: 20100430205503911.DE56E1C0021C@mwinf3411.me.freeserve.com Message-ID: <24C8460A2E2642F9B2E2E7D4994D32BA@AGB> From: "Graham" To: References: <618970.37366.qm@web28105.mail.ukl.yahoo.com>, <005801cae88f$64116770$0401a8c0@xphd97xgq27nyf> <4BDB2274.14798.2CE59E3@dave.davesergeant.com> <6BE921B6077A41AE814432EC5C9590B1@JimPC> In-Reply-To: <6BE921B6077A41AE814432EC5C9590B1@JimPC> Date: Fri, 30 Apr 2010 21:55:03 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8089.726 X-MIMEOLE: Produced By Microsoft MimeOLE V14.0.8089.726 X-Antivirus: avast! (VPS 100430-0, 30/04/2010), Outbound message X-Antivirus-Status: Clean X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: Re: ROS s/ware Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original 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.1 required=5.0 tests=MISSING_OUTLOOK_NAME 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-sid: 3039ac1d405b4bdb43d81c65 X-AOL-IP: 193.82.116.20 Thank you for that Jim, As you well know ,transmitting data modes on 500 is not a simple mater and takes a great deal of technical input to ensure the system is on frequency , stable , liner and fit for purpose , and not causing interference to the other two band users. reports of over modulation and distortion detectable at range may be appreciated by the few, but are in fact an allegation of criminal activity as defined in the 1949 post and telegraph act , a fact that's perhaps not lost on the real pirates of this world when the custom and excise where given durastriction over the implementation of the act , transmitting out of band is defined as operating out side the terms of your licence and are therefore in breach of the act . As for trailing data modes and yes , fully aware of the SS nature of the mode , and very well it works too ... we should be mindful of the reason 'we' are on 500 in the first place and to the quite level headed approach of Ofcom ... sure SS is banned in the usa and now after the second 'Concorde' moment is the Domino data mode that also used SS .... after the arrl made good use of it for disaster communication over such a long period .... Of interest tonight was the low power qso between Gary and myself using the Ros eme mode , with a power reduction from my station of 3 watts feeding the antenna via a 20 dB attenuator, 30 mW to the antenna , which roughly requires 50 Watt to radiate 100 mW erp .. a thither reduction of 500:1 ! This level produced 100 % copy over 30 miles to a similar Ae , the Ros 500/8 mode failed at a signal level of approximately 10 dB higher ( I will check with Jose, to see if this measurement is as expected) 73 - G .. -------------------------------------------------- From: "James Moritz" Sent: Friday, April 30, 2010 8:41 PM To: Subject: LF: Re: ROS s/ware > Dear Dave, LF Group, > > >Their first suggested working frequency on 20m put it splattering >> right over the IARU beacons on 14100, which it seems the developers had >> never heard of. > > "Splatter" usually refers to distortion products outside the signal > bandwidth of a signal, but these don't really occur with ROS and other > constant-amplitude, FSK, modes since there is only a single tone being > transmitted at any one time, and so nothing else to intermodulate with, > even > if the TX is highly non-linear. So this complaint is technically > nonsensical, although 14.1MHz obviously isn't a good choice of frequency! > What people seem to get excited about is that the transmission has a > bandwidth of 500Hz, or 2.2kHz - somewhat wider than some other modes, with > the objective of trading off increased bandwidth against achieving > increased > robustness. The theory is fine; finding out if this actually works and > offers any practical advantages is why we should be trying it out of > course. > The 500Hz bandwidth easily fits into the "digital" segment even of 500kHz, > so no problem there. > > BTW, now getting about 95% copy of G4WGT/ 100% of G0NBD having a QSO in > ROS > 500Hz / 16baud mode - the bandwidth and centre frequency is as > advertised - > see attachment. Might try transmitting later, but have some other problems > to sort out first... > > Cheers, Jim Moritz > 73 de M0BMU > >