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;
Message-ID: <52608759.1070509@iup.uni-heidelberg.de>
Date: Fri, 18 Oct 2013 02:56:57 +0200
From: =?ISO-8859-15?Q?Stefan_Sch=E4fer?= <Stefan.Schaefer@iup.uni-heidelberg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
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>
In-Reply-To: <005401cecb51$fb859bf0$6d01a8c0@DELL4>
Subject: Re: LF: T/A OPDS DK7FC
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: quoted-printable
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

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=20
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
> <Stefan.Schaefer@iup.uni-heidelberg.de>
> To: <rsgb_lf_group@blacksheep.org>
> 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
>