Envelope-to: dave@picks.force9.co.uk Delivery-date: Mon, 03 Oct 2005 23:28:08 +0100 Received: by pih-mxcore06.plus.net with spam-scanned (PlusNet MXCore v2.00) id 1EMYn2-00025C-2K for dave@picks.force9.co.uk; Mon, 03 Oct 2005 23:28:08 +0100 Received: from post.thorcom.com ([193.82.116.20]) by pih-mxcore06.plus.net with esmtp (PlusNet MXCore v2.00) id 1EMYn1-00024D-Qo for dave@picks.force9.co.uk; Mon, 03 Oct 2005 23:28:08 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1EMYmg-0004F3-NK for rs_out_1@blacksheep.org; Mon, 03 Oct 2005 23:27:46 +0100 Received: from [193.82.116.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1EMYmf-0004Eu-Uw for rsgb_lf_group@blacksheep.org; Mon, 03 Oct 2005 23:27:45 +0100 Received: from rwcrmhc13.comcast.net ([216.148.227.118] helo=rwcrmhc12.comcast.net) by relay1.thorcom.net with esmtp (Exim 4.51) id 1EMZNI-00031G-Dj for rsgb_lf_group@blacksheep.org; Tue, 04 Oct 2005 00:05:39 +0100 Received: from AIRPORTTERMINAL (c-67-177-102-19.hsd1.ct.comcast.net[67.177.102.19]) by comcast.net (rwcrmhc13) with SMTP id <2005100322273401500b7pmoe>; Mon, 3 Oct 2005 22:27:34 +0000 Message-ID: <004301c5c86b$13ad2f60$6901a8c0@AIRPORTTERMINAL> From: "Jay Rusgrove" To: rsgb_lf_group@blacksheep.org References: <17879303.1126259836649.JavaMail.www@wwinf3201> <000001c5c7f2$322a1940$8701a8c0@IBMF7542B482FC> <001901c5c80f$8ce35320$6401a8c0@JAYTERMINAL> <001601c5c849$d2b6a480$e801a8c0@bob2l2u6k2n1g3> Date: Mon, 3 Oct 2005 18:37:45 -0400 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: LF: Re: Re: Re: ZM2E LF DX aspirations Content-Type: text/html; charset=windows-1252 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-PN-SpamFiltered: by PlusNet MXCore (v2.00) Content-transfer-encoding: 8bit

Bob

Thanks anyway...GL on the tests!

Jay

----- Original Message -----

From: Vernall

To: rsgb_lf_group@blacksheep.org

Sent: Monday, October 03, 2005 2:38 PM

Subject: LF: Re: Re: ZM2E LF DX aspirations

Jay,

No beaconing as such is scheduled by ZM2E. We are concentrating on two-way
contacts. However, as all participating stations will use the same nominal
frequency, you can see what you get as the night rolls on even though you
would not know in advance as to the sequence.

73, Bob ZL2CA

----- Original Message -----
From: "Jay Rusgrove" <JRusgrove@comcast.net>
To: <rsgb_lf_group@blacksheep.org>
Sent: Tuesday, October 04, 2005 12:42 AM
Subject: LF: Re: ZM2E LF DX aspirations

> Bob, Steve, Martin, Scott, Ed
>
> If possible, any spare time that could be filled with "beacon" operation
> would be greatly appreciated. East coast USA sunset 2230Z and sunrise
> 1050Z.
>
> Thanks in advance for any transmissions.
>
> Jay, W1VD
>
>
> ----- Original Message -----
> From: "Vernall" <vernall@xtra.co.nz>
> To: <rsgb_lf_group@blacksheep.org>
> Sent: Monday, October 03, 2005 4:08 AM
> Subject: LF: ZM2E LF DX aspirations
>
>
> Hi all,
>
> ZM2E at Quartz Hill should be ready by sunset Tuesday 4 October to begin
> QSO attempts with VA7LF and then RU6LA later in the night. The sunset
> and sunrise sequence is as follows:
> 0626 UTC ZL sunset and the path becomes dark to VA7LF
> 1417 UTC VA7LF sunrise, so nearly 8 hours of dark path to ZL (path is
> mostly north/south)
> 1453 UTC RU6LA sunset and the path becomes darl to ZL
> 1754 UTC ZL sunrise, so only 3 hours of dark path with RU6LA (path is
> mostly east/west)
>
> So there is time for a coffee break at ZM2E between each dark path.
> Three successive nights are arranged so we can "try again" the next
> night. The participants are agreed that they will not consider "carry
> over" from a previous night, and any successful QSO will need to be
> started and completed in the one night.
>
> ZM2E will be using 137.7890/137.7886 kHz FSK and with dot length
> selected at the time. VA7LF will use very similar frequencies and FSK.
> RU6LA (and possibly a special call sign) may use either QRSS or FSK but
> will be similar to ZM2E frequency. This means that third party
> monitoring could see what they get from any or all particpants, and as a
> compromise it may be best to set 60 second dot length as that is more
> likely to be the QSO attempt rate than 120 seconds (the sun comes up too
> soon!).
>
> 73, Bob ZL2CA
>
>
>
>