Two identical DC power supplies wired straight together in parallel do not make a redundant system - they make a fault waiting to happen, because a failed supply can drag the shared bus down and take the healthy one with it. To parallel supplies safely you need a redundancy module and, ideally, active current sharing. This guide explains why paralleled supplies cannot simply be joined at the terminals, how diode or MOSFET ORing isolates a failing unit, how current sharing keeps both supplies aging evenly, how N+1 sizing works, and how feeding supply-fail signals into SCADA turns a silent power loss into an alarm you actually see.
Power Supply Load Sharing in one line: Power supply load sharing is the technique that lets two or more DC supplies work in parallel so that they split the load and one can fail without dropping the bus. It relies on a redundancy or ORing module that uses diodes or MOSFETs to isolate each supply's output, so a failed or short-circuited supply cannot pull down the common bus or back-feed the healthy units. Active current sharing additionally balances the load between supplies so both carry a fair share and age at the same rate, rather than one doing all the work.
The intuition that two supplies wired together give you a backup is wrong in a specific and dangerous way. When you tie two power-supply outputs directly to the same bus, they are not independent anymore - they are one node. If one supply develops an internal short, that fault is now on the shared bus, and instead of one supply dying quietly, the failed unit becomes a sink that pulls the bus voltage down and drains current out of the healthy supply. Rather than surviving the failure, the whole load loses power, which is the opposite of what redundancy is supposed to deliver.
Even without an outright short, directly paralleled supplies fight over who carries the load. Small differences in their output-voltage set points mean the slightly higher supply carries most or all of the current while the other loafs, so you get no real sharing and the harder-working unit wears out faster. To parallel supplies safely you have to insert something between each supply and the bus that lets current flow out toward the load but blocks it from flowing back into a failed supply, and that isolates each unit so its failure stays its own problem.
That something is a redundancy module - a dedicated device, not a wire nut and not a hope. It is the component that makes parallel supplies actually redundant, and skipping it is one of the more common ways a well-intentioned dual-supply design turns into a single point of failure that no one discovers until the day one supply fails and takes the panel down with it.
The classic isolation method is diode ORing: a diode in each supply's output path allows current to pass toward the bus but blocks any reverse current, so a failed supply is automatically cut off from the healthy one and from the load. The name comes from the logical OR - the bus is powered if supply A or supply B is good. The tradeoff of plain diodes is the forward voltage drop across them, which wastes a little power as heat and slightly reduces the delivered voltage. Modern redundancy modules often replace the diodes with MOSFETs that switch to emulate an ideal diode with far lower drop, giving the same reverse-blocking isolation with much less loss and heat.
Isolation keeps a failure contained, but it does not by itself make the supplies share the load evenly - that is what active current sharing adds. A current-sharing scheme monitors how much each supply is delivering and coordinates the units so they carry roughly equal portions of the total load, instead of one supply doing most of the work while the other idles. The practical payoff is even aging: power supplies wear with use and heat, so a unit that constantly carries the full load ages faster and fails sooner. When both supplies share, they age together, and the redundancy you paid for is more likely to be intact when you need it.
Together, ORing and current sharing describe a proper redundant supply. ORing provides the fault isolation that makes a failure survivable; current sharing provides the balance that keeps both units healthy for the long run. A good redundancy module does both, and it is worth confirming a given module actually shares current rather than only ORing, because the two features solve different halves of the problem.
Redundancy is sized with the N+1 idea: N supplies are enough to carry the full load, and you add one more so that any single supply can fail and the remaining ones still power everything. If a panel needs one supply's worth of capacity, N+1 means two supplies, either of which can be lost. If it needs the capacity of two, N+1 means three. The point is that after a failure the surviving supplies are not overloaded - they were sized to carry the whole load without the failed unit - so the system runs indefinitely on the remainder rather than limping until the next one goes.
The quiet danger of redundancy is that it hides failures. When one supply in an N+1 set fails, everything keeps running on the others, so nothing looks wrong - the panel is powered, the process is fine, and no one knows the redundancy is gone. The system is now unprotected: the next failure will drop the load. That is why supply-fail signaling matters. Redundancy modules and quality supplies provide a fault contact or status output that changes state when a unit fails, and wiring that signal into the control system converts an invisible loss into a discrete alarm the moment it happens.
Feeding those supply-fail and redundancy-module status signals up into a cloud SCADA platform such as Merobix is what closes the loop for distributed field operations. A power supply that quietly dies in a remote cabinet - one nobody visits for weeks - would otherwise sit undetected until the second failure blacks out the node. As a monitored tag, that first failure raises an alarm on the operator screen and in the history, so a crew can be dispatched to swap the failed unit while the backup is still holding the load, rather than after both are gone. The redundancy hardware keeps the site running through the first failure; the SCADA visibility ensures the first failure gets fixed before it becomes the outage.
Because directly paralleled supplies share a common bus, so a supply that fails or shorts internally can drag the bus voltage down and back-feed the healthy supply, dropping the whole load - the opposite of redundancy. They also fight over the load, so one carries most of it and wears out faster. You need a redundancy module with ORing between each supply and the bus to isolate a failed unit and make the pair genuinely redundant.
An ORing module puts a diode - or a MOSFET emulating an ideal diode - in each supply's output path so current can flow toward the load but not back into a failed supply. This isolates each unit, so if one shorts or fails it is automatically cut off and the healthy supply keeps powering the bus. MOSFET-based modules do the same job with far less voltage drop and heat than plain diodes.
N+1 means you install one more supply than the load actually requires. N supplies carry the full load, and the extra one is spare capacity, so any single supply can fail and the remaining units still power everything without being overloaded. It is the standard way to size redundant power so a single failure is survivable and the system keeps running on the rest.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.