Delivered-To: daveyxm@virginmedia.com Received: by 10.50.237.98 with SMTP id vb2csp148293igc; Fri, 10 Jan 2014 12:17:56 -0800 (PST) X-Received: by 10.180.107.136 with SMTP id hc8mr2531417wib.11.1389385075143; Fri, 10 Jan 2014 12:17:55 -0800 (PST) Return-Path: Received: from post.thorcom.com (post.thorcom.com. [195.171.43.25]) by mx.google.com with ESMTP id o10si4288080wjz.142.2014.01.10.12.17.54 for ; Fri, 10 Jan 2014 12:17:55 -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 1W1iD2-0007Yn-KB for rs_out_1@blacksheep.org; Fri, 10 Jan 2014 19:57:36 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1W1iD2-0007Yd-2B for rsgb_lf_group@blacksheep.org; Fri, 10 Jan 2014 19:57:36 +0000 Received: from omr-d07.mx.aol.com ([205.188.109.204]) by relay1.thorcom.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1W1iCz-00011W-Lw for rsgb_lf_group@blacksheep.org; Fri, 10 Jan 2014 19:57:34 +0000 Received: from mtaout-mcc01.mx.aol.com (mtaout-mcc01.mx.aol.com [172.26.253.77]) by omr-d07.mx.aol.com (Outbound Mail Relay) with ESMTP id D34EB701BD7D7 for ; Fri, 10 Jan 2014 14:57:31 -0500 (EST) Received: from White (95-91-238-155-dynip.superkabel.de [95.91.238.155]) by mtaout-mcc01.mx.aol.com (MUA/Third Party Client Interface) with ESMTPA id 17042380000BB for ; Fri, 10 Jan 2014 14:57:30 -0500 (EST) Message-ID: <85E009AC938B4BB2BA2DB992D6B18BBC@White> From: "Markus Vester" To: References: ,<52C6EE6C.31591.1BEE17D@mike.dennison.ntlworld.com> <52C711F7.2080905@gmx.de> <52CFFB49.7060803@gmx.de> Date: Fri, 10 Jan 2014 20:57:28 +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=1389383851; bh=NT94hXF7nzVS2XnWJjGeL2qwNY2RzPDW/+gJgG2e150=; h=From:To:Subject:Message-ID:Date:MIME-Version:Content-Type; b=hWg2lAiw0/ntzSECMCFCe4ePKWmtvFfZ52glBDfIqqrIERQGwiCSf2iMMRMtzAN1s JLKSA09AXV4jpAFLNLm+tXNQUly3DskgH2nTwbzrq/io4xhQzVBGZ8VxNUNUYW7Lll e3GbjJm1HxDrQd9Gn2a+p+JWrxAysxrVKu22Ttyg= x-aol-sid: 3039ac1afd4d52d050aa58ef 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: Yes Joe, 100% duty cycle would be ideal. But occasional CW or QRSS id's won't hurt either, as long as phase is being preserved. 73, Markus From: Friday, January 10, 2014 8:21 PM To: Re: LF: Hartmut's Grabber -- QRP TA [...] 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 [205.188.109.204 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: 070d9ab39265047b7fb462cd62854f10 Subject: Re: LF: Hartmut's Grabber -- QRP TA Content-Type: multipart/alternative; boundary="----=_NextPart_000_001C_01CF0E46.92C16080" 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 Dies ist eine mehrteilige Nachricht im MIME-Format. ------=_NextPart_000_001C_01CF0E46.92C16080 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes Joe, 100% duty cycle would be ideal. But occasional CW or QRSS id's = won't hurt either, as long as phase is being preserved.=20 73, Markus From: jcraig@mun.ca=20 Sent: Friday, January 10, 2014 8:21 PM To: rsgb_lf_group@blacksheep.org=20 Subject: Re: LF: Hartmut's Grabber -- QRP TA Hi Markus, That is most interesting. I remember that occasion when TX was on = later than usual. It will take a bit of tinkering to get the phase coherent = exciter to the class E TX, but this is long overdue anyway. Would you like a continuous QRP carrier without any keying? Best Regards Joe VO1NA On Fri, 10 Jan 2014, Markus Vester wrote: > Joe, > > when you were sending CW a couple of days ago, the coherent carrier = was detectable in my 438 uHz spectrogram in broad daylight, until 12 UT! = So I'm wondering how a low power straight carrier would fare during = night and day? > > Best 73, > Markus > > > > From: jcraig@mun.ca > Sent: Friday, January 10, 2014 7:44 PM > To: rsgb_lf_group@blacksheep.org > Subject: Re: LF: Hartmut's Grabber -- QRP TA > > > Hi Hartmut, > > Yes, DCF39 must be a real pest as it is so close geographically and > in frequency. You seem to be dealing with it very effectively. > Thank-you for running the grabber. > > It's a pest over here too, but sometimes useful to check the RX = system. > > The TX will be on again tonight. In keeping with the spirit of energy > conservation being requested by our power company, the TX will run > at <5 watts tonight to the 100m wire. I hope to watch for the signals > on your grabber. > > Cheers > Joe VO1NA > > On Fri, 10 Jan 2014, Hartmut Wolff wrote: > >> Hello Joe, >> >> thank you for your kind words! >> >> Still struggling here with my local Pest DCF39. Between 03:15 and = 04:40 UTC >> DCF39 was sending a higher pulse frequence. That is the reason of the = higher >> noise level at that time and poorer reception of your beacon. >> >> Thank you for your signal! >> >> 73 >> Hartmut >> >> >> Am 2014-01-10 13:26, schrieb jcraig@mun.ca: >>> >>> Hello Hartmut and Group, >>> >>> Even with only 65 watts from the TX, strong QRSS100 signals were = seen on >>> Hartmut's grabber at 137.777 so the power was cut to <10 watts by >>> reducing the drain voltage of the class E amp to 12 V. The grabber >>> traces faded substantially, but rebounded to clearly readable around >>> 0630 utc. >>> >>> Congrats on your impressive RX setup, Martmut! >>> >>> 73 >>> Joe VO1NA >>> >>> >> >> >> >> >> > > ------=_NextPart_000_001C_01CF0E46.92C16080 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Yes Joe, 100% duty=20 cycle would be ideal. But occasional CW or QRSS id's won't hurt either, = as long=20 as phase is being preserved.
 
