Received-SPF: neutral (google.com: 193.82.116.20 is neither permitted nor denied by best guess record for domain of owner-rsgb_lf_group@blacksheep.org)
From: "Dave Sergeant" <dave@davesergeant.com>
To: rsgb_lf_group@blacksheep.org
Date: Sat, 14 Apr 2007 06:39:15 +0100
MIME-Version: 1.0
Message-ID: <46207713.9950.198A93@dave.davesergeant.com>
In-reply-to: <461FE625.15382.2FDB5E9@dave.davesergeant.com>
References: <BDEMKFCNLMIILGIFNONNOEBBCEAA.vvkooten@wanadoo.nl>, <461FE625.15382.2FDB5E9@dave.davesergeant.com>
Content-description: Mail message body
Subject: Re: LF: DI2BO
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org
Status: O

Just to report that when I came back into the shack at 2100z DI2BO 
was clearly audible to my ears, peaking 439 here in Bracknell IO91PJ. 
I was rather amused to clearly hear it send its CW id 'DI2AG' !! 
GI4DPE was also heard beaconing in normal CW around 501.15.

This maybe highlights the problem with QRSS on 500kHz. I have already 
noted slow and very deep QSB on many signals. While I was watching 
DI2BO on Argo last night I found that it would pop above my noise 
level for only 1 out of 3 or 4 callsign sequences and between that 
there was little more than the odd dot visible. When it appeared most 
but never all of a complete call was visible and it clearly peaked 
quite strong for just a few characters. If I had not known what the 
call was I would have had to listen a long time to postively identify 
it. However when it sent its ID on normal CW when listening without 
Argo later that was copyable in its entirety (admittedly wrong!).

73 Dave G3YMC


http://www.davesergeant.com