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, 4 Sep 2020 12:56:49 -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 084JkGuS027470; Fri, 4 Sep 2020 15:46:46 -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 084JkFXW027467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 4 Sep 2020 15:46:16 -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 084JjqPh005094 for ; Fri, 4 Sep 2020 15:46:15 -0400 Received: from w92exhyb2.exchange.mit.edu (18.7.71.32) by w92exedge4.exchange.mit.edu (18.7.73.16) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Fri, 4 Sep 2020 15:45:26 -0400 Received: from oc11exhyb3.exchange.mit.edu (18.9.1.99) by w92exhyb2.exchange.mit.edu (18.7.71.32) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 4 Sep 2020 15:45:56 -0400 Received: from NAM02-BL2-obe.outbound.protection.outlook.com (104.47.38.53) by oc11exhyb3.exchange.mit.edu (18.9.1.99) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Fri, 4 Sep 2020 15:45:56 -0400 Received: from DM5PR07CA0160.namprd07.prod.outlook.com (2603:10b6:3:ee::26) by SN6PR01MB3677.prod.exchangelabs.com (2603:10b6:805:17::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.16; Fri, 4 Sep 2020 19:45:54 +0000 Received: from DM3NAM03FT025.eop-NAM03.prod.protection.outlook.com (2603:10b6:3:ee:cafe::9e) by DM5PR07CA0160.outlook.office365.com (2603:10b6:3:ee::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.16 via Frontend Transport; Fri, 4 Sep 2020 19:45:54 +0000 Received: from mail-ej1-f50.google.com (209.85.218.50) by DM3NAM03FT025.mail.protection.outlook.com (10.152.82.181) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.16 via Frontend Transport; Fri, 4 Sep 2020 19:45:54 +0000 Received: by mail-ej1-f50.google.com with SMTP id z22so10079083ejl.7 for ; Fri, 04 Sep 2020 12:45:54 -0700 (PDT) From: Sean Breheny To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Fri, 4 Sep 2020 12:45:42 -0700 Subject: Re: [OT] Simple LiPo charging circuit Thread-Topic: [OT] Simple LiPo charging circuit Thread-Index: AdaC9Yd25eiNtfhYTsK7YCwraQ8YLQ== Message-ID: References: <6091de9f-23e5-b862-5cde-28e7450429d0@gmail.com> <20200904030306.GA30954@laptop.org> <7d0c7aa5-e974-9e82-015e-2e3501768c5d@gmail.com> <20200904060223.GC30954@laptop.org> <6e6855d8-1672-c321-c397-0459849c1da3@gmail.com> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <6e6855d8-1672-c321-c397-0459849c1da3@gmail.com> 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.50 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.218.50; helo=mail-ej1-f50.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cornell.edu; s=g.20171207; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=RgLqzuSWXk6EnkmBM21Ft2Vx4FnSb+LZbiIKAC1jVOc=; b=EGfOrRsEiYflzA6lH40/1xjyQ4Q9OfS7ujM32ZlBGONhk7X1tYEu965e0WeQdI5oYx Ij4IAlZDgODjgoaMNdDBmc2XNiS72dEp1kNJqbRqvz0cqn5PGC51d/mfW/JLucuxW/OY vYAgr7SmFKNFegwoUCcHBNq7tpJ+9+2WggqLXDzlHTuEO0KBtU9o+gAbSvgwaQrH/aLF 3rWtUvlXDouyBXXFJy0GayQKZnKCiopmZwQKYSjqn+8f/xW9v8V3TfQXSGYqRrYAsqS0 VUptRXWnZEYOJhFJ8RC9MudTQ7+iBFxQiMf9lNYV3kLV26cr+ZY/7cfz7YjDRMn81IJS 92yA== authentication-results: spf=pass (sender IP is 209.85.218.50) smtp.mailfrom=gmail.com; mit.edu; dkim=pass (signature was verified) header.d=cornell.edu; mit.edu; dmarc=pass action=none header.from=cornell.edu; 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:c1c3:: with SMTP id bw3mr8987619ejb.516.1599248753112; Fri, 04 Sep 2020 12:45:53 -0700 (PDT) x-topics: [OT] 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 I don't think I've ever seen a LiPo that is "puffy" which has not been abused in some way. It may not get hot during normal use now but it has almost certainly been hot in the past. Sean On Fri, Sep 4, 2020 at 2:24 AM Jim Ruxton wrote: > It has been "puffy" since I got it. It isn't warm at all when charging > so I think it's ok. About to change it out anyway however. > > > > It's not just you; but I couldn't be sure from the angle of view and > > not knowing angle of lighting. > > > > On Fri, Sep 04, 2020 at 05:51:18PM +1200, Ryan O'Connor wrote: > >> Is it just me or is that battery swollen to the point where it might > >> explode? > -- > 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 http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .