Delivered-To: daveyxm@virginmedia.com Received: by 10.50.96.198 with SMTP id du6csp82762igb; Thu, 17 Oct 2013 20:47:31 -0700 (PDT) X-Received: by 10.180.198.5 with SMTP id iy5mr942339wic.45.1382068050896; Thu, 17 Oct 2013 20:47:30 -0700 (PDT) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id g7si3694550wib.1.2013.10.17.20.47.30 for ; Thu, 17 Oct 2013 20:47:30 -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 1VWyx7-0004DO-Ei for rs_out_1@blacksheep.org; Fri, 18 Oct 2013 02:34:09 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1VWyx6-0004DF-Qn for rsgb_lf_group@blacksheep.org; Fri, 18 Oct 2013 02:34:08 +0100 Received: from omr-m08.mx.aol.com ([64.12.222.129]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1VWyx4-0005qk-6P for rsgb_lf_group@blacksheep.org; Fri, 18 Oct 2013 02:34:07 +0100 Received: from mtaout-db03.r1000.mx.aol.com (mtaout-db03.r1000.mx.aol.com [172.29.51.195]) by omr-m08.mx.aol.com (Outbound Mail Relay) with ESMTP id A594B7000009A for ; Thu, 17 Oct 2013 21:34:03 -0400 (EDT) Received: from White (95-91-237-85-dynip.superkabel.de [95.91.237.85]) by mtaout-db03.r1000.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 95694E000085 for ; Thu, 17 Oct 2013 21:34:00 -0400 (EDT) Message-ID: From: "Markus Vester" To: References: <000701cecb29$d06ee7f0$6401a8c0@JAYDELL> <525FCC72.3080506@iup.uni-heidelberg.de> <002001cecb35$90568ea0$6d01a8c0@DELL4> <525FFA57.1020001@iup.uni-heidelberg.de> <525FFAD3.2000406@iup.uni-heidelberg.de> <005401cecb51$fb859bf0$6d01a8c0@DELL4> <52608759.1070509@iup.uni-heidelberg.de> Date: Fri, 18 Oct 2013 03:33:58 +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 x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1382060043; bh=hGFrOf53kt52/XNQ0ErIqtbCOrrmLJmYTX1mj4VZqGQ=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=mrYOalz2xagddMybQOOjbVa7r0uGA2CQU9coStjpvclwbhNe1QFmjvFvlggd1zxlF TjhntpbslYuR4TsWMbChPt/NkwIrABrv4zDvPBQLADmgSo2oIm3N4K4XaA5DRVnaFI +mc+0bpolelMNtkoWKScZE1F6jwXyHDytn6xQHqs= x-aol-sid: 3039ac1d33c3526090085cea X-AOL-IP: 95.91.237.85 X-Spam-Score: -0.4 (/) 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: Problem solved ;-) date time call distance frequency bandwidth snr correlation 2013-10-18 01:49:25 DK7FC 175km 137559.913Hz 4mHz -19.1dBOp 45% 19.8dB 2013-10-18 01:18:08 R7NT 2060km 137590.998Hz 4mHz -42.0dBOp 100% 18.5dB 2013-10-17 23:17:43 DK7FC 175km 137559.914Hz 7mHz -20.7dBOp 20% 17.1dB [...] Content analysis details: (-0.4 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.222.129 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.4 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: c96efc14f58f84aa05b44c520f48db32 Subject: Re: LF: T/A OPDS DK7FC Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01CECBB2.E12E2CC0" 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_20_30,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: 3047 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_0005_01CECBB2.E12E2CC0 Content-Type: text/plain; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable Problem solved ;-) date time call distance frequency bandwidth snr = correlation 2013-10-18 01:49:25 DK7FC 175km 137559.913Hz 4mHz -19.1dBOp 45% = 19.8dB 2013-10-18 01:18:08 R7NT 2060km 137590.998Hz 4mHz -42.0dBOp 100% = 18.5dB 2013-10-17 23:17:43 DK7FC 175km 137559.914Hz 7mHz -20.7dBOp 20% = 17.1dB 73, Markus From: Stefan Sch=E4fer=20 Sent: Friday, October 18, 2013 2:56 AM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: T/A OPDS DK7FC Hi Jay, I wanted to give it a try tonite. First i wanted to use DF6NM's OPDS=20 software which i would really prefer over the ROS-OP stuff. But then i=20 found that the sndoutpt.exe creates a ramp in the audio tone. My FETs=20 didn't like that at all, they made a crrrk at the beginning and end of=20 each dash. This is because the audio passes a comparator which makes a=20 clear hard keyed tone for the mixer which keys the IXDD414 anyway. FETs=20 survived but it showed that i need to do hardware modifications if i=20 want to use Markus' tool. In WSPR-15 it may be the same but then it is just 4 times per hour and=20 in OP32 is is much more. Then i installed the standard Opera program which i find very annoying.=20 It is not even possible to select a TXD line of the RS232 which i=20 normally use for PTT. When using the standard program i'm generating the = tone with SpecLab (on the "LF TX PC") and key the PTT with the program=20 (on the "LF/MF RX/TX PC"). Didn't work :-/ Soldered arround to use RTS=20 instead. PTT was keyed when pressing the tune button and released when=20 pressing it again, as intended. But then, when pressing "Beacon", the=20 PTT was key down, permanent tone. Need a VOX or so... So i can do no OPDS tests tonite, sorry. 73, Stefan/DK7FC PS: I'll continue with DFCW-90 now! Am 17.10.2013 18:00, schrieb jrusgrove@comcast.net: > Stefan > > Wasn't expecting you to start transmitting OPDS today ... just a=20 > thought for the future. But if you want to, that's okay too. > > OPDS32 is capable of of decoding at about -50 dB s/n (relative to SSB=20 > bandwidth). > > Your call and grid is easily added at the receiving end. > > Jay > > > ----- Original Message ----- From: "Stefan Sch=E4fer"=20 > > To: > Sent: Thursday, October 17, 2013 10:57 AM > Subject: Re: LF: T/A OPDS DK7FC > > > PS: Jay, Markus, > > What is the S/N performance of OPDS compared to WSPR-15 (apart from = the > fact that the callsigns must be known in advance and that there is = less > information into one sequence) ?? > > 73, Stefan > > Am 17.10.2013 16:55, schrieb Stefan Sch=E4fer: >> Jay, >> >> Am 17.10.2013 14:36, schrieb jrusgrove@comcast.net: >>> >>> Several stations on this end are now set up to receive OP Deep=20 >>> Search ... including Garry K3SIW in IL. Being that far inland is=20 >>> quite a disadvantage for T/A signal reception compared to 'coastal'=20 >>> stations. >> Garry got several WSPR-15 decodes of me last season, so i think he=20 >> could make it in OPDS as well. >>> >>> On my end I'm interested to see if it's possible to roll back the=20 >>> earliest T/A reception times (current best of about 2045Z mid=20 >>> season). There are probably other 'unknowns' waiting to be=20 >>> discovered along the way ;~) . >> OK, i can give it a try. Not sure if i can make it today arround 20=20 >> UTC but i will try. >> Am i already included in the OPDS list as a possible station? >> >> 73, Stefan/DK7FC > ------=_NextPart_000_0005_01CECBB2.E12E2CC0 Content-Type: text/html; charset="ISO-8859-15" Content-Transfer-Encoding: quoted-printable
Problem solved ;-)
 
   = date     =20 time   call   distance  frequency = bandwidth =20 snr    correlation
