Return to KLUBNL.PL main page

rsgb_lf_group
[Top] [All Lists]

Re: LF: VLF traces O/T sorry

To: <[email protected]>
Subject: Re: LF: VLF traces O/T sorry
From: "mal hamilton" <[email protected]>
Date: Sat, 12 Mar 2011 16:58:22 -0000
References: <006301cbe00d$762f0220$0401a8c0@xphd97xgq27nyf><D347A1D1854746FE92B7E06C0C286E0D@White><001501cbe091$863ebf50$0401a8c0@xphd97xgq27nyf><5DA936C746C7432AA6E833B9CACE239F@AGB><[email protected]><[email protected]><00d801cbe0d0$f0a67010$0401a8c0@xphd97xgq27nyf> <[email protected]>
Reply-to: [email protected]
Sender: [email protected]
See my previous message addressed to Tracy this applies also to u
g3kev
 
----- Original Message -----
Sent: Saturday, March 12, 2011 4:43 PM
Subject: Re: LF: VLF traces O/T sorry

Dear Mal,

As Marcus said yesterday, why not download a suitable version of a Spectrum Lab .usr file locked to GBZ and set about looking for some of these very weak VLF signals you've not copied yet? G3XIZ is probably copyable by you in a bandwidth that will not take that long to display. Chris would appreciate the report. Likewise for some of the other less strong European VLF stations.

If you need a suitable .usr file several people here will send you one. It is not hard to run a very stable and frequency accurate system - even I managed it with my crap set-up here, so for an expert like you it should be easy.

We all understand you prefer real QSOs with good IDs but please, give it a go. You will enjoy it.

73s
Roger G3XBM



On 12 March 2011 16:17, mal hamilton <[email protected]> wrote:
Some of you would believe anything !!!!!!!!!!!!! I expect you go every Sunday and Wednesdays for Confession
Another version is nailed to the PLUS sign for those that cannot read
 
 
 
 
----- Original Message -----
Sent: Saturday, March 12, 2011 3:25 PM
Subject: Re: LF: VLF traces O/T sorry

Hi Gary, Graham (Billy) LF

No very radio that, I prefer Luke 14:28, (and it's not nail him to a torture stake)

Eddie

On 12/03/2011 15:09, Gary - G4WGT wrote:
Graham, LF,

It looks pretty close to me, are you some kind of "book worm" finding/knowing these quotes ?? Hi.

73, Gary - G4WGT.

On 12 March 2011 11:47, Graham <[email protected]> wrote:


Acts 20:35   may  be  applicable  in this case ?

--------------------------------------------------
From: "mal hamilton" <[email protected]>
Sent: Saturday, March 12, 2011 8:43 AM
To: <[email protected]>
Subject: Re: LF: VLF traces


Yes Markus
But I do not intend to wait hours, weeks and months to observe a signal at
rediculous narrow bandwidths. My limit of time is QRS 60 and preferably
Faster.
We need the transmitting stations to increase power ie more ERP then there
would be no need for uH bandwidths and year long dashes hi
de mal/g3kev

----- Original Message -----
From: "Markus Vester" <[email protected]>
To: <[email protected]>
Sent: Friday, March 11, 2011 9:30 PM
Subject: Re: LF: VLF traces


Dear Mal,

with all due respect, I very much disagree here.

Whenever I see a clear trace appear at the right time and within a milliHz
of a confirmed and correctly calibrated frequency, I have hardly a doubt
about the validity of the reception. Even more so if the transmission can
be
verified by comparison to a calibrated grabber in another location.

It seems that the G3KEV antenna does have excellent sensitivity at VLF. It
would be fantastic if you could augment that with a stable, properly
calibrated, and narrowband reception system. SpecLab has made that so easy
now - throw out the wildly drifting "receiver", connect your antenna
directly to the soundcard instead, lock to one of your MSK neighbours (GBZ
or GQD), and your in the game.

Best regards,
Markus (DF6NM)


From: mal hamilton
Sent: Friday, March 11, 2011 5:57 PM
To: rsgb
Subject: LF: VLF traces


I can see a couple of vy weak traces around 8970 but this is no guarantee
who it might be because there is no ID. Frequency alone is not a VALID
report- it could be anything.
G3KEV














--
g3xbm-qrp.blogspot.com/
www.g3xbm.co.uk
www.youtube.com/user/g3xbm
G3XBM   GQRP 1678    ISWL G11088
<Prev in Thread] Current Thread [Next in Thread>