Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp70796igb; Sun, 8 Dec 2013 14:30:45 -0800 (PST) X-Received: by 10.180.74.45 with SMTP id q13mr11342406wiv.47.1386541844828; Sun, 08 Dec 2013 14:30:44 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id fv11si2646105wic.45.2013.12.08.14.30.44 for ; Sun, 08 Dec 2013 14:30:44 -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 header.i=@mx.aol.com Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1VpmRe-0002zP-Jx for rs_out_1@blacksheep.org; Sun, 08 Dec 2013 22:03:22 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VpmRd-0002zG-Ne for rsgb_lf_group@blacksheep.org; Sun, 08 Dec 2013 22:03:21 +0000 Received: from omr-m03.mx.aol.com ([64.12.143.77]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1VpmRb-00019Y-Dr for rsgb_lf_group@blacksheep.org; Sun, 08 Dec 2013 22:03:20 +0000 Received: from mtaout-db01.r1000.mx.aol.com (mtaout-db01.r1000.mx.aol.com [172.29.51.193]) by omr-m03.mx.aol.com (Outbound Mail Relay) with ESMTP id 83DCD7000009E for ; Sun, 8 Dec 2013 17:03:16 -0500 (EST) Received: from White (95-91-238-155-dynip.superkabel.de [95.91.238.155]) by mtaout-db01.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 9237FE0000AB for ; Sun, 8 Dec 2013 17:03:13 -0500 (EST) Message-ID: <2504E90AEBE5469E956314C7151BF777@White> From: "Markus Vester" To: References: <000f01cef3f4$56d013d0$0802a8c0@acer> Date: Sun, 8 Dec 2013 23:03:10 +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=1386540196; bh=kH6HR6TRcBkqyCRG5w0ngwkugmQn7NVdps60dFlYxPU=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=lmrWJCp7iHieLb65wnQdrmYaU2MU1rZtjWEmzOPAHv56vfMSANe0QacoCdGH7+KTC i/AloF087wCiBqu7P7GGCAjMRqTlq2p7MjWoDEieop6aRFiZLvqRfKVpsPjNVjTNmc 3TGtBbl68TP4M27Sm4OouEMF4FhOStOECVFIoX58= x-aol-sid: 3039ac1d33c152a4eca11321 X-AOL-IP: 95.91.238.155 X-Spam-Score: -0.1 (/) 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: Regarding opds-64 (or 65?) setup, I had forgotten to mention two more lines to be edited in opds.ini: opspeed=64 ' speed definition spotdelay=58 ' same timestamp offset as from Opera In Graham's words, there's really a whole "cactus" of spikes in the 238 µHz 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. [...] Content analysis details: (-0.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [64.12.143.77 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.1 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: f45514038df04b1035abb1d5446da941 Subject: Re: LF: 74550 - opds-64 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01CEF469.AA7CC490" X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.6 required=5.0 tests=HTML_40_50,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: 1951 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_000C_01CEF469.AA7CC490 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 Graham's words, there's really a whole "cactus" of spikes in the 238 = =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 Anyway given the QRSS levels from Bob last night I am quite optimistic. Best 73,=20 Markus (DF6NM) From: Markus Vester=20 Sent: Sunday, December 08, 2013 8:40 PM To: rsgb_lf_group@blacksheep.org=20 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=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 . Best 73, Markus (DF6NM) ------=_NextPart_000_000C_01CEF469.AA7CC490 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Regarding opds-64 (or 65?) setup, I had = forgotten=20 to mention two more lines to be edited in opds.ini:
 opspeed=3D64    ' = speed=20 definition
 spotdelay=3D58  ' same timestamp = offset as from=20 Opera
 
In Graham's words, there's really = a whole=20 "cactus" of spikes in the 238 =B5Hz spectrum. Most are on = a 16.67=20 mHz raster, because large parts of the BCD time-message from DCF77 = are=20 repeating every minute. I have now recalibrated the frequency = scale, and=20 restricted the opds search range from 74548.1 to 74550.0 Hz. =
 
Anyway given the QRSS levels from Bob = last night I=20 am quite optimistic.
 
Best 73,
Markus (DF6NM)
 

Sent: Sunday, December 08, 2013 8:40 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: LF: 74550

...
For the night to come, I'm set up for=20 monitoring opds-64 in a 4 Hz slot around 74.55 kHz, and will be = uploading=20 screenshots and possible detections to the usual opds grabber = http://dl.d= ropboxusercontent.com/u/26404526/opds.htm
In case others want to try: = SpecLab FFT=20 settings can be similar to opds-32 but more decimation is = needed for=20 half bandwidth (0.238 mHz). In opds.ini, center = frequency and=20 decimation should be = edited: fc=3D74550, dec=3D50331648=20 .
 
Best 73,
Markus (DF6NM)
 
 
------=_NextPart_000_000C_01CEF469.AA7CC490--