Return-Path: Received: (qmail 12617 invoked from network); 3 Oct 1999 06:42:31 +0100 Received: from unknown (HELO magnus.force9.net) (195.166.128.27) by guiness.force9.net with SMTP; 3 Oct 1999 06:42:31 +0100 Received: (qmail 24526 invoked from network); 3 Oct 1999 05:41:47 -0000 Received: from unknown (HELO post.thorcom.com) (212.172.148.70) by magnus.plus.net.uk with SMTP; 3 Oct 1999 05:41:47 -0000 Received: from majordom by post.thorcom.com with local (Exim 3.02 #1) id 11XeAd-0004rN-00 for rsgb_lf_group-outgoing@blacksheep.org; Sun, 03 Oct 1999 06:26:51 +0100 Received: from dh-img-rel-1.compuserve.com ([149.174.206.132] helo=hpdmraaa.compuserve.com) by post.thorcom.com with esmtp (Exim 3.02 #1) id 11XeAY-0004rH-00 for rsgb_lf_group@blacksheep.org; Sun, 03 Oct 1999 06:26:46 +0100 Received: (from mailgate@localhost) by hpdmraaa.compuserve.com (8.8.8/8.8.8/HP-REL-1.2) id BAA28507 for rsgb_lf_group@blacksheep.org; Sun, 3 Oct 1999 01:26:40 -0400 (EDT) Received: from dave (host212-140-126-20.host.btclick.com [212.140.126.20]) by hpdmraaa.compuserve.com (8.8.8/8.8.8/HP-REL-1.2) with SMTP id BAA28487 for ; Sun, 3 Oct 1999 01:26:31 -0400 (EDT) Message-ID: <000001bf0d5f$b206af60$147e8cd4@dave> From: "Dave Sergeant" To: rsgb_lf_group@blacksheep.org References: <004801bf0c5b$78aca1c0$23088cd4@default> Subject: LF: Re: re Dave's Comment on filters Date: Sat, 2 Oct 1999 15:27:03 +0100 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.00.2314.1300 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: >From Dave G3YMC I was about to reply direct to Alan about his receiver bandwidth suggestions, but other mails now demand a reply to the reflector. Nick G4WHO sums it up very nicely when he says that the theoretical improvement is for noise considerations only. This assumes you are listening to a single signal on an otherwise unoccupied band. In this case there will be little difference between the 500Hz signal and 350Hz. However we live in a real world, with often several strong in-band signals and the weak one we want to copy among them. For this purpose the bandwidth and skirt response is the most important thing. Frequently at weekends it is impossible to find a clear frequency in the normal CW part of the band when using normal bandwidth CW filters. My 350Hz Yaesu filter is rather lacking in slope response, such that for instance when G3XTZ's signal is on 136.0 I have to tune up to 136.5 to totally clear it. Most HF transceivers are configured for upper sideband CW. An audio filter may help (I have not tried one) but AGC effects will still reduce sensitivity for copying weak signals in the skirts of stronger ones. As a long time HF CW operator, both in contests and DX pile up chasing, I could never go back to using an SSB filter for CW, it is just literally as wide as a barn door. Like on HF when it is the norm to have 500Hz or less, it should also be the norm on 136. However though I know some operators have much narrower filters than that, when I transmit I always try to avoid transmitting too close to others, assuming if it is too close with my filter it will be too close for the other amateur's receiver as well. Not that I am a big enough signal to cause much QRM! Note that most good CW operators tend to tune for a note of 600Hz or below, as copyability and human ear filtering is better for lower notes. Those of you attending the HF convention next weekend may like to try your hand at the CW pile up competition, which will give you a feel about what real CW operating is like! I am also rather puzzled by the emphasis given to DCF39. With a normal CW filter it is so far out of the band that it simply doesn't come into the equation (unless you have receiver overload problems that is). 73s Dave G3YMC sergeantd@compuserve.com http://ourworld.compuserve.com/homepages/sergeantd