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; Mon, 12 Jul 2021 12:19:15 -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 16CJ9g0b003680; Mon, 12 Jul 2021 15:10:28 -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 16CJ9e4n003677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL) for ; Mon, 12 Jul 2021 15:09:40 -0400 Received: from oc11exedge2.exchange.mit.edu (OC11EXEDGE2.EXCHANGE.MIT.EDU [18.9.3.18]) by outgoing-exchange-1.mit.edu (8.14.7/8.12.4) with ESMTP id 16CJ9Vxb032552 for ; Mon, 12 Jul 2021 15:09:40 -0400 Received: from w92extsm1.exchange.mit.edu (18.7.74.52) by oc11exedge2.exchange.mit.edu (18.9.3.18) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Mon, 12 Jul 2021 15:09:02 -0400 Received: from oc11exhyb5.exchange.mit.edu (18.9.1.110) by w92extsm1.exchange.mit.edu (18.7.74.52) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Mon, 12 Jul 2021 15:09:06 -0400 Received: from NAM10-DM6-obe.outbound.protection.outlook.com (104.47.58.100) by oc11exhyb5.exchange.mit.edu (18.9.1.110) with Microsoft SMTP Server (TLS) id 15.0.1497.18 via Frontend Transport; Mon, 12 Jul 2021 15:09:05 -0400 Received: from BN6PR17CA0030.namprd17.prod.outlook.com (2603:10b6:405:75::19) by BYAPR01MB3623.prod.exchangelabs.com (2603:10b6:a02:90::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4242.23; Mon, 12 Jul 2021 19:09:04 +0000 Received: from BN8NAM11FT061.eop-nam11.prod.protection.outlook.com (2603:10b6:405:75:cafe::c7) by BN6PR17CA0030.outlook.office365.com (2603:10b6:405:75::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4308.20 via Frontend Transport; Mon, 12 Jul 2021 19:09:04 +0000 Received: from mail-wr1-f47.google.com (209.85.221.47) by BN8NAM11FT061.mail.protection.outlook.com (10.13.177.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4308.20 via Frontend Transport; Mon, 12 Jul 2021 19:09:03 +0000 Received: by mail-wr1-f47.google.com with SMTP id v5so27078192wrt.3 for ; Mon, 12 Jul 2021 12:09:03 -0700 (PDT) Received: from raspberry (cpc113460-oxfd27-2-0-cust322.4-3.cable.virginm.net. [86.24.157.67]) by smtp.gmail.com with ESMTPSA id s6sm5369178wrt.45.2021.07.12.12.09.02 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 12 Jul 2021 12:09:03 -0700 (PDT) From: Alan Pearce To: "piclist@mit.edu" Sender: "piclist-bounces@mit.edu" Date: Mon, 12 Jul 2021 12:08:59 -0700 Subject: Re: [EE] Redundant PSU for critical NAS server Thread-Topic: [EE] Redundant PSU for critical NAS server Thread-Index: Add3Us5lWxKURiX5QQeBUAi7SVzroA== Message-ID: <20210712200859.60c4f038@raspberry> References: <2fd4df00967f3c7f872cc7c87c6cc133.squirrel@mai.hallikainen.org> List-Help: List-Subscribe: , List-Unsubscribe: , In-Reply-To: <2fd4df00967f3c7f872cc7c87c6cc133.squirrel@mai.hallikainen.org> 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 googlemail.com designates 209.85.221.47 as permitted sender) receiver=protection.outlook.com; client-ip=209.85.221.47; helo=mail-wr1-f47.google.com; dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=from:date:to:subject:message-id:in-reply-to:references:organization :mime-version:content-transfer-encoding; bh=jsluUVBOrMsIy0p61Zk74qdAp3N8DKfJJEY5jX4Z5vk=; b=bz93FaUHlWtsF35oFLVv0BcC93uhpg+UOWBq5jpwHESL8kt0jqM2xuQTJWK6QGflOa QXtXYaei3fGH0nNtO3TqqBb7gGSdNyzrbTw0M5GmpAJRGO09V6MhFEz6vMZ98bGoNo7U L/cfKmziUVWb6VN7pJjMkHEb+pe98FIvNdGd0ERFd9NYedxsKWbINN5s8tkjZg6IMg8q vOFh7NHs3laz9gUxC0WnETp/c6xm/99i6LoV8Q97d0gUFmO+JoFnIP8K6XUU78P5VHlU aDl4A+1tzqVVgNzxrNNiTv+auFE0jfkd26zTrNLy91r42M9Hud7YXjateBho3XFKUzXU J3aw== authentication-results: spf=pass (sender IP is 209.85.221.47) smtp.mailfrom=googlemail.com; mit.edu; dkim=pass (signature was verified) header.d=googlemail.com;mit.edu; dmarc=pass action=none header.from=googlemail.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:adf:d235:: with SMTP id k21mr614605wrh.222.1626116943138; Mon, 12 Jul 2021 12:09:03 -0700 (PDT) x-topics: [EE] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 On Mon, 12 Jul 2021 11:16:37 -0700 "Harold Hallikainen" wrote: > ... In any > case, I wonder if the outputs of such supplies could just be > connected in parallel. There's already a diode in each supply.=20 I think that is the arrangement in systems I dealt with that had N+1 supplies for reliability. The particular system i am thinking of (it was 25 years ago now) was a disk subsystem for mainframe connection which could take up to 8 power supplies, each time you added a disk drive to the system you also added a power supply. A maximum populated system required 7 supplies to run plus one spare. The supplies were also hot swappable, so when you had a failure it could be pulled without taking down the system, and its replacement fitted. The system was also complicated by provision for two mains inputs to the system. I don't know how the power supplies were set up internally to handle this, I don't believe that the supplies were split between mains supplies. --=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 .