Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp111227igb; Sun, 27 Oct 2013 11:28:36 -0700 (PDT) X-Received: by 10.180.189.132 with SMTP id gi4mr6085064wic.19.1382898516134; Sun, 27 Oct 2013 11:28:36 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id t5si6398584wja.72.2013.10.27.11.28.35 for ; Sun, 27 Oct 2013 11:28:36 -0700 (PDT) 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 header.i=@mx.aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1VaUbo-0006IL-Hx for rs_out_1@blacksheep.org; Sun, 27 Oct 2013 17:58:40 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VaUbn-0006IC-VX for rsgb_lf_group@blacksheep.org; Sun, 27 Oct 2013 17:58:39 +0000 Received: from omr-d06.mx.aol.com ([205.188.109.203]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1VaUbl-0007I2-Fv for rsgb_lf_group@blacksheep.org; Sun, 27 Oct 2013 17:58:38 +0000 Received: from mtaout-da02.r1000.mx.aol.com (mtaout-da02.r1000.mx.aol.com [172.29.51.130]) by omr-d06.mx.aol.com (Outbound Mail Relay) with ESMTP id 4A537700000A3 for ; Sun, 27 Oct 2013 13:58:35 -0400 (EDT) Received: from White (95-91-237-85-dynip.superkabel.de [95.91.237.85]) by mtaout-da02.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 94E47E000086 for ; Sun, 27 Oct 2013 13:58:31 -0400 (EDT) Message-ID: <2027067839434D0AA51A8FF173D6B5A4@White> From: "Markus Vester" To: References: <526D3F49.8070204@iup.uni-heidelberg.de> <1382892371.130567697@f293.i.mail.ru> <526D44B0.5080909@iup.uni-heidelberg.de> Date: Sun, 27 Oct 2013 18:58:29 +0100 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 12.0.1606 X-MimeOLE: Produced By Microsoft MimeOLE V12.0.1606 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1382896715; bh=geccA9Vdd/ue+wGcKK/Cb5QtfvPVGapm1iiuoK8om1A=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=ld0FwBmFEOyeHjrm56CXz/MEGwyRZ/92Rt/pLAhTb3QLNCIJeH4T0EH8N1n1/ss2W W5bYa0HJ/P6TxjCWqQzTGCSXgkONct+O0DZca7LgQUl1fAQPb4QQ+1tqFyF2gvsSoP yXzeEIAxk+68OAq2MEzObmt/aPJYA8hPtWl7luWc= x-aol-sid: 3039ac1d3382526d544777f5 X-AOL-IP: 95.91.237.85 X-Spam-Score: -0.5 (/) 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: Yas, Alex, Stefan, opds decodes with correlation peaks just above 15 dB are on the borderline, and there's always a chance for false positives. The implicit downside of the use of a template list is that a false detection always shows a valid callsign, known to be active on LF. [...] Content analysis details: (-0.5 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [205.188.109.203 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (markusvester[at]aol.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.5 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 X-Scan-Signature: fcf77e2759cb043d8839e008dc214d5a Subject: Re: LF: Re: OPDS 32... Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01CED346.86888B30" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.3 required=5.0 tests=HTML_50_60,HTML_MESSAGE, MISSING_OUTLOOK_NAME 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: 2843 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_000C_01CED346.86888B30 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Yas, Alex, Stefan, opds decodes with correlation peaks just above 15 dB are on the = borderline, and there's always a chance for false positives. The = implicit downside of the use of a template list is that a false = detection always shows a valid callsign, known to be active on LF. Often the false ones don't just come "out of the blue" (ie plain noise), = and inspecting the spectrogram can be enlightening. The bogus detection = of RA3YO was probably a partial correlation, associated with a prior = strong reception from JP1ODJ: 2013-10-27 12:17:23 RA3YO 7813km 137569.599Hz 8mHz -50.5dBOp 66% = 15.4dB 2013-10-27 11:59:21 JP1ODJ 43km 137569.966Hz 4mHz -22.2dBOp 100% = 21.1dB Opds does have a built-in mechanism to suppress such aliases. But they = can still occasionally come through if opds happens to trigger on a = spurious peak contained in the skirts of the strong signal. 2013-10-27 16:01:02 VE7BDQ 7566km 137572.172Hz 3mHz -46.2dBOp 99% = 15.0dB There seems to be a permanent line on Yas' waterfall, but this one = dosn't seem to match one of the known Loran line frequencies for the = area:=20 http://dl.dropboxusercontent.com/u/26404526/Loran_lines_in_LF_slots.txt If you see strong Loran lines, and your receiver and samplerate are very = accurately calibrated, you can tell opds to ignore them by enabling and = editing the lorangri=3D and lorantol=3D lines in = opds.ini.=20 Best 73, Markus PS: Nothing at all wrong with Mal's opinion, everything in life is = "guess-work" to some extent ;-)=20 From: Stefan Sch=C3=A4fer=20 Sent: Sunday, October 27, 2013 5:52 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Re: OPDS 32... Oooh! Markus? What now?=20 Hopefully Mal don't see it ;-) 73, Stefan Am 27.10.2013 17:46, schrieb Alex R7NT:=20 Stefan, =D0=92=D0=BE=D1=81=D0=BA=D1=80=D0=B5=D1=81=D0=B5=D0=BD=D1=8C=D0=B5, 27 = =D0=BE=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8F 2013, 17:28 +01:00 = =D0=BE=D1=82 Stefan Sch=C3=A4fer : JA8SCD, PM95VQ: 2013-10-27 11:52:13 UA0AET 4175km 137580.826Hz 15mHz -44.8dBOp 95% = 17.2dB=20 2013-10-27 12:17:23 RA3YO 7813km 137569.599Hz 8mHz -50.5dBOp 66% = 15.4dB !!! ERROR :-( 2013-10-27 16:01:02 VE7BDQ 7566km 137572.172Hz 3mHz -46.2dBOp 99% = 15.0dB =20 VE7BDQ's Sunrise abt 15z I think there is a real chance for VE7BDQ to appear at YV7MAE! = Must be best during 7...10 UTC Looks like RA3YO made the best distance in that mode so far (?). 73, Stefan/DK7FC 73! Alex R7NT 136.73.ru ------=_NextPart_000_000C_01CED346.86888B30 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Yas, Alex, Stefan,
 
