Can Two DC/DC Converter Outputs Be Paralleled?

Confirm the architecture before calculating capacity

Ask whether the intended converter model supports the proposed parallel arrangement. An affirmative answer should identify the applicable revision, number of modules, operating conditions and required interface/control arrangement.

Highidea's RP products establish a DC/DC converter context, not documented parallel capability for every model. Do not infer permission from a common voltage rating or from an example using another manufacturer's modules.

Vicor's AN:030 Parallel DCMs application note discusses current sharing, load-line behavior, startup and thermal considerations for specified DCM products. It demonstrates why supported parallel operation is a designed architecture. Its requirements do not approve an RP connection or provide a transferable wiring recipe.

Build a parallel-eligibility schedule

Keep each unresolved condition visible and assign it to the converter supplier or system designer. A spreadsheet sum is not a substitute for the missing architecture statement.

The schedule organizes a design review. It specifies no wiring, protection device or adjustment method and should not be used to assemble an unapproved circuit.

Distinguish combined capacity from survival

Consider two hypothetical 500 W modules in an explicitly approved parallel system, with a required load of 800 W. Even if the validated arrangement can supply 800 W normally, loss of one 500 W module leaves insufficient individual capacity for that load. The pair's normal capacity therefore does not establish an N+1 result.

The values are illustrative, not RP specifications. Actual available capacity depends on the supported architecture, operating conditions and derating. A module's isolated nameplate rating cannot simply be multiplied and treated as guaranteed parallel output.

Even where surviving capacity is sufficient, the designer must assess fault interaction and shared dependencies. A common input, controller or distribution path can remain outside a narrowly defined module-loss claim.

Use reject, clarify and approve decisions

Reject a proposal that relies on an unsupported output connection or contradicts the selected manufacturer's requirements. Clarify a proposal where model applicability, current sharing or fault behavior is unknown. An approval should cite the actual configuration and responsible technical authority, rather than a broad statement that the family “supports parallel.”

If the supplier cannot substantiate the architecture, ask for an approved higher-capacity product or another supported system option. Do not experiment by connecting outputs to discover whether they share.

A numerical mismatch is useful evidence for a design revision. It is not a reason to change trim settings, bypass protection or improvise an isolation arrangement based on a generic article.

Keep the approval with the system revision

Retain the converter identities, approved architecture documents, environmental assumptions and reviewed failure scenarios. Changes in module type, firmware where applicable, cooling or load may require reassessment.

Give Highidea the intended input/output conditions, demand and availability objective when asking about RP options. Request an explicit supported or unsupported response for parallel operation. A clear limitation is safer and more commercially useful than an ambiguous quotation for twice the number of converters.

Primary references

The references support the specific distinctions stated above. Manufacturer examples apply to their documented products; they do not establish the same capability in a Highidea model. Proposed worksheets and hypothetical examples are editorial decision tools, not approved installation or operating procedures.

Vicor: AN:030 Parallel DCMs