2013-10-18 01:49:25 = DK7FC    175km=20 137559.913Hz   4mHz -19.1dBOp  45% 19.8dB
2013-10-18 = 01:18:08=20 R7NT    2060km 137590.998Hz   4mHz -42.0dBOp = 100%=20 18.5dB
2013-10-17 23:17:43 DK7FC    175km=20 137559.914Hz   7mHz -20.7dBOp  20% = 17.1dB
73, = Markus

From: Stefan = Sch=E4fer
Sent: Friday, October 18, 2013 2:56 AM
Subject: Re: LF: T/A OPDS DK7FC

Hi Jay,

I wanted to give it a try tonite. First i = wanted=20 to use DF6NM's OPDS
software which i would really prefer over the = ROS-OP=20 stuff. But then i
found that the sndoutpt.exe creates a ramp in the = audio=20 tone. My FETs
didn't like that at all, they made a crrrk at the = beginning=20 and end of
each dash. This is because the audio passes a comparator = which=20 makes a
clear hard keyed tone for the mixer which keys the IXDD414 = anyway.=20 FETs
survived but it showed that i need to do hardware modifications = if i=20
want to use Markus' tool.
In WSPR-15 it may be the same but then = it is=20 just 4 times per hour and
in OP32 is is much more.

Then i = installed=20 the standard Opera program which i find very annoying.
It is not = even=20 possible to select a TXD line of the RS232 which i
normally use for = PTT.=20 When using the standard program i'm generating the
tone with SpecLab = (on the=20 "LF TX PC") and key the PTT with the program
(on the "LF/MF RX/TX = PC").=20 Didn't work :-/ Soldered arround to use RTS
instead. PTT was keyed = when=20 pressing the tune button and released when
pressing it again, as = intended.=20 But then, when pressing "Beacon", the
PTT was key down, permanent=20 tone.

