Procurement fit
Use this product when the project requires a confirmed EV charging configuration before quotation.
Apex 6513 High-Power Charging Hub Controller is high-density controller for high-power DC charging hubs and multi-terminal EVSE architectures.
This product is intended for High-power EVSE manufacturers, Charging hub integrators, Fleet depot system builders, DC fast charger OEMs. It supports B2B teams that need a clear product configuration before quotation, sampling, integration planning or project comparison.
Buyer and application
Who it fits and what problem it solves.
Buyer fitHigh-power EVSE manufacturers, Charging hub integrators, Fleet depot system builders, DC fast charger OEMs
Application fitHigh-power charging hubs, Fleet depots, Multi-terminal systems, Centralized DC charging architecture
Project problemIt helps charger developers and integrators evaluate controller architecture, power module communication, HMI connection, payment module interface and OCPP platform requirements.
Integration scopeIntegration discussion should cover power modules, HMI, meter, payment system, communication interfaces, connector configuration, OCPP platform and cabinet architecture.
Confirmed Specifications
Technical Specifications
| Model | Apex JC-6513 |
|---|
| Digital outputs | 50 channels, sourced, 12V/3A per channel |
|---|
| Digital inputs | 53 channels, sourced |
|---|
| Communication | 8 channels, CAN, RS485, RS232, Ethernet |
|---|
| Operating voltage | DC 12V +/-10% |
|---|
| Operating temperature | -40C to +85C |
|---|
| Dimensions | 385 x 143 x 75mm |
|---|
| Weight | Approx. 1.8kg |
|---|
| Mounting | 35mm standard DIN rail |
|---|
| Operating system | PN-OS Embedded OS |
|---|
| Protection class | IP20 |
|---|
RFQ Inputs
What information is required for quotation?
- Target market and buyer type.
- Power requirement, connector standard and installation scenario.
- OCPP or backend platform requirement.
- Estimated quantity, project stage and expected timeline.
- Branding, firmware, interface, documentation or packaging scope.
Key Features
Key Features
- 50 output channels and 53 input channels support complex charging stack control.
- Suitable for high-power charging hubs, fleet depots and multi-terminal systems.
- 35mm DIN rail mounting supports cabinet-level industrial integration.
- Wide temperature range supports demanding operating environments.
- Good fit for OEMs moving from single-pile chargers to centralized high-power charging systems.
Gallery Images
Gallery Images
Product Details / Interface Images
Product Details / Interface Images
Dimension Drawings
Dimension Drawings
Product FAQ
What information is required for a quotation?
Please provide target market, power requirement, connector standard, quantity, OCPP or platform requirement, application scenario and customization scope for Apex 6513 High-Power Charging Hub Controller.
Which connector standards can be evaluated for this product?
Connector standards can be evaluated during RFQ based on the target market, charger type and available configuration for the selected model.
Can this product integrate with an existing OCPP platform?
OCPP or platform integration should be reviewed against the exact charger model, controller configuration, protocol version and backend platform requirements.
Is the controller configuration project-specific?
Controller and communication configuration can be project-specific and should be confirmed with the charger architecture, HMI, payment system and communication interface requirements.
Can the product be adapted for a target market?
Target-market adaptation can be discussed for connector, communication, documentation and configuration requirements. Compliance details should be confirmed by exact model and market.
What technical information should an OEM buyer provide?
OEM buyers should provide product type, power range, connector standard, controller or platform requirements, branding scope, quantity and application scenario.
Request a Technical RFQ
Send your target station power, number of outputs, required I/O count and backend protocol so we can assess the controller architecture.
