Battery-cluster, PCS/DC-bus, and protected-load interfaces
An ESS PDU or HVJB can organize high-voltage paths between battery clusters, PCS/DC buses, and protected branches. The exact topology follows the system single-line diagram.
Custom ESS PDU capability
custom ESS PDU · Product category / ESS distribution and protection platform overview
Custom ESS Power Distribution Units for Battery Energy Storage Systems
TRHT supports project-based ESS PDU and HV distribution engineering for battery energy storage architectures. Scope is defined around the battery/rack arrangement, PCS or DC-bus interface, protection strategy, enclosure, communications, and validation plan.
The role of an ESS PDU
Distribution, isolation, protection, sensing, and control
Project scope may include contactors, pre-charge, fuses or breakers, current/voltage sensing, insulation-monitoring interfaces, busbars, harnesses, and communications.
TRHT ESS PDU and HVJB capability
Cluster-level HVJB platforms
Controlled ESS master records describe 750V/250A and 1000V/400A HVJB reference targets. Values remain target or conditional design windows pending system, thermal, protection, and validation review.
Multi-branch DC distribution platforms
A 1000V maximum, 400A main-bus, multi-branch DC PDU target is described for project-defined branch protection and interface coordination. It is not a universal released rating.
Reference platform families
750V/250A HVJB reference target
The controlled target window is 600–750VDC with a 250A continuous target and 400A/10s peak target, subject to final thermal, fault, and validation conditions.
1000V/400A HVJB and multi-branch PDU reference targets
The controlled 1000V-class records describe 600–1000VDC and 400A continuous HVJB targets, plus a 1000V maximum/400A bus multi-branch PDU target. Treat these as reference windows, not guarantees.
Engineering inputs required before selection
- System voltage window and continuous/peak current
- SLD, rack/string arrangement, PCS or inverter interface
- Branch count, fault current and time-constant data
- Contactor, fuse, breaker, pre-charge, sensing and communication requirements
- Cabinet envelope, cooling, environment, IP target, quantity and project stage
Protection coordination and validation boundaries
Final protection selection requires system and fault data, thermal review, interface definition, and an agreed validation plan. DVP&R and EOL templates describe process planning; they do not prove that every platform has completed the named tests.
TRHT's defensible C&I scope is HVJB/DC PDU, busbar and harness support, interface coordination, and test support. Complete cells, packs, BMS/EMS, PCS, cooling, fire protection, and whole-system certification remain system or partner scope unless separately contracted.
Applications within TRHT's component scope
The capability is relevant to battery cabinets, cluster distribution, PCS/DC-bus interfaces, protected branches, and related high-voltage storage architectures. The specific application, responsibility split, and release criteria must be confirmed for each project.
Evidence context
Real TRHT engineering and testing context
These visuals support a conservative engineering and workmanship context. They do not identify an exact model or prove a universal rating, certification, customer case, or completed validation result.
Buyer questions
Frequently asked questions
What is an ESS PDU?
An ESS PDU is a high-voltage distribution and protection assembly used within a battery energy storage architecture. It may connect battery racks or clusters to PCS/DC buses and protected branches.
What is the difference between an ESS PDU and an HVJB?
An HVJB commonly centers on main isolation, pre-charge, sensing, and cluster-level protection, while an ESS PDU may also manage multiple protected branches or DC-bus distribution. The system SLD determines the appropriate role.
What information is required to design an ESS PDU?
Share the voltage window, continuous and peak current, SLD, rack/string arrangement, PCS interface, branch list, fault data, protection requirements, enclosure, cooling, environment, communications, quantity, and project stage.
How are branch protection devices selected?
Branch protection follows load duty, fault current, time constant, coordination requirements, service strategy, thermal conditions, and the selected fuse, isolator, breaker, or contactor architecture.
Can communication interfaces be customized?
Communication and status interfaces can be defined around the BMS, EMS, PCS, and project control architecture. Final protocol and frame requirements must be frozen during engineering review.
What remains project-specific after selecting a reference platform?
Final voltage/current limits, protection coordination, branch interfaces, enclosure/IP, thermal conditions, communications, BOM, drawings, DVP&R, EOL criteria, and certification scope remain project-specific.
Continue your review
Related TRHT resources
Move from category understanding to architecture review, factory context, or an RFQ conversation.