Return-Path: Received: (qmail 13516 invoked from network); 28 Apr 2001 20:32:07 -0000 Received: from unknown (HELO murphys-inbound.servers.plus.net) (212.159.14.225) by excalibur.plus.net with SMTP; 28 Apr 2001 20:32:07 -0000 Received: (qmail 17243 invoked from network); 28 Apr 2001 20:32:06 -0000 Received: from unknown (HELO post.thorcom.com) (212.172.148.70) by murphys with SMTP; 28 Apr 2001 20:32:06 -0000 Received: from majordom by post.thorcom.com with local (Exim 3.16 #2) id 14tbHl-0005Uo-00 for rsgb_lf_group-outgoing@blacksheep.org; Sat, 28 Apr 2001 21:25:45 +0100 Received: from tomts8.bellnexxia.net ([209.226.175.52] helo=tomts8-srv.bellnexxia.net) by post.thorcom.com with esmtp (Exim 3.16 #2) id 14tbHk-0005Uj-00 for rsgb_lf_group@blacksheep.org; Sat, 28 Apr 2001 21:25:44 +0100 Received: from server1 ([216.209.110.86]) by tomts8-srv.bellnexxia.net (InterMail vM.4.01.03.16 201-229-121-116-20010115) with SMTP id <20010428202439.BIBK26551.tomts8-srv.bellnexxia.net@server1> for ; Sat, 28 Apr 2001 16:24:39 -0400 Message-ID: <004701c0d021$0c66b650$0a00a8c0@ThreeLakes.ca> From: "Larry Kayser" To: rsgb_lf_group@blacksheep.org References: <3AE8196D.2654.C681E0@localhost> Subject: LF: Re: Re: Wolf Tests Date: Sat, 28 Apr 2001 16:23:06 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Sender: Mike Dennison et all: > > No comments from you lately so I will reiterate, I am sending you WOLF every > > night from 01 utc to 02 utc...........137.7894 is the TX freq > > Larry > > VA3LK >Does anyone know of a way to make a WAV file on a > timer? I suspect by now this has been solved. > Secondly - and this will cause some discussion (smoke!) I hope not, we dont need any of that kind of discussion as I see it...... - there is > considerable wideband noise at the top of the band very late at night. It is > usually attributed to the Luxemburg Effect. In the past it has caused little > problem as (1) we have used only QRS which by virtue of its bandwidth has a > high level of immunity to wideband QRM, and (2) there is very little activity at > the times the noise on on - This is a regretable situation. >note that VE1ZZ used a much lower frequency. I > think this will make it much more difficult to receive a WOLF transmission than > QRSS. The 136.5 frequency as used by VE1ZZ earlier this year was the subject of extensive discussion that was not complimentary as to the location with the European 136 Band Plan. I choose not to tempt fate by transmitting in that area. >I suggest that Larry uses a frequency closer to the 'data' allocation, > say 137.400kHz. "'data' allocation" that must be part of a European LF Band Plan that apparently does not consider North American requirements. There is no way I would transmit 400 Hz from CFH, that would be an unwise move even if I did it once just for fun - it would not be taken well. > I am keen to listen for Larry but these two obstacles are making it not > worthwhile at the moment. I did operate on 137.75 and that was a problem because of the European LF Band Plan, I moved, based on a strong recommendation up to 137.790. 137.790 is clear in ZL and VK and I do not have at the moment a way to remotely change the DDS frequency in any case. If I was to move over 1 kHz I would have to retune the loading coil for optimum output and while I now have a tuning mechanism to do this I do not have a driver motor that will survive being exposed to the elements. If the WOLF transmissions are not going to be readable in Europe we have the option to change the time, or add another hour at a different time, or the digital session can be ended if it is not being used by anyone. Comments? Larry VA3LK