Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp146594igb; Mon, 9 Dec 2013 10:15:29 -0800 (PST) X-Received: by 10.180.212.98 with SMTP id nj2mr15527069wic.52.1386612928047; Mon, 09 Dec 2013 10:15:28 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id ch1si1325612wib.55.2013.12.09.10.15.27 for ; Mon, 09 Dec 2013 10:15:28 -0800 (PST) Received-SPF: neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) client-ip=195.171.43.25; Authentication-Results: mx.google.com; spf=neutral (google.com: 195.171.43.25 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org) smtp.mail=owner-rsgb_lf_group@blacksheep.org Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Vq52r-0001ZV-QU for rs_out_1@blacksheep.org; Mon, 09 Dec 2013 17:55:01 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Vq52q-0001ZK-SL for rsgb_lf_group@blacksheep.org; Mon, 09 Dec 2013 17:55:00 +0000 Received: from blu0-omc1-s25.blu0.hotmail.com ([65.55.116.36]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1Vq52o-0006Ry-Cm for rsgb_lf_group@blacksheep.org; Mon, 09 Dec 2013 17:54:59 +0000 Received: from BLU180-W56 ([65.55.116.9]) by blu0-omc1-s25.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 9 Dec 2013 09:54:56 -0800 X-TMN: [3Vh0jDtiBN6J7jFBEQ15f5Wd12FPWDg0] X-Originating-Email: [rjraide@hotmail.com] Message-ID: From: Bob Raide To: "rsgb_lf_group@blacksheep.org" Date: Mon, 9 Dec 2013 12:54:56 -0500 Importance: Normal In-Reply-To: <52A600A7.1060906@iup.uni-heidelberg.de> References: <2504E90AEBE5469E956314C7151BF777@White> <8D0C2E6EC29A51B-1A78-495@webmail-m255.sysops.aol.com>,<52A600A7.1060906@iup.uni-heidelberg.de> MIME-Version: 1.0 X-OriginalArrivalTime: 09 Dec 2013 17:54:56.0948 (UTC) FILETIME=[C59FBF40:01CEF507] 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: Congrats to you Stefan! That is one long haul for LF and multi-decodes to boot-73, Bob Date: Mon, 9 Dec 2013 18:40:55 +0100 From: Re: LF: 74550 - opds-64 Markus, Bob, [...] 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 [65.55.116.36 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (rjraide[at]hotmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message X-Scan-Signature: ce481d129b1a7277ee248e941d6e5100 Content-Type: multipart/alternative; boundary="_3e39ab3f-16c4-4385-a7ac-374a9718e991_" Subject: RE: LF: 74550 - opds-64 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.8 required=5.0 tests=FORGED_HOTMAIL_RCVD,HTML_30_40, HTML_MESSAGE,TO_ADDRESS_EQ_REAL 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 Status: O X-Status: X-Keywords: X-UID: 1344 --_3e39ab3f-16c4-4385-a7ac-374a9718e991_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Congrats to you Stefan! That is one long haul for LF and multi-decodes to = boot-73=2C Bob =20 Date: Mon=2C 9 Dec 2013 18:40:55 +0100 From: Stefan.Schaefer@iup.uni-heidelberg.de To: rsgb_lf_group@blacksheep.org Subject: Re: LF: 74550 - opds-64 =0A= =0A= =0A= =0A= =0A= =0A= Markus=2C Bob=2C=20 =0A= =0A= Congrats to that success! It's a remarkable distance for that band and=0A= in a digital mode!! =0A= Keep up the work! =0A= =0A= 73=2C Stefan/DK7FC =0A= =0A= Am 09.12.2013 12:14=2C schrieb Markus Vester:=0A= =0A= Hi Bob=2C=0A= LF=2C=0A= =0A= I am=0A= very pleased to find that your Opera-64 signal produced five=0A= correlation detections here last night. In the attached spectrogram=2C=0A= the symmetrical Opera modulation sidebands are clearly visible between=0A= the many DCF-77 interference lines. =0A= =0A= Unfortunately=0A= the timestamps from SpecLab temporarily suffered from an unexplained=0A= offset=2C affecting both the spectrogram and the exported spectrum data.=0A= Such transient errors have also happened to other slow SpecLab=0A= instances=2C eg. 8.97 kHz - sometime after startup=2C time seems to=0A= spontaneously jump back=2C and suddenly comes back to normal after a few=0A= hours. In this case=2C timestamps were found to be exactly 5h 46m 4s=0A= early=2C allowing to derive corrected spot times (appended to the end of=0A= the lines here):=0A= =0A= =0A= date time call distance frequency bandwidth snr =0A= correlation =0A= 2013-12-09 07:53:55 WG2XRS 6448km 74549.500Hz 1mHz -49.5dBOp 95%=0A= 15.6dB =0A= 2013-12-09 05:42:27 WG2XRS 6448km 74549.500Hz 1mHz -47.3dBOp 82%=0A= 16.7dB =0A= 2013-12-09 04:36:41 WG2XRS 6448km 74549.500Hz 1mHz -44.4dBOp 100%=0A= 19.6dB =0A= 2013-12-08 22:50:39 WG2XRS 6448km 74549.500Hz 1mHz -45.2dBOp 91%=0A= 19.1dB 04:36:43 (same transmission as above) =0A= 2013-12-08 21:44:53 WG2XRS 6448km 74549.500Hz 1mHz -41.8dBOp 92%=0A= 19.3dB 03:30:57 =0A= 2013-12-08 20:39:07 WG2XRS 6448km 74549.500Hz 1mHz -49.2dBOp 98%=0A= 16.1dB 02:25:11=0A= =0A= The=0A= grass is always greener on the other side... Regarding the choice of=0A= frequency=2C the high resolution spectrogram seems to confirm the gap in=0A= the DCF77 interference around 74552.0 Hz. So Bob=2C Dex and others may=0A= consider moving up there=2C further reducing the QRM for other observers=0A= (eg. Hartmut) as well.=0A= =0A= My=0A= understanding is that Opera's 28 bit payload can encode six character=0A= callsigns=2C but no extra appendix. This would result in ambiguities if=0A= several WG2XGR/n stations were transmitting simultaneously. As a simple=0A= workaround=2C I would suggest to replace the number "2" by the number=0A= from the appendix=2C eg. just use WG4XGR instead of WG2XGR/4 etc. One=0A= could argue that "sending the wrong callsign" might be considered=0A= illegal. But it would be unabiguous=2C and we could publicly announce it=0A= as an appropriate extension of the Opera encoding scheme.=0A= =0A= Best=0A= 73=2C =0A= Markus (DF6NM) =0A= =0A= =20 =0A= =0A= -----Urspr=FCngliche Mitteilung-----=20 =0A= Von: Markus Vester =0A= An: rsgb_lf_group =0A= Verschickt: So=2C 8 Dez 2013 11:05 pm =0A= Betreff: Re: LF: 74550 - opds-64 =0A= =20 =0A= =0A= =0A= =0A= Regarding opds-64 (or 65?) setup=2C I=0A= had forgotten to mention two more lines to be edited in opds.ini:=0A= opspeed=3D64 ' speed definition =0A= spotdelay=3D58 ' same timestamp offset as from Opera=0A= =0A= In Graham's words=2C there's really a=0A= whole "cactus" of spikes in the 238 =B5Hz spectrum. Most are on a 16.67=0A= mHz raster=2C because large parts of the BCD time-message from DCF77 are=0A= repeating every minute. I have now recalibrated the frequency scale=2C=0A= and restricted the opds search range from 74548.1 to 74550.0 Hz. =0A= =0A= Anyway given the QRSS levels from=0A= Bob last night I am quite optimistic.=0A= =0A= Best 73=2C =0A= Markus (DF6NM)=0A= =0A= =0A= =20 =0A= =0A= =0A= From: Markus=0A= Vester =0A= Sent: Sunday=2C December 08=2C 2013 8:40 PM=0A= To: rsgb_lf_group@blacksheep.org=0A= =0A= Subject: LF: 74550=0A= =0A= =0A= =20 =0A= =0A= ...=0A= For the night to come=2C I'm set up=0A= for monitoring opds-64 in a 4 Hz slot around 74.55 kHz=2C and will be=0A= uploading screenshots and possible detections to the usual opds grabber=0A= http://dl.dropboxusercontent.com/u/26404526/opds.htm =0A= In case others want to try: SpecLab=0A= FFT settings can be similar to opds-32 but more decimation is needed=0A= for half bandwidth (0.238 mHz). In opds.ini=2C center frequency and decimat= ion should be edited: fc=3D74550=2C dec=3D50331648=0A= .=0A= =0A= Best 73=2C=0A= Markus (DF6NM)=0A= =0A= =0A= =0A= =0A= =0A= =0A= = --_3e39ab3f-16c4-4385-a7ac-374a9718e991_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Congrats to you Stefan! =3B = That is one long haul =3Bfor LF and multi-decodes to boot-73=2C Bob
=  =3B
Date: Mon=2C 9 Dec 2013 18:40:55 += 0100
From: Stefan.Schaefer@iup.uni-heidelberg.de
To: rsgb_lf_group@bl= acksheep.org
Subject: Re: LF: 74550 - opds-64

=0A= =0A= =0A= =0A= =0A= =0A= Markus=2C Bob=2C
=0A=
=0A= Congrats to that success! It's a remarkable distance for that band and=0A= in a digital mode!!
=0A= Keep up the work!
=0A=
=0A= 73=2C Stefan/DK7FC
=0A=
=0A= Am 09.12.2013 12:14=2C schrieb Markus Vester:=0A=
=0A=
<= span style=3D"display: inline-block=3B">Hi Bob=2C=0A= LF=2C
=0A=
&= nbsp=3B
=0A=
I= am=0A= very pleased to find that your Opera-64 signal produced five=0A= correlation detections here last night. In the attached spectrogram=2C=0A= the symmetrical Opera modulation sidebands are clearly visible between=0A= the many DCF-77 interference lines.
=0A=
&= nbsp=3B
=0A=
U= nfortunately=0A= the timestamps from SpecLab temporarily suffered from an unexplained=0A= offset=2C affecting both the spectrogram and the exported spectrum data.=0A= Such transient errors have also happened to other slow SpecLab=0A= instances=2C eg. 8.97 kHz - sometime after startup=2C time seems to=0A= spontaneously jump back=2C and suddenly comes back to normal after a few=0A= hours. In this case=2C timestamps were found to be exactly 5h 46m 4s=0A= early=2C allowing to derive corrected spot times (appended to the end of=0A= the lines here):
=0A=
&= nbsp=3B
=0A=
&= nbsp=3B =3B=0A= date =3B =3B =3B =3B =3B time =3B =3B call = =3B =3B distance =3B frequency bandwidth =3B snr =3B = =3B =3B=0A= correlation
=0A= 2013-12-09 07:53:55 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -49.5dBOp =3B 95%=0A= 15.6dB
=0A= 2013-12-09 05:42:27 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -47.3dBOp =3B 82%=0A= 16.7dB
=0A= 2013-12-09 04:36:41 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -44.4dBOp 100%=0A= 19.6dB
=0A= 2013-12-08 22:50:39 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -45.2dBOp =3B 91%=0A= 19.1dB =3B 04:36:43 (same transmission as above)
=0A= 2013-12-08 21:44:53 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -41.8dBOp =3B 92%=0A= 19.3dB =3B 03:30:57
=0A= 2013-12-08 20:39:07 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -49.2dBOp =3B 98%=0A= 16.1dB =3B 02:25:11
=0A=
&= nbsp=3B
=0A=
T= he=0A= grass is always greener on the other side... Regarding the choice of=0A= frequency=2C the high resolution spectrogram seems to confirm the gap in=0A= the DCF77 interference around 74552.0 Hz. So Bob=2C Dex and others may=0A= consider moving up there=2C further reducing the QRM for other observers=0A= (eg. Hartmut) as well.
=0A=
&= nbsp=3B
=0A=
M= y=0A= understanding is that Opera's 28 bit payload can encode six character=0A= callsigns=2C but no extra appendix. This would result in ambiguities if=0A= several WG2XGR/n stations were transmitting simultaneously. As a simple=0A= workaround=2C I would suggest to replace the number "2" by the number=0A= from the appendix=2C eg. just use WG4XGR instead of WG2XGR/4 etc. One=0A= could argue that "sending the wrong callsign" might be considered=0A= illegal. But it would be unabiguous=2C and we could publicly announce it=0A= as an appropriate extension of the Opera encoding scheme.
=0A=
&= nbsp=3B
=0A=
B= est=0A= 73=2C
=0A= Markus (DF6NM)
=0A=
=0A=

=0A=
=0A=
-----Urspr=FCngliche Mitteilung-----
=0A= Von: Markus Vester <=3Bmarkusvester@aol.com>=3B
=0A= An: rsgb_lf_group <=3Brsgb_lf_group@blacksheep.org>=3B
= =0A= Verschickt: So=2C 8 Dez 2013 11:05 pm
=0A= Betreff: Re: LF: 74550 - opds-64
=0A=
=0A=
=0A=
=0A=
=0A=
Regarding opds-64 (or 65?) setup=2C = I=0A= had forgotten to mention two more lines to be edited in opds.ini:=0A=
 =3Bopspeed=3D64 =3B =3B=  =3B' speed definition
=0A=  =3Bspotdelay=3D58 =3B ' =3Bsame timestamp offset =3Bas fro= m Opera
=0A=
 =3B
=0A=
In =3BGraham's words=2C there's = really a=0A= whole "cactus" of spikes =3Bin the =3B238 =B5Hz spectrum. =3BMo= st are on a 16.67=0A= mHz raster=2C because large parts of =3Bthe BCD time-message from DCF77= are=0A= repeating =3Bevery minute. I have now recalibrated the frequency scale= =2C=0A= and restricted the opds search range from 74548.1 =3Bto 74550.0 Hz.
=0A=
 =3B
=0A=
Anyway given the QRSS levels from=0A= Bob last night I am quite optimistic.
=0A=
 =3B
=0A=
Best 73=2C
=0A=
Markus (DF6NM)
=0A=
 =3B
=0A=
=0A=

=0A=
=0A=
=0A= =0A=
Sent: Sunday=2C December 08=2C 2013 8:40 PM
=0A= =0A=
Subject: LF: 74550
=0A=
=0A=
=0A=

=0A=
=0A=
...
=0A=
For the night to come=2C I'm set up= =0A= for monitoring =3Bopds-64 in a 4 Hz slot around 74.55 kHz=2C and will b= e=0A= uploading screenshots and possible detections to the usual opds grabber=0A= http://dl.dropboxusercontent.com/u/26404526/opds.htm
=0A=
In case others =3Bwant to try: S= pecLab=0A= FFT settings can be =3Bsimilar to =3Bopds-32 but more decimation is= needed=0A= for half bandwidth (0.238 mHz). =3BIn opds.ini=2C =3Bcenter frequen= cy =3Band decimation should be e= dited: =3Bfc=3D74550=2C =3B<= /font>dec=3D50331648=0A= .
=0A=
 =3B
=0A=
Best 73=2C
=0A=
Markus (DF6NM)
=0A=
 =3B
=0A=
=0A=
 =3B
=0A=
=0A=
=0A=
=0A=
= --_3e39ab3f-16c4-4385-a7ac-374a9718e991_--