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; Tue, 7 Apr 2020 20:31:11 -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 0383LDEa009932; Tue, 7 Apr 2020 23:21:42 -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 0383LBQS009929 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 7 Apr 2020 23:21:11 -0400 Received: from w92exedge4.exchange.mit.edu (W92EXEDGE4.EXCHANGE.MIT.EDU [18.7.73.16]) by outgoing-exchange-7.mit.edu (8.14.7/8.12.4) with ESMTP id 0383KlUc001014 for ; Tue, 7 Apr 2020 23:20:56 -0400 Received: from oc11expo11.exchange.mit.edu (18.9.4.16) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Tue, 7 Apr 2020 23:20:51 -0400 Received: from oc11exhyb6.exchange.mit.edu (18.9.1.111) by oc11expo11.exchange.mit.edu (18.9.4.16) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 7 Apr 2020 23:20:59 -0400 Received: from NAM12-DM6-obe.outbound.protection.outlook.com (104.47.59.175) by oc11exhyb6.exchange.mit.edu (18.9.1.111) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 7 Apr 2020 23:20:59 -0400 Received: from MWHPR19CA0065.namprd19.prod.outlook.com (2603:10b6:300:94::27) by BYAPR01MB4582.prod.exchangelabs.com (2603:10b6:a03:99::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.20; Wed, 8 Apr 2020 03:20:57 +0000 Received: from CO1NAM03FT046.eop-NAM03.prod.protection.outlook.com (2603:10b6:300:94:cafe::ec) by MWHPR19CA0065.outlook.office365.com (2603:10b6:300:94::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2878.15 via Frontend Transport; Wed, 8 Apr 2020 03:20:57 +0000 Received: from omta04.suddenlink.net (208.180.40.74) by CO1NAM03FT046.mail.protection.outlook.com (10.152.81.15) with Microsoft SMTP Server id 15.20.2878.15 via Frontend Transport; Wed, 8 Apr 2020 03:20:56 +0000 Received: from wb5agz ([47.217.105.76]) by dalofep04.suddenlink.net (InterMail vM.8.04.03.22.02 201-2389-100-169-20190213) with ESMTP id <20200408032055.QWT28299.dalofep04.suddenlink.net@wb5agz> for ; Tue, 7 Apr 2020 22:20:55 -0500 Received: from martin by wb5agz with local (Exim 4.92) (envelope-from ) id 1jM1Gp-0000IK-Dj for piclist@mit.edu; Tue, 07 Apr 2020 22:20:55 -0500 From: Martin McCormick To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Tue, 7 Apr 2020 20:20:55 -0700 Subject: [EE] The Raspberry Pi Power Plug Thread-Topic: [EE] The Raspberry Pi Power Plug Thread-Index: AdYNViaS2lYIarRkQH2tfJtC4oLEHw== 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 suddenlink.net designates 208.180.40.74 as permitted sender) receiver=protection.outlook.com; client-ip=208.180.40.74; helo=omta04.suddenlink.net; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mitprod.onmicrosoft.com; s=selector2-mitprod-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=WOX1o4KbtcUl/brl1ICR/YQdXNU9qNEyy1t5Zq7DQdg=; b=NL3OsDBOrzsXQbfCEE0MEDzSLn46B0rFV9ZIl+pbd3yp7LwFfeMcitl7k7meg860EUA4jp9vF7dYOIXK0tol6tsotaoZfPuaBGLDi+Df+apbwF1af0fNhc7CqoYu76sDh+lLGPzxc0t+jkVGWgrIipiH1JtpYpQnMx9yyV2Br6U= authentication-results: spf=pass (sender IP is 208.180.40.74) smtp.mailfrom=suddenlink.net; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=bestguesspass action=none header.from=suddenlink.net;compauth=pass reason=109 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-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 After a several-year-old Raspberry Pi didn't come back up after a power failure, the problem turned out to be the 5-volt switching supply. Adafruit, the company that sells the Pi and supply matched the part number we supplied and I just got 2 new 2-amp 5-volt supplies today. The 2 Raspberry PI's I have both use what I believe to be a microusb plug for power only. The replacement supply is the correct supply but comes with a round coaxial-style power plug like one sees on a zillion and 1 gadgets these days. There are lots of sizes and variations on the theme but the body of the plug is often-times negative ground and the center conductor is, in this case, +5 volts DC. Being the pack rat that I am, I did save the power cord off the dead supply so I cut the power cable from the new supply in half to save the molded coax connector. Stripping the bare wires shows a red and black just like the microusb plug so after splicing the old plug on to the new cable, the Pi rises high again. Do new Raspberry PI's use a different power plug these days or do they just figure people are smart enough to figure out they can save the day by saving the old cord and splicing it on to the new supply. In this case, more power means the components in the supply are probably not straining as hard and therefore are running cooler. Martin McCormick --=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 .