How Does Power Sharing Work in a Multi-Connector DC Charger?

Multi-connector DC charger power sharing allocates a limited available power pool among active vehicles; it does not automatically mean that every connector receives its maximum rating at the same time. The actual result depends on the charger’s internal architecture, allocation mode, connector limits, vehicle demand, and any site-level power limit. Buyers should therefore verify the named model’s simultaneous-use and allocation behavior before treating a connector count as delivered capacity.

Part 1. What does power sharing mean in a multi-connector DC charger?

Power sharing is the distribution of DC charging capacity among more than one active connector. A dynamic system can reallocate capacity as vehicles connect, taper, or disconnect. Kempower’s charging-power-management documentation describes a power-distribution module routing and re-routing available channels during a charging session.

The key phrase is “available power.” A charger may have a cabinet-level power pool, individual connector limits, and a site-level cap. Those three numbers can differ. A product label or a two-connector front panel alone does not establish how much power two vehicles can receive simultaneously.

Part 2. Which components set the available power pool?

DC charging equipment converts incoming electrical supply into controlled DC output. In some architectures, power modules are grouped in one cabinet and routed to one or more connectors or dispensers. In other designs, sharing is more limited by fixed internal paths or connector rules.

The EVBox PowerHub description is one example of a centralised architecture that routes power to multiple charging points. It also distinguishes static delivery from optional dynamic load sharing. That distinction matters: centralised architecture does not by itself prove that every deployment uses dynamic allocation.

Part 3. Does power always split equally between active connectors?

No. Some systems use a fixed split, some use equal sharing, some prioritise one connector, and some dynamically assign available channels according to demand. The BTC Power explanation of dynamic sharing describes real-time allocation rather than a permanent equal division.

Real buyer questions reflect this difference: some units allow only one active vehicle, some use a 50/50 split, and some change allocation with finer granularity. That language is not a model specification; it reinforces why a quotation must name the allocation mode.

Important: Do not promise a vehicle a particular charging rate from cabinet power alone. Vehicle acceptance, connector limits, temperature, state of charge, and site controls can all reduce delivered power. Kempower’s charging-power-management documentation describes allocation as equipment-configuration dependent.

Part 4. What happens when one vehicle tapers or disconnects?

Vehicle charging demand commonly changes during a session. In a dynamic architecture, capacity that is no longer needed by one vehicle can become available to another active connector, subject to the charger’s allocation rules and limits. BTC Power uses this tapering behaviour to explain why dynamic allocation can use a shared pool more effectively than a fixed split.

The reallocation is not universal. It depends on the named charger’s routing design, minimum allocation increments, firmware/configuration, active connector limits, and the site’s permitted input. A commissioning test should confirm the observed response with representative vehicles or an approved test method, rather than relying only on a diagram.

Part 5. Which limits can reduce the power each vehicle receives?

The power visible to a driver is the result of several constraints working together. A multi-connector charger can have unused cabinet capacity while a particular vehicle is limited by its acceptance curve. Conversely, two vehicles can request more than the cabinet or site is allowed to deliver.

The commercial EV charging load-profiling guide should be completed before selecting a shared-power configuration. It identifies the site demand and concurrency assumptions that product ratings cannot answer on their own.

Part 6. What should buyers verify before specifying a shared-power charger?

An RFQ needs explicit sharing questions. “Two connectors” is not enough to compare offers.

Part 7. When does a multi-connector DC architecture fit the site?

Shared-power DC architecture can fit commercial sites, fleets, or public locations where concurrent charging is expected and a measured demand model supports the chosen pool. It may be less suitable where each vehicle requires a guaranteed dedicated rate, where the site capacity is not established, or where the model documentation does not clearly state allocation behaviour.

XYDF publishes DC fast charger and commercial solution routes, including a split DC station product route. These are appropriate starting points for a product discussion. They do not, without model-specific evidence, establish a sharing algorithm, module granularity, simultaneous-use behaviour, or delivered-power outcome.

For an informed discussion, send XYDF the required connector count, vehicle mix, dwell and departure pattern, site power limit, target throughput, preferred allocation policy, and expansion plan.

FAQ

Can a dual-connector DC charger charge two vehicles at once?

It can only do so if the named model supports simultaneous operation. Verify this in the model documentation and quotation.

Does power always split 50/50?

No. Some systems use a fixed split, while others use equal, priority-based, or dynamic allocation.

What happens when one EV tapers?

In a dynamic system, unused capacity may be reassigned to another active connector, subject to the charger’s rules and limits.

Is connector power the same as cabinet power?

Not necessarily. Cabinet capacity is the shared pool; connector and cable limits can cap the output available at an individual outlet.

What limits shared charging power?

Site caps, cabinet capacity, routing design, connector limits, vehicle acceptance, allocation rules, and operating conditions can all limit it.

Can site load management reduce charger output?

Yes, when the site control design applies a cap to charging. Verify the integration, settings, and fallback behaviour for the specific project.

What should a buyer verify in an RFQ?

Verify simultaneous use, cabinet and connector limits, allocation mode, routing granularity, site-control interface, and commissioning test method.

References

• Kempower Charging Power Management Documentation
• BTC Power: Dynamic Power Sharing
• EVBox PowerHub Centralised Architecture
• EV Connect: EV Charger Load Management