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, 15 Jul 2021 23:19:20 -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 16G685vo006071; Fri, 16 Jul 2021 02:08:55 -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 16G684GK006068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Fri, 16 Jul 2021 02:08:04 -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 16G67Lwd008397 for ; Fri, 16 Jul 2021 02:08:04 -0400 Received: from oc11exhyb8.exchange.mit.edu (18.9.1.113) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.23; Fri, 16 Jul 2021 02:07:49 -0400 Received: from oc11exhyb2.exchange.mit.edu (18.9.1.98) by oc11exhyb8.exchange.mit.edu (18.9.1.113) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Fri, 16 Jul 2021 02:07:48 -0400 Received: from NAM11-BN8-obe.outbound.protection.outlook.com (104.47.58.175) by oc11exhyb2.exchange.mit.edu (18.9.1.98) with Microsoft SMTP Server (TLS) id 15.0.1497.18 via Frontend Transport; Fri, 16 Jul 2021 02:07:48 -0400 Received: from DM5PR06CA0046.namprd06.prod.outlook.com (2603:10b6:3:5d::32) by DM5PR0102MB3510.prod.exchangelabs.com (2603:10b6:4:a3::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4308.25; Fri, 16 Jul 2021 06:07:42 +0000 Received: from DM6NAM11FT063.eop-nam11.prod.protection.outlook.com (2603:10b6:3:5d:cafe::8f) by DM5PR06CA0046.outlook.office365.com (2603:10b6:3:5d::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4331.21 via Frontend Transport; Fri, 16 Jul 2021 06:07:42 +0000 Received: from omta013.uswest2.a.cloudfilter.net (35.164.127.236) by DM6NAM11FT063.mail.protection.outlook.com (10.13.172.219) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4331.21 via Frontend Transport; Fri, 16 Jul 2021 06:07:42 +0000 Received: from cxr.smtp.a.cloudfilter.net ([10.0.17.210]) by cmsmtp with ESMTP id 3xCImIdxpU7TQ4H0fmPRtz; Fri, 16 Jul 2021 06:07:41 +0000 Received: from DRC ([68.101.106.6]) by cmsmtp with ESMTPA id 4H0cmcu9ihXzT4H0emvk4p; Fri, 16 Jul 2021 06:07:41 +0000 From: David Challis To: 'Microcontroller discussion list - Public.' Sender: "piclist-bounces@mit.edu" Date: Thu, 15 Jul 2021 23:07:38 -0700 Subject: RE: [EE] Redundant PSU for critical NAS server Thread-Topic: [EE] Redundant PSU for critical NAS server Thread-Index: AQHxBt28Nvgbw/+9joaNhLjArz3PagN+2eMUqvYM1EA= Message-ID: References: List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: Reply-To: Microcontroller discussion list - Public. Accept-Language: en-US Content-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 cox.net designates 35.164.127.236 as permitted sender) receiver=protection.outlook.com; client-ip=35.164.127.236; helo=omta013.uswest2.a.cloudfilter.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=VOn8VLd9YIYYyHAH+u//uJ/48m6eLWoO9BuVnFauEGA=; b=mqtzA6EsVvaOt67YXVpygTObL8Tmk2sYlOkqvBc4sFPcug0BwRLFM1+76y6BhvKczvc/41l6e25kVDmgAotKoWQjqUSVIm5ihM+5nbLcWk1NdK9ttgavkBH7ouWiCSFwz/SAJCcRZz8cZo2v41N3b7wT/yn+KlZBNasOOD29OSM= authentication-results: spf=pass (sender IP is 35.164.127.236) smtp.mailfrom=cox.net; mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=pass action=none header.from=cox.net; 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-authority-analysis: v=2.4 cv=YqbK+6UX c=1 sm=1 tr=0 ts=60f1222d a=ZYX/eMYROZMxE7JXhRj8CQ==:117 a=ZYX/eMYROZMxE7JXhRj8CQ==:17 a=IkcTkHD0fZMA:10 a=s2o9kXtcAAAA:8 a=F07sB3KiAAAA:8 a=Gz7s5_CCAAAA:8 a=lEGtvlLfRk6DlBmxCkYA:9 a=QEXdDO2ut3YA:10 a=s31QAnCAJgd9yEMSk0Pk:22 a=8rYrM0obaTRgCqsvCuYq:22 x-topics: [EE] x-mime-autoconverted: from quoted-printable to 8bit by PCH.mit.edu id 16G684GK006068 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Check out page 20 of the LTC4364. It may be what you are looking for. Dave Challis (many years MIA from this list). -----Original Message----- From: piclist-bounces@mit.edu On Behalf Of smplx Sent: Thursday, July 15, 2021 10:35 AM To: Microcontroller discussion list - Public. Subject: Re: [EE] Redundant PSU for critical NAS server Some time ago I came across a circuit for combining PSUs. It used something= called and ideal diode. I've had a ***quick*** look but can't find the cir= cuit again but there is lots of stuff out there using ideal diodes. Perhaps= you could do a search and find something? Regards Sergio Masci On Mon, 12 Jul 2021, foros@arocholl.com wrote: > Hi there, > > Over the last couple of years have experienced problems with PSU=20 > failing and shutting down connected NAS servers, twice. These PSUs are=20 > 12v/100W external units from the manufacturer (Synology). The funniest=20 > thing is the PSUs are fully protected with 220v UPS but of course=20 > nothing helps if they fail themselves, and they do, without any=20 > advice... Not a good setup for a critical server. > > So I rather no longer rely on the manufacturer PSU and design my own,=20 > overrated 12v/200W redundant supply. My current thinking is to proceed=20 > like this: > > * Have two identical 12v PSU adjusted to different DC levels (12.6v=20 > and > 12.2v) each one connected to a pair of schottky diodes (2x parallel=20 > 15V 9A 95SQ015 I have spare) so one PSU is the active one and the=20 > second PSU is running ready but passive. > * In theory if the active PSU fails, the passive one becomes active=20 > and diodes prevent anything funny from happening. > > [Active PSU 12.6v] -> 2x Parallel Diode -> Joint [Passive PSU 12.2v]=20 > -> 2x Parallel Diode -> Joint -> NAS server > > I've been testing this setup and the diodes get barely warm so=20 > everything looks kosher to move to production. I also tested the=20 > active/passive -> dead/active scenario with some alternative charge=20 > but don't want to risk the actual server with a full charge test. > > So I wanted to check if you have been there already and found a better=20 > setup, or if this approach may have an obvious issue I currently do not s= ee. > > > Regards, > Ariel > -- > http://www.piclist.com/techref/piclist PIC/SX FAQ & list archive=20 > View/change your membership options at=20 > 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 .