Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mh06.r1000.mx.aol.com (Internet Inbound) with ESMTP id 861C6380000B1; Fri, 15 Jun 2012 09:10:45 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1SfWHB-0002AO-72 for rs_out_1@blacksheep.org; Fri, 15 Jun 2012 14:09:21 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1SfWHA-0002AF-HV for rsgb_lf_group@blacksheep.org; Fri, 15 Jun 2012 14:09:20 +0100 Received: from out1.ip05ir2.opaltelecom.net ([62.24.128.241]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1SfWH8-0006BM-0v for rsgb_lf_group@blacksheep.org; Fri, 15 Jun 2012 14:09:19 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkkFAM8z209cF/7E/2dsb2JhbABFgkWiMJBdgQiCEwUBAQQJAQEDICEIAiEFBgEBCAIBAxEEAQEBCQwtAQQYAgYMCAIODwQBCQECAgEBAQsEh1wDBgkHsDcDiViLNoJqgycDiA+FNJEFhlmCYA X-IronPort-AV: E=Sophos;i="4.77,417,1336345200"; d="scan'208,217";a="384719295" Received: from host-92-23-254-196.as13285.net (HELO xphd97xgq27nyf) ([92.23.254.196]) by out1.ip05ir2.opaltelecom.net with SMTP; 15 Jun 2012 14:09:14 +0100 Message-ID: <002d01cd4af8$0f5620e0$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: "rsgb" Cc: Date: Fri, 15 Jun 2012 13:09:12 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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: I think some careful thought should go into the bandplanning to avoid a conflict of modes especially those that want to QSO as opposed to those unattended Beacon qrm generators in any mode. ie REPEATIVE CW, QRSS, OPERA and other data modes. also some countries might not get the full allocation and might need a different slot for their chosed mode. de G3KEV [...] 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 [62.24.128.241 listed in list.dnswl.org] 0.0 FSL_XM_419 Old OE version in X-Mailer only seen in 419 spam -0.0 SPF_PASS SPF: sender matches SPF record 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 FSL_UA FSL_UA 0.0 AXB_XMAILER_MIMEOLE_OL_024C2 AXB_XMAILER_MIMEOLE_OL_024C2 X-Scan-Signature: c1295c176f29281d31cecda7e6248180 Subject: LF: Fw: [rsgb_lf_group] Re: New Opera QRG for 472 Khz Band ? Content-Type: multipart/alternative; boundary="----=_NextPart_000_002A_01CD4AF8.0F0764A0" 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=HTML_60_70,HTML_MESSAGE 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-SCOLL-SCORE: 1:2:495122048:93952408 X-AOL-SCOLL-URL_COUNT: 8 x-aol-sid: 3039ac1d60da4fdb34541f9f 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_002A_01CD4AF8.0F0764A0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I think some careful thought should go into the bandplanning to avoid a = conflict of modes especially those that want to QSO as opposed to those = unattended Beacon qrm generators in any mode. ie REPEATIVE CW, QRSS, = OPERA and other data modes.=20 also some countries might not get the full allocation and might need a = different slot for their chosed mode. de G3KEV ----- Original Message -----=20 From: Mike Dennison=20 To: rsgb_lf_group@yahoogroups.co.uk=20 Sent: Friday, June 15, 2012 12:13 PM Subject: Re: [rsgb_lf_group] Re: New Opera QRG for 472 Khz Band ? =20 I agree there should be thought given to bandplanning. Where, for=20 instance, should I set my QRSS receiver? However, the band is 7kHz wide and the suggestion to "go 1k up may=20 be , 473 dial to give room for cw etc" would in fact give just 2.2kHz=20 of the band for what will presumably be the most popular mode.=20 Currently the two modes of the 500kHz version of Opera occupies from=20 1.2kHz to 1.8kHz above dial frequency. I think we need first to look at how much each mode might occupy. A=20 useful division might be 3.8kHz for CW, 0.2Hz for QRSS (perhaps in=20 two wide-spaced sub-bands) and 3kHz for all "data" (machine-read=20 modes including Opera). There is an argument that any mode involving=20 beacons (including some uses of QRSS and Opera) should be widely=20 separated from two-way QSOs. Lower bandwidth modes should be nearer the band edge. Perhaps 'DX'=20 modes should avoid the active NDB frequencies - say between 476 and=20 478kHz. Currently, it seems that Opera had a dial frequency of 500kHz, and=20 the 1.2kHz below it has some QRSS activity (eg IQ2MI). That sort of=20 arrangement may work on 472kHz provided the Opera allocaton does not=20 eventually migrate as it did on 137kHz. Perhaps in the short term there should be allocated (or at least=20 agreed) frequencies with an understanding by all that there will need=20 to be adjustments eventually. All food for thought. Mike, G3XDV =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Well , could set the lower band edge frequency , that fits in with > using USB, puts signal 1.4Khz inside the band .. or do we need to go > 1k up may be , 473 dial to give room for cw etc ? >=20 > G. >=20 > --- In rsgb_lf_group@yahoogroups.co.uk, Rik Strobbe > wrote: > > Either the upper or lower band end ? > > > > 73, Rik ON7YD > - OR7T > > > > ________________________________ > Van: > rsgb_lf_group@yahoogroups.co.uk [rsgb_lf_group@yahoogroups.co.uk] > namens graham787 [g0nbd@...] > Verzonden: vrijdag 15 juni 2012 2:13 > > Aan: rsgb_lf_group@yahoogroups.co.uk > Onderwerp: [rsgb_lf_group] New > Opera QRG for 472 Khz Band ? > > > > New QRG for 472 Khz Band > > > Suggestions needed for a QRG for the new 472 KHz band > Dial set USB > frequency , taking into account other band users ! > > Tnx - G > >=20 >=20 >=20 __._,_.___ Reply to sender | Reply to group | Reply via web post | Start a new = topic=20 Messages in this topic (4)=20 Recent Activity: a.. New Members 4=20 Visit Your Group=20 Switch to: Text-Only, Daily Digest . Unsubscribe . Terms of Use. =20 __,_._,___ ------=_NextPart_000_002A_01CD4AF8.0F0764A0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
I think some careful thought should go into the=20 bandplanning to avoid a conflict of modes especially those that want to = QSO as=20 opposed to those unattended Beacon qrm generators in any mode. ie = REPEATIVE=20 CW, QRSS, OPERA and other data modes. 
also some countries might not get the full = allocation and=20 might need a different slot for their chosed mode.
 de G3KEV
 
----- Original Message -----=20
From: Mike=20 Dennison
Sent: Friday, June 15, 2012 12:13 PM
Subject: Re: [rsgb_lf_group] Re: New Opera QRG for 472 Khz = Band=20 ?

  =

I agree there should be thought given to bandplanning. Where, for=20
instance, should I set my QRSS receiver?

However, the band is = 7kHz=20 wide and the suggestion to "go 1k up may
be , 473 dial to give room = for cw=20 etc" would in fact give just 2.2kHz
of the band for what will = presumably be=20 the most popular mode.
Currently the two modes of the 500kHz version = of=20 Opera occupies from
1.2kHz to 1.8kHz above dial frequency.

I = think we=20 need first to look at how much each mode might occupy. A
useful = division=20 might be 3.8kHz for CW, 0.2Hz for QRSS (perhaps in
two wide-spaced=20 sub-bands) and 3kHz for all "data" (machine-read
modes including = Opera).=20 There is an argument that any mode involving
beacons (including some = uses of=20 QRSS and Opera) should be widely
separated from two-way = QSOs.

Lower=20 bandwidth modes should be nearer the band edge. Perhaps 'DX'
modes = should=20 avoid the active NDB frequencies - say between 476 and=20
478kHz.

Currently, it seems that Opera had a dial frequency = of=20 500kHz, and
the 1.2kHz below it has some QRSS activity (eg IQ2MI). = That sort=20 of
arrangement may work on 472kHz provided the Opera allocaton does = not=20
eventually migrate as it did on 137kHz.

Perhaps in the short = term=20 there should be allocated (or at least
agreed) frequencies with an=20 understanding by all that there will need
to be adjustments=20 eventually.

All food for thought.
Mike,=20 G3XDV
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

> Well , could set = the lower band edge frequency=20 , that fits in with
> using USB, puts signal 1.4Khz inside the = band .. or=20 do we need to go
> 1k up may be , 473 dial to give room for cw etc = ?
>
> G.
>
> --- In rsgb_lf_group@yahoogrou= ps.co.uk,=20 Rik Strobbe <rik.strobbe@...>
> wrote: > > Either the = upper or=20 lower band end ? > > > > 73, Rik ON7YD
> - OR7T > = > >=20 > ________________________________ > Van:
> rsgb_lf_group@yahoogrou= ps.co.uk=20 [rsgb_lf_group@yahoogrou= ps.co.uk]
>=20 namens graham787 [g0nbd@...] > Verzonden: vrijdag 15 juni 2012 2:13=20 >
> Aan: rsgb_lf_group@yahoogrou= ps.co.uk=20 > Onderwerp: [rsgb_lf_group] New
> Opera QRG for 472 Khz Band ? = >=20 > > > New QRG for 472 Khz Band > >
> Suggestions = needed for=20 a QRG for the new 472 KHz band > Dial set USB
> frequency , = taking into=20 account other band users ! > > Tnx - G >
>
> =
>=20

__._,_.___
Rep= ly=20 to sender | group | Reply=20 via web post | Start=20 a new topic
Messages=20 in this topic (4) =
Recent=20 Activity:=20 New=20 Members 4 =
Visit=20 Your Group
=20
Switch to: Text-Only,=20 Daily=20 Digest =95 Unsubscribe=20 =95 Terms of = Use
.

__,_._,___
------=_NextPart_000_002A_01CD4AF8.0F0764A0--