Delivered-To: daveyxm@virginmedia.com Received: by 10.50.237.98 with SMTP id vb2csp256332igc; Tue, 17 Dec 2013 16:37:32 -0800 (PST) X-Received: by 10.195.13.45 with SMTP id ev13mr21725820wjd.20.1387327050518; Tue, 17 Dec 2013 16:37:30 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id wa3si7719168wjc.149.2013.12.17.16.37.30 for ; Tue, 17 Dec 2013 16:37:30 -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 1Vt4Pp-0002qX-5V for rs_out_1@blacksheep.org; Tue, 17 Dec 2013 23:51:05 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Vt4Po-0002qO-K0 for rsgb_lf_group@blacksheep.org; Tue, 17 Dec 2013 23:51:04 +0000 Received: from omr-d09.mx.aol.com ([205.188.108.133]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1Vt4Pm-0004Ys-9W for rsgb_lf_group@blacksheep.org; Tue, 17 Dec 2013 23:51:03 +0000 Received: from mtaout-da01.r1000.mx.aol.com (mtaout-da01.r1000.mx.aol.com [172.29.51.129]) by omr-d09.mx.aol.com (Outbound Mail Relay) with ESMTP id 54B4E701B590D for ; Tue, 17 Dec 2013 18:51:00 -0500 (EST) Received: from White (95-91-238-155-dynip.superkabel.de [95.91.238.155]) by mtaout-da01.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 88124E0000CD for ; Tue, 17 Dec 2013 18:50:57 -0500 (EST) Message-ID: From: "Markus Vester" To: References: ,<7801ED65CA834BA3A0CAEC7DA80106DD@White> Date: Wed, 18 Dec 2013 00:50:51 +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=1387324260; bh=6mtY2yeNWOnG1+o2NCAxNuC6y4wg3Puk7Vm6QPB0Cf4=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=uQqLIKdPw/gJQPt8/5MqrcUDs94CehaUsBTC0clr61n6f8p+mI2NbAgCPZ3z3AaMl 2VhwP/wXZXlPC4DR+1IqrSL9F3YXxhujRU4fRDYA2H1OYV6rt6YVkXDMbzc3GLSW1q Bu/vV+aDfwiJtF+cREhr5LOWD000GNAVzwqRev7E= x-aol-sid: 3039ac1d338152b0e3612235 X-AOL-IP: 95.91.238.155 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: Bob, the bandwidth displayed by opds is supposed to tell you the width of the central carrier, it's ideally zero and not related to the modulation speed. A stable and coherent signal like yours usually shows 1 or 2 mHz, but the figure surely won't be good to the last digit. The carrier is only present when the transmitter is being keyed with phase continuity from dash to dash, and it can then be used by opds as a phase-reference for synchroneous AM demodulation. [...] 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.108.133 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 1.0 FREEMAIL_REPLY From and body contain different freemails X-Scan-Signature: 3a21c85df7468d917c96c4564305897b Subject: Re: LF: 136 Dial freq for OP-OPDS 32 for tonight..., Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CEFB8B.32C48950" 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=HTML_30_40,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: 1867 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0004_01CEFB8B.32C48950 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Bob, the bandwidth displayed by opds is supposed to tell you the width of the = central carrier, it's ideally zero and not related to the modulation = speed. A stable and coherent signal like yours usually shows 1 or 2 mHz, = but the figure surely won't be good to the last digit. The carrier is = only present when the transmitter is being keyed with phase continuity = from dash to dash, and it can then be used by opds as a phase-reference = for synchroneous AM demodulation. On the other hand, the conveyed keying information resides in the AM = sidebands around the carrier, with a width proportional to the inverse = dot length. In Hartmut's Op-16 (4 second dots) capture, we find about = 0.2 Hz wide main lobes on each side of the carrier. Due to the = "unspreading" effect of the correlation, opds can still retrieve the = most likely callsign even when the power density of the sidebands is = well below the noise. Best 73,=20 Markus (DF6NM) From: Bob Raide=20 Sent: Wednesday, December 18, 2013 12:13 AM To: rsgb_lf_group@blacksheep.org=20 Subject: RE: LF: 136 Dial freq for OP-OPDS 32 for tonight..., Markus; Was wondering why my bandwidth was over twice as high as usual last = night on 73 band OP16? Must have something to do with faster OPERA mode? = And looking at my signal on Hartmut's grabber was what appeared to be = digital data on each side of the carrier. Wonder what would cause those = sidebands as I understand OPERA is nothing but keyed CW with no = modulation-unless it was hum on my carrier? Bob =20 -------------------------------------------------------------------------= ------- From: markusvester@aol.com To: rsgb_lf_group@blacksheep.org Date: Tue, 17 Dec 2013 23:59:41 +0100 Subject: Re: LF: 136 Dial freq for OP-OPDS 32 for tonight..., Bob, Alex, welcome again!=20 2013-12-17 23:03:34 WE2XEB 6448km 137540.999Hz 2mHz -47.7dBOp 76% = 15.5dB 2013-12-17 23:03:07 R7NT 2060km 137590.028Hz 4mHz -42.4dBOp 77% = 17.0dB 73, Markus (DF6NM) From: Bob Raide=20 Sent: Tuesday, December 17, 2013 6:53 PM To: rsgb_lf_group@blacksheep.org ; Bob Raide=20 Subject: LF: 136 Dial freq for OP-OPDS 32 for tonight..., WE2XEB NY will be on at 2200 or so with OP/OPDS 32 tonight at 136 dial = freq 137.541 TX freq as of now-all decodes appreciated-Bob ------=_NextPart_000_0004_01CEFB8B.32C48950 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Bob,
 
the bandwidth displayed by opds is = supposed to tell=20 you the width of the central carrier, it's ideally zero and not = related to=20 the modulation speed. A stable and coherent signal like yours usually=20 shows 1 or 2 mHz, but the figure surely won't = be good=20 to the last digit. The carrier is only present when=20 the transmitter is being keyed with phase continuity from dash to = dash, and=20 it can then be used by opds as a phase-reference for synchroneous AM=20 demodulation.
 
On the other hand, = the conveyed keying=20 information resides in the AM sidebands around the carrier, with a=20 width proportional to the inverse dot length. In = Hartmut's Op-16=20 (4 second dots) capture, we find about 0.2 Hz wide main lobes on each = side of=20 the carrier. Due to the "unspreading" effect of the correlation, opds = can still=20 retrieve the most likely callsign even when the power density of the=20 sidebands is well below the noise.
 
Best 73,
Markus (DF6NM)
 

From: Bob Raide
Sent: Wednesday, December 18, 2013 12:13 AM
Subject: RE: LF: 136 Dial freq for OP-OPDS 32 for=20 tonight...,

Markus;
Was wondering why my bandwidth was over twice = as high as=20 usual last night on 73 band OP16? Must have something to do = with faster=20 OPERA mode?  And looking at my signal on Hartmut's grabber was = what=20 appeared to be digital data on each side of the carrier.  Wonder = what would=20 cause those sidebands as I understand OPERA is nothing but keyed CW with = no=20 modulation-unless it was hum on my carrier?  Bob
 
From: markusvester@aol.com
To: rsgb_lf_group@blacksheep.org
Date: = Tue, 17=20 Dec 2013 23:59:41 +0100
Subject: Re: LF: 136 Dial freq for OP-OPDS 32 = for=20 tonight...,

Bob, Alex,
 
welcome again!
 
2013-12-17 23:03:34 WE2XEB  6448km = 137540.999Hz   2mHz -47.7dBOp  76% 15.5dB
2013-12-17 = 23:03:07=20 R7NT    2060km 137590.028Hz   4mHz = -42.4dBOp  77%=20 17.0dB
 
73, Markus (DF6NM)

From: Bob Raide
Sent: Tuesday, December 17, 2013 6:53 PM
Subject: LF: 136 Dial freq for OP-OPDS 32 for=20 tonight...,

WE2XEB NY will be on at 2200 or so with OP/OPDS 32 = tonight at 136=20 dial freq 137.541 TX freq as of now-all decodes appreciated-Bob=20
------=_NextPart_000_0004_01CEFB8B.32C48950--