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;
Date: Fri, 13 Dec 2013 22:09:18 -0330 (NST)
From: jcraig@mun.ca
To: rsgb_lf_group@blacksheep.org
In-Reply-To: <52ABB401.7040000@iup.uni-heidelberg.de>
Message-ID: <Pine.LNX.4.64.1312132207110.10814@plato.ucs.mun.ca>
References: <BLU180-W2256C7E90DED7254DE112DACD30@phx.gbl>,<8D0C31F8DA1EC8D-9A4-2C1C@webmail-vd013.sysops.aol.com>
 <BLU180-W278F10D10A21AB2AACF302ACD30@phx.gbl> <52A60989.5070402@iup.uni-heidelberg.de>
 <52A63084.20006@iup.uni-heidelberg.de> <Pine.LNX.4.64.1312092105570.16448@plato.ucs.mun.ca>
 <Pine.LNX.4.64.1312092121280.16448@plato.ucs.mun.ca> <52A765CE.8060000@iup.uni-heidelberg.de>
 <Pine.LNX.4.64.1312101557060.24676@plato.ucs.mun.ca> <52ABAC38.1080901@iup.uni-heidelberg.de>
 <Pine.LNX.4.64.1312132141120.10773@plato.ucs.mun.ca> <52ABB401.7040000@iup.uni-heidelberg.de>
MIME-Version: 1.0
Subject: Re: LF: VO1NA
Content-Type: MULTIPART/MIXED; BOUNDARY="-1719232024-1035932700-1386985158=:10814"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1719232024-1035932700-1386985158=:10814
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

Hi Stefan,

Just started qrss3 beacon which will run to 0200 when the telegram
starts per schedule. Will watch your grabber and mine!

73
Joe

On Sat, 14 Dec 2013, Stefan Sch=C3=A4fer wrote:

> Hi Joe,
>
> I'm stopping my beacon and watch for you the whole time. Maybe you will=
=20
> appear in the QSB, so we can get a first impression over that path. Could=
 you=20
> run it a few times longer? As soon as i can read you, i will attempt a QS=
O.
>
> 73, Stefan
>
> Am 14.12.2013 02:20, schrieb jcraig@mun.ca:
>> Hi Stefan,
>> Been calling you on qrss3 but no reply.  Your sigs were variable so I
>> doubt the path is good at the moment.  The exciter is not frequency agil=
e
>> yet -- sorry.  This will be a project soon.   We can try again tomorrow.
>> QRSS at 0000-0100.
>>=20
>> 73 and thanks
>> Joe
>>=20
>>=20
>> On Sat, 14 Dec 2013, Stefan Sch=C3=A4fer wrote:
>>=20
>>> Hi Joe,
>>>=20
>>> I just found the latest spot in the 630m DX cluster. You are already QR=
V?=20
>>> Can we make a sked please?
>>> Can you listen on 472.2 kHz? Or suggest another frequency. I will try t=
o=20
>>> listen for you. Or, send some QRSS-3 on 476.180 or so. My grabber is=20
>>> running at=20
>>> http://www.iup.uni-heidelberg.de/schaefer_vlf/DK7FC_MF_Grabber.html
>>>=20
>>> 73, Stefan/DK7FC
>>>=20
>>> PS: There is local QRM on 477.7 here, at least for CW this is not odeal=
=20
>>> for me...
>>>=20
>>>=20
>>> Am 10.12.2013 20:40, schrieb jcraig@mun.ca:
>>>> Hi Stefan,
>>>>=20
>>>> The band is fairly clear.  Only a few carriers and WD2XSH stations
>>>> were heard so far; there is no preferred frequency so just let me know
>>>> where you will be.  476.17 is fine but there is a carrier 10 Hz below
>>>> that.  I share your doubt we will be able to do CW because my ERP is
>>>> only about 1.5 watts, but we can certainly try.  The plan is to run
>>>> the CW beacon while there is no CW and QRSS QSO activity, ie: 0300
>>>> to 2300 UTC for the 14 and 15th.  The TX QRG is 477.70 kHz.
>>>>=20
>>>> 73
>>>> Joe
>>>>=20
>>>=20
>>>=20
>
>
---1719232024-1035932700-1386985158=:10814--