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, 18 Mar 2021 18:46:30 -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 12J1ZdQN004888; Thu, 18 Mar 2021 21:36:34 -0400 Received: from outgoing-exchange-1.mit.edu (OUTGOING-EXCHANGE-1.MIT.EDU [18.9.28.15]) by PCH.mit.edu (8.14.7/8.12.8) with ESMTP id 12J1Zci3004885 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Thu, 18 Mar 2021 21:35:38 -0400 Received: from w92exedge3.exchange.mit.edu (W92EXEDGE3.EXCHANGE.MIT.EDU [18.7.73.15]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 12J1ZbBd022072 for ; Thu, 18 Mar 2021 21:35:37 -0400 Received: from oc11expo15.exchange.mit.edu (18.9.4.20) by w92exedge3.exchange.mit.edu (18.7.73.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 18 Mar 2021 21:35:21 -0400 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by oc11expo15.exchange.mit.edu (18.9.4.20) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 18 Mar 2021 21:35:37 -0400 Received: from NAM02-DM3-obe.outbound.protection.outlook.com (104.47.56.42) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 18 Mar 2021 21:35:37 -0400 Received: from MW4PR04CA0161.namprd04.prod.outlook.com (2603:10b6:303:85::16) by DM6PR01MB3707.prod.exchangelabs.com (2603:10b6:5:81::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.18; Fri, 19 Mar 2021 01:35:35 +0000 Received: from CO1NAM11FT056.eop-nam11.prod.protection.outlook.com (2603:10b6:303:85:cafe::b3) by MW4PR04CA0161.outlook.office365.com (2603:10b6:303:85::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.18 via Frontend Transport; Fri, 19 Mar 2021 01:35:35 +0000 Received: from mail-pl1-f181.google.com (209.85.214.181) by CO1NAM11FT056.mail.protection.outlook.com (10.13.175.107) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3955.18 via Frontend Transport; Fri, 19 Mar 2021 01:35:35 +0000 Received: by mail-pl1-f181.google.com with SMTP id v8so2194013plz.10 for ; Thu, 18 Mar 2021 18:35:35 -0700 (PDT) From: Justin Richards To: Microcontroller discussion list - Public. Sender: "piclist-bounces@mit.edu" Date: Thu, 18 Mar 2021 18:35:33 -0700 Subject: [EE]: Battery eliminator for Solar powered pond pump and slowly rising Vin issues Thread-Topic: [EE]: Battery eliminator for Solar powered pond pump and slowly rising Vin issues Thread-Index: AdccYa/PgwVfKLB/TBKZXE1Yxc+G0A== 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 gmail.com designates 209.85.214.181 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.214.181; helo=mail-pl1-f181.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=omev7jUtjlBSBY1z+qQmDTzZZ8KBzqBjdXUNupbzYHU=; b=kNCcVesSq87D60qm8TUAvvUvtBih5YNg+hgGHifx1/G5i07eNA8bM4hjO2C1KbgPEW S0I27uMYGc1+4IYKV26i9HaSpKiKHo4REfNVKfKO4mJErlQes6thfAUEvTPE+dddJaFA 8cscT5TIgp9clMZNWMWc4M1bbl2K1Gnx8lwM/3lfEMuZ6mMpgS1e8AdnWytaQup9xB58 2PEHZ66pIhbiSIATiSEnVZJSjzIdmvGU5/84wQ7Meb9YVf8ePVG/nMdkP6vmPWMfbE3h YSnl9ma2m6lDcov0YQqyAkckcfDCjbCHHSFMpKsn4Jo3ncgjgfvCFpKyTg24VizGnILr odFw== authentication-results: spf=pass (sender IP is 209.85.214.181) 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; 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:90b:804:: with SMTP id bk4mr7210762pjb.25.1616117733364; Thu, 18 Mar 2021 18:35:33 -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 The problem I have is the morning powered solar panel presents a 'very' slowly rising Vin and the buck converter powered ESP8266 does not start correctly. Anyone know of an elegant design to provide a clean enable signal that will deal with very very slowly rising Vin. Perhaps it has to be a belt and braces approach with an Op-Amp type solution. The obvious simple answer is to use a battery but there is no challenge and not what I want. If interested, read on for a lengthy description.. I have repeatedly and successfully bench tested a design with slowly rising Vin with 0.1V increments. A cheap buck converter has an enable pin that was tied to Vin via 10K. I removed and inserted 10v Zener and bias resistors. Works great on the bench PSU but solar panels are a very different beast. I was aware that a solar panel was a complex device to model but I was not prepared for just how complex. The challenge: (which I thought would be trivial) Solar powered aquaponics water circulation system with remote monitoring (as I work away 2 weeks) while maximising pump life (by varying duty cycle) and eliminating the need for a battery (as they need replacing). I built a 555 based controller that did just that. i.e turned on 10mins every hour and clamped the supply to the pump so the pump was never over 'voltaged'. (see https://hackaday.io/project/19863-aquaponics-solar-battery-eliminator) However, it failed after some time while I was away due to corrosion, so the obvious solution was to add remote monitoring in the form of an ESP8266 that sends regular http get requests to my local server. From there I can do blah. (remotely task a family member to investigate the failure) . Bonus of using a ESP8266 is that many other environmental conditions can be monitored such as water temperature, did the water actually flow, water tank levels etc. Other problems encountered: Voc (Solar Panel Open Circuit Voltage) is definitely not a viable way to determine available power (I thought I could use it as a rough guide but I was so wrong). However, load testing to produce useful data often results in the supply rail drooping causing a ESP8266 reset at sun-up, sun-down and cloud cover in between. To solve i connected bulk capacitors across the ESP8266 and separating it from the drooping supply via a diode. Which works but creates another issue of slowing rising Vcc at start up which the ESP8266 does not like. I already eliminated this problem with a device that only powers up the system when the Voc exceeds 16v. A game of cat and mouse. The current system works ok after a successful initial startup. i.e with a two stage volt check, it performs a quick load test to determine if the panel can deliver before it runs the pump proper. It continues to monitor and shut off the pump if it falls below a preset value. Basically, if Voc is over 16v proceed to 0.5s load test. If Vload > 10v, turn on pump. If Vload < 10V halt, reset timers and try again later, Using a 33w solar panel nominal voltage 21v Measured Voc 19v, Isc ~1.3A midday. (manufacture date 1985) 17watt water pump 12V nominal. Work effectively for my purposes down to about 7v. Also observed very strange behaviour when powering the pump from a Rigol DP831. Set to 12v 2amps, the display after startup would read ~12.5v and the current would 'decrease' when 'increasing' the flow restriction. It was very odd and counter intuitive . Using a scope revealed that the pump generates periodic spikes and I had to conclude that the DP831 was struggling to regulate given such a complex load. It has been quite a learning experience for something that on the surface I considered trivial. --=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 .