80 kW DC Charger: Vehicle Fit, Site Input and RFQ Guide

Technical review: Marvin
HG Power public DC portfolio context: 40-480 kW

An 80 kW DC charger should be bought as a defined configuration and test plan, not as a promise that every vehicle or both connectors will receive 80 kW. For the reviewed ANSI-DCL080B manual configuration, the stated fields include 80 kW charger capacity, two DC outputs, a 200-750 V / 200 A output field and a 380 V +/-15% three-phase input field. The delivered result still depends on the ordered connector arrangement, vehicle request, simultaneous-use rule, site design and destination-specific evidence. [HG-80-01]

80 kW at a glance

Decision	What must be written down	Why it matters
Rating boundary	Is 80 kW a cabinet, one output or a shared total?	A headline number cannot state how simultaneous sessions behave.
Vehicle envelope	Requested voltage/current and expected charging curve	The vehicle may be the active limit.
Two-output logic	Allowed two-session combinations and priority rule	“Two outputs” does not establish a 40 kW + 40 kW split.
Site input	Exact selected SKU input data, upstream design and local code review	DC output is not a transformer or breaker specification.

What does “80 kW DC charger” actually mean?

It means that a product or proposal has been labelled with an 80 kW capacity boundary. That label becomes procurement-useful only after the seller states what it belongs to, how it is allocated and under which input, environmental and vehicle conditions it is tested.

The reviewed first-party manual identifies an 80 kW unit as ANSI-DCL080B. Its technical-data page lists two outputs, a DC 200-750 V / 200 A field, 380 V +/-15% three-phase five-wire input, 45-65 Hz, IP54 and forced-air cooling. Those are model-manual facts, not a blanket specification for every HG Power DC charger, every connector option or every destination. [HG-80-01]

The useful procurement question is therefore not “Is it 80 kW?” It is: what exact output can the selected configuration deliver to each active vehicle, under which simultaneous-use and site conditions, and what record will prove it?

Build an 80 kW Delivery Ledger before comparing quotes

The 80 kW Delivery Ledger is a one-page configuration record. It should be referenced by the quotation, layout, factory acceptance test (FAT) and site acceptance test (SAT). It is not a replacement for a contract or a local electrical design. It prevents a proposal from drifting between a brochure claim and an untestable delivery.

Ledger field	Buyer question	Required supplier deliverable
Exact model and revision	Which configuration is actually priced?	Model code, datasheet revision and option schedule
Rating boundary	Where does 80 kW apply?	Cabinet/output/system boundary statement
Connector record	What vehicle inlet/interface is quoted?	Connector type, quantity, cable record and target market
Output envelope	What voltage/current can each output use?	Numeric per-output envelope and any shared limits
Concurrent sessions	What happens when both outputs are active?	Two-session matrix and allocation/priority logic
Site input	What must the upstream design use?	Selected SKU input sheet, auxiliaries and local-design assumptions
Backend/options	What is ordered, not merely available?	Protocol version, network route, authentication/payment options and test method
Evidence	How will the proposal be proven?	FAT/SAT plan, readings, pass criteria and exclusions

If a bidder cannot populate this ledger, price comparison is premature. A lower price may describe a different output boundary, fewer ordered options or a different market package.

Why a vehicle may draw less than 80 kW

Charging power is the product of voltage and current: P = V x I. It is useful arithmetic, but not an 80 kW performance promise. At a given point in a session, the vehicle requests a voltage/current pair and changes that request as battery state, temperature and its charging curve change. The connector/output envelope, allocation rule and site cap can impose additional ceilings.

For illustration only, 80 kW at 400 V corresponds to 200 A; at 500 V it corresponds to 160 A. These calculations help a buyer see why the stated DC envelope matters. They do not predict any vehicle's charging session, since the vehicle may not request the needed current and an active second session may change the available power.

Before asking for a promised charge time, capture the vehicle make/model/year, inlet, usable energy window, target state-of-charge window, expected arrival state, ambient/thermal condition and expected concurrent demand. Use the charging-time guide for the conditional calculation; it is the canonical owner for that question.

Two outputs require a Two-Output Proof Card

The manual lists two outputs. It does not state that two vehicles each receive 40 kW, that one vehicle always receives 80 kW, or that allocation follows a particular priority rule. Do not derive those outcomes from a connector count.

Ask each supplier for a Two-Output Proof Card that answers the following with the exact offered SKU:

1. What is the maximum permitted output combination with one vehicle connected?
2. What are the permitted combinations with two vehicles connected?
3. Is allocation fixed, dynamic, priority-based or set by an operator configuration?
4. What voltage/current envelope applies to each connector in each combination?
5. What readings will be recorded during a two-session FAT?

Scenario to witness	Required record	Why a brochure is insufficient
One active vehicle	DC voltage, current, power, duration and alarms	A headline kW label omits vehicle and output limits.
Two active vehicles	Both outputs' voltage, current, power, allocation state and duration	It verifies the actual concurrent rule.
Site cap or control event, if specified	Command/event, response, alarms and recovery	It distinguishes ordered integration from assumed integration.

For general connector-versus-cabinet terminology, see Dual Gun Charging. This page remains focused on proving the exact 80 kW offer.

Site fit: use declared input data, then design locally

The reviewed manual lists a 380 V +/-15% nominal input field, three-phase five-wire supply and 45-65 Hz for ANSI-DCL080B. It also gives model-specific installation notes, including foundation and cable-entry guidance. [HG-80-01] [HG-80-02]

Those fields are necessary inputs to a site review, but they are not enough to size a transformer, feeder, protective device, earthing arrangement or civil foundation. The local engineer must use the final model's documents, applicable code, upstream load study, fault protection, cable route, metering approach, ambient conditions and the project load-management policy.

Site input to freeze	Do not replace it with	Evidence to request
Selected SKU input current and supply field	80 kW / voltage arithmetic alone	Current datasheet, single-line assumptions and drawing
Upstream service capability	Charger nameplate	Site load study and utility/site-owner confirmation
Protection and earthing design	Generic internet recommendation	Local engineer design and destination code review
Civil/foundation layout	Another project's photo	Supplier drawing, cable entry plan and site dimensions
Heat, access and maintenance route	IP or cooling label alone	Clearance, airflow, drainage and maintenance plan

The manual calls for regular checks of fasteners, connections, emergency stop availability, grounding and protection-related conditions. That supports making maintainability and safe access part of the project handover record; it does not demonstrate future uptime or a particular maintenance interval. [HG-80-03]

What the reviewed 80 kW manual states – and where its authority stops

Manual field for ANSI-DCL080B	What it can help a buyer ask	What still must be confirmed in the order
80 kW capacity	What is the declared product boundary?	Is the same exact model and option set being supplied?
Two outputs	Which concurrent-use proof is needed?	Per-output allocation, priority and test matrix
DC 200-750 V / 200 A field	Does the vehicle/output-envelope discussion start with compatible numbers?	Final connector/inlet, output logic and actual vehicle request
380 V +/-15%, three-phase five-wire input	What input data must enter the site review?	Local design, protection, upstream capacity and final datasheet
IP54 / forced air	Which environmental/mechanical questions should be asked?	Location, enclosure, derating, clearance and local requirements
OCPP 1.6 and listed interfaces	Which backend integration should be defined?	Ordered implementation, security, CSMS compatibility and witnessed tests

This distinction is especially important across borders. A manual can orient the engineering discussion. The quotation, target-market document pack and configuration label determine what is actually offered.

OCPP, access and network functions: specify the implementation, then test it

The manual lists OCPP 1.6, RS-485/GPRS-oriented network descriptions and authentication/UI fields. [HG-80-01] The Open Charge Alliance describes OCPP as a protocol between charge points and charging-management systems. It also notes that OCPP 2.0.1 is not backward-compatible with OCPP 1.6. [OCPP-01]

Therefore, “OCPP” in a quotation is not enough. Ask for the exact protocol edition/transport, backend endpoint provisioning process, authentication behaviour, network route, certificate/security responsibility, remote-operation tests, meter-value fields and failure/recovery behaviour. Do not claim compatibility until the offered charger and selected CSMS have passed the agreed integration test.

