Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dh01.r1000.mx.aol.com (Internet Inbound) with ESMTP id 0BEC138000193; Tue, 30 Apr 2013 18:21:53 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UXIuw-00077r-Ho for rs_out_1@blacksheep.org; Tue, 30 Apr 2013 23:20:58 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UXIuv-00077i-Up for rsgb_lf_group@blacksheep.org; Tue, 30 Apr 2013 23:20:57 +0100 Received: from smtpout1.wanadoo.co.uk ([80.12.242.29] helo=smtpout.wanadoo.co.uk) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UXIuq-0002wi-J4 for rsgb_lf_group@blacksheep.org; Tue, 30 Apr 2013 23:20:56 +0100 Received: from AGB ([2.26.30.10]) by mwinf5d05 with ME id WNLX1l0070D5rMe03NLXKc; Wed, 01 May 2013 00:20:32 +0200 Message-ID: From: "Graham" To: References: <30B51BE26CE840C199634AB5473A3506@Black> In-Reply-To: <30B51BE26CE840C199634AB5473A3506@Black> Date: Tue, 30 Apr 2013 23:20:31 +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: Ok Markus , wspr is based 1500 Hz and OP4 1800 Hz the pass bands are not overlapping , this was the original 500 KHz configuration for some years , until the 'dash to the mid band' occurred shortly after the new band was allocated , [...] 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.29 listed in list.dnswl.org] 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: f9bb43a66658129469273581af35b296 Subject: Re: LF: Re: SUGGESTED TEMPORARY CHANGE TO [OPERA ] MF QRG Content-Type: multipart/alternative; boundary="----=_NextPart_000_00AE_01CE45F9.4EFD9D20" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.9 required=5.0 tests=HTML_30_40,HTML_MESSAGE, LINES_OF_YELLING,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: 3039ac1d4115518044012fe5 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none This is a multi-part message in MIME format. ------=_NextPart_000_00AE_01CE45F9.4EFD9D20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Ok Markus , wspr is based 1500 Hz and OP4 1800 Hz the pass bands are not = overlapping , this was the original 500 KHz configuration for = some years , until the 'dash to the mid band' occurred shortly = after the new band was allocated ,=20 When the software is used , the carrier placement is dictated by = the noise level within the pass band , in keeping with agile = frequency practice =20 Dual mode tx and monitoring was the normal situation=20 73 -Graham=20 From: Markus Vester=20 Sent: Tuesday, April 30, 2013 10:55 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: Re: SUGGESTED TEMPORARY CHANGE TO [OPERA ] MF QRG=20 Hi Graham, going by my experience with Op-32 correlation experiments on LF, I would = much rather have separate frequency bands for Op and WSPR. I also = believe that 100 Hz for Opera-32 is much wider than necessary (that's = 400 channels of 0.25 Hz bandwidth). It would be more economical and also = computationally efficient to restrict the range to say 25 Hz (similar to = WSPR-15). All this would be easier if the audio frequencies weren't hardcoded into = the Opera software. 73, Markus (DF6NM) ----- Original Message -----=20 From: Graham=20 To: rsgb_lf_group@blacksheep.org=20 Sent: Tuesday, April 30, 2013 11:26 PM Subject: LF: SUGGESTED TEMPORARY CHANGE TO [OPERA ] MF QRG=20 SUGGESTED TEMPORARY CHANGE TO MF QRG =20 Its proposed to drop the MF Opera operating QRG to 474.2 dial set = USB As it would appear , the WSPR qrg is not to move back to the = original 477 spot any time soon, to enable dual monitoring of = Opera and WSPR as was the original status , Opera tones being = arranged to fall out side the wspr pass band , the two modes = coexist on the same dial-set usb qrg=20 No change to the software is envisaged as an eventual return to = 477 is anticipated once any band planning is implemented, or = more normal use is made of the mid band.=20 The move was previously suggested, but not implemented to prevent = a clash with wspr-15 activity , which now appears to of subsided = . Where as it was unlikely to compromise the Opera decode engine , = it was evident from events that conversely wspr could of been = affected. =20 Comments any one ? Tnx- Graham ------=_NextPart_000_00AE_01CE45F9.4EFD9D20 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Ok Markus ,
 
wspr  is  based 1500  Hz and  OP4  =20 1800  Hz  the  pass  bands  are  not  = overlapping  , this  was the  original   500 = KHz =20 configuration  for  some  years   , = until =20 the  'dash to the  mid band'  occurred   = shortly =20 after the  new band was  allocated ,
 
When the  software  is  used , the  = carrier =20 placement  is   dictated by the  noise level =20 within  the  pass  band  , in keeping  with = agile=20 frequency practice 
 
Dual   mode  tx and  monitoring  was  = the  normal  situation
 
73 -Graham
 
 

Sent: Tuesday, April 30, 2013 10:55 PM
Subject: LF: Re: SUGGESTED TEMPORARY CHANGE TO [OPERA ] MF = QRG=20

Hi Graham,
 
going by my experience with = Op-32 correlation=20 experiments on LF, I would much rather have separate frequency = bands for Op=20 and WSPR. I also believe that 100 Hz for Opera-32 is much wider = than=20 necessary (that's 400 channels of 0.25 Hz bandwidth). It would be = more=20 economical and also computationally efficient to restrict = the=20 range to say 25 Hz (similar to WSPR-15).
 
All this would be easier if the audio = frequencies=20 weren't hardcoded into the Opera software.
 
73, Markus (DF6NM)
 
 
----- Original Message -----=20
From: Graham=20
Sent: Tuesday, April 30, 2013 11:26 PM
Subject: LF: SUGGESTED TEMPORARY CHANGE TO [OPERA ] MF QRG=20

SUGGESTED TEMPORARY   CHANGE TO MF   QRG  =
 
Its proposed to drop the MF Opera   operating   = QRG=20 to   474.2 dial set USB
 
As it  would  appear , the  WSPR   = qrg  is=20 not to  move  back to  the  original  477  = spot  any time  soon, to  enable   dual =20 monitoring  of  Opera and  WSPR  as was  = the =20 original  status , Opera tones being  arranged to  = fall  out=20 side the  wspr  pass  band , the  two  = modes =20 coexist on the  same  dial-set usb qrg
 
No  change to  the  software is  = envisaged =20 as  an  eventual  return to 477  is  = anticipated =20 once  any  band  planning  is  implemented, = or =20 more normal use  is made of the  mid  band.
 
The  move was  previously  suggested, = but =20 not  implemented  to  prevent a   clash =20 with  wspr-15   activity , which now appears to  = of =20 subsided .
 
Where  as  it was  unlikely  to  = compromise=20 the  Opera  decode  engine , it was evident from  = events=20 that  conversely  wspr  could  of  been = affected. =20
 
Comments   any one ?
 
Tnx- Graham
------=_NextPart_000_00AE_01CE45F9.4EFD9D20--