Return-Path: Received: from post.thorcom.com (post.thorcom.com [195.171.43.25]) by klubnl.pl (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id w8IBFMYQ023343 for ; Tue, 18 Sep 2018 13:15:23 +0200 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1g2DtW-0004OW-KJ for rs_out_1@blacksheep.org; Tue, 18 Sep 2018 12:10:14 +0100 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1g2DtW-0004ON-9o for rsgb_lf_group@blacksheep.org; Tue, 18 Sep 2018 12:10:14 +0100 Received: from mail-wm1-x335.google.com ([2a00:1450:4864:20::335]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91_59-0488984) (envelope-from ) id 1g2DtU-00076l-A6 for rsgb_lf_group@blacksheep.org; Tue, 18 Sep 2018 12:10:13 +0100 Received: by mail-wm1-x335.google.com with SMTP id 207-v6so2209889wme.5 for ; Tue, 18 Sep 2018 04:10:12 -0700 (PDT) X-DKIM-Result: Domain=gmail.com Result=Good and Known Domain DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:reply-to:message-id:to:subject:in-reply-to:references :mime-version:content-transfer-encoding; bh=xTRbusLvWFVWJv9Zb4wTGd+sa3iBK5Yz+PfdseyXUVQ=; b=iTQ3kP7rfJStxQOG/ZRKFVf9Z4ehWZ1CIl3WASqP+jON7Y5gOufOuF3toqRrj8ISOK WOgCNeiAuroCRqziZUG1IcSzwxEFViWZ3RVbeg3QrmaB8ucxz3LGWQH9rMj3SDT0JPmC 8jWGWMc8TZxI9GSfcrOG30HeptfHbUZP2oUSO+eAgSEjW2lISeBIWnl5vBR4EG8Gu8Nx pNsjd9Bs3Pk0caWSBxBWojAHWS8VqyMC0tbA8VqCVFLhctDAaaUJYGrhs4JE/BriCN3B ZzcpvAuvAKtMxmDiTcbS7bNw5PUZH+3/jyOskuciob1ZW2JL6Ots3N+S3Xj57JgUSzzq Z3Ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:reply-to:message-id:to:subject :in-reply-to:references:mime-version:content-transfer-encoding; bh=xTRbusLvWFVWJv9Zb4wTGd+sa3iBK5Yz+PfdseyXUVQ=; b=Kg9WzvjFz5j5RloP0wHYxcP+pNVqCwnhL3rx+BCZ8kBvW6gNvV2qXXP3Km7s8pxcFT 6zczk2aUAMOpobZ5puu8W6vpodh2gLaY/LPbxN3R4HLwtzt/6V4o3TJDuQuB7jaKbRAL w5D+NUhNxe1sq+KMByuSWO0kAmK8aj3oQU2BQitdf5rvh8+AJcf0XgjgJ31zldFIqsIK OGTk/O8T1NDPj9WBp8wyXtg09ws8rLZqzRYol5TCzSMjd+7kgH+cb/lKYm5iVQnlsKLr BuwXRfGj30ufRtbe9BzSRQaMg4DaxeafgDB0eqMHp/WkaLmyW/xZQTwxnZLum8NKAHwb w3ww== X-Gm-Message-State: APzg51DW3/BD74BVjueNRkTfsY37/QepnrszLsuyDzUiGC5NDJOetaQL vV+AWBd7/scYmuCXiIMqBBt3Rp5e X-Google-Smtp-Source: ANB0VdZJPUOLhzQX3IfOUXxUFkYMi5vQNr5ZSEtCVwMoQ2jeFaq2m5BIX0eW04h4FO7TjZzHUw1Jjg== X-Received: by 2002:a7b:c10c:: with SMTP id w12-v6mr15508271wmi.132.1537269011151; Tue, 18 Sep 2018 04:10:11 -0700 (PDT) Received: from OfficeWin7.lan (82-70-254-222.dsl.in-addr.zen.co.uk. [82.70.254.222]) by smtp.gmail.com with ESMTPSA id 198-v6sm2086242wmm.0.2018.09.18.04.10.10 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 18 Sep 2018 04:10:10 -0700 (PDT) Date: Tue, 18 Sep 2018 12:10:09 +0100 From: Chris Wilson X-Priority: 3 (Normal) Message-ID: <19864612.20180918121009@gmail.com> To: N1BUG In-Reply-To: References: <1402307201.20180918094016@gmail.com> <31f7c601-0496-7a6a-144e-86e7e3eaff0c@n1bug.com> <1405681597.20180918113832@gmail.com> MIME-Version: 1.0 X-Spam-Score: 0.0 (/) X-Spam-Report: Spam detection software, running on the system "relay1.thorcom.net", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see @@CONTACT_ADDRESS@@ for details. Content preview: Hello N1BUG, Tuesday, September 18, 2018, 11:58:28 AM, you wrote: > On 09/18/2018 06:38 AM, Chris Wilson wrote: [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [2a00:1450:4864:20:0:0:0:335 listed in] [list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (dead.fets[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Scan-Signature: 6ffbd2c9950b634d6cc91f9565b01a8b Subject: Re: LF: Re: And again! Content-Type: text/plain; charset=us-ascii 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.8 required=5.0 tests=PRIORITY_NO_NAME 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 Hello N1BUG, Tuesday, September 18, 2018, 11:58:28 AM, you wrote: > On 09/18/2018 06:38 AM, Chris Wilson wrote: >> Hellish noise last night here too, but you made it through. Have you >> increased power? > Not since July when I got the new PA running. If it's still noisy > there and you are hearing me, perhaps during the quiet months I will > be strong enough for that 5 minute JT9 QSO. ;-) > Paul I certainly look forward to trying! I asked this question on a couple of forums is it something you would have looked into paul? With devices like this, (linked to below), limited to a max of 36V how do you apply the technology to say a Class D FET ended RF amp running on 60v or even rectified 240V mains? And secondly, with the amp powered, when a signal is applied, let's say the digital amateur mode, WSPR commences, there is a high current for a short time. How do you allow for this yet provide effective over current protection for rapidly failing devices like FET's? Thanks http://www.ti.com/product/INA300 -- Best regards, Chris mailto:dead.fets@gmail.com