v5.33
operator
manufacturer
Last updated on
OCPP
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 (scroll down to "Application Notes")
- Secure transfer of the Eichrecht OCPP public key via hastobe spec
- EVSE Check V3
1. Setting up the connection and verifying it
-
Basic Requirements
- Valid ChargePointID (found under BACKEND > OCPP)
- Working network connection (GSM, Ethernet, or WLAN)
- OCPP backend URL (format:
ws://backend:8080/OCPPJProxy/v16/
)
-
Connection Verification
- Check BACKEND > Connection Status
- Verify heartbeat messages are being sent/received
- Confirm transaction messages are flowing
2. Troubleshooting guide
2.1. Common connection issues
-
No Backend Connection
- Check network connectivity (ping test)
- Verify ChargePointID is correct
- Confirm backend URL format
- Check SSL certificates if using WSS
-
Connection Drops
- Check network stability
- Verify heartbeat interval settings
- Monitor system logs for timeout errors
-
Authentication Failures
- Verify basic auth credentials
- Check authorization key format
- Confirm OCPP version compatibility
2.2. Diagnostic Steps
-
Check real-time logs:
- DIAGNOSTICS > OCPP Status
- DIAGNOSTICS > System Logs
-
Verify network settings:
- BACKEND > Connection Type
- NETWORK > Configuration
-
Test backend communication:
- Initiate test transaction
- Monitor message exchange
- Check error responses
3. Supported feature profiles
4. Supported messages based on "Open Charge Point Protocol 1.6"
5. Supported messages based on "Using ISO 15118 Plug & Charge with OCPP 1.6"
6. List of all configuration keys and equivalent Config UI labels
|