EN CN

EV Charging Module Voltage Range: How to Match Voltage, Current and Constant-Power Requirements

Home News News Showcase

EV Charging Module Voltage Range: How to Match Voltage, Current and Constant-Power Requirements

2026-09-02

UUGreenPower

0

An EV charging module should be evaluated against the operating points the charger must actually serve, not against a headline voltage alone. The buyer needs one record that keeps output voltage, current, constant-power range, thermal condition and model revision together. This Operating-Envelope Worksheet helps engineering decide whether to retain a model, request evidence or hold the comparison.


ChatGPT Image 2026年9月2日 11_42_25 (1).png


Freeze charger inputs in one worksheet

 

Before comparing models, record the charger-level requirement: lowest and highest requested voltage, power at each important point, current, number of active ports, concurrency rule, ambient range and the evidence behind each vehicle or system point. Add the exact model suffix, document revision, date and any option or change notice. A port or controller allocation rule belongs to the complete charger; it should not be inferred from a module count.

 

Use these worksheet fields:

 

Requirement row

Evidence to capture

Decision check

Voltage and power points

Required voltage, power and current at each point

Is the point in the named model evidence?

Constant-power region

Stated range and condition

Is full power documented at the required voltage?

Thermal condition

Operating range, derating start and requested test data

Is the start point being mistaken for a curve?

Port/concurrency

Ports, allocation rule and per-port requirement

Is system behavior separately owned?

Model/version

Suffix, revision, date, option and deviation status

Can another reviewer reproduce the row?

 

Read output range and constant power separately

 

The UUGreenPower catalogue illustrates why each row must stay model-bound.

 

Named model

Output range

Constant-power range

Current

Temperature / derating

Cooling wording

UR100040-IP65(EU)

150–1000VDC

300–1000VDC at 40kW

0.5–133.3A

−40°C to 75°C; from 55°C

Cooling: Air; independent air duct wording on the named entry

UR100040-SW(EU)

150–1000V

300–1000V at 40kW

0.5–133.3A

−40°C to 75°C; from 55°C

Cooling: Air

UR100040-LQ(EU)

150–1000V

300–1000V at 40kW

0.5–133.3A

−40°C to 75°C; from 60°C

Cooling: Liquid

UR150027L(EU)

200–1500V

300–1000V at 40kW

0.5–106.6A

−40°C to 75°C; from 60°C

Cooling: Liquid

 

The output range is not the constant-power range. UR150027L(EU) is listed up to 1500V, but its documented constant-power range remains 300–1000V; it must not be described as 40kW constant power from 300V to 1500V. The same distinction applies to the 150–1000V entries. A derating start temperature is also not a complete derating curve. Request the applicable test table or curve instead of drawing intermediate output points.

 

Keep evidence at the named model level

 

Treat the model, version and condition as one evidence unit. If the source does not identify current at the required voltage, write “evidence required.” Do not use a family value to fill a missing row, and do not transfer module cooling or IP wording to a cabinet or complete charger. The worksheet should state which party closes each unresolved row: supplier clarification, engineering test, external official requirement or project approval.

 

Efficiency is intentionally not a scoring column here. Peak, rated and full-load wording belongs in the efficiency comparison owned by M1-015; adding a second efficiency discussion would duplicate that decision. The operating-envelope worksheet only records the conditions needed to establish voltage, current, power and thermal fit.

 

Apply the worksheet at the operating points

 

Begin with the lowest voltage at which the charger must deliver its required power. Check the named model’s output range, then check whether the same point is inside the documented constant-power region. Record the current required there and compare it with the model’s stated current field. Repeat the check at the upper operating point and at any mandatory intermediate point. If the vehicle requirement is expressed as a battery or system window, preserve that source and do not replace it with a single nominal voltage.

 

Next, test the conditions that can change the decision. Mark whether one or several ports are active, which controller rule allocates power, and whether the cabinet or connector imposes a lower limit. Add the ambient condition and the source’s derating start temperature beside the operating point. If the project needs data between the stated points, request a controlled table or curve; do not interpolate from a start temperature or a maximum output value.

 

The worksheet should also show what is not being concluded. A module row can establish a documented component envelope, but it cannot prove the complete charger’s simultaneous behavior, vehicle compatibility, cabinet thermal performance or regional approval. Those items can be linked as separate project rows with their own owners. This keeps the operating-envelope decision useful without turning it into a universal product claim.

 

Release or hold the comparison

 

Use three outcomes:

 

Retain: every required operating point and model/version field is traceable.

Retain with open evidence: the route may fit, but a named test, condition or responsibility remains open.

Hold: a missing field could change the charger architecture or safe operating envelope.

 

Before release, attach the source revision, unresolved questions, owner and next review date. If the requested power lies outside the documented constant-power range, request evidence or revise the requirement rather than filling the worksheet with an assumed curve. A clean row lets procurement and engineering compare the same object when the shortlist is revisited.

 

Before the design freeze

 

An EV charging module voltage range becomes decision-useful only when it is connected to current, constant-power range, thermal conditions and version. For a dc charging module, the next action is to complete one evidence row per named model and escalate any unresolved condition before the architecture is frozen. UUGreenPower catalogue entries can support that model-level review without becoming a complete-charger or vehicle-compatibility claim.


Back

Online

TOP

We use cookies on this site, including third party cookies, in order for the site to work properly and to analyse traffic, offer enhanced functionality, social media features, and personalise content and ads. Learn more