Date: Thu, 22 Feb 2018 06:35:19 -0500
From: Markus Vester <markusvester@aol.com>
To: rsgb_lf_group@blacksheep.org
Message-Id: <161bd4bd6cb-647e-2207@webjas-vad080.srv.aolmail.net>
In-Reply-To: <5A8E8A7A.8020201@posteo.de>
MIME-Version: 1.0
Subject: Re: LF: K7PO testing 8270.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_10922_2140020037.1519299319499"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

------=_Part_10922_2140020037.1519299319499
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Compliments to Ward, Jay, as well as Mike and Paul. Great work!=20

As Stefan says, it may not always be easy to avoid subtle couplings from th=
e 1pps fed to one soundcard channel into the receive antenna circuitry on t=
he other channel. The problem is clearly visible on my 21 uHz spectrogram a=
t home. But a large 0.1 Hz offset would put you out of range of many alread=
y running grabbers, so I'd tend to stay within a couple of milliHz of 8270 =
Hz.

Best 73,
Markus =20


-----Urspr=C3=BCngliche Mitteilung-----=20
Von: DK7FC <selberdenken@posteo.de>
An: rsgb_lf_group <rsgb_lf_group@blacksheep.org>
Verschickt: Do, 22. Feb 2018 10:18
Betreff: Re: LF: K7PO testing 8270.0


Jay, Ward,=20

 Be careful, it could be that your GPS 1 PPS leaves a 'fence' of 1 Hz sideb=
ands in your signal stream, at least when looking deeply into the noise. To=
 avoid this, it is sometimes better to avoid transmitting on integer Hz fre=
quencies.

 Currently VO1NA is transmitting on 8270.0075 Hz.
 DK7FC is transmitting on 8270.1 Hz.
 Maybe it is helpful if Ward moves a bit away from 8270.000 Hz, e.g. 0.1 Hz=
 down, to avoid interferences from and to VO1NA. This way you can exclude t=
he eventuality that someone detects his own 1PPS signal instead of your car=
rier.

 73, Stefan

 Am 22.02.2018 05:33, schrieb jrusgrove@comcast.net:=20
#AOLMsgPart_2_27a92e30-e450-4c99-a420-ab4c87fbf2c4 td{color: black;} .aolRe=
placedBody { margin:0.7em; } .aolReplacedBody body.aolmail_OECFntDef,.aolRe=
placedBody body.aolmail_OECFntDef div { font-family:Arial,"Segoe UI",Tahoma=
,Verdana,Helvetica,sans-serif;font-size:10pt; }=20
Ward

=20

A later file produced a better Carrier S/N of 14.65 dB in 35.2 uHz. Daytime=
 files did not produce a decode of the carrier. =20

=20

Jay W1VD  WD2XNS  WE2XGR/2
------=_Part_10922_2140020037.1519299319499
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<div style=3D"font-size:10pt;font-family:arial,helvetica,sans-serif;color:b=
lack;"><div style=3D"color: black; font-family: arial,helvetica,sans-serif;=
 font-size: 10pt;">Compliments to Ward, Jay,&nbsp;as well as Mike and Paul.=
 Great work! <br><br>As Stefan says, it may not always be easy to&nbsp;avoi=
d subtle couplings from the 1pps&nbsp;fed to one soundcard channel into the=
 receive antenna&nbsp;circuitry on the other channel. The problem is clearl=
y visible on my 21 uHz spectrogram at home. But a large 0.1 Hz offset would=
 put you out of&nbsp;range of many already running grabbers, so&nbsp;I'd te=
nd to stay&nbsp;within a couple of&nbsp;milliHz&nbsp;of&nbsp;8270 Hz.<br><b=
r>Best 73,<br>Markus&nbsp;&nbsp;<br><br><br><br>-----Urspr=C3=BCngliche Mit=
teilung----- <br>Von: DK7FC &lt;selberdenken@posteo.de&gt;<br>An: rsgb_lf_g=
roup &lt;rsgb_lf_group@blacksheep.org&gt;<br>Verschickt: Do, 22. Feb 2018 1=
0:18<br>Betreff: Re: LF: K7PO testing 8270.0<br><br></div>
<div id=3D"AOLMsgPart_2_27a92e30-e450-4c99-a420-ab4c87fbf2c4">
<div class=3D"aolReplacedBody" text=3D"#000000" bgcolor=3D"#ffffff">
Jay, Ward, <br>
<br>
Be careful, it could be that your GPS 1 PPS leaves a 'fence' of 1 Hz
sidebands in your signal stream, at least when looking deeply into the
noise. To avoid this, it is sometimes better to avoid transmitting on
integer Hz frequencies.<br>
<br>
Currently VO1NA is transmitting on 8270.0075 Hz.<br>
DK7FC is transmitting on 8270.1 Hz.<br>
Maybe it is helpful if Ward moves a bit away from 8270.000 Hz, e.g. 0.1
Hz down, to avoid interferences from and to VO1NA. This way you can
exclude the eventuality that someone detects his own 1PPS signal
instead of your carrier.<br>
<br>
73, Stefan<br>
<br>
Am 22.02.2018 05:33, schrieb <a class=3D"aolmail_moz-txt-link-abbreviated" =
href=3D"mailto:jrusgrove@comcast.net:" target=3D"_blank" rel=3D"noopener no=
referrer">jrusgrove@comcast.net:</a>
<blockquote cite=3D"about:blank">
  <style type=3D"text/css">#AOLMsgPart_2_27a92e30-e450-4c99-a420-ab4c87fbf2=
c4 td{color: black;}  .aolReplacedBody   { margin:0.7em; } .aolReplacedBody=
 body.aolmail_OECFntDef,.aolReplacedBody  body.aolmail_OECFntDef div { font=
-family:Arial,"Segoe UI",Tahoma,Verdana,Helvetica,sans-serif;font-size:10pt=
; }</style>
 =20
  <div>Ward</div>
  <div>&nbsp;</div>
  <div>A later file produced a better Carrier S/N of 14.65 dB&nbsp;in 35.2
uHz. Daytime files&nbsp;did not produce a decode of&nbsp;the carrier. &nbsp=
;</div>
  <div>&nbsp;</div>
  <div>Jay W1VD&nbsp; WD2XNS&nbsp; WE2XGR/2</div>
</blockquote>


</div>
</div></div>
------=_Part_10922_2140020037.1519299319499--