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; Sun, 6 Sep 2020 11:20:34 -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 086IBDof017043; Sun, 6 Sep 2020 14:11: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 086IBCr8017040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Sun, 6 Sep 2020 14:11: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 086IBBKX013864 for ; Sun, 6 Sep 2020 14:11:12 -0400 Received: from oc11expo19.exchange.mit.edu (18.9.4.50) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1293.2; Sun, 6 Sep 2020 14:10:56 -0400 Received: from oc11exhyb4.exchange.mit.edu (18.9.1.100) by oc11expo19.exchange.mit.edu (18.9.4.50) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Sun, 6 Sep 2020 14:11:11 -0400 Received: from NAM04-SN1-obe.outbound.protection.outlook.com (104.47.44.50) by oc11exhyb4.exchange.mit.edu (18.9.1.100) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Sun, 6 Sep 2020 14:11:11 -0400 Received: from DM3PR12CA0130.namprd12.prod.outlook.com (2603:10b6:0:51::26) by BL0PR01MB4276.prod.exchangelabs.com (2603:10b6:208:44::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.15; Sun, 6 Sep 2020 18:11:09 +0000 Received: from DM3NAM03FT013.eop-NAM03.prod.protection.outlook.com (2603:10b6:0:51:cafe::70) by DM3PR12CA0130.outlook.office365.com (2603:10b6:0:51::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; Sun, 6 Sep 2020 18:11:09 +0000 Received: from mail-ej1-f50.google.com (209.85.218.50) by DM3NAM03FT013.mail.protection.outlook.com (10.152.82.79) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3348.16 via Frontend Transport; Sun, 6 Sep 2020 18:11:09 +0000 Received: by mail-ej1-f50.google.com with SMTP id z22so14984108ejl.7 for ; Sun, 06 Sep 2020 11:11:09 -0700 (PDT) From: Sean Breheny To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Sun, 6 Sep 2020 11:10:56 -0700 Subject: Re: [OT] Simple LiPo charging circuit Thread-Topic: [OT] Simple LiPo charging circuit Thread-Index: AdaEemnfyTwkFy1ARpC2T0fT1pNW/g== 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: 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=N5bBizsYOeh3qZaulXjcayLVYlfFbdA34jvvKOA1gtM=; b=WTeMh62DBzfUv6LPQEgCJYSo3AFu0iTnHgoIiQW1K+gCHIF8Rey4QWdEaCM18r/Fp4 2VxHU4Luxh+8Vi1KNlr9AomDrBEiq22Y727lWqWG8gXpSXc/cvMuo49w91O+A5wEwSED 7GS2uzGeaAgbeKF5yg/9N56te6Nt/URAwNRyB7ClJYc//pb405rCZ81h3BElfR5F/TKQ 9jo8LpbI4Jfb3wgaiQRPfBh8sdXvRn2fbBjtRsp6yYkA8GjDqhJtr2s3zfSFzjZOwK4/ x2db+aFVpD3xoKcDrzlTGuFWObRCa7+9MzjPx3BrbBP4379MfNiFGDOJNGzeFGozVsDs vYYA== 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:2704:: with SMTP id z4mr17090149ejc.350.1599415867863; Sun, 06 Sep 2020 11:11:07 -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 think your charging regime is indeed a very good one for longevity for typical Li ion chemistry. As far as charging current I don't think it matters much as long as the current doesn't warm up the battery much. As temperature increases, the "calendar life" wear on the battery is accelerated exponentially (see Arrhenius equation for a mathematical model). So, the less time you spend hot (whether it is charging, discharging, or idle) the better. There are two kinds of "life" - calendar and cycle. Calendar life is shortened by higher temperature and by high state of charge (for typical Li ion chemistry - this is not true of most battery chemistries). Cycle life is shortened by large changes in state of charge and maximized for making cycles smaller (less change in SOC). This effect is not simply linear. In other words, if you add up the total coulombs of charge which pass through a 1 amp-hour battery in its life, then typically you might find that it is able to to 1000 1 amp-hour cycles but is able to do 15000 0.1 AH cycles (i.e., 50% better cycle life in terms of amp-hours). Sean On Sun, Sep 6, 2020 at 1:34 PM Bob Blick wrote: > Hijacking the thread, I have a question about the battery in my mobile > phone. I'm careful about charging, and want to get as many useful years o= f > life as possible out of the battery. I try to never let the battery get t= oo > low, never charge the phone if it's hot, and never let it charge fully. > Based on the phone's gauge, I charge it when it's down to 40% and take it > off charge when it reaches 80 or 85%. I think this is probably a pretty > good way of doing it. I plug the charger into a timer so I don't have to > watch it, I'm not totally OCD :) > > My question regards preferred charging current. The charger that came wit= h > the phone will do my normal charge regime in about 20 minutes. The good > quality charger from a previous phone will take 90 minutes to do the same > thing. Neither charger noticeably heats the phone. > > Which is easier on the battery, high current for a short period of time, > or medium current for a longer time, both taking the battery from 40% to > 80% state of charge? > > Thanks, Bob > > -- > 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 .