opds decodes with correlation = peaks just=20 above 15 dB are on the borderline, and there's always a chance for = false=20 positives. The implicit downside of the use of a template list is = that a=20 false detection always shows a valid callsign, known to be = active on=20 LF.
 
Often the false = ones don't just=20 come "out of the blue" (ie plain noise), and inspecting the spectrogram = can be=20 enlightening. The bogus detection of RA3YO was probably a = partial=20 correlation, associated with a prior strong reception from=20 JP1ODJ:
2013-10-27 12:17:23 = RA3YO  =20 7813km 137569.599Hz   8mHz -50.5dBOp  66% = 15.4dB
2013-10-27=20 11:59:21 JP1ODJ    43km 137569.966Hz   4mHz = -22.2dBOp=20 100% 21.1dB
Opds does have a built-in mechanism to = suppress=20 such aliases. But they can still occasionally come through if opds = happens=20 to trigger on a spurious peak contained in the skirts of the strong = signal.
 
2013-10-27 16:01:02 = VE7BDQ  7566km=20 137572.172Hz   3mHz -46.2dBOp  99% 15.0dB
There seems to be a permanent line on=20 Yas' waterfall, but this one dosn't seem to match one of the = known=20 Loran line frequencies for the = area: 
http://dl.dropboxusercontent.com/u/26404526/Loran_lines_in_LF_slo= ts.txt
If you see strong Loran = lines, and your=20 receiver and samplerate are very accurately calibrated, you can = tell opds=20 to ignore them by enabling and editing the lorangri=3D<GRI=20 list> and lorantol=3D<tolerance> lines in=20 opds.ini. 
 
Best 73,
Markus
 
PS: Nothing at all wrong = with Mal's=20 opinion, everything in life is "guess-work" to some = extent=20 ;-) 
 
 

From:=20 Stefan Sch=C3=A4fer
Sent: Sunday, October 27, = 2013 5:52=20 PM
To: rsgb_lf_group@blacksheep.org
Subject: Re: LF: Re: OPDS=20 32...

Oooh! Markus? What now?
Hopefully = Mal don't see=20 it ;-)

73, Stefan

Am 27.10.2013 17:46, schrieb Alex = R7NT:=20
Stefan,

=D0=92=D0=BE=D1=81=D0=BA=D1=80=D0=B5=D1=81=D0= =B5=D0=BD=D1=8C=D0=B5, 27 =D0=BE=D0=BA=D1=82=D1=8F=D0=B1=D1=80=D1=8F = 2013, 17:28 +01:00 =D0=BE=D1=82=20 Stefan Sch=C3=A4fer :
JA8SCD,=20 PM95VQ:
2013-10-27 11:52:13 UA0AET 4175km 137580.826Hz = 15mHz=20 -44.8dBOp 95% 17.2dB
2013-10-27=20 12:17:23 RA3YO 7813km 137569.599Hz 8mHz -50.5dBOp 66%=20 15.4dB   = !!!
ERROR =  :-(
2013-10-27 16:01:02 = VE7BDQ=20 7566km 137572.172Hz 3mHz -46.2dBOp 99%=20 15.0dB   
VE7BDQ's Sunrise abt 15z
I think there is a real = chance for=20 VE7BDQ to appear at YV7MAE! Must be best during 7...10 = UTC

Looks=20 like RA3YO made the best distance in that mode so far = (?).

73,=20 Stefan/DK7FC

73! Alex = R7NT=20  136.73.ru
------=_NextPart_000_000C_01CED346.86888B30--