To: rsgb_lf_group@blacksheep.org References: <17879303.1126259836649.JavaMail.www@wwinf3201> Date: Mon, 3 Oct 2005 21:08:30 +1300 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: LF: 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

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