Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by mtain-dc05.r1000.mx.aol.com (Internet Inbound) with ESMTP id 9BBA238000096; Sun, 19 Feb 2012 10:41:35 -0500 (EST) Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1Rz8sE-00054T-Og for rs_out_1@blacksheep.org; Sun, 19 Feb 2012 15:40:26 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1Rz8sE-00054K-3B for rsgb_lf_group@blacksheep.org; Sun, 19 Feb 2012 15:40:26 +0000 Received: from out1.ip01ir2.opaltelecom.net ([62.24.128.237]) by relay1.thorcom.net with esmtp (Exim 4.63) (envelope-from ) id 1Rz8sC-00047g-Nn for rsgb_lf_group@blacksheep.org; Sun, 19 Feb 2012 15:40:26 +0000 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFAI0XQU9Ok87r/2dsb2JhbABEiU2oW4EIgW4FAQEEAQgBAQNJAhwKBgEBAwUCAQMRBAEBCiUUAQQaBhYIBhMKAQICAQGHbwO4TIt/Cw8WAQE6AwIBAQGDX1iDHgSIG4U6mk8 X-IronPort-AV: E=Sophos;i="4.73,446,1325462400"; d="scan'208";a="381066497" Received: from host-78-147-206-235.as13285.net (HELO xphd97xgq27nyf) ([78.147.206.235]) by out1.ip01ir2.opaltelecom.net with SMTP; 19 Feb 2012 15:40:18 +0000 Message-ID: <002201ccef1c$c8321570$0401a8c0@xphd97xgq27nyf> From: "mal hamilton" To: References: <002a01ccee25$c2416cd0$0401a8c0@xphd97xgq27nyf> <4F3F800B.2000201@xs4all.nl> <003e01ccee2d$49b17f50$0401a8c0@xphd97xgq27nyf> <007f01ccee6c$3eca0f50$0401a8c0@xphd97xgq27nyf> <6ADDBBA8CD0B4DC38D7950C75294B505@AGB> <004601cceee8$7566da80$0401a8c0@xphd97xgq27nyf> <2AB0A82B2A6F4A0ABCD855D8AB420777@lindavideo> <000f01cceef9$bbcbe130$0401a8c0@xphd97xgq27nyf> <843575FA34474CE38D153A1E6BAB30B9@JimPC> Date: Sun, 19 Feb 2012 15:40:17 -0000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Score: 0.0 (/) X-Spam-Report: autolearn=disabled,none Subject: Re: LF: opera 500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on post.thorcom.com X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63 X-SA-Exim-Scanned: Yes Sender: owner-rsgb_lf_group@blacksheep.org Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group X-SA-Exim-Rcpt-To: rs_out_1@blacksheep.org X-SA-Exim-Scanned: No; SAEximRunCond expanded to false x-aol-global-disposition: G X-AOL-SCOLL-SCORE: 0:2:426474432:93952408 X-AOL-SCOLL-URL_COUNT: 0 x-aol-sid: 3039ac1d40854f41182e7027 X-AOL-IP: 195.171.43.25 X-AOL-SPF: domain : blacksheep.org SPF : none Jim es Co I have made no effort so far to investigate the problem since I do not use Opera much. I do have plenty of decoupling both in the OSC/DIVIDER stages also the LT es HT supplies to the TX MODULE. I have several cables running into the shack from various antennas which are quite a distance away and it could well be that one is picking up the RF even at a vy low level and leaking it into the modem. The modem recovers quickly after a transmission but seemingly not quick enough to get a result from the database. It looks like this needs an immediate response during transmission or immediately afterwards. It means I cannot see who has copied my transmission when I stop. I did think of putting the divider es driver into a screened box with all power leads going to es from decoupled. That might cure it. The osc running at 5 Mhz (Kenwood VFO 520) is in a screened box and not a problem. 73 de mal/g3kev ----- Original Message ----- From: "James Moritz" To: Sent: Sunday, February 19, 2012 1:48 PM Subject: Re: LF: opera 500 > Dear Mal, LF Group, > > If the internet connection falls over when only the PA driver is operating > as you descibed, the modem must be extraordinarily EMI-sensitive. I would > suspect there is some problem with cabling and/or decoupling of the TX in > order to cause this kind of failure. Since Opera is just a variant of QRSS > as far as the radiated signal goes, you would certainly expect similar > behaviour when transmitting QRSS. But you don't seem to have much trouble > downloading pictures of your QRSS signal from all the various grabbers and > uploading them to this reflector, so I wonder if the problem really is RF > related? > > Cheers, Jim Moritz > 73 de M0BMU > >