Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp132741igb; Mon, 9 Dec 2013 07:37:15 -0800 (PST) X-Received: by 10.180.78.165 with SMTP id c5mr14937929wix.3.1386603432223; Mon, 09 Dec 2013 07:37:12 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id kq2si4815957wjc.87.2013.12.09.07.37.11 for ; Mon, 09 Dec 2013 07:37:12 -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 1Vq2QY-0000sP-21 for rs_out_1@blacksheep.org; Mon, 09 Dec 2013 15:07:18 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Vq2QX-0000sG-6V for rsgb_lf_group@blacksheep.org; Mon, 09 Dec 2013 15:07:17 +0000 Received: from blu0-omc1-s5.blu0.hotmail.com ([65.55.116.16]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1Vq2QU-0005b9-H5 for rsgb_lf_group@blacksheep.org; Mon, 09 Dec 2013 15:07:16 +0000 Received: from BLU180-W22 ([65.55.116.8]) by blu0-omc1-s5.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 9 Dec 2013 07:07:13 -0800 X-TMN: [Av4RYx5P+/CHj9cuvbQgmejVs3FFunY/] X-Originating-Email: [rjraide@hotmail.com] Message-ID: From: Bob Raide To: "rsgb_lf_group@blacksheep.org" Date: Mon, 9 Dec 2013 10:07:13 -0500 Importance: Normal In-Reply-To: <8D0C2E6EC29A51B-1A78-495@webmail-m255.sysops.aol.com> References: <2504E90AEBE5469E956314C7151BF777@White>,<8D0C2E6EC29A51B-1A78-495@webmail-m255.sysops.aol.com> MIME-Version: 1.0 X-OriginalArrivalTime: 09 Dec 2013 15:07:13.0484 (UTC) FILETIME=[575500C0:01CEF4F0] 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: Markus; All your hard work certainly paid off! OPDS modes have made a big difference and congrats to Stefan who made more than one Europe-S America decodes. As for call signs, we had to do that with WSPR modes as well at first-it worked out well. Hopefully there is more than just one good freq to work with on or about 74.5520? For now you might give Dex and me a couple of freqs 1 HZ apart or so and we can try them tonight. Would you prefer to continue with the slower OPDS64 or try to get opds32 to work? 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.16 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: 6d05203b0dc31085ea7fa8b214773e41 Content-Type: multipart/alternative; boundary="_aa9cdcec-0afa-44a4-9257-22e92d9fea9f_" 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.9 required=5.0 tests=FORGED_HOTMAIL_RCVD,HTML_30_40, HTML_FONTCOLOR_UNKNOWN,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: 1342 --_aa9cdcec-0afa-44a4-9257-22e92d9fea9f_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Markus=3B All your hard work certainly paid off! OPDS modes have made a big differen= ce and congrats to Stefan who made more than one Europe-S America decodes. As for call signs=2C we had to do that with WSPR modes as well at first-it = worked out well. Hopefully there is more than just one good freq to work with on or about 7= 4.5520? For now you might give Dex and me a couple of freqs 1 HZ apart or = so and we can try them tonight. =20 Would you prefer to continue with the slower OPDS64 or try to get opds32 to= work? Bob =20 To: rsgb_lf_group@blacksheep.org From: markusvester@aol.com Date: Mon=2C 9 Dec 2013 06:14:12 -0500 Subject: Re: LF: 74550 - opds-64 =0A= Hi Bob=2C LF=2C=0A= =0A= =0A= =0A= =0A= =0A= I am very pleased to find that your Opera-64 signal produced five correlati= on detections here last night. In the attached spectrogram=2C the symmetric= al Opera modulation sidebands are clearly visible between the many DCF-77 i= nterference lines. =0A= =0A= =0A= =0A= =0A= =0A= Unfortunately the timestamps from SpecLab temporarily suffered from an unex= plained offset=2C affecting both the spectrogram and the exported spectrum = data. Such transient errors have also happened to other slow SpecLab instan= ces=2C eg. 8.97 kHz - sometime after startup=2C time seems to spontaneously= jump back=2C and suddenly comes back to normal after a few hours. In this = case=2C timestamps were found to be exactly 5h 46m 4s early=2C allowing to = derive corrected spot times (appended to the end of the lines here):=0A= =0A= =0A= =0A= =0A= =0A= date time call distance frequency bandwidth snr correlatio= n =0A= 2013-12-09 07:53:55 WG2XRS 6448km 74549.500Hz 1mHz -49.5dBOp 95% 15.6d= B =0A= 2013-12-09 05:42:27 WG2XRS 6448km 74549.500Hz 1mHz -47.3dBOp 82% 16.7d= B =0A= 2013-12-09 04:36:41 WG2XRS 6448km 74549.500Hz 1mHz -44.4dBOp 100% 19.6d= B =0A= 2013-12-08 22:50:39 WG2XRS 6448km 74549.500Hz 1mHz -45.2dBOp 91% 19.1d= B 04:36:43 (same transmission as above) =0A= 2013-12-08 21:44:53 WG2XRS 6448km 74549.500Hz 1mHz -41.8dBOp 92% 19.3d= B 03:30:57 =0A= 2013-12-08 20:39:07 WG2XRS 6448km 74549.500Hz 1mHz -49.2dBOp 98% 16.1d= B 02:25:11=0A= =0A= =0A= =0A= =0A= =0A= The grass is always greener on the other side... Regarding the choice of fr= equency=2C the high resolution spectrogram seems to confirm the gap in the = DCF77 interference around 74552.0 Hz. So Bob=2C Dex and others may consider= moving up there=2C further reducing the QRM for other observers (eg. Hartm= ut) as well.=0A= =0A= =0A= =0A= =0A= =0A= My understanding is that Opera's 28 bit payload can encode six character ca= llsigns=2C but no extra appendix. This would result in ambiguities if sever= al WG2XGR/n stations were transmitting simultaneously. As a simple workarou= nd=2C I would suggest to replace the number "2" by the number from the appe= ndix=2C eg. just use WG4XGR instead of WG2XGR/4 etc. One could argue that "= sending the wrong callsign" might be considered illegal. But it would be un= abiguous=2C and we could publicly announce it as an appropriate extension o= f the Opera encoding scheme.=0A= =0A= =0A= =0A= =0A= =0A= Best 73=2C =0A= Markus (DF6NM) =0A= =0A= =0A= =0A= =0A= =0A= =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= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= Regarding opds-64 (or 65?) setup=2C I had forgotten to mention two more lin= es to be edited in opds.ini:=0A= =0A= =0A= opspeed=3D64 ' speed definition =0A= spotdelay=3D58 ' same timestamp offset as from Opera=0A= =0A= =0A= =0A= =0A= =0A= In Graham's words=2C there's really a whole "cactus" of spikes in the 238 = =B5Hz spectrum. Most are on a 16.67 mHz raster=2C because large parts of th= e BCD time-message from DCF77 are repeating every minute. I have now recali= brated the frequency scale=2C and restricted the opds search range from 745= 48.1 to 74550.0 Hz. =0A= =0A= =0A= =0A= =0A= =0A= Anyway given the QRSS levels from Bob last night I am quite optimistic.=0A= =0A= =0A= =0A= =0A= =0A= Best 73=2C =0A= =0A= =0A= Markus (DF6NM)=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= From: Markus Vester =0A= =0A= =0A= Sent: Sunday=2C December 08=2C 2013 8:40 PM=0A= =0A= =0A= To: rsgb_lf_group@blacksheep.org =0A= =0A= =0A= Subject: LF: 74550=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= ...=0A= =0A= =0A= For the night to come=2C I'm set up for monitoring opds-64 in a 4 Hz slot a= round 74.55 kHz=2C and will be uploading screenshots and possible detection= s to the usual opds grabber http://dl.dropboxusercontent.com/u/26404526/opd= s.htm =0A= =0A= =0A= In case others want to try: SpecLab FFT settings can be similar to opds-32 = but more decimation is needed for half bandwidth (0.238 mHz). In opds.ini= =2C center frequency and decimation should be edited: fc=3D74550=2C dec=3D5= 0331648 .=0A= =0A= =0A= =0A= =0A= =0A= Best 73=2C=0A= =0A= =0A= Markus (DF6NM)=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= = --_aa9cdcec-0afa-44a4-9257-22e92d9fea9f_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Markus=3B
All your hard work = certainly paid off! =3B OPDS modes have made a big difference and congr= ats to Stefan who made =3Bmore than one =3BEurope-S America decodes= .
As for call signs=2C we had to do that with WSPR modes as well at firs= t-it worked out well.
Hopefully there is more than just one good freq to= work with on =3B or about 74.5520? =3B For now you might give Dex = and me a couple of freqs 1 HZ apart or =3Bso and we can try them tonigh= t. =3B
Would you prefer to continue with the slower =3BOPDS64 o= r try to get =3Bopds32 to work?
Bob
 =3B
To: rsgb_lf_group@blacksheep.org
From: markusvester@aol.com<= br>Date: Mon=2C 9 Dec 2013 06:14:12 -0500
Subject: Re: LF: 74550 - opds-= 64

=0A=
Hi Bob=2C LF=2C
=0A= =0A= =0A=
&nb= sp=3B
=0A= =0A= =0A=
I a= m very pleased to find that your Opera-64 signal produced five correlation = detections here last night. In the attached spectrogram=2C the symmetrical = Opera modulation sidebands are clearly visible between the many DCF-77 inte= rference lines.
=0A= =0A= =0A=
&nb= sp=3B
=0A= =0A= =0A=
Unf= ortunately the timestamps from SpecLab temporarily suffered from an unexpla= ined offset=2C affecting both the spectrogram and the exported spectrum dat= a. Such transient errors have also happened to other slow SpecLab instances= =2C eg. 8.97 kHz - sometime after startup=2C time seems to spontaneously ju= mp back=2C and suddenly comes back to normal after a few hours. In this cas= e=2C timestamps were found to be exactly 5h 46m 4s early=2C allowing to der= ive corrected spot times (appended to the end of the lines here):
=0A= =0A= =0A=
&nb= sp=3B
=0A= =0A= =0A=
&nb= sp=3B =3B date =3B =3B =3B =3B =3B time =3B&nbs= p=3B call =3B =3B distance =3B frequency bandwidth =3B snr&= nbsp=3B =3B =3B correlation
=0A= 2013-12-09 07:53:55 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -49.5dBOp =3B 95% 15.6dB
=0A= 2013-12-09 05:42:27 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -47.3dBOp =3B 82% 16.7dB
=0A= 2013-12-09 04:36:41 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -44.4dBOp 100% 19.6dB
=0A= 2013-12-08 22:50:39 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -45.2dBOp =3B 91% 19.1dB =3B 04:36:43 (same transmission a= s above)
=0A= 2013-12-08 21:44:53 WG2XRS =3B 6448km =3B 74549.500Hz =3B = =3B 1mHz -41.8dBOp =3B 92% 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% 16.1dB =3B 02:25:11
=0A= =0A= =0A=
&nb= sp=3B
=0A= =0A= =0A=
The= grass is always greener on the other side... Regarding the choice of frequ= ency=2C the high resolution spectrogram seems to confirm the gap in the DCF= 77 interference around 74552.0 Hz. So Bob=2C Dex and others may consider mo= ving up there=2C further reducing the QRM for other observers (eg. Hartmut)= as well.
=0A= =0A= =0A=
&nb= sp=3B
=0A= =0A= =0A=
My = understanding is that Opera's 28 bit payload can encode six character calls= igns=2C but no extra appendix. This would result in ambiguities if several = WG2XGR/n stations were transmitting simultaneously. As a simple workaround= =2C I would suggest to replace the number "2" by the number from the append= ix=2C eg. just use WG4XGR instead of WG2XGR/4 etc. One could argue that "se= nding the wrong callsign" might be considered illegal. But it would be unab= iguous=2C and we could publicly announce it as an appropriate extension of = the Opera encoding scheme.
=0A= =0A= =0A=
&nb= sp=3B
=0A= =0A= =0A=
Bes= t 73=2C
=0A= Markus (DF6NM)
=0A=
=0A= =0A= =0A=

=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=
=0A= =0A=
=0A= =0A=
Regarding opds-64 (or 65?) setup=2C I = had forgotten to mention two more lines to be edited in opds.ini:=0A= =0A= =0A=
 =3Bopspeed=3D64 =3B =3B &= nbsp=3B' speed definition
=0A=  =3Bspotdelay=3D58 =3B ' =3Bsame timestamp offset =3Bas fro= m Opera
=0A= =0A= =0A=
 =3B
=0A= =0A= =0A=
In =3BGraham's words=2C there's re= ally a whole "cactus" of spikes =3Bin the =3B238 =B5Hz spectrum.&nb= sp=3BMost are on a 16.67 mHz raster=2C because large parts of =3Bthe BC= D time-message from DCF77 are repeating =3Bevery minute. I have now rec= alibrated the frequency scale=2C and restricted the opds search range from = 74548.1 =3Bto 74550.0 Hz.
=0A= =0A= =0A=
 =3B
=0A= =0A= =0A=
Anyway given the QRSS levels from Bob = last night I am quite optimistic.
=0A= =0A= =0A=
 =3B
=0A= =0A= =0A=
Best 73=2C
=0A= =0A= =0A=
Markus (DF6NM)
=0A= =0A= =0A=
 =3B
=0A= =0A= =0A=
=0A= =0A=

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

=0A=
=0A= =0A= =0A=
...
=0A= =0A= =0A=
For the night to come=2C I'm set up fo= r monitoring =3Bopds-64 in a 4 Hz slot around 74.55 kHz=2C and will be = uploading screenshots and possible detections to the usual opds grabber http://dl.dropboxusercontent.com/u/26404526/opds.htm
=0A= =0A= =0A=
In case others =3Bwant to try: Spe= cLab FFT settings can be =3Bsimilar to =3Bopds-32 but more decimati= on is needed for half bandwidth (0.238 mHz). =3BIn opds.ini=2C =3Bc= enter frequency =3Band decimatio= n should be edited: =3Bfc=3D7455= 0=2C =3Bdec=3D50331648 .<= /div>=0A= =0A= =0A=
 =3B
=0A= =0A= =0A=
Best 73=2C
=0A= =0A= =0A=
Markus (DF6NM)
=0A= =0A= =0A=
 =3B
=0A= =0A= =0A=
=0A= =0A=
 =3B
=0A=
=0A=
=0A=
= --_aa9cdcec-0afa-44a4-9257-22e92d9fea9f_--