Delivered-To: daveyxm@virginmedia.com Received: by 10.67.23.138 with SMTP id ia10csp268113pad; Wed, 18 Sep 2013 16:29:14 -0700 (PDT) X-Received: by 10.180.10.136 with SMTP id i8mr9179853wib.46.1379546951889; Wed, 18 Sep 2013 16:29:11 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id fb12si1929184wic.38.1969.12.31.16.00.00; Wed, 18 Sep 2013 16:29:11 -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 1VMQGF-0006IX-Nq for rs_out_1@blacksheep.org; Wed, 18 Sep 2013 23:30:15 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VMQGF-0006IO-1i for rsgb_lf_group@blacksheep.org; Wed, 18 Sep 2013 23:30:15 +0100 Received: from smtpout2.wanadoo.co.uk ([80.12.242.42] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1VMQGD-0008JY-1f for rsgb_lf_group@blacksheep.org; Wed, 18 Sep 2013 23:30:13 +0100 Received: from AGB ([2.31.70.107]) by mwinf5d30 with ME id SmW81m0042JsCfW03mW80t; Thu, 19 Sep 2013 00:30:11 +0200 Message-ID: From: "Graham" To: References: <505020E9D2554C49B4B4F7258CFCC3DD@White> <12FD30B2DFA24C5B8D9F376415614152@AGB> In-Reply-To: Date: Wed, 18 Sep 2013 23:30:07 +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: 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 ! [...] 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.42 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: 64bc660a83b79b15f4c44d2b2147e02d Subject: Re: LF: VO1NA Op-32 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001D_01CEB4C7.02CFAFA0" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,HTML_MESSAGE, 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: 3234 This is a multi-part message in MIME format. ------=_NextPart_000_001D_01CEB4C7.02CFAFA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Thanks for that Markus=20 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 ..=20 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,=20 From: Markus Vester=20 Sent: Wednesday, September 18, 2013 9:15 PM To: rsgb_lf_group@blacksheep.org=20 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.=20 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=20 Sent: Wednesday, September 18, 2013 5:36 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: VO1NA Op-32 Joe, Looking at the psk-map , Its quite possible , all the monitors = where=20 looking for OP8 signals ve7bdq <> we2xpq is also showing as = OP8=20 as well No reason why OP8 should not decode from you , just need to = qsy=20 to the OP8 centre qrg 137.650 KHz 73 -G, ------=_NextPart_000_001D_01CEB4C7.02CFAFA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Thanks  for  that  Markus
 
That  info  could be  gathered at the  = RX  =20 stations  and  shared  via the  web  beacon , = but =20 would  only  be of  use  is the  = 'audio'  =20 tx  drive  was  used  ..
 
For  such a short  tx time   , 4 mins  = of =20 'carrier'  and  anything  over  2  mins =20 needed  for  a  decode  , OP8  seems  = to =20 be  producing  some  very  good  results , = unless =20 there  is  some  'flutter'   , which the =20 shorter  cycle  is able  to  make  use of = ?  if=20 nothing  else  , the  power bill  is  25% = of =20 op32  !
 
W1VD is  also  showing  on the  PSK map =20 ,   Gus is  running  higher  power  = than  at=20 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= =20
Subject: Re: LF: VO1NA Op-32

Yes op-8 would have been in easy reach. = This=20 morning, Joe's dashes were well discernible even in the 0.7 Hz grabber = window.=20
 
Having said that, my personal=20 preference regarding overnight beaconing is more towards "the = slower the=20 better" ;-) In the morning I'd rather be greeted=20 by 10 really deep detections than by a long list of spots = with=20 intermediate sensitivity.
 
As for frequency, using 137650 = exactly might=20 not be ideal, as observers in East Europe would likely be affected = by the=20 Russian Loran / Chayka chain. Actually here in Central Europe the 6.25 = Hz=20 multiples reappeared today when Slonim (the most westerly station in the = chain) came back on air after several weeks outage. Staying = away from=20 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= =20
Subject: Re: LF: VO1NA Op-32

Joe,

Looking  at the  = psk-map =20 , Its  quite possible  , all the  monitors  where=20
looking  for  OP8   signals   = ve7bdq =20 <> we2xpq   is also  showing as  OP8
as=20 well

No reason  why OP8 should not  decode  = from =20 you  ,  just  need  to   qsy
to =20 the  OP8 centre   qrg   137.650 KHz

73=20 -G,
------=_NextPart_000_001D_01CEB4C7.02CFAFA0--