73, Markus

Sent: Friday, January 10, 2014 8:21 PM
Subject: Re: LF: Hartmut's Grabber -- QRP = TA

Hi=20 Markus,

That is most interesting.   I remember that = occasion=20 when TX was on later
than usual.  It will take a bit of = tinkering to get=20 the phase coherent exciter
to the class E TX, but this is long = overdue=20 anyway.  Would you like
a continuous QRP carrier without any=20 keying?

Best Regards
Joe VO1NA

On Fri, 10 Jan 2014, = Markus=20 Vester wrote:

> Joe,
>
> when you were sending CW = a couple=20 of days ago, the coherent carrier was detectable in my 438 uHz = spectrogram in=20 broad daylight, until 12 UT! So I'm wondering how a low power straight = carrier=20 would fare during night and day?
>
> Best 73,
>=20 Markus
>
>
>
> From: jcraig@mun.ca
> Sent: Friday, = January 10,=20 2014 7:44 PM
> To: rsgb_lf_group@blacksheep.org=
>=20 Subject: Re: LF: Hartmut's Grabber -- QRP TA
>
>
> Hi=20 Hartmut,
>
> Yes, DCF39 must be a real pest as it is so = close=20 geographically and
> in frequency. You seem to be dealing with it = very=20 effectively.
> Thank-you for running the grabber.
>
> = It's a=20 pest over here too, but sometimes useful to check the RX = system.
>
>=20 The TX will be on again tonight. In keeping with the spirit of = energy
>=20 conservation being requested by our power company, the TX will = run
> at=20 <5 watts tonight to the 100m wire.  I hope to watch for the=20 signals
> on your grabber.
>
> Cheers
> Joe=20 VO1NA
>
> On Fri, 10 Jan 2014, Hartmut Wolff=20 wrote:
>
>> Hello Joe,
>>
>> thank you = for your=20 kind words!
>>
>> Still struggling here with my local = Pest=20 DCF39. Between 03:15 and 04:40 UTC
>> DCF39 was sending a = higher pulse=20 frequence. That is the reason of the higher
>> noise level at = that time=20 and poorer reception of your beacon.
>>
>> Thank you = for your=20 signal!
>>
>> 73
>>=20 Hartmut
>>
>>
>> Am 2014-01-10 13:26, schrieb = jcraig@mun.ca:
>>>
>&= gt;>=20 Hello Hartmut and Group,
>>>
>>> Even with only = 65 watts=20 from the TX, strong QRSS100 signals were seen on
>>> = Hartmut's=20 grabber at 137.777 so the power was cut to <10 watts = by
>>>=20 reducing the drain voltage of the class E amp to 12 V. The=20 grabber
>>> traces faded substantially, but rebounded to = clearly=20 readable around
>>> 0630 = utc.
>>>
>>>=20 Congrats on your impressive RX setup, = Martmut!
>>>
>>>=20 73
>>> Joe=20 VO1NA
>>>
>>>
>>
>>
>>=
>>
>>
>
>

------=_NextPart_000_001C_01CF0E46.92C16080--