Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp197856igb; Tue, 10 Dec 2013 00:52:10 -0800 (PST) X-Received: by 10.194.61.84 with SMTP id n20mr10485940wjr.61.1386665529317; Tue, 10 Dec 2013 00:52:09 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id w3si6382550wjz.135.2013.12.10.00.52.08 for ; Tue, 10 Dec 2013 00:52:09 -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; dkim=pass (test mode) header.i=@comcast.net Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1VqIdy-0004Jd-82 for rs_out_1@blacksheep.org; Tue, 10 Dec 2013 08:26:14 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VqIdx-0004JU-3p for rsgb_lf_group@blacksheep.org; Tue, 10 Dec 2013 08:26:13 +0000 Received: from qmta13.westchester.pa.mail.comcast.net ([76.96.59.243]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1VqIdt-0001Ck-Cg for rsgb_lf_group@blacksheep.org; Tue, 10 Dec 2013 08:26:11 +0000 Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta13.westchester.pa.mail.comcast.net with comcast id zkS61m0011HzFnQ5DkS6di; Tue, 10 Dec 2013 08:26:06 +0000 Received: from Owner ([166.137.182.53]) by omta14.westchester.pa.mail.comcast.net with comcast id zkRj1m00T19Y0ty3akRqjx; Tue, 10 Dec 2013 08:26:01 +0000 From: "hvanesce" To: References: <2504E90AEBE5469E956314C7151BF777@White> <8D0C2E6EC29A51B-1A78-495@webmail-m255.sysops.aol.com> In-Reply-To: <8D0C2E6EC29A51B-1A78-495@webmail-m255.sysops.aol.com> Date: Tue, 10 Dec 2013 01:25:34 -0700 Message-ID: <1ad801cef581$6fd55000$4f7ff000$@comcast.net> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQKm5EpT/2x/TR+l2CE1n8R9LAySUQKZmsXRmIhtMIA= Content-Language: en-us DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1386663966; bh=45Qm/zl/CF3tMgDtpNWhcE5kqapiEX7IwbRhn2EXOPQ=; h=Received:Received:From:To:Subject:Date:Message-ID:MIME-Version: Content-Type; b=Y/lsHcaY5TlYSswpWMN4Ocj9IjheNiLL4srbZ52jN28VwhVC/gSHkhtMMs2jo7QpU wh/qAGrhmGr2F9VuVgtihTGj67hVEFLM487UaTQ0/W59MdDAPQb6/Tp3WrulimXnRR 9jijel7aBBJOGLiJLdoAqGU65A9LCgHuSLyiqV7sGyRfrxApfP0FhYIryKLGmSQG2/ dOwpbjdpeycfH8mZHXlDGcbKPFZ0F6DB2xto0KZ614fOqY28yJHyof8QPYIcxsKNOg SC9jglbK5ZAQJLahc6VkcT/KSum9Z4H0yRREEaOJEniA4xNQQ4qrCnRyUd0+Gsvcix XZGm182Zl61nA== X-Spam-Score: 0.8 (/) 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: Bob and Markus, Very impressive, 73, [...] Content analysis details: (0.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [76.96.59.243 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (hvanesce[at]comcast.net) -0.0 SPF_PASS SPF: sender matches SPF record -0.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 HTML_MESSAGE BODY: HTML included in message 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: b3b0f15d0cbaee08765b7bacd0352512 Subject: RE: LF: 74550 - opds-64 Content-Type: multipart/alternative; boundary="----=_NextPart_000_1AD9_01CEF546.C377D790" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.2 required=5.0 tests=HTML_50_60,HTML_MESSAGE 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: 1346 This is a multipart message in MIME format. ------=_NextPart_000_1AD9_01CEF546.C377D790 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Bob and Markus, =20 Very impressive, =20 73, =20 Jim AA5BW =20 From: owner-rsgb_lf_group@blacksheep.org = [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Markus Vester Sent: Monday, December 9, 2013 4:14 AM To: rsgb_lf_group@blacksheep.org Subject: Re: LF: 74550 - opds-64 =20 Hi Bob, LF, =20 I am very pleased to find that your Opera-64 signal produced five = correlation detections here last night. In the attached spectrogram, the = symmetrical Opera modulation sidebands are clearly visible between the = many DCF-77 interference lines.=20 =20 Unfortunately the timestamps from SpecLab temporarily suffered from an = unexplained offset, affecting both the spectrogram and the exported = spectrum data. Such transient errors have also happened to other slow = SpecLab instances, eg. 8.97 kHz - sometime after startup, time seems to = spontaneously jump back, and suddenly comes back to normal after a few = hours. In this case, timestamps were found to be exactly 5h 46m 4s = early, allowing to derive corrected spot times (appended to the end of = the lines here): =20 date time call distance frequency bandwidth snr = correlation 2013-12-09 07:53:55 WG2XRS 6448km 74549.500Hz 1mHz -49.5dBOp 95% = 15.6dB 2013-12-09 05:42:27 WG2XRS 6448km 74549.500Hz 1mHz -47.3dBOp 82% = 16.7dB 2013-12-09 04:36:41 WG2XRS 6448km 74549.500Hz 1mHz -44.4dBOp 100% = 19.6dB 2013-12-08 22:50:39 WG2XRS 6448km 74549.500Hz 1mHz -45.2dBOp 91% = 19.1dB 04:36:43 (same transmission as above) 2013-12-08 21:44:53 WG2XRS 6448km 74549.500Hz 1mHz -41.8dBOp 92% = 19.3dB 03:30:57 2013-12-08 20:39:07 WG2XRS 6448km 74549.500Hz 1mHz -49.2dBOp 98% = 16.1dB 02:25:11 =20 The grass is always greener on the other side... Regarding the choice of = frequency, the high resolution spectrogram seems to confirm the gap in = the DCF77 interference around 74552.0 Hz. So Bob, Dex and others may = consider moving up there, further reducing the QRM for other observers = (eg. Hartmut) as well. =20 My understanding is that Opera's 28 bit payload can encode six character = callsigns, but no extra appendix. This would result in ambiguities if = several WG2XGR/n stations were transmitting simultaneously. As a simple = workaround, I would suggest to replace the number "2" by the number from = the appendix, 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 unabiguous, and we could publicly announce it as an = appropriate extension of the Opera encoding scheme. =20 Best 73, Markus (DF6NM) =20 -----Urspr=C3=BCngliche Mitteilung-----=20 Von: Markus Vester An: rsgb_lf_group Verschickt: So, 8 Dez 2013 11:05 pm Betreff: Re: LF: 74550 - opds-64 Regarding opds-64 (or 65?) setup, I had forgotten to mention two more = lines to be edited in opds.ini: opspeed=3D64 ' speed definition spotdelay=3D58 ' same timestamp offset as from Opera =20 In Graham's words, there's really a whole "cactus" of spikes in the 238 = =C2=B5Hz spectrum. Most are on a 16.67 mHz raster, because large parts = of the BCD time-message from DCF77 are repeating every minute. I have = now recalibrated the frequency scale, and restricted the opds search = range from 74548.1 to 74550.0 Hz.=20 =20 Anyway given the QRSS levels from Bob last night I am quite optimistic. =20 Best 73,=20 Markus (DF6NM) =20 =20 From: Markus Vester =20 Sent: Sunday, December 08, 2013 8:40 PM To: rsgb_lf_group@blacksheep.org=20 Subject: LF: 74550 =20 ... For the night to come, I'm set up for monitoring opds-64 in a 4 Hz slot = around 74.55 kHz, and will be uploading screenshots and possible = detections to the usual opds grabber = http://dl.dropboxusercontent.com/u/26404526/opds.htm=20 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, center frequency and decimation should be edited: fc=3D74550, = dec=3D50331648 . =20 Best 73, Markus (DF6NM) =20 =20 ------=_NextPart_000_1AD9_01CEF546.C377D790 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Bob and Markus,

 

Very impressive,

 

73,

 

Jim AA5BW

 

From:= = owner-rsgb_lf_group@blacksheep.org = [mailto:owner-rsgb_lf_group@blacksheep.org] On Behalf Of Markus = Vester
Sent: Monday, December 9, 2013 4:14 AM
To: = rsgb_lf_group@blacksheep.org
Subject: Re: LF: 74550 - = opds-64

 

H= i Bob, LF,

&= nbsp;

I= am very pleased to find that your Opera-64 signal produced five = correlation detections here last night. In the attached spectrogram, the = symmetrical Opera modulation sidebands are clearly visible between the = many DCF-77 interference lines.

&= nbsp;

U= nfortunately the timestamps from SpecLab temporarily suffered from an = unexplained offset, affecting both the spectrogram and the exported = spectrum data. Such transient errors have also happened to other slow = SpecLab instances, eg. 8.97 kHz - sometime after startup, time seems to = spontaneously jump back, and suddenly comes back to normal after a few = hours. In this case, timestamps were found to be exactly 5h 46m 4s = early, allowing to derive corrected spot times (appended to the end of = the lines here):

&= nbsp;

&= nbsp;  date      time   = call   distance  frequency bandwidth  = snr    correlation
2013-12-09 07:53:55 WG2XRS  = 6448km  74549.500Hz   1mHz -49.5dBOp  95% = 15.6dB
2013-12-09 05:42:27 WG2XRS  6448km  = 74549.500Hz   1mHz -47.3dBOp  82% 16.7dB
2013-12-09 = 04:36:41 WG2XRS  6448km  74549.500Hz   1mHz = -44.4dBOp 100% 19.6dB
2013-12-08 22:50:39 WG2XRS  6448km  = 74549.500Hz   1mHz -45.2dBOp  91% 19.1dB  04:36:43 = (same transmission as above)
2013-12-08 21:44:53 WG2XRS  = 6448km  74549.500Hz   1mHz -41.8dBOp  92% = 19.3dB  03:30:57
2013-12-08 20:39:07 WG2XRS  6448km  = 74549.500Hz   1mHz -49.2dBOp  98% 16.1dB  = 02:25:11

&= nbsp;

T= he grass is always greener on the other side... Regarding the choice of = frequency, the high resolution spectrogram seems to confirm the gap in = the DCF77 interference around 74552.0 Hz. So Bob, Dex and others may = consider moving up there, further reducing the QRM for other observers = (eg. Hartmut) as well.

&= nbsp;

M= y understanding is that Opera's 28 bit payload can encode six character = callsigns, but no extra appendix. This would result in ambiguities if = several WG2XGR/n stations were transmitting simultaneously. As a simple = workaround, I would suggest to replace the number "2" by the = number from the appendix, 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 unabiguous, and we could publicly = announce it as an appropriate extension of the Opera encoding = scheme.

&= nbsp;

B= est 73,
Markus (DF6NM)

 

-----Urspr=C3=BCngliche Mitteilung----- =
Von: Markus Vester <markusvester@aol.com>
An: = rsgb_lf_group <rsgb_lf_group@blacksheep.org= >
Verschickt: So, 8 Dez 2013 11:05 pm
Betreff: Re: LF: = 74550 - opds-64

Regarding = opds-64 (or 65?) setup, I had forgotten to mention two more lines to be = edited in opds.ini:

 opspeed= =3D64    ' speed definition
 spotdelay=3D58  = ' same timestamp offset as from = Opera

 

In Graha= m's words, there's really a whole "cactus" of spikes in = the 238 =C2=B5Hz spectrum. Most are on a 16.67 mHz raster, = because large parts of the BCD time-message from DCF77 are = repeating every minute. I have now recalibrated the frequency = scale, and restricted the opds search range from 74548.1 to 74550.0 = Hz.

 

Anyway given = the QRSS levels from Bob last night I am quite = optimistic.

 

Best 73, =

Markus = (DF6NM)

 

 <= /o:p>

From:= = Markus Vester =

Sent:= = Sunday, December 08, 2013 8:40 PM

Subject: LF: = 74550

 

...

For the = night to come, I'm set up for monitoring opds-64 in a 4 Hz slot = around 74.55 kHz, and will be uploading screenshots and possible = detections to the usual opds grabber http://dl.dropboxusercontent.com/u/26404526/opds.htm =

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, center frequency and decimation should = be edited: fc=3D74550, dec=3D50331648 = .

 

Best = 73,

Markus = (DF6NM)

 

 <= /o:p>

------=_NextPart_000_1AD9_01CEF546.C377D790--