Delivered-To: daveyxm@virginmedia.com Received: by 10.216.214.132 with SMTP id c4csp289470wep; Thu, 19 Sep 2013 09:14:08 -0700 (PDT) X-Received: by 10.194.93.72 with SMTP id cs8mr2025044wjb.49.1379607248265; Thu, 19 Sep 2013 09:14:08 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id pp9si3296711wjc.150.1969.12.31.16.00.00; Thu, 19 Sep 2013 09:14:08 -0700 (PDT) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1VMgTb-00008t-1T for rs_out_1@blacksheep.org; Thu, 19 Sep 2013 16:49:07 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VMgTa-00008i-JV for rsgb_lf_group@blacksheep.org; Thu, 19 Sep 2013 16:49:06 +0100 Received: from smtpout4.wanadoo.co.uk ([80.12.242.68] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1VMgTY-0003fW-JP for rsgb_lf_group@blacksheep.org; Thu, 19 Sep 2013 16:49:05 +0100 Received: from AGB ([2.27.189.136]) by mwinf5d56 with ME id T3p01m00m2x0oVu033p0o0; Thu, 19 Sep 2013 17:49:03 +0200 Message-ID: <9EE04A9659494E7E8E206CCED6A88F4A@AGB> From: "Graham" To: References: <505020E9D2554C49B4B4F7258CFCC3DD@White> <12FD30B2DFA24C5B8D9F376415614152@AGB> In-Reply-To: Date: Thu, 19 Sep 2013 16:49:00 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 14.0.8117.416 X-MimeOLE: Produced By Microsoft MimeOLE V14.0.8117.416 X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: op32 from last night G, VO1NA W1TAG 2200m OPERA 1604 kms 09:11:56 VO1NA W1VD 2200m OPERA 1724 kms 09:11:56 VO1NA TF3HZ 2200m OPERA 2601 kms 07:00:10 VO1NA G4WGT 2200m OPERA 3519 kms 04:15:32 [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [80.12.242.68 listed in list.dnswl.org] X-Scan-Signature: 8ef270cc2ec30cd34b6313d7ada17a45 Subject: Re: LF: VO1NA Op-32 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response 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 Status: O X-Status: X-Keywords: X-UID: 3236 op32 from last night G, VO1NA W1TAG 2200m OPERA 1604 kms 09:11:56 VO1NA W1VD 2200m OPERA 1724 kms 09:11:56 VO1NA TF3HZ 2200m OPERA 2601 kms 07:00:10 VO1NA G4WGT 2200m OPERA 3519 kms 04:15:32 -------------------------------------------------- From: Sent: Wednesday, September 18, 2013 11:49 PM To: "Graham" Cc: Subject: Re: LF: VO1NA Op-32 > Hi Graham and Markus, > > It's a relief to learn that the TX has drifted off QRG! Thanks Markus. > Will continue with OP32 tonight. > > Graham, to make OP8 from 32, just divide by 4, right? (8192/4 ms pulses) > And will it be OK to stay on 137.555 as 650 seems a bit congested? > > 73 to all > Joe > > On Wed, 18 Sep 2013, Graham wrote: > >> Thanks for that Markus >> >> That info could be gathered at the RX stations and shared via >> the web beacon , but would only be of use is the 'audio' tx >> drive was used .. >> >> For such a short tx time , 4 mins of 'carrier' and anything over >> 2 mins needed for a decode , OP8 seems to be producing some >> very good results , unless there is some 'flutter' , which the >> shorter cycle is able to make use of ? if nothing else , the >> power bill is 25% of op32 ! >> >> W1VD is also showing on the PSK map , Gus is running higher >> power than at the start , so may be W1VD is in range ? >> >> 73-G, >> >> >> From: Markus Vester >> Sent: Wednesday, September 18, 2013 9:15 PM >> To: rsgb_lf_group@blacksheep.org >> Subject: Re: LF: VO1NA Op-32 >> >> >> Yes op-8 would have been in easy reach. This morning, Joe's dashes were >> well discernible even in the 0.7 Hz grabber window. >> >> Having said that, my personal preference regarding overnight beaconing is >> more towards "the slower the better" ;-) In the morning I'd rather be >> greeted by 10 really deep detections than by a long list of spots with >> intermediate sensitivity. >> >> As for frequency, using 137650 exactly might not be ideal, as observers >> in East Europe would likely be affected by the Russian Loran / Chayka >> chain. Actually here in Central Europe the 6.25 Hz multiples reappeared >> today when Slonim (the most westerly station in the chain) came back on >> air after several weeks outage. Staying away from the Loran lines by a Hz >> or so will avoid that problem. >> >> Best 73, >> Markus (DF6NM) >> >> From: Graham >> Sent: Wednesday, September 18, 2013 5:36 PM >> To: rsgb_lf_group@blacksheep.org >> Subject: Re: LF: VO1NA Op-32 >> >> >> Joe, >> >> Looking at the psk-map , Its quite possible , all the monitors >> where >> looking for OP8 signals ve7bdq <> we2xpq is also showing as >> OP8 >> as well >> >> No reason why OP8 should not decode from you , just need to qsy >> to the OP8 centre qrg 137.650 KHz >> >> 73 -G, >> > > This electronic communication is governed by the terms and conditions at > http://www.mun.ca/cc/policies/electronic_communications_disclaimer_2012.php >