Message-ID: <002a01c08aad$279f4ae0$02ca28c3@ericadodd>
From: "g3ldo" <g3ldo@ukonline.co.uk>
To: rsgb_lf_group@blacksheep.org, 
 "Dexter McIntyre w4dex" <dmcintyre@att.net>
References: <000901c08a1e$9ad55ca0$54c928c3@ericadodd> <3A75B7B5.DEAD0B45@att.net> <001a01c08a41$594b7a80$f77f28c3@ericadodd> <3A75F01A.2AE1C355@att.net> <000801c08a51$12f983a0$a9ca28c3@ericadodd> <3A760DA7.860B7DE@att.net>
Subject: Re: LF: beacon, Monday night
Date: Tue, 30 Jan 2001 10:46:09 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Sender: <majordom@post.thorcom.com>


Dexter McIntyre w4dex said:

> I am in 30 second dot mode with Argo so I see 6 hz.  At about 0028 UT I
> saw a nice 30 second line at 135912.2 hz.  That's all so far.  I will
> put Argo on automatic after 0500 UT if you will be transmitting all
> night.

I transmitted in beacon mode, just sending my callsign, QRSS, 10 second dots
from 2340 until 0035, with short breaks for monitoring VE1ZZ.
He was visible at around midnight but although the signal was good the QRN
level was very high.

I had problems with frequency control because the outside shack temperature
dropped rather dramatically and I could not initially maintain the frequency
within 3Hz. At around 2315 the temperature stabilized together with the
frequency, which finished up at 135912.2Hz according to my frequency
counter. The transmitter was switched off at 0035 when I went to bed.

In my limited experience of marginal QRSS signals I have found that slight
imperfections (characteristics) went a long way to initial identification.
This is because the signal is embedded in a mass of 'perfect', and often
dashed Loran lines.

Regards,
Peter, G3LDO

<g3ldo@ukonline.co.uk>