When should an 80 kW configuration be modelled?

An 80 kW option can be worth modelling where the operation needs more than lower-power DC service but does not yet justify a higher 120 kW-class configuration after vehicle, concurrency and site limits are considered. That is a modelling prompt, not a universal market recommendation.

Operating condition	80 kW may be worth modelling when…	Do not decide from…
Commercial parking	Dwell and expected energy demand are documented, with a credible site input path.	A desire for a “fast” label.
Fleet/depot	Arrival windows, vehicle envelopes and simultaneous sessions are known.	Total fleet count without mission energy data.
Distributor project	Connector/destination requirements and evidence package are defined.	A catalogue photo or a generic certificate claim.
Two-vehicle operation	The Two-Output Proof Card can be supplied and witnessed.	“Dual output” wording.

Do not select the configuration yet if the vehicle interface is unknown, the site supply has not been checked, concurrent-use priority is unstated, a protocol is presumed rather than integrated, or destination documentation has not been assigned.

Use the Four-Document Ladder from quote to handover

Stage	Required content	Release question
Configuration quotation	Exact model, connector/options, rating boundary, exclusions	Are competing bids describing the same deliverable?
Approved technical record	Drawings, site assumptions, destination document plan, test matrix	Can civil/electrical design proceed against a stable configuration?
FAT record	Instrument/readings, one- and two-output tests, alarms and agreed options	Did the factory prove the ordered boundary?
SAT/handover record	Installed configuration, site conditions, functional/integration tests, open items	Was the same configured system accepted at the site?

The strongest project control is traceability: the model/options and the claimed boundary should remain recognizable from the commercial quote through the final test record.

The 12-input RFQ for an 80 kW DC charger

1. Destination country and applicable project/customer requirements.
2. Vehicle make/model/year and inlet type, or the required interface standard.
3. Target charging energy window and operating dwell window.
4. Expected number of simultaneous sessions and their priority.
5. Required one- and two-output behaviour.
6. Available site supply, measured/declared spare capacity and utility constraints.
7. Site layout, cable route, access, foundation and drainage constraints.
8. Indoor/outdoor exposure, temperature, altitude and protection expectations.
9. Authentication, payment and user-flow requirements.
10. Backend/CSMS, protocol edition, network route and integration-test owner.
11. Required documents, language, destination conformity and inspection expectations.
12. Required FAT, SAT, readings, acceptance criteria and exclusions register.

Send these inputs with the requested delivery date and quantity. HG Power can then respond with a configuration-specific proposal, not an 80 kW headline detached from vehicle, site and acceptance conditions.

FAQ

Can an 80 kW DC charger charge two EVs at 40 kW each?

Only if the exact offered configuration states that allocation and the vehicle/output/site conditions support it. The reviewed manual's two-output field alone does not establish that split. Request the Two-Output Proof Card and witness it during FAT.

How long does an 80 kW DC charger take to charge a car?

There is no universal time. It depends on the vehicle's requested voltage/current, its charging curve, battery state and temperature, the allocated output and the site/control conditions. Use the charging-time guide with a defined vehicle and energy window.

What electrical supply does an 80 kW DC charger need?

For the named ANSI-DCL080B manual configuration, the manual lists 380 V +/-15% three-phase five-wire input and 45-65 Hz. This does not determine the final upstream design. Use the exact quoted SKU and a local electrical engineer's design for the project.

Does OCPP 1.6 guarantee backend compatibility?

No. It identifies a protocol scope, not a completed deployment. Define the protocol/transport, backend, credentials, security and test cases, then verify the ordered charger with the selected CSMS.

Sources and review scope

• HG Power, 80KW DC Charger for Electric Vehicle User Manual, ANSI-DCL080B, pp. 3-9, 19, 26-27; reviewed 2026-10-13. [HG-80-01] [HG-80-02] [HG-80-03]
• Open Charge Alliance, OCPP protocols; reviewed 2026-10-13. [OCPP-01]

Technical review: Marvin. Review confirms the article's manual-scope and procurement boundaries only; it does not substitute for destination-specific engineering, conformity review or contract acceptance.