Message-ID: <FAE50C6CEA8D4C7892AD2386B1F4D041@IBM7FFA209F07C>
From: "Chris" <c.ashby435@btinternet.com>
To: "RSGB LF Group" <rsgb_lf_group@blacksheep.org>
Date: Mon, 11 Feb 2013 10:15:30 -0000
MIME-Version: 1.0
Subject: LF: 472kHz Bandplan or whatever
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0028_01CE0840.B8588060"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


This is a multi-part message in MIME format.

------=_NextPart_000_0028_01CE0840.B8588060
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Mal,
Re your comment:-
Those shouting most and expression opinions about LF and MF are never =
heard on the bands.=20
Surely equal weight should be given to the opinions of those who just =
listen or run QRP? I have been running 1W RF on the band since January, =
probably well below your RX threshold, and working a couple of 'locals' =
regularly. So my opinion doesn't count in your book?
Rik has come up with the most logical suggestion so far. We really do =
need some sort of organisation on the band, all be it of the 'light =
touch' variety.
My feeling (which apparently probably doesn't count) is, modes with long =
carriers should be near the band edges, ideally QRSS near the bottom and =
others near the top. Filters easily resolve the issue of QRSS being =
close to faster CW, as you, Mal, pointed out to me some years ago.
Criticising suggestions is all very well, but it would be better if such =
criticism was supported by reasoned argument or a better proposal.
On another point, someone commented about the 'Subject' in e-mails to =
this site. I entirely agree with what was said. Not only the mode under =
discussion, but it has been confusing sometimes in the past when the =
band is not specified either in the 'Subject', or even the content!
Vy 73,
Chris, G4AYT.
------=_NextPart_000_0028_01CE0840.B8588060
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META name=3DGENERATOR content=3D"MSHTML 8.00.6001.19394">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2 face=3DArial>Hi Mal,</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Re your comment:-</FONT></DIV>
<DIV><FONT face=3DArial>Those shouting most and expression opinions =
about LF and=20
MF are never heard on the bands. </FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Surely equal weight should be given to =
the opinions=20
of those who just listen or run QRP? I have been running 1W RF on the =
band since=20
January, probably well below your RX threshold, and working a couple of =
'locals'=20
regularly. So my opinion doesn't count in your book?</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Rik has come up with the most logical =
suggestion so=20
far. We really do need some sort of organisation on the band, all be it =
of the=20
'light touch' variety.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>My feeling (which apparently probably =
doesn't=20
count) is, modes with long carriers should be near the band edges, =
ideally QRSS=20
near the bottom and others near the top. Filters easily resolve the =
issue of=20
QRSS being close to faster CW, as you, Mal, pointed out to me some years =

ago.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Criticising suggestions is all very =
well, but it=20
would be better if such criticism was supported by reasoned argument or =
a better=20
proposal.</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>On another point, someone commented =
about the=20
'Subject' in e-mails to this site. I entirely agree with what was said. =
Not only=20
the mode under discussion, but it has been confusing sometimes in the =
past when=20
the band is not specified either in the 'Subject',&nbsp;or even&nbsp;the =

content!</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Vy 73,</FONT></DIV>
<DIV><FONT size=3D2 face=3DArial>Chris, =
G4AYT.</FONT></DIV></BODY></HTML>

------=_NextPart_000_0028_01CE0840.B8588060--