Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-mk02.r1000.mx.aol.com (Internet Inbound) with ESMTP id 0B7D33800008D; Thu, 6 Jun 2013 18:48:59 -0400 (EDT) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1UkiyN-0003Dy-Hh for rs_out_1@blacksheep.org; Thu, 06 Jun 2013 23:47:59 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1UkiyN-0003Dp-2J for rsgb_lf_group@blacksheep.org; Thu, 06 Jun 2013 23:47:59 +0100 Received: from omr-m09.mx.aol.com ([64.12.143.82]) by relay1.thorcom.net with esmtp (Exim 4.77) (envelope-from ) id 1UkiyL-0006ub-5G for rsgb_lf_group@blacksheep.org; Thu, 06 Jun 2013 23:47:57 +0100 Received: from mtaout-mb06.r1000.mx.aol.com (mtaout-mb06.r1000.mx.aol.com [172.29.41.70]) by omr-m09.mx.aol.com (Outbound Mail Relay) with ESMTP id 42AB5700000BA for ; Thu, 6 Jun 2013 18:47:55 -0400 (EDT) Received: from White (188-195-246-26-dynip.superkabel.de [188.195.246.26]) by mtaout-mb06.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 6CA62E0000E2 for ; Thu, 6 Jun 2013 18:47:52 -0400 (EDT) Message-ID: From: "Markus Vester" To: References: <51AA488C.4020800@eastlink.ca> <9F4D930ED1F64F7C974C9F3570FE5DEA@White> <106509721.20130603101147@mterrier.net> <511259661.20130605104210@mterrier.net> <22F50727DAB943178CABF2FE9A731025@GaryAsus> <89A40DBD5FD24F7DAF1DC48FF71ABC37@White> <006801ce6251$bbd6c290$6401a8c0@JAYDELL> <89839D0C2679435898627697705F04C3@F6CNIAndyHP> <0F9E760BA8A740059FFCE5431EE11E6B@AGB> Date: Fri, 7 Jun 2013 00:47:25 +0200 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 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1370558875; bh=OxrXcEDBW1J1gPaLOSiOdPHQhCGRD1Sd4Eyw7bDHxFE=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=BKWJ2zlv1t44j/00qpNj95VrgHngg1Jeani2t7HJMb9PbTRIbBfc2iXZIjerEwcLD QZnZzK7tiKFtkzetQVRI1lPR0QCwENpIuYJzPKHzaDhzwhKm/JwD9RB0riBAOGoR5K bq+gmW/VnEI6X3EZQN1XK5EgDxVSqcnWFZH2UnGE= X-AOL-SCOLL-SCORE: 0:2:285824832:93952408 X-AOL-SCOLL-URL_COUNT: 0 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: Hi Graham, yes it's true that the opds correlation detector does not attempt to directly decode any of the Opera 28-bit message contents (ie. the callsign). But you do get more than a single yes-or-no information. Opds tells you fairly reliably which entry from the predefined callsign list actually produced the hit. The list currently contains 28 candidates which makes up about 5 bits worth. Also it measures the TX carrier frequency down to a milli-Hz out of a 100 Hz range, which in itself could be used to encode another 17 bits... So I'd say it gives you less than 28 bits but certainly more than one bit. [...] 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 [64.12.143.82 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: f3d1da032404cd5ad9531631c09e3b44 Subject: Re: LF: VO1NA - 137.7770 kHz Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01CE6318.941A9CA0" 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 x-aol-global-disposition: G X-AOL-SCOLL-AUTHENTICATION: mtain-mk02.r1000.mx.aol.com ; domain : mx.aol.com DKIM : pass x-aol-sid: 3039ac1d618651b111db26cc X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0003_01CE6318.941A9CA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Graham, yes it's true that the opds correlation detector does not attempt to = directly decode any of the Opera 28-bit message contents (ie. the = callsign). But you do get more than a single yes-or-no information. Opds = tells you fairly reliably which entry from the predefined callsign list = actually produced the hit. The list currently contains 28 candidates = which makes up about 5 bits worth. Also it measures the TX carrier = frequency down to a milli-Hz out of a 100 Hz range, which in itself = could be used to encode another 17 bits... So I'd say it gives you less = than 28 bits but certainly more than one bit. Best wishes, Markus (DF6NM) From: Graham=20 Sent: Thursday, June 06, 2013 7:13 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: VO1NA - 137.7770 kHz ... Where as Op is designed to use standard tx/rx and soundcards with = afc routines , Marcus is running a correlation process , looking = for=20 the pattern match , this in effect is decoding a single data = 'bit'=20 and stability will affect his decode system , but with another 10 = dB=20 s/n it may extend the range considerably ! ... ------=_NextPart_000_0003_01CE6318.941A9CA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Graham,
 
yes it's true that the opds correlation = detector=20 does not attempt to directly decode any of the Opera 28-bit = message=20 contents (ie. the callsign). But you do get more than a single = yes-or-no=20 information. Opds tells you fairly reliably which entry from the = predefined=20 callsign list actually produced the hit. The list currently = contains 28=20 candidates which makes up about 5 bits worth. Also it = measures=20 the TX carrier frequency down to a milli-Hz out of a 100 Hz range,=20 which in itself could be used to encode another 17 bits... So = I'd say=20 it gives you less than 28 bits but certainly more than one = bit.
 
Best = wishes,
Markus = (DF6NM)

From: Graham
Sent: Thursday, June 06, 2013 7:13 PM
To: rsgb_lf_group@blacksheep.org= =20
Subject: Re: LF: VO1NA - 137.7770 kHz

...
Where  as Op is  designed to  use  standard = tx/rx =20 and  soundcards  with
afc  routines , Marcus  = is =20 running  a  correlation  process  , looking  = for=20
the  pattern  match , this  in effect  is =20 decoding  a single  data  'bit'
and  = stability =20 will  affect his  decode  system , but  with another = 10 dB=20
s/n it  may extend the  range  considerably=20 !

...
------=_NextPart_000_0003_01CE6318.941A9CA0--