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 x1Q0bpFH028486 for ; Tue, 26 Feb 2019 01:37:59 +0100 Received: from majordom by post.thorcom.com with local (Exim 4.14) id 1gyQek-0006F3-Ba for rs_out_1@blacksheep.org; Tue, 26 Feb 2019 00:31:34 +0000 Received: from [195.171.43.32] (helo=relay1.thorcom.net) by post.thorcom.com with esmtp (Exim 4.14) id 1gyQdl-0006Eu-LF for rsgb_lf_group@blacksheep.org; Tue, 26 Feb 2019 00:30:33 +0000 Received: from resqmta-ch2-11v.sys.comcast.net ([2001:558:fe21:29:69:252:207:43]) by relay1.thorcom.net with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1gyQdh-0007L0-Rq for rsgb_lf_group@blacksheep.org; Tue, 26 Feb 2019 00:30:31 +0000 Received: from resomta-ch2-02v.sys.comcast.net ([69.252.207.98]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id yPI7gtBcpdcv3yQdegsz0o; Tue, 26 Feb 2019 00:30:26 +0000 X-DKIM-Result: Domain=comcast.net Result=Signature OK DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1551141026; bh=d3e1QiLt3c074y2zp9eM/B2cfc+CeMIoIiYlZAvVtFM=; h=Received:Received:From:Subject:To:Content-Type:Date:Message-ID; b=d+9HOBEkZYzKhjBtNvjzvAWkXreBjmKlK373YkiPOe01XkHcCiFn7xIzHSQrRDSXI FA1rX02gbKty6DnNNCx0QzbdlvJQiNwI8tbS9PipwgIPPL9QOrMDpu6KSpleKpS3E7 TB8mGas0zJ7T5JnFjdZQCBSuApq1QYR1BAfHr94Mq/mxySrsPLumu43IKOPLC0U8rz twpRcYY4pxJRmvGCOeQN4U7037U4o5J8rw6Hz29NMMpHRIPjHA6HfkY3qlbf/EiBoJ p/y4SaWATgSCxI/hu+HDYxgr8CkyBsCHPkUuISd3CpslL2BRA/ZYcK/DE0DQ0+N0fh eSqZdtafy5OLg== Received: from Optiplex980-PC ([73.4.253.141]) by resomta-ch2-02v.sys.comcast.net with ESMTPSA id yQdcgi3ye01mcyQddgjtFw; Tue, 26 Feb 2019 00:30:25 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedutddrudekgddvvdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffuvfgtgfhffffkjggfsehtqhertddtreejnecuhfhrohhmpedfjhhruhhsghhrohhvvgestghomhgtrghsthdrnhgvthdfuceojhhruhhsghhrohhvvgestghomhgtrghsthdrnhgvtheqnecuffhomhgrihhnpegthhhrihhsfihilhhsohhnrdhtvhenucfkphepjeefrdegrddvheefrddugedunecurfgrrhgrmhephhgvlhhopefqphhtihhplhgvgielkedtqdfrvedpihhnvghtpeejfedrgedrvdehfedrudeguddpmhgrihhlfhhrohhmpehjrhhushhgrhhovhgvsegtohhmtggrshhtrdhnvghtpdhrtghpthhtoheprhhsghgspghlfhgpghhrohhuphessghlrggtkhhshhgvvghprdhorhhgnecuvehluhhsthgvrhfuihiivgeptd X-Xfinity-VMeta: sc=0;st=legit From: "jrusgrove@comcast.net" To: rsgb_lf_group@blacksheep.org References: <942860C848184BA2A0A9103E0EE56DF7@DELL4> Date: Mon, 25 Feb 2019 19:30:24 -0500 Message-ID: <1UTEEgOcyQ.DAejAuRZtn9@optiplex980-pc> In-Reply-To: <942860C848184BA2A0A9103E0EE56DF7@DELL4> User-Agent: OEClassic/2.9 (Win7.7601; P; 2018-07-03) X-Spam-Score: -0.7 (/) 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 the administrator of that system for details. Content preview: Chris Thanks for the waveforms ... very informative. Sure looks like something is triggering the input of the amplifier and thus causing the problem. Since the problem doesn't exist with U3S's (which generates the various modes internally) driving the amplifier (either directly or through a frequency doubler) one has to wonder what the difference i [...] Content analysis details: (-0.7 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low trust [2001:558:fe21:29:69:252:207:43 listed in] [list.dnswl.org] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (jrusgrove[at]comcast.net) X-Scan-Signature: b4085bc26841e34d79a2f3beb8f287b1 Subject: Re: LF: Class D current spikes Content-Type: text/plain; charset=utf-8 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by klubnl.pl id x1Q0bpFH028486 Chris Thanks for the waveforms ... very informative. Sure looks like something is triggering the input of the amplifier and thus causing the problem. Since the problem doesn't exist with U3S's (which generates the various modes internally) driving the amplifier (either directly or through a frequency doubler) one has to wonder what the difference is between the U3S and the other exciter setups that cause the problem. The fact that the U3S / amplifier combination works correctly would argue that the 'problem' is likely not the amplifier. The one thing that the non U3S setups have in common is that the modes are generated by software / computer / sound card. Think the first step in tracking down the problem would be to see if there are any unexpected outputs from the soundcard that are causing the problem. When you get a chance maybe you can capture waveforms of the sound card output up to and after the end of a transmission. Assume that you have disabled all 'computer sounds' on the machines that are supplying audio for the various modes? Jay W1VD ----- Original Message ----- From: "Chris Wilson" To: "N1BUG" Sent: Monday, February 25, 2019 5:02 PM Subject: Re: LF: Class D current spikes > > > Hello Paul. everyone > > A series of overlapping scope captures at end of WSPR > sequence with expensive high voltage / current Wolfspeed FET's > that usually survived, into the antenna and into a 10kW dummy load, taken > after the choke and also at the drains of the W1VD amp. Driver TS-590 > / W1VD doubler, and W1VD amp ( end part of another circuit). U3S does > not show anything like this oscillating end to a TX sequence.: > > http://www.chriswilson.tv/wolfspeed-choke-and-drain-50v-smps-antenna.zip > > http://www.chriswilson.tv/wolfspeed-choke-and-drain-50v-smps-dummy-load.zip > > Green trace drain, yellow after the choke. > > > > Monday, February 25, 2019, 4:34:05 PM, you wrote: > >> Chris, LF, > >> Yes, although I run mine differently. I use the full output of the >> U3S into a doubler. I have run WSPR, JT9, and DFCW from the U3S >> without having any problems. I have also extensively used CW ID with >> the U3S and amp without problems. Yet both other exciters blow FETs >> at the instant RF stops. > >> Chris, I know you are busy but if you get a chance I would like to >> see those scope captures. I thought I had it figured out that this >> is a voltage mode amp and should be seeing current spikes, but maybe >> I still have that wrong! If they are voltage spikes that may be >> easier to control. > >> One thing I would like to learn more about is why do the drivers >> leave one phase high for a longer period than a half cycle when RF >> stops. What causes this? Is this only with specific FET drivers or >> are all of them prone to this? > >> 73, >> Paul > > >> On 2/25/19 11:13 AM, Eric NO3M wrote: >>> Chris, et.al. >>> >>> N1BUG relayed the same information regarding the U3S and class-D amp >>> behavior, so your observation is not a one off... >>> >>> >>> >>>> >>>> I have a series of scope captures from my W1VD amp showing huge >>>> voltage spikes on the FET drains at the end of WSPR and especially >>>> OPERA TX sequences. I suspected inductance was the cause. In fact I >>>> try not use OPERA at high power as i am pretty sure to kill a FET >>>> after a few sessions... Oddly (although I hope msomeone more >>>> knowlegeable has the answer), using WSPR from my U3S direct from CLK0 >>>> of th Si535a or whatever it is never causes these spikes... Or at >>>> least they are well contained. > > > > > -- > Best regards, > Chris mailto:dead.fets@gmail.com > >