Envelope-to: dave@picks.force9.co.uk
Delivery-date: Wed, 05 Oct 2005 01:25:18 +0100
Message-ID: <001f01c5c945$4d9a2040$c401a8c0@quaycustomer>
From: "Vernall" <vernall@xtra.co.nz>
To: rsgb_lf_group@blacksheep.org
References: <000301c5c8df$f1f98150$0100a8c0@HOST>
Date: Wed, 5 Oct 2005 13:39:44 +1300
MIME-Version: 1.0
Subject: LF: Re: ZM2E LF DX
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org

Hi all,

Confirming ZM2E had an active night transmitting wise, got part of the VA7LF
call sign and there were problems for R6L (RU6LA special call sign)
transmitting when it came to QSO time.

Around 0840 UTC we received quite a good 7 at 120 second dot length and
elements either side fitted what would be VA7LF, but that part call sign was
the best we got in all the various receiving times for ZM2E before Gulf
Island sunrise.

When it came time to try R6L we were advised by HF liaison that R6L had
problems, and we should start the QSO rather than the earlier arrangement
that R6L would start at 1500 UTC.  We later got advice to go to beacon mode
so at 1637 UTC we set the message to ZM2E ZM2E .... and got to bed earlier
than expected.  The beacon ran till well after ZL sunrise.

>From the other reports it would seem DX propagation was "not good".

We are back tonight for another bite at the cherry.

73, Bob ZL2CA and Mike ZL4OL