Need a VOX or so...

So i can do no OPDS tests = tonite,=20 sorry.

73, Stefan/DK7FC

PS: I'll continue with DFCW-90=20 now!



Am 17.10.2013 18:00, schrieb jrusgrove@comcast.net:
> = Stefan
>
> Wasn't expecting you to start transmitting OPDS = today ...=20 just a
> thought for the future. But if you want to, that's okay=20 too.
>
> OPDS32 is capable of of decoding at about -50 dB = s/n=20 (relative to SSB
> bandwidth).
>
> Your call and grid = is=20 easily added at the receiving end.
>
> = Jay
>
>
>=20 ----- Original Message ----- From: "Stefan Sch=E4fer"
> <Stefan.Schaefer@iup= .uni-heidelberg.de>
>=20 To: <rsgb_lf_group@blacksheep.org= >
>=20 Sent: Thursday, October 17, 2013 10:57 AM
> Subject: Re: LF: T/A = OPDS=20 DK7FC
>
>
> PS: Jay, Markus,
>
> What is = the S/N=20 performance of OPDS compared to WSPR-15 (apart from the
> fact = that the=20 callsigns must be known in advance and that there is less
> = information=20 into one sequence) ??
>
> 73, Stefan
>
> Am = 17.10.2013=20 16:55, schrieb Stefan Sch=E4fer:
>> = Jay,
>>
>> Am=20 17.10.2013 14:36, schrieb jrusgrove@comcast.net:
>&= gt;>
>>>=20 Several stations on this end are now set up to receive OP Deep =
>>>=20 Search ... including Garry K3SIW in IL. Being that far inland is=20
>>> quite a disadvantage for T/A signal reception compared = to=20 'coastal'
>>> stations.
>> Garry got several = WSPR-15=20 decodes of me last season, so i think he
>> could make it in = OPDS as=20 well.
>>>
>>> On my end I'm interested to see if = it's=20 possible to roll back the
>>> earliest T/A reception times = (current=20 best of about 2045Z mid
>>> season). There are probably = other=20 'unknowns' waiting to be
>>> discovered along the way ;~)=20 .
>> OK, i can give it a try. Not sure if i can make it today = arround=20 20
>> UTC but i will try.
>> Am i already included in = the=20 OPDS list as a possible station?
>>
>> 73,=20 Stefan/DK7FC
>

------=_NextPart_000_0005_01CECBB2.E12E2CC0--