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; Fri, 29 May 2020 14:25:03 -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 04TLGCKE019163; Fri, 29 May 2020 17:16:18 -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 04TLGBtW019160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 29 May 2020 17:16:11 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 04TLFIbk001505 for ; Fri, 29 May 2020 17:15:20 -0400 Received: from w92expo17.exchange.mit.edu (18.7.74.71) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 29 May 2020 17:15:07 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92expo17.exchange.mit.edu (18.7.74.71) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Fri, 29 May 2020 17:15:35 -0400 Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.58) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 29 May 2020 17:15:35 -0400 Received: from MWHPR2001CA0008.namprd20.prod.outlook.com (2603:10b6:301:15::18) by SN6PR01MB4717.prod.exchangelabs.com (2603:10b6:805:d0::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.19; Fri, 29 May 2020 21:15:34 +0000 Received: from CO1NAM03FT056.eop-NAM03.prod.protection.outlook.com (2603:10b6:301:15:cafe::e) by MWHPR2001CA0008.outlook.office365.com (2603:10b6:301:15::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.17 via Frontend Transport; Fri, 29 May 2020 21:15:34 +0000 Received: from mail-ej1-f48.google.com (209.85.218.48) by CO1NAM03FT056.mail.protection.outlook.com (10.152.81.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3045.17 via Frontend Transport; Fri, 29 May 2020 21:15:34 +0000 Received: by mail-ej1-f48.google.com with SMTP id o15so3398757ejm.12 for ; Fri, 29 May 2020 14:15:34 -0700 (PDT) Received: by 2002:a54:3107:0:0:0:0:0 with HTTP; Fri, 29 May 2020 14:15:31 -0700 (PDT) From: Jason White To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 29 May 2020 14:15:31 -0700 Subject: Re: [EE] 2n3904 pulse current Thread-Topic: [EE] 2n3904 pulse current Thread-Index: AdY1/55ZWcPEDY5GSf2v9KYtkT2QUQ== Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: 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.218.48 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.48; helo=mail-ej1-f48.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=5k18i63Ui9So3OZE5Yn3UcEUaD01s6AnWiU/6f0JsWU=; b=UvkxqfX3DVxAoQPCco9eBcNpIWSK4A9qre38OR5v+gOOez5nVvodZQTiQEuSSCWhB2 y/6ILSZVSUjmjy0ACeYqalTaICi1gBpghN8qmxhbgJYO4AyRlTD9T7H7KNdsOLX6baPN KjjrTodvothEKT8sigO3gei3MHXRQJAQx9mXQ8CssAYlU4xdtcutORBm2ds17zuaW8uA F0+1iZ1onSOKk6tWplaPaFo0Jo4tIvEi87eIQZu/3AEGdY9a4wOPFUrw/TjDRlMDv2uu EF7wQMzaww6BcvuBEYAvAXIsh/1z0omjKSZTQkvY3KZGjjYwogF5jTrZd9cnk1OwiStq nCRw== authentication-results: spf=pass (sender IP is 209.85.218.48) 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;compauth=pass reason=100 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:a17:906:34c5:: with SMTP id h5mr9183671ejb.325.1590786932417; Fri, 29 May 2020 14:15:32 -0700 (PDT) x-topics: [EE] x-content-filtered-by: Mailman/MimeDel 2.1.6 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 For hobbyist work you can get away with it. Especially if you are willing to tolerate shortened component lifespan, and the risk that difficult batches of parts behave differently. For professional work: I would advise against it. NXP MMBT3904 datasheet (2004 Feb 03) (1) abs. max peak collector current is 200mA (2) on figure 2-5 as collector current approaches 200mA, current gain approaches zero. Above that current the thermal load due to low gain/poor performance gets concerning. On Friday, May 29, 2020, madscientistatlarge < madscientistatlarge@protonmail.com> wrote: > Can a 2n3904 handle 320mA pulses at less than 10% duty cycle, maximum > pulse width 1ms? I want to use them for the common cathode drivers drivi= ng > 7 segment display, 12 digits multiplexed (7 seg+DP@40mA ea. worst case). > The spec sheet says 200 mA continuous and I can't find pulse information. > Thanks. > > > Sent with ProtonMail Secure Email. > > > > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 Jason White --=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 .