JP-PLC — a WiFi-enabled Dual-core PLC (factory-flashed) and JP-CTRL — a Quad-core Industrial Controller (image pre-loaded). The EV-side brain and the Linux-side brain of a DC fast charger. Certified firmware inside. Built-in UV/OV + ground-fault protection. WS2812B-driven RGB LED animations. RS485 + CAN + Ethernet + WiFi + USB + HDMI on-board. Snap together, wire up, ship.
Joulepoint
DC fast-charging controller & PLC · ready-to-assemble
Most charger problems aren't about the power electronics — they're about the brain. This is what we rebuilt.
Linux-based controller running our hardened charging stack. Real-time control plane to the power modules, supervisory plane to the CSMS, operator plane to the kiosk HMI.
Optional encrypted peer-to-peer mesh tunnel for support and diagnostics. No port forwarding, no static IPs, no cellular VPN bills. Toggle on only when needed.
Edit modules, OCPP profile, RFID, planner, PLC transport, authorization — and save without restarting the controller. Field-tunable in minutes.
Upload your logo and support phone. The kiosk and admin views rebrand immediately. OEM-ready on day one.
Activation codes are minted against the Linux device fingerprint. Codes for any other unit are rejected — refurb and clone protection without DRM friction.
Driver-based abstraction over power modules (LAN GenericKM2 BLN and others). Qualify two or three module vendors and source whichever wins each batch.
From the Tata Ace EV on your last-mile fleet to the Kia EV9 at the family parking bay — the SLAC engine, HLC stack, Plug & Charge handshake, and module CAN orchestration are validated against 16+ brands and 44 passenger and commercial models. New India-launch lineups join the test matrix as they land.
Nexon EV · Punch EV · Tiago EV +3
XUV400 · BE 6 · XEV 9e
e Vitara
ZS EV · Comet EV · Windsor EV +1
Kona Electric · Ioniq 5 · Creta Electric
EV6 · EV9 · Carens Clavis EV
Atto 3 · Seal · e6 +1
eC3 · eC3 Aircross
Enyaq
VF 6 · VF 7 · VF e34
Ace EV · Yodha EV · Intra V20 EV
Pro 2049 EV · Pro 6055 EV
EiV 12 · IeV4 LCV
K9 · C9 · K7
Galaxy · Citylife
Featherlite · PMI-FE
Connector compatibility
Every connector your customers will roll up with.
CCS2
Primary India standard
Used by every passenger EV brand on this page — the JoulePoint default validation target.
Type 2 AC
AC backup path
Type 2 AC compatible for vehicles that fall back from CCS2 DC during pre-charge or thermal events.
GB/T
China-fleet ready
Driver path validated via the Tonhe module family for sites with imported Chinese commercial EVs.
CHAdeMO
Legacy support
Driver path available for older fleet vehicles still on CHAdeMO — same controller, no hardware change.
16+
Brands on the test matrix
Indian + global, mass + premium
44
Models validated
passenger + commercial
6
Countries of origin
India · Korea · Germany · China · Japan · USA · Sweden · France · Czechia · Vietnam · UK · Italy
4
DC connector types
CCS2 (primary) · Type 2 AC · GB/T · CHAdeMO
Brand names, model names, and marks shown are the property of their respective owners. The “tested with” claim refers to vehicle-side handshake validation (SLAC, HLC, ISO 15118-2/-20, OCPP-side metering and stop conditions) against vehicles of these brands — no endorsement, partnership, or affiliation is implied. Validation coverage is continuously extended as new EVs reach India.
Every Joulepoint charger is built from two cooperating compute units plus a hardware safety chain. The PLC owns everything the EV touches; the controller owns everything the operator and the CSMS touch. Regulatory-slow firmware stays still — product-fast software ships monthly.
EV
CCS2 · CCS1 · GB/T
EV-side brain
JP-PLC
WiFi Dual-core · HPGP modem · 3-relay drive · WS2812B
Linux-side brain
JP-CTRL
Quad-core ≥ 1.5 GHz · ≥ 2 GB RAM · RS485 · CAN · ETH · WiFi · USB · HDMI
Power modules
Maxwell · UUGreen · Tonhe
DC output
to EV battery
Your CSMS
OCPP 1.6J · 2.0.1
JP-CTRL peripherals
JP-HMI
7 / 10 / 15" HDMI capacitive touch
JP-RFID
USB HID · ISO 14443 · MIFARE
Status visibility
WS2812B addressable RGB on both the connector collar and the cabinet — themable per OEM.
Backhaul
Ethernet · WiFi · LTE · Tailscale auto-failover.
JP-SAFE · hardware-rooted safety chain
UV · OV · phase-loss · ground-fault · IMD · welded-contactor · surge · ESD · tamper · thermal — independent of both MCUs. If the firmware locks up, JP-SAFE still trips.
WiFi-enabled Dual-core PLC
Power-Line Communication
Sealed module, factory-flashed, NVS-provisioned to your charger ID + gun ID
Owns
Quad-core Industrial Controller
Linux supervisory + ops plane
Sealed industrial unit, image pre-loaded, ≥ 1.5 GHz, ≥ 2 GB RAM, signed boot
Owns
Hardware safety chain
Hardware-rooted, MCU-independent
Analog + digital safety board between AC input and the DC stage — trips even if both MCUs lock up
Owns
Regulatory cycles for high-voltage HLC firmware (ISO 15118) are slow. Linux controller cycles (OCPP profiles, UI, billing, planner) are fast. JoulePoint lets your product team ship monthly UI and OCPP updates without retouching certified HLC firmware. One image scales from STD to XTREME — no code forks per SKU.
Every SKU below ships flashed, tested, and provisioned to your charger ID. You don't compile anything. You don't NDA-license anyone's SDK. You bolt them in, wire the harness, scan the QR code, and the charger is live.
JP-CTRL
Quad-core Linux brain. Image pre-loaded. RS485 · CAN · Ethernet · WiFi · USB · HDMI · WS2812B — all on-board.
JP-PLC
Sealed module, factory-flashed with the full SLAC + HLC + PnC stack. HomePlug GreenPHY modem on-board.
JP-SAFE
UV · OV · phase-loss · ground-fault · IMD · welded-contactor · surge · ESD · tamper · thermal — hardware, not firmware.
JP-HMI
7″ · 10″ · 15″. 10-point capacitive, optical bonded, sunlight-readable option.
JP-RFID
ISO 14443-A/B, MIFARE Classic / DESFire, HID Prox, EM4100, NTAG2xx — plug-and-play.
JP-LED
Connector-collar ring + cabinet status strip. Driven independently by PLC and Controller.
JP-WIRING
Pre-built, factory-cut, color-coded harness with pluggable Phoenix-style terminals. Match colors, done.
The controller image runs unchanged across STD, PRO, and XTREME — only the silicon changes. No code forks per SKU, no per-tier firmware build, no extra QA matrix. Pick the chassis your deployment climate and topology demand.
Entry / mid · 1–2 gun
Operating temperature
0 to +60 °C
Production · 2–4 gun · networked
Operating temperature
−20 to +70 °C
Industrial / outdoor / extreme climate
Operating temperature
−40 to +85 °C
Full hardware matrix
Spec-by-spec across all three tiers
| Capability | STD | PRO | XTREME |
|---|---|---|---|
Compute | |||
| CPU | Quad-core ≥ 1.5 GHz | Quad-core ≥ 1.8 GHz | Quad-core ≥ 2.0 GHz |
| RAM | 2 GB DDR4 | 4 GB DDR4 | 8 GB DDR4 |
| Storage | 32 GB eMMC | 64 GB eMMC | 128 GB eMMC |
I/O | |||
| RS485 | 1× | 1× | 2× isolated |
| CAN | 1× iso | 1× CAN-FD iso | 2× CAN-FD iso |
| Gigabit Ethernet | 1× | 2× | 2× |
| WiFi | 2.4 / 5 GHz | WiFi 6 | WiFi 6 |
| USB | 2× | 4× | 4× |
| HDMI 1080p | Included | Included | Included |
| WS2812B out | Included | Included | Included |
| BLE | — | Included | Included |
| M.2 LTE / 5G slot | — | Included | Included |
| Audio out | — | Included | Included |
| PoE-in | — | — | Included |
| Isolated 24 V industrial I/O | — | — | Included |
| TPM 2.0 | — | — | Included |
Environmental | |||
| Operating temp | 0 → +60 °C | −20 → +70 °C | −40 → +85 °C |
| Conformal coating | — | — | Included |
Every Joulepoint charger ships with a production-grade admin and kiosk HMI — no separate UI subscription, no third-party vendor portal. Below is what your operators get out of the box.
Single-pane controller / CSMS / PLC / network health, plus a live operations snapshot — the first thing your field engineer sees on every visit.
Live electrical values for every gun, session and auth state, planner context, vehicle demand — plus stop / clear-fault controls without leaving the kiosk.
Active and historical sessions with energy, power, duration, and per-row deep links. Built in, not a separate dashboard product.
Hot-reloadable site limit, OCPP SmartCharging integration, group power cap per PLC chain, cross-PLC borrowing toggle — editable without a controller restart.
Connector and PLC fault history with active vs resolved separation. No more digging through 30 MB log files to find what tripped the bay.
Edit modules, OCPP, RFID, planner, PLC transport, authorization — and save without restarting the controller. Field-tunable in minutes.
Upload your logo and support phone. The kiosk and admin views rebrand immediately. OEMs ship branded UI on day one.
Wi-Fi SSID scan + on-screen connect, wired primary device control, gateway and address visibility, plus a one-click Capture Diagnostic for field handoff.
Optional encrypted peer-to-peer mesh tunnel. The charger works fully without it — leave it off when you don't need remote access. No port forwarding, no static IP, no cellular VPN bill.
Per-chain health for every PLC chain in the cabinet — separate from controller health so you can isolate where a fault really lives.
Time-windowed runtime log access from the UI. Pair with Capture Diagnostic to ship an evidence bundle to engineering without SSH.
Health checklist plus operator-grade actions: Refresh Health, Recompute Planner, Restart Controller. No full reboot, no field engineer escalation.
Activation codes are minted against the Linux device fingerprint of that specific controller. Codes for any other unit are rejected — anti-counterfeit and refurb protection without DRM friction.
Driver-based abstraction over power modules. Qualify two or three vendors and source whichever wins each batch — no firmware change.
Live walkthroughs and screen recordings are available under NDA — talk to our sales engineering team.
What actually happens between T+0 and T+END on a Joulepoint charger. Every CP transition, SLAC step, HLC sub-state, AUTH check, relay command, module ramp, and meter read is timestamped and exported to the controller's journal.
Driver plugs in. CP transitions A → B1 within milliseconds.
JP-PLC samples the CP front-end, debounces, and emits a connector state event to the controller. Connector LED ring switches from idle breathe to plug-detect.
JP-CTRL opens a new session, leases a heartbeat to the PLC, and queues authorization while SLAC is armed.
PLC starts PWM @ 5 % duty and runs the full SLAC handshake: CM_SLAC_PARM → MNBC → ATTEN_CHAR → SLAC_MATCH.
TCP + TLS over EXI. SupportedAppProtocol → SessionSetup. EVCCID / EMAID captured.
Identity is checked in this order: OCPP Authorize.req → local allowlist → RFID allowlist → MAC autocharge (if enabled).
PLC continues the HLC sequence and exports every ISO message sub-state + age to the controller.
JP-SAFE confirms isolation > threshold. Only after this does the PreCharge sequence advance.
EV voltage is within ΔV of EVSE. Controller commands all three relays closed with a hold timeout.
PLC enters CurrentDemand and answers the EV with controller-fed values. Connector LED switches to the charging power-bar animation; cabinet LED pulses online.
BMS publishes target V / target I / SOC / stage every 100 ms. Module CAN @ 100 ms control / 50 ms telemetry. Orchestrator clamps to module capability + site limit. Meter @ 1 s for OCPP MeterValues. JP-SAFE monitors UV / OV / ground-fault continuously.
EV / user / RFID / CSMS triggers STOP. Modules ramp down (300 V/s, 120 A/s) → wait for quiet current → open relays. JP-SAFE confirms no welded contactor. OCPP StopTransaction with final meterStop.
Every step above is replayed by Joulepoint field-support from the on-board journal. The exact ISO message, relay command, or module ramp that misbehaved is quoted back to you in minutes — not hours.
JP-SAFE sits between the AC input and the DC stage as an independent analog + digital board. If both MCUs lock up, JP-SAFE still trips. Every protection here is hardware-rooted — and every trip event is journaled, surfaced to the HMI, raised to the CSMS via OCPP, and flashed on the cabinet LED strip.
AC input
Grid · 1Φ / 3Φ
Hardware safety chain · MCU-independent
DC stage
Contactor · modules · gun
Independent E-Stop chain
The mushroom button cuts contactor drive directly — bypassing both MCUs. The controller is informed, not consulted.
Per-supply tunable
Configurable threshold with hysteresis to avoid chatter. Trips contactor below set point.
Per-supply tunable
Configurable threshold above the rated supply. Hard trip protects every downstream stage.
3-phase aware
Detected on 3-phase input. Trips contactor and reports to controller for CSMS alarm.
6 mA AC · 6 mA DC
Residual-current monitoring per IEC 62752 / IEC 61851-1 Annex E. Separate AC and DC thresholds.
Pre-PreCharge gating
Industry-standard Bender / SMA-compatible analog interface. Trip on insulation below threshold.
Post-stop verification
Runs after every PowerDeliveryStop. Welded? Charger is automatically removed from CSMS service.
MCU-independent
Mushroom button interrupts contactor drive independently of firmware. Controller is informed but not in the safety path.
Class-II
Class-II SPD on AC input. GDT + MOV stack catches grid transients before the DC stage.
All external ports
TVS diodes on every external signal line. Per-rail current monitor logs abnormal draw.
Ramp + cutoff
NTC on the cabinet temperature. Power ramps down at the soft threshold, hard trip at the limit.
Cabinet door
Cabinet-open input. Logs the event, optionally disables service until cleared by operator.
Boot-time safe
Protected controller DC input. NTC + bypass relay inrush limiter on supply rails.
On any trip
Journaled
Append-only event in the controller journal
On any trip
Surfaced
HMI fault card with class + timestamp
On any trip
Raised
OCPP alarm + diagnostic upload
On any trip
Encoded
WS2812B red flash with morse fault class
Addressable RGB lives in two places: the connector collar ring (driven by JP-PLC) and the cabinet status strip (driven by JP-CTRL). Drivers cross a station and know what's happening from a hundred metres away. OEM palette is themable, animation choreography is a JSON keyframe pack — no firmware rebuild.
Cabinet strip
Slow breathe in the OEM accent color. Cabinet strip pulses gently.
Cabinet strip
Solid brand color the instant CP transitions A → B1.
Cabinet strip
Sweep / chase animation. Cabinet pulses faster to mirror handshake progress.
Cabinet strip
Faster sweep until the EV answers with ChargeParameterDiscovery + CableCheck.
Cabinet strip
Yellow pulse — RFID or CSMS Authorize.req in flight.
Cabinet strip
Power-bar fill. Hue shifts from cyan → green as SOC climbs. Cabinet glows online.
Cabinet strip
Red flash with morse-coded fault class. Cabinet flashes in sync.
Cabinet strip
Blue progress bar on the connector ring, chase on the cabinet strip.
Pixels addressable
16+24
per gun (typical)
CPU overhead
< 1 %
at 30 fps
Themable per OEM
JSON
no firmware rebuild
Most charger problems aren't about the power electronics — they're about the controller, the HMI, the remote access, the licensing, and the lock-in. We rebuilt that whole layer.
Industry default — every parameter tweak means a field visit
Hot-reloadable Config Editor + Remote Tunnel: change driver, modules, OCPP profile, RFID, planner from anywhere, no controller restart.
Most CPOs pay $30–80 per charger per month for a managed APN + remote SSH
Built-in Tailscale mesh — peer-to-peer, encrypted, no port forwarding, no static IP. Toggle on only when support is needed.
Most charger controllers are hard-wired to one module brand
Driver-based module abstraction (we ship LAN GenericKM2 BLN and others). Source the cheapest qualified module without rewriting firmware.
Refurbed and grey-market chargers eat OEM margin
Per-device hardware-bound licence — activation codes are minted from a Linux device fingerprint; codes for any other unit are rejected.
Most OEMs ship a vendor HMI on top of someone else's controller
Production-grade admin HMI with white-label logo + support phone upload. OEMs ship a branded UI on day one.
Static splits waste headroom; live sharing usually needs a separate dispatcher box
Built-in site-aware planner: site limit + OCPP SmartCharging + group cap + cross-PLC borrowing — hot-editable from the UI.
Operators end up calling the OEM for every fault, every time
Fault Center, Refresh Health, Recompute Planner, Restart Controller — operator-grade actions in the UI, no SSH required.
Many OEM controllers only talk to that OEM's CSMS
Native OCPP 1.6J / 2.0.1 — point Charge-Point ID + CSMS URL at any CSMS (ours, AmpEco, Driivz, Monta, your own). Change it from the live config without firmware.
Concrete cost arguments by buyer persona. Numbers are mid-market estimates from public CPO operating benchmarks and our own deployments in India and Europe.
Cut remote-access spend
Tailscale's free / starter plans replace the typical cellular APN + VPN concentrator. For a 500-charger network this is $15k–$40k/year of OPEX gone, with stronger encryption than most managed APNs.
~$30–80 / charger / month saved
Kill truck-rolls for config
Every site visit costs ₹3,000–8,000 in fuel + engineer time in India, $100–400 in the EU/US. Hot-reload + remote tunnel removes 60–80% of those visits — the ones that exist today only to change a parameter or restart a process.
~60–80% of config-driven truck-rolls eliminated
Stop paying for a third-party HMI
Our kiosk + admin is included. No separate UI subscription, no per-charger licence on top of the controller, no $5–15/month-per-charger HMI vendor.
$60–180 / charger / year saved
Ship a branded controller on day one
Upload your logo + support phone, mint per-device licence codes from a fingerprint. Skip the 6–12 month effort of building your own admin HMI and licensing pipeline.
~6–12 months engineering avoided
Protect aftermarket revenue
Each activation code is bound to a specific Linux device fingerprint. Refurbished units can't be cloned, grey-market boxes can't bypass spare-parts revenue.
Refurb / grey-market arbitrage removed
Source modules competitively
The module abstraction lets you qualify two or three power-module vendors and quote whichever wins each batch — without firmware changes. Direct margin lift on every cabinet.
5–15% margin on power-module BOM
Most CPOs pay $30–80 per charger per month for a managed cellular APN plus a VPN concentrator just so engineering can SSH in. We replaced that with Tailscale's peer-to-peer encrypted mesh — the same technology used by enterprise infra teams. It costs almost nothing, encrypts end-to-end, requires no port forwarding, and the operator can revoke a key in a single click.
Charger ships with the tunnel OFF. The unit works fully without it.
When you need remote support, the operator turns the tunnel on from /admin/tunnel.
The shared key is minted by your support tenant — not by a third-party VPN vendor — so revocation is in your hands.
Tailscale connects engineer ↔ charger over its encrypted mesh. No port forwarding on the site router, no static IP, no SIM-card APN.
Disconnect, Logout (keep key), or Forget Key — three states the operator controls, all from the UI.
On first boot the controller derives a Linux device fingerprint. The Licence page shows it so you can copy it to your vendor support contact.
Support mints a 15-character code bound to that exact fingerprint. Codes for any other unit are rejected at activation.
Once active, every page shows a verified badge with activation date, stored code, and code file path.
Refurbished or grey-market units can't reuse another unit's code. Protects OEM aftermarket revenue without imposing DRM friction on the legitimate operator.
Each activation code is derived from the Linux device fingerprint of that specific controller. Refurbished units can't be cloned, grey-market boxes can't bypass spare-parts revenue, and the legitimate operator never has to deal with a network-call licence check.
The controller runs a site-aware planner that respects the contracted grid cap, OCPP SmartCharging profiles, group power caps per PLC chain, and cross-PLC borrowing — all live, all hot-editable.
Site limit (kW)
Hot-reloadable transformer/grid cap. Changes apply within ~50 ms.
OCPP SmartCharging limit
Respects active SmartChargingProfile from the CSMS.
Group power per PLC chain
Per-chain cap so a sticky vehicle doesn't starve siblings.
Cross-PLC borrowing
Optional — let an idle chain lend headroom to a busy one.
Live planner analytics
Requested / offered / allowed / assigned kW visible per cycle.
The PLC stack is observable, swappable, and tunable from the admin — not a black box. Each chain reports health separately so you can isolate a failed chain without guessing.
| Parameter | Value |
|---|---|
| Standard | HomePlug Green PHY · ISO 15118 PLC profile |
| Frequency range | 2–30 MHz |
| Data rate | Up to 10 Mbps typical |
| Per-cabinet chains | Multiple PLC chains supported, cross-PLC borrowing under planner control |
| Interface | Ethernet / CAN to the controller, PLC physical to the vehicle inlet |
| Power supply | 9–16 V DC |
| Operating temperature | −40 °C to 85 °C |
| Protection | Surge + ESD protected, conformal coated |
| Health visibility | Each PLC chain surfaces healthy / faulty separately to the admin Fault Center |
| Capability | Profile | Joulepoint |
|---|---|---|
| StartTransaction / StopTransaction | OCPP 1.6J | ✓ |
| Authorize / IdTag | OCPP 1.6J + 2.0.1 | ✓ |
| MeterValues + signed OCMF | OCPP 1.6J + 2.0.1 | ✓ |
| RemoteStart / RemoteStop | OCPP 1.6J + 2.0.1 | ✓ |
| SmartCharging (Profile) | OCPP 1.6J + 2.0.1 | ✓ planner-aware |
| FirmwareUpdate (signed) | OCPP 1.6J + 2.0.1 | ✓ signed + rollback |
| Diagnostics upload | OCPP 1.6J + 2.0.1 | ✓ Capture Diagnostic bundle |
| Security Profile 3 (TLS + cert) | OCPP 2.0.1 | ✓ TPM-backed |
| ISO 15118 PnC handshake | ISO 15118-20 | ✓ PKI provisioning |
| OCPI Locations / CDRs | OCPI 2.2.1 | ✓ via CSMS |
What "production" means here: 6 of 6 controller tests passing, 53 module orchestration unit tests across 3,419 lines all green, OCPP boot + connect verified against the production CSMS, live MAC autocharge across the full sequence, a 6× field overbill caught before the customer complained.
2.8%
Idle CPU (entry tier)
Quad-core ≥ 1.5 GHz baseline · controller image, idle session
Before vs after
12–18%
Charging-state CPU
Including full module CAN + planner + journal + HMI
Before vs after
< 25s
Cold boot to ready
Power-on to first session-accepting state
Before vs after
< 2s
Crash recovery
Journal-replayed; resumes a live transaction
Before vs after
< 4W
Idle power (entry tier)
Wide-input 9–36 V DC, reverse-polarity protected
Up to 16
Concurrent connectors
Per controller (PRO / XTREME tier)
6× overbill
Anti-fraud catch in field
52 kWh reported vs 8.5 kWh delivered — caught by dual-register Wh consistency check
53 · 3 419 LoC
Module orchestration unit tests
All passing — every release
Standards & certification posture
Inside every kit, validated every release.
| Standard | Scope | JoulePoint status |
|---|---|---|
| ISO 15118-3 | SLAC · HPGP physical layer | Inside JP-PLC — validated on real EVs |
| DIN 70121 | DC HLC | Inside JP-PLC — production traffic |
| ISO 15118-2 | AC + DC | Inside JP-PLC |
| ISO 15118-2 PnC | Plug & Charge contract certs | Inside JP-PLC — cert chain + OCSP |
| ISO 15118-20 | DC BPT (V2G) | Roadmap — same hardware, OTA upgrade path |
| IEC 61851-1 | Control Pilot | Inside JP-PLC |
| IEC 61851-21-2 | EVSE EMC | Reference designs aligned · JP-SAFE front end |
| IEC 61851-23 | DC charger | Reference designs aligned |
| IEC 61851 Annex E | RCD-MD | Inside JP-SAFE |
| IEC 62752 | RCD-MD (IC-CPD) | Inside JP-SAFE |
| ISO 17409 | EV-side isolation | JP-SAFE IMD interface |
| OCPP 1.6J | Charge Point Protocol | Inside JP-CTRL — CSMS-validated |
| OCPP 2.0.1 | Charge Point Protocol | Inside JP-CTRL |
| GB/T 27930 | China DC | Module CAN supported via Tonhe driver |
| WiFi (CE / FCC / IC) | Wireless | JP-CTRL + JP-PLC pre-tested |
| Common Criteria · TPM 2.0 | Hardware root of trust | JP-CTRL-XTREME |
A side-by-side against every category of competitor we encounter — the bare-HLC vendors, the DIN-rail HLC vendors, the carrier-board ecosystems, the NDA-SDK vendors, the build-it-yourself path, and the closed turnkey OEMs.
vs
Bare HLC module — you integrate everything else.
| Capability | Phoenix Contact | JoulePoint |
|---|---|---|
| Form | Bare HLC module to integrate | Flashed PLC + pre-loaded controller + safety board + LED kit |
| OCPP | Separate add-on box | Inside the controller image |
| Module CAN orchestration | Bring your own | Inside the image (4 vendor families ready) |
| Vendor module support | Customer integrates each | Maxwell MXR · ENR-S0 · UUGreen · Tonhe — production today |
| HMI | None — you build it | Included, OEM-themable |
| UV/OV + ground-fault | You design separately | JP-SAFE included |
| RGB status LEDs | You wire and drive | WS2812B engine included |
| Time to first CCS handshake on a real car | Order → integrate → weeks | Power on → minutes |
| OTA from one supplier | No | Yes — single OTA channel |
| Parameter | Value |
|---|---|
| Operating voltage | 9–36 V DC |
| Processor | ARM Cortex-A class (Linux) for supervisory + Cortex-M class for real-time |
| Interfaces | Ethernet, Wi-Fi, optional 4G/5G, CAN, RS485, USB |
| Protocols | OCPP 1.6J + 2.0.1, ISO 15118-20 (PnC), ISO 15118-2, DIN 70121, OCMF |
| Operating temperature | −40 °C to 85 °C |
| Security | TLS 1.3, OCPP Security Profile 3, per-device hardware-bound licence |
| I/O | 8 digital I/O, 4 analog inputs, dedicated charge-pilot lines |
| Firmware updates | Remote OTA (signed), with rollback + version pinning |
| HMI runtime | Embedded React HMI — admin + kiosk modes, white-label brandable |
| Remote access | Tailscale mesh tunnel (optional, encrypted, peer-to-peer) |
| Multi-connector | Up to N connectors per cabinet with shared power planner |
| Smart charging | Built-in site planner + OCPP SmartChargingProfile execution |
The controller speaks open standards. You can point it at Joulepoint software, third-party systems, or your own stack — change it from the live config without firmware.
Native pairing — chargers, sessions, plans, wallets, OCPI roaming all in one workspace.
Explore CSMS →Stream telemetry to the Edge platform for cross-asset analytics and alarms alongside meters, OBD, and site equipment.
Explore Edge →Native OCPP 1.6J + 2.0.1. Point Charge-Point ID + CSMS URL at AmpEco, Driivz, Monta, EVConnect, or your in-house stack — change it live from the config editor.
The single biggest cost of a contract-manufactured charger is integration labor. We engineered every connector to remove that cost. Tell us your charger, receive the sealed kit, assemble, activate. First charge in hours.
Guns per cabinet, max kW per gun, preferred power-module family (Maxwell · UUGreen · Tonhe — or mix), which CSMS, indoor/outdoor, and your OEM theme.
JP-CTRL pre-loaded · JP-PLC labeled & pre-paired · JP-SAFE · JP-HMI · JP-RFID · JP-LED · JP-WIRING factory-cut · activation codes · one-page wiring diagram.
Bolt JP-CTRL into the cabinet, snap in PLC modules, wire JP-SAFE between AC and contactor, plug HMI/RFID/LED. SW4 captive WiFi portal handles PLC commissioning.
Type the 15-char activation code on the HMI, point at your CSMS URL (or pick Joulepoint cloud), optional Tailscale auth-key. First charge in hours, not months.
Volume tier
Pilot
1–10 chargers
Standard pricing · manual provisioning
Volume tier
Production
10–1,000 chargers
OEM-family pricing · factory-NVS provisioning · OTA-managed included
Volume tier
Fleet
1,000+ chargers
Bespoke factory-flashing line · dedicated OTA channel · support SLA
What ships from Bengaluru
Hardware SKUs
OTA · theming · integration · support
Service SKUs
CPO buying chargers? OEM looking to white-label the platform? Tell us guns, kW, and CSMS — our engineering team comes back with a BOM, an activation plan, and a pilot quote.
Tell us whether you're a CPO buying chargers or an OEM looking to white-label the controller. Our engineering team will scope the integration, licensing, and remote-access plan on the same call.