Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-db04.r1000.mx.aol.com (Internet Inbound) with ESMTP id 6D76238000085; Sat, 11 Aug 2012 18:51:40 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1T0KWE-0001Jj-HB for rs_out_1@blacksheep.org; Sat, 11 Aug 2012 23:50:54 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1T0KWE-0001Ja-2l for rsgb_lf_group@blacksheep.org; Sat, 11 Aug 2012 23:50:54 +0100 Received: from smtpout3.wanadoo.co.uk ([80.12.242.59] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1T0KWB-00068O-VN for rsgb_lf_group@blacksheep.org; Sat, 11 Aug 2012 23:50:52 +0100 Received: from AGB ([2.26.22.67]) by mwinf5d42 with ME id laqq1j00A1Sqkyi03aqqar; Sun, 12 Aug 2012 00:50:51 +0200 Message-ID: <197CA7A463F8408C89D9838A879134C3@AGB> From: "Graham" To: References: <50267F73.16960.E363EA@mike.dennison.ntlworld.com>, <50268A99.29543.10EEFCD@mike.dennison.ntlworld.com> <4C180ADA69F743CF964FC9EDBB58AA20@AGB> <5026C4D0.9040206@iup.uni-heidelberg.de> In-Reply-To: <5026C4D0.9040206@iup.uni-heidelberg.de> Date: Sat, 11 Aug 2012 23:50:50 +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: ''to need endless for one decode! 32 minutes is not endless'' ......? Of course , a pixel is one thing , the full call is the other :) what we can see is , not all the pixels show all the time , I think is is predicted by Mr S law's of propagation ? , so as to the call this is open to debate :( [...] 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.59 listed in list.dnswl.org] X-Scan-Signature: ead411ce91f9601ce3974c7575797436 Subject: Re: LF: Op32 tonight on 137kHz Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit 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: 3039ac1d40585026e1fb6ad4 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none ''to need endless for one decode! 32 minutes is not endless'' ......? Of course , a pixel is one thing , the full call is the other :) what we can see is , not all the pixels show all the time , I think is is predicted by Mr S law's of propagation ? , so as to the call this is open to debate :( The OP mode is a data mode , running in single pass and can make use of fast qsb/ripple Yes 32 is a long time , but we think is the lowest s/n single pass data move available for use at the moment another 5 or 6 db could be gained from fsk / psk modulation , but then , that puts it outside the user group OP32 at -40 dB s/n offers the best possible range for the 'average' 136 station , and the possibility of ''extended'' range for the slightly larger installations :)) Hopefully the long range monitors are running Rx OP8 and OP32 , I see Mike has just started sending OP32 at 100% cycle .. 73 -G.. DK7FC RD4HU 2200m OPERA 2907 kms 21:36:57 -------------------------------------------------- From: "Stefan Schäfer" Sent: Saturday, August 11, 2012 9:47 PM To: Subject: Re: LF: Op32 tonight on 137kHz > G.., > > OP32 appear to need endless for one decode! 32 minutes is not endless and > transmitting a call in QRSS-60 takes even longer but when i start > transmitting in QRSS-60 it takes not longer than 1 minute until i see it > on the YO/4X1RF grabber... > > BTW the OE3GHB grabber is back! http://members.aon.at/grabber/ > > Tonite there are OP8 and OP32 decodes. I will also TX in OP8 since this is > faster... Confusing. > > 73, Stefan > > Am 11.08.2012 18:18, schrieb Graham: >> Ok Mike >> >> TF3HZ is showing OP32 at the moment along with some in the Moscow >> triangle , I think as long as your 3 Hz apart, then each will decode , >> so that should not be a problem.. >> >> 73 -G.. >> >> >> -------------------------------------------------- >> From: "Mike Dennison" >> Sent: Saturday, August 11, 2012 4:38 PM >> To: >> Subject: Re: LF: Op32 tonight on 137kHz >> >>> Yes, 136.000kHz USB dial setting. I usually also specify my actual >>> transmit frequency in case another transmitting station wants to >>> avoid that frequency, or perhaps someone wants to look for me with >>> Argo or SpecLab. >>> >>> Mike, G3XDV >>> >>>> Mike >>>> >>>> Is that 136.000 KHz usb 'dial set' ? >>>> >>>> G.. >>>> >>>> -------------------------------------------------- >>>> From: "Mike Dennison" >>>> Sent: Saturday, August 11, 2012 3:51 PM >>>> To: ; >>>> Subject: LF: Op32 tonight on 137kHz >>>> >>>> > I will be transmitting an Opera32 beacon on 137.52kHz (136kHz dial) >>>> > overnight from around 2200UTC tonight until 0800 tomorrow morning. >>>> > >>>> > Mike, G3XDV >>>> > >>>> > >>>> >>> >>> >>> >>> >