v5.33
operator
manufacturer
Last updated on
OCPP Backend
caution
This documentation is being revised.
The Charge Controller family implements the OCPP standard based on the official OCPP 1.6 standard defined by the Open Charge Alliance. Download relevant documents from the Open Charge Alliance website.
- OCPP 1.6
- OCA ISO 15118
- Secure transfer of the Eichrecht OCPP public key via hastobe spec
- EVSE Check V3
1. Supported feature profiles
| Feature profile | Features | Compliance | Info |
|---|---|---|---|
| The Charge Controller family provides mature support for the OCPP 1.6 protocol. | |||
| Some specifications leave room for propietary implementations. Where this is the case, details are outlined. |
| Feature profile | Features | Compliance | Info |
|---|---|---|---|
| Core | compliant | Basic Charge Station functionality comparable with OCPP 1.5 without support for firmware updates, local authorization list management and reservations. | |
| Firmware Management | compliant | Support for firmware update management and diagnostic log file download | |
| Local Auth List Management | compliant | Features to manage the local authorization list in Charge Stations | |
| Reservation | compliant | Support for reservation of a Charge Station | |
| Smart Charging | compliant | Support for basic Smart Charging, for instance using control pilot | |
| Remote Trigger | compliant (proprietary implementation) | Support for remote triggering of Charge Station messages | |
| Firmware Management | compliant | Support for firmware update management and diagnostic log file download | |
| Local Auth List Management | compliant | Features to manage the local authorization list in Charge Stations | |
| Reservation | compliant | Support for reservation of a Charge Station | |
| Smart Charging | compliant | Support for basic Smart Charging, for instance using control pilot | |
| Remote Trigger | compliant (proprietary implementation) | Support for remote triggering of Charge Station messages |
2. Supported messages based on "Open Charge Point Protocol 1.6"
| Message | "Open Charge Point Protocol 1.6" (edition 2 FINAL, 2017-09-28) chapter numbers |
|---|---|
| Authorize | Ch. 6.1 — 6.2 |
| BootNotification | Ch. 6.3 — 6.4 |
| CancelReservation | Ch. 6.5 — 6.6 |
| ChangeAvailability | Ch. 6.7 — 6.8 |
| ChangeConfiguration | Ch. 6.9 — 6.10 |
| ClearCache | Ch. 6.11 — 6.12 |
| ClearChargingProfile | Ch. 6.13 — 6.14 |
| DataTransfer | Ch. 6.15 — 6.16 |
| DiagnosticsStatusNotification | Ch. 6.17 — 6.18 |
| FirmwareStatusNotification | Ch. 6.19 — 6.20 |
| GetCompositeSchedule | Ch. 6.21 — 6.22 |
| GetConfiguration | Ch. 6.23 — 6.24 |
| GetDiagnostics | Ch. 6.25 — 6.26 |
| GetLocalListVersion | Ch. 6.27 — 6.28 |
| Heartbeat | Ch. 6.29 — 6.30 |
| MeterValues | Ch. 6.31 — 6.32 |
| RemoteStartTransaction | Ch. 6.33 — 6.34 |
| RemoteStopTransaction | Ch. 6.35 — 6.36 |
| ReserveNow | Ch. 6.37 — 6.38 |
| Reset | Ch. 6.39 — 6.40 |
| SendLocalList | Ch. 6.41 — 6.42 |
| SetChargingProfile | Ch. 6.43 — 6.44 |
| StartTransaction | Ch. 6.45 — 6.46 |
| StatusNotification | Ch. 6.47 — 6.48 |
| StopTransaction | Ch. 6.49 — 6.50 |
| TriggerMessage | Ch. 6.51 — 6.52 |
| UnlockConnector | Ch. 6.53 — 6.54 |
| UpdateFirmware | Ch. 6.55 — 6.56 |
3. Supported messages based on "Using ISO 15118 Plug & Charge with OCPP 1.6"
| Request message | "Using ISO 15118 Plug & Charge with OCPP 1.6" (v1.0, 2020-09-16) chapter numbers |
|---|---|
| Authorize | Ch. 6.1.1 — 6.1.2 |
| CertificateSigned | Ch. 6.2.1 — 6.2.2 |
| DeleteCertificate | Ch. 6.3.1 — 6.3.2 |
| Get15118EVCertificate | Ch. 6.4.1 — 6.4.2 |
| GetCertificateStatus | Ch. 6.5.1 — 6.5.2 |
| GetInstalledCertificateIds | Ch. 6.6.1 — 6.6.2 |
| InstallCertificate | Ch. 6.7.1 — 6.7.2 |
| SignCertificate | Ch. 6.8.1 — 6.8.2 |
| TriggerMessage | Ch. 6.9.1 — 6.9.2 |
4. OCPP-relevant configuration parameters in Config UI
| Category | Parameter | Purpose | Cleaned-up Remarks |
|---|---|---|---|
| General Connectivity | Connection Type | Physical connection method for OCPP Backend communication | Defines the preferred connection method. If both Ethernet and GSM are active, Ethernet is always used automatically. If no Backend is configured, no OCPP communication occurs. |
| OCPP ChargeBoxIdentity (ChargePointID) | Unique identifier for the Charge Controller | Required for proper communication with the OCPP backend. | |
| OCPP Mode | Defines the OCPP version and transport protocol | Always set this to OCPP-J 1.6. | |
| WebSockets JSON OCPP URL of the Backend | URL of the OCPP central system for WebSocket | Use the format ws://backend:8080/OCPP/v16/. Do not include the ChargePointID in the URL, even if some backends suggest it. | |
| WebSockets proxy | Proxy server for WebSocket connections | WebSocket proxy in the format HOST:PORT. If no port is given, 80 is used by default. | |
| WebSockets keep-alive interval | Interval for WebSocket ping messages | Value in seconds (0–10000). Use 60 seconds to help maintain connection stability. Use this if the backend connection drops unexpectedly. More | |
| Security & Authentication | OCPP connection strictness | Security level for OCPP connections | Sets minimum encryption standard. Use only-secure-cyphers when possible. Set to all-cyphers if the backend doesn't support modern encryption. |
| HTTP Basic Authentication password | Password for OCPP authentication | Used if required by the backend. Username is automatically set to the ChargePointID. | |
| Send status for webui login event | Send notification when web UI is accessed | Sends an info-level status message to the backend when someone logs into the web UI. More | |
| SSL Strictness as client | SSL/TLS security level | Set to Skip host check if DNS server fails and you use IP addresses in place of domain names. More | |
| Connection Behavior | Force Heartbeat request messages | Whether to force sending heartbeat messages | Some backends need this to maintain a stable connection. Enable if you witness frequent disconnects. |
| TCP Watchdog Timeout | Timeout for TCP connection monitoring | If the TCP Watchdog Timeout is reached and the Backend cannot be reached, a reboot on the Charge Controller is triggered. More | |
| Backend connection timeout | Timeout for OCPP connection attempts | (OCPP standard) Default: 60s. Range: 3-300s. Full behavior details | |
| Disallow charging if OCPP queue full | Block charging when message queue is full | Charging is blocked when the internal OCPP message queue is full. Prevents new sessions that would result in message loss — especially critical for Eichrecht compliance. More | |
| Display backend disconnect as error | Whether to show disconnection as an error on the HMI | Error is shown on the HMI in case a Backend is configured but connection fails. | |
| StatusNotification Control | Send informative StatusNotifications | Whether to send informational status updates | Sends additional status info, helpful for debugging or to enhance backend insights. More |
| Send error StatusNotifications | Whether to send error status updates | Enables more detailed error reporting to the backend. More | |
| Send USB error StatusNotifications | Whether to send USB-specific error updates | Controls if USB-related errors are reported to the backend. More | |
| State 'unavailable' at FW update begin | Set status to unavailable when firmware is being downloaded | ||
| Maintenance & Overrides | Force OCPP connector state | Override connector availability state | Overrides the connector availability state regardless of Backend-side state. |
| Compatibility & Legacy | Strategy for StatusNotification | When to change connector status to Occupied | Deprecated. Legacy setting from OCPP 1.5. Can be ignored. |
| Allow long get configuration keys | Extends the max. length of configuration key values to 500+ characters | Allows more than the OCPP standard for the value length of GetConfiguration requests. Needed for proprietary certificate exchange. | |
| Integer values for boolean config keys | Use integers instead of booleans in responses | (Deprecated) Scoped to standard OCPP configuration key values. Behavior to output those values as integer is deprecated. | |
| Retry Logic | Number of transaction message attempts | Retries for transaction messages | Used for all transaction-related messages except Eichrecht-bound ones. More |
| Eichrecht transaction message attempts | Retries for Eichrecht-specific messages | Used only if Eichrecht is active and message is Start/Stop/MeterValues tied to a transaction. More | |
| Metering & Reporting | DataTransfer for Tariff And Total Usage | Send tariff and usage data via DataTransfer | |
| Meter values sampled data (OCPP) | Meter values to be sent based on sampling interval | ||
| Meter Value Sample Interval (OCPP) | Time between meter value samples | ||
| Meter values aligned data (OCPP) | Meter values to be sent at regular intervals | ||
| Clock aligned data interval (OCPP) | Interval for clock-aligned meter values | ||
| Retransmit MeterValues | Whether to retry sending meter values | When enabled, transaction-bound MeterValues are held in the queue and retried until success or limit reached. Affects queue size and charging availability. More |