DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=rQsWMC0G97NnyRz6EDS9tY+2JUhkZYZa5Yhcc2R+f3AWjOtdD6D66zPVWwDb4V6Bzq
         scZ2p8Pdad6QxV5+BYlQoOBZCF4Xg0Ed0SoVLVDlrllxwm+qFIvEaAh6pVRh/J5tEs2a
         KYGUFHUMR7xAMosXxJ3ZA2Zu95zKp5p6NYhsk=
MIME-Version: 1.0
In-Reply-To: <D812D7F98DBA499EB733CCE0B5F71C49@JimPC>
References: <fc7eccec0909190406r6b596274h8e84feed93216356@mail.gmail.com>
	 <D812D7F98DBA499EB733CCE0B5F71C49@JimPC>
Date: Sat, 19 Sep 2009 13:17:03 +0100
Message-ID: <fc7eccec0909190517p374a2af8ne11dc361eed1326f@mail.gmail.com>
From: Andy Talbot <andy.g4jnt@googlemail.com>
To: rsgb_lf_group@blacksheep.org
DomainKey-Status: good (testing) 
Subject: Re: LF: Re: 'JNT Dual purpose beacons
Content-Type: multipart/alternative; boundary=001485f5e916f48ec60473ed39ff
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


--001485f5e916f48ec60473ed39ff
Content-Type: text/plain; charset=ISO-8859-1

hi Jim / group

Ok.   I've put it on air with some preliminary values.   The WSPR signal is
on 503.850kHz  and its running 6db down on the 15 minute beacon at 50% duty
cycle.  Teh hiuh duty cycle is for my local monitoring purposes - save
haviign to wait too long.

When its had a run at this setting, I can reduce the duty cycle a bit (the
S/W hasn't been tested at lower DCy yet) and could increase power a bit.
Don't really want to run at full power, mainly in the interest of longevity
of the PA and my leccy bill!

The WSPR slots are currently at  0,2,6,10,14,22,26,28,32,36,40,44,46,52,56
minutes past the hour, with the orther signal at 4,19,34,49 minutes past.

Any changes are just a case of reprogramming the PIC EE Data

Andy
www.g4jnt.com

this email has been scanned for political correctness by the nanny state


2009/9/19 James Moritz <james.moritz@btopenworld.com>

> Dear Andy,
>
> I would suggest a frequency between 503.825 and 503.900, to avoid the QRM
> around 504kHz some people experience, and give a bit of tolerance for
> receiver frequency errors, which are sometimes suprisingly large. For some
> reason, the frequencies below 503.9 seem to be less widely used. But since
> there are only about half a dozen stations transmitting in this mode, there
> is plenty of space.
>
> A 25% or 33% duty cycle seems to be frequent enough to catch most
> "openings" - probably less would be OK. As for power, I would suggest
> running as much as possible - monitoring signal level of a strong beacon  is
> easier than a weak one, and a relatively high power will give the greatest
> chance of being received by the maximum number of stations under the maximum
> range of conditions. You could argue that the presence of a "strong" beacon
> would sometimes prevent reception of very weak signals nearby in frequency,
> but since this only can happen 25% or 33% of the time, and the signal is not
> so strong at a few 100 mW ERP,  it is probably not a serious objection in
> practice.
>
> Cheers, Jim Moritz
> 73 de M0BMU
>
>

--001485f5e916f48ec60473ed39ff
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>hi Jim / group</div>
<div>=A0</div>
<div>Ok.=A0=A0 I&#39;ve=A0put it on air with some preliminary values.=A0=
=A0=A0The WSPR signal is on=A0503.850kHz=A0 and its running 6db down on th=
e 15 minute beacon at 50% duty cycle.=A0 Teh hiuh duty cycle is for my loc=
al monitoring purposes - save haviign to wait too long.</div>

<div>=A0</div>
<div>When its had a run at this setting, I=A0can reduce the duty cycle a=
 bit (the S/W hasn&#39;t been tested at lower DCy yet) and could increase=
 power a bit.=A0 Don&#39;t really want to run at full power, mainly in the=
 interest of longevity of the PA and my leccy bill!</div>

<div>=A0</div>
<div>The WSPR slots are currently at=A0 0,2,6,10,14,22,26,28,32,36,40,44,4=
6,52,56=A0=A0 minutes past the hour, with the orther signal at 4,19,34,49=
 minutes past.</div>
<div>=A0</div>
<div>Any changes are just a case of reprogramming the PIC EE Data</div>
<div><br clear=3D"all">Andy<br><a href=3D"http://www.g4jnt.com">www.g4jnt.=
com</a><br><br>this email has been scanned for political correctness by th=
e nanny state<br><br><br></div>
<div class=3D"gmail_quote">2009/9/19 James Moritz <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:james.moritz@btopenworld.com">james.moritz@btopenworld.com=
</a>&gt;</span><br>
<blockquote style=3D"BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8e=
x; PADDING-LEFT: 1ex" class=3D"gmail_quote">Dear Andy,<br><br>I would sugg=
est a frequency between 503.825 and 503.900, to avoid the QRM around 504kH=
z some people experience, and give a bit of tolerance for receiver frequen=
cy errors, which are sometimes suprisingly large. For some reason, the fre=
quencies below 503.9 seem to be less widely used. But since there are only=
 about half a dozen stations transmitting in this mode, there is plenty of=
 space.<br>
<br>A 25% or 33% duty cycle seems to be frequent enough to catch most &quo=
t;openings&quot; - probably less would be OK. As for power, I would sugges=
t running as much as possible - monitoring signal level of a strong beacon=
 =A0is easier than a weak one, and a relatively high power will give the=
 greatest chance of being received by the maximum number of stations under=
 the maximum range of conditions. You could argue that the presence of a=
 &quot;strong&quot; beacon would sometimes prevent reception of very weak=
 signals nearby in frequency, but since this only can happen 25% or 33% of=
 the time, and the signal is not so strong at a few 100 mW ERP, =A0it is=
 probably not a serious objection in practice.<br>
<br>Cheers, Jim Moritz<br>73 de M0BMU <br><br></blockquote></div><br>

--001485f5e916f48ec60473ed39ff--