Zaptec OCPP 1.6J Compliance FAQ
As the electric vehicle (EV) ecosystem evolves, Charge Point Operators (CPOs), Energy Management Systems (EMS), and other energy stakeholders require reliable, standards-compliant charging infrastructure that ensures interoperability, security, and grid responsiveness.
This compliance scorecard outlines Zaptec’s implementation of the 'box level' OCPP 1.6J, specifically focusing on the capabilities and behavior of individual charge points. It addresses common questions from energy sector partners regarding authentication, metering, transaction control, firmware management, and communication security.
The goal of this document is to provide clear, transparent answers that help energy players evaluate the readiness and compatibility of Zaptec's EV chargers within modern energy management platforms.
This document reflects the current state of compliance and includes specific charger models, supported firmware versions, and any limitations or planned features.
1. Chargepoint Authentication via TLS
| Requirement | Supported | Notes |
|---|---|---|
| Full RFC 7617 BASIC Authentication | ✅ Yes | Fully implemented |
| Unique credentials per charge point | ✅ Yes | Each charge point uses unique credentials |
| TLS 1.2+ Support | ✅ Yes | Secure WebSocket using TLS 1.2 |
| Overall Status | ❌ No | All features coming in upcoming release; will be available for testing upon request |
2. Basic Protocol Support
Connector ID Status Management
| Feature | Supported | Notes |
|---|---|---|
| Connector ID 0 (Main controller status) | ✅ Yes | Available, Unavailable supported |
| Connector ID 1 (Connector operational status) | ✅ Yes | All major states supported |
| Faulted State on Connector ID 0 | ✅ Yes |
3. Heartbeat and Sampling Configuration
| Configuration | Default Value | Configurable | Supported Range |
|---|---|---|---|
| HeartbeatInterval | 86400 seconds (24 hrs) | ✅ Yes (via ChangeConfiguration) | Min: ≥ 0, Max: ~49 days |
| MeterValueSampleInterval | 0 (disabled) | ✅ Yes (via ChangeConfiguration) | Min: ≥ 0, Max: ~49 days |
4. Meter Value Reporting Configuration
| Configuration Option | Supported |
|---|---|
Remote configuration of MeterValuesSampledData | ✅ Yes |
Remote configuration of MeterValueSampleInterval | ✅ Yes |
Remote configuration of ClockAlignedDataInterval | ✅ Yes |
Remote configuration of MeterValuesAlignedData | ✅ Yes |
5. Meter Value Transmission
| Trigger Mode | Supported | Notes |
|---|---|---|
On every transaction event (start/stop) | ✅ Yes | |
| At fixed intervals during transaction | ✅ Yes | |
| Other | ✅ Yes | Supports OCPP TriggerMessage standard |
6. Supported Metering Measurands
| Measurand | Supported |
|---|---|
Energy.Active.Import.Register | ✅ Yes |
Power.Active.Import | ✅ Yes |
Frequency | ❌ No |
Power.Offered | ❌ No |
Current.Offered | ✅ Yes |
| SoC (State of Charge) | ❌ No |
| Other (Temperature, Voltage) | ✅ Yes |
7. Measurand Configuration Handling
| Unsupported Config Request | Response |
|---|---|
MeterValuesSampledData change with unsupported setting | ✅ Rejected |
8. Transaction and Charging Profiles
Remote Start Transaction Support
| Feature | Supported |
|---|---|
RemoteStartTransaction command | ✅ Yes |
| Requires pre-registered ID tag (e.g., RFID) | ✅ Yes |
| ID Tag may be an empty string | ✅ Yes |
TxProfile support on remote start | ✅ Yes |
Charging Profile (TxProfile) Support
| Feature | Supported |
|---|---|
Apply TxProfile on remote start | ✅ Yes |
Apply TxProfile via SetChargingProfile | ✅ Yes |
Multiple schedule periods in TxProfile | ✅ Yes |
| Support stacked charging profiles | ✅ Yes |
Override TxProfile mid-session | ✅ Yes |
Charging Profile Limits Go and Go2
| Parameter | Minimum | Maximum | Notes |
|---|---|---|---|
| ChargeProfileMaxStackLevel | 0 | 8 | enforced by firmware |
| MaxChargingProfilesInstalled | 0 | 24 | stackable |
| ChargingScheduleMaxPeriods | 0 | 32 | |
| ChargingScheduleAllowedChargingRateUnit | Current |
Charging Profile Limits PRO
| Parameter | Minimum | Maximum | Notes |
|---|---|---|---|
| ChargeProfileMaxStackLevels | 0 | 42 | enforced by firmware |
| MaxChargingProfilesInstalled | 0 | 42 | stackable |
| ChargingScheduleMaxPeriods | 0 | 42 | |
| ChargingScheduleAllowedChargingRateUnit | Current, Power |
9. Firmware Management
Signed Firmware Updates
| Feature | Supported | Notes |
|---|---|---|
| Remote firmware updates via OCPP | ❌ No | Not currently supported |
| Manual intervention required for updates | ✅ Yes | |
| Support for Signed Update Firmware (Whitepaper Edition 3) | ❌ No | |
| Support for Signed Firmware Status Notification | ❌ No |
Firmware Delivery
| Option | Selected | Notes |
|---|---|---|
| Energy stakeholder manages delivery (OEM provides binaries) | ❌ No | |
| Manufacturer manages and delivers firmware updates | ✅ Yes | Zaptec will handle firmware delivery |
10. Charger Model Compliance
OCPP 1.6J Compliant Models
| Model | Firmware Version Requirement |
|---|---|
| Zaptec Go EU All variants | Only compliant from FW version 2.4.2.4+ |
| Zaptec Go UK | Only compliant from FW 2.5.1.0 + |
| Zaptec Go 2 All variants | Only compliant from FW version 3.2.1.0 + |
| Zaptec Pro, all variants from Serial Numbers ZPR080000 and up, as well as ZPG | Only compliant from FW 7.5.3.0 + |
You can find additional information in the OCPP 1.6J release notes.
Updated 2 months ago