Received: from PCH.mit.edu (18.7.21.50) by mail.efplus.com (192.168.0.8) with Microsoft SMTP Server (TLS) id 8.3.485.1; Thu, 12 Aug 2021 22:21:50 -0700 Received: from PCH.MIT.EDU (localhost.localdomain [127.0.0.1]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17D5CEVK004217; Fri, 13 Aug 2021 01:13:24 -0400 Received: from outgoing-exchange-7.mit.edu (OUTGOING-EXCHANGE-7.MIT.EDU [18.9.28.58]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 17D5CCWC004213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Fri, 13 Aug 2021 01:12:12 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 17D5CCF7003237 for ; Fri, 13 Aug 2021 01:12:12 -0400 Received: from w92expo31.exchange.mit.edu (18.7.74.43) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 13 Aug 2021 01:12:11 -0400 Received: from oc11exhyb7.exchange.mit.edu (18.9.1.112) by w92expo31.exchange.mit.edu (18.7.74.43) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 13 Aug 2021 01:12:11 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.106) by oc11exhyb7.exchange.mit.edu (18.9.1.112) with Microsoft SMTP Server (TLS) id 15.0.1497.23 via Frontend Transport; Fri, 13 Aug 2021 01:12:11 -0400 Received: from MW4PR03CA0195.namprd03.prod.outlook.com (2603:10b6:303:b8::20) by PH0PR01MB6312.prod.exchangelabs.com (2603:10b6:510:a::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.14; Fri, 13 Aug 2021 05:12:09 +0000 Received: from CO1NAM11FT044.eop-nam11.prod.protection.outlook.com (2603:10b6:303:b8:cafe::c5) by MW4PR03CA0195.outlook.office365.com (2603:10b6:303:b8::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.13 via Frontend Transport; Fri, 13 Aug 2021 05:12:09 +0000 Received: from mail-vs1-f49.google.com (209.85.217.49) by CO1NAM11FT044.mail.protection.outlook.com (10.13.175.188) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4415.16 via Frontend Transport; Fri, 13 Aug 2021 05:12:09 +0000 Received: by mail-vs1-f49.google.com with SMTP id h7so5462526vso.13 for ; Thu, 12 Aug 2021 22:12:09 -0700 (PDT) From: K S To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 12 Aug 2021 22:12:00 -0700 Subject: [EE] Tek DSO display issue? Thread-Topic: [EE] Tek DSO display issue? Thread-Index: AdeQAx9cKPMMU86QQVKzR02y19/s0w== Message-ID: List-Help: List-Subscribe: , List-Unsubscribe: , Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-AuthSource: TS500.efplus4.local X-MS-Has-Attach: X-Auto-Response-Suppress: All X-MS-Exchange-Organization-SenderIdResult: Pass X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of gmail.com designates 209.85.217.49 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.217.49; helo=mail-vs1-f49.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=+vHWN6r3mqvhKXCy7kumnOrx56jMvysUe5VVFxhRpYk=; b=R8dfqfge53QZr0RjBz/YqkNboxT6v6+OMVA3EJExwxEv19A2AGvWOfuJIxChb/Z4qy mD2dfD1R8qeKMpVuZRAfdsFYxE+oIzEsa+buJ5uHU8aLPjSzBmHP+S7ffJkcCkEn2+O+ JLyin8bqo3ATZNtB+NMtoMj2wK67IBsR0vfNHMJ+k9gTa3IUnkPLkGazyYfLRMCV1yfm uIDA6Fyz0vmziV7kQmy4MPAuLV5tddfQyOYuRFEMVJprFvi8ATjyKGaFlVQLqmvYjASs e4ClummOXqJ/IusmUPnPgxajwkW8nYPnnUbRQxNsV5vJEVYHKwagGtZ94SjqQkXhQqu4 7I9A== authentication-results: spf=pass (sender IP is 209.85.217.49) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=gmail.com; mit.edu; dmarc=pass action=none header.from=gmail.com; errors-to: piclist-bounces@mit.edu list-id: "Microcontroller discussion list - Public." list-post: x-beenthere: piclist@mit.edu x-mailman-version: 2.1.6 x-received: by 2002:a67:e957:: with SMTP id p23mr275334vso.13.1628831528234; Thu, 12 Aug 2021 22:12:08 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Help me PICLIST! I'm working on a buck converter and the main switching FET is heating up plenty. To see what's going on I am measuring Vgs (purple) and Vds (blue) with my trusty 20year old Tek TPS2014 - 4 isolated channels, nice! See pic here: https://we.tl/t-t4t2USmkIU Vgs reaches just over 5V. I'm not too happy about that but it's what the chip (MP24830) gives me and it should be just enough. To see what I'm losing across in the FET I'm measuring Vds and hoping it's low when the FET is on. So there are 2 shots in the pic, one with the vertical scale set to 5V and the other at 2V/div. The 5V trace looks beautiful, as expected. The 2V trace looks hmmm. Vds is shown clipped in both cases; it reaches 48V. I'm noticing lots of funnies when I switch from 5V to 2V. I thought I'd try something else: rather than measure volts directly across the drain-source I thought I'd measure both the drain and source volts w.r.t. GND and use the scope math function to get the difference. With scales set to 5V/div I get what I'm expecting, with 2V the trace disappears all together! I then tried this last experiment on a mate's scope, also a Tek, TDS2022B, and got similar results. (I did try across the FET itself with his scope but was getting FET misfirings - I suspect that some small capacitive loading from this non-isolated scope's inputs are causing some issues - I have many more pics if anyone is interested). Anyone have any idea what might be happening here? TIA, Kris. --=20 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .