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, 9 Apr 2020 15:46:52 -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 039MYqLJ011572; Thu, 9 Apr 2020 18:35:31 -0400 Received: from outgoing-exchange-3.mit.edu (OUTGOING-EXCHANGE-3.MIT.EDU [18.9.28.13]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 039MYpaQ011556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 9 Apr 2020 18:34:51 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-3.mit.edu (8.14.7/8.12.4) with ESMTP id 039MZG2o026893 for ; Thu, 9 Apr 2020 18:35:16 -0400 Received: from w92expo16.exchange.mit.edu (18.7.74.70) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Thu, 9 Apr 2020 18:33:59 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92expo16.exchange.mit.edu (18.7.74.70) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 9 Apr 2020 18:34:50 -0400 Received: from NAM10-BN7-obe.outbound.protection.outlook.com (104.47.70.103) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Thu, 9 Apr 2020 18:34:50 -0400 Received: from DM6PR07CA0066.namprd07.prod.outlook.com (2603:10b6:5:74::43) by MWHPR0101MB2990.prod.exchangelabs.com (2603:10b6:301:2d::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.15; Thu, 9 Apr 2020 22:34:48 +0000 Received: from DM3NAM03FT051.eop-NAM03.prod.protection.outlook.com (2603:10b6:5:74:cafe::5b) by DM6PR07CA0066.outlook.office365.com (2603:10b6:5:74::43) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2900.16 via Frontend Transport; Thu, 9 Apr 2020 22:34:48 +0000 Received: from standingwave.org (173.230.152.118) by DM3NAM03FT051.mail.protection.outlook.com (10.152.83.56) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_RSA_WITH_AES_256_CBC_SHA) id 15.20.2900.15 via Frontend Transport; Thu, 9 Apr 2020 22:34:47 +0000 Received: from [17.150.220.197] (unknown [17.150.220.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: peterl) by standingwave.org (Postfix) with ESMTPSA id A0DEC11C004 for ; Thu, 9 Apr 2020 15:34:46 -0700 (PDT) From: Peter Loron To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 9 Apr 2020 15:34:43 -0700 Subject: Re: [EE] The Raspberry Pi Power Plug Thread-Topic: [EE] The Raspberry Pi Power Plug Thread-Index: AdYOwMPM4YczZM8gTE+DsjTOayQpCA== 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: TempError X-MS-Exchange-Organization-PRD: mit.edu X-MS-TNEF-Correlator: received-spf: Pass (protection.outlook.com: domain of standingwave.org designates 173.230.152.118 as permitted sender) receiver=protection.outlook.com; client-ip=173.230.152.118; helo=standingwave.org; 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=PP2eKXy5PjtQxqA7UGZCfqJ7SnHPNEeQnZ7YBFFTDPA=; b=MjR3M7fKmIOCwqKgT5/MS8JMTBjoPS48yoXj41XT1zkLKD1t/3gYqOwBv+kbf5biyVC61kuvzXzLvVAdCumh75ChYby/NRSWBzu//BtN6D2RsCMMXOOyop0UrathTQTnDLntfZgBnSGG8HfAKIdCZ6SRx7KKRb9r2I84A/O0cQ4= authentication-results: spf=pass (sender IP is 173.230.152.118) smtp.mailfrom=standingwave.org; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=bestguesspass action=none header.from=standingwave.org;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] x-mime-autoconverted: from quoted-printable to 8bit by PCH.mit.edu id 039MYpaQ011556 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 If the connector is constructed so that it can only be inserted one way (a = la micro-USB), then it is not USB-C. -Pete > On Apr 8, 2020, at 08:21, Martin McCormick wrot= e: >=20 > Bob Blick writes: >> Hi Martin, >> It seems like every new generation of Raspberry Pi uses new power, video= ,=20 >> and audio connections. The GPIO connectors retain the largest amount of= =20 >> compatibility. >>=20 >> My new Pi uses a USB-C connector for power. I bought the official AC=20 >> adapter. I think it was 3 amps. >>=20 >> Friendly regards, Bob >=20 > Fortunately, this appears to be a minor foul-up. I am glad I > saved half the new power cable with the round plug as there will > surely be some need for it on some future day. >=20 > The old supply has a much more robust stranded wire in it > than does the new cable but one just needs to be a little more > careful with it while working on the splice as the new strands > are more easily broken. >=20 > The usbC connector is the little flat one with 2 keys or > pegs that are on one side so that it can't be inserted backwards. > I'm glad that they are still using the same connector for all the > Pi's as I have 2 and may want to get some more soon. They are > pretty impressive considering what they cost. >=20 > Martin >=20 > --=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 >=20 --=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 .