The Spelsberg Wallbox has standardised interfaces and protocols to communicate with external backend systems. The Open Charge Point Protocol (OCPP) has established itself in the area of the charging infrastructure for electric vehicles. This enables manufacturer-independent communication between a charging station and a management system. The Spelsberg Wallbox is compatible with the following backend systems. List of compatible backend systems
To configure communication between the wall box and external backend system, open the app and go to System - Settings. Open "More settings" and select "OCCP".
The following parameters must be set:
OCCP parameter overview | |
App Parameter | Settings |
Backend connection type | Select: |
OCPP Charge Point ID | Inpur _ _ _ _ _ _ _ _ |
OCPP mode | Select: OCPP-J 1.6 |
OCPP backend URL | Input [WS / WSS-URL of the OCPP backend server] _ _ _ _ _ _ _ _ |
OCPP backend password | Inpur _ _ _ _ _ _ _ _ |
OCCP authorisation* | Select: |
Whitelist for permissions* | Select: OCPP whitelist |
OCPP SSL client mode | Configuration of the backend authentication and encryption |
OCPP WebSocket Proxy URL | URL of the WebSocket Proxy in the format HOST:PORT. Specification of the port is optional (if not specified, port 80 is used). |
WebSocket Keep-Alive interval | OCPP WebSocket Keep-Alive interval in seconds (0 seconds if not used). |
Transaction restart following a power outage | Activate |
Local offline authorisation | Activate if transactions for locally authorized RFID chips should start when the charging station is offline |
Offline RFID authorisation | Activate |
*Setting dependent upon range of functions desired by the operator.
The "OCPP SSL client mode" parameter configures the encryption between the wall box and the external backend system. Changes to the encryption method are dictated by the external backend system.
"OCPP WebSocket Proxy URL" parameter: URL of the WebSocket Proxy in the format HOST:PORT. Specification of the port is optional (if not specified, port 80 is used) and is dictated by the server of the external backend.
"WebSocket Keep-Alive interval" parameter: This setting is dependent upon what interval the server needs. Using keep-alive can be beneficial if you employ a NAT router between charging point and backend, to prevent closing of the WebSocket connection.