Content of the Article
General Information
This article describes the basic configuration settings for connecting a charging station to be.ENERGISED. To configure your charging station, you can use OCPP endpoints. This configuration allows your station to communicate with the be.ENERGISED backend using a SIM card or VPN certificate issued by has·to·be.
Please note, secure access is only possible with SIM cards or VPN certificates issued by has·to·be.
There is the option of a direct connection via SOAP or Websocket (JSON) or a "bundled" connection via the broker to be.ENERGISED. The broker connection is discussed first, and then we explain how to make a direct connection.
Broker Connection
The broker is a "connection bundler," and acts as an adapter or distributor between the charging stations and the has·to·be backend. It bundles charging station data, communicated via OCPP through the broker, and passes the relevant data to the backend.
The advantage of this "connection bundler" feature is that it can take in unlimited data and scale it. If you would like to connect via the OCPP broker to the be.ENERGISED backend, the URL must first be "released" by our Support Team and configured in the backend for the respective client. Please contact our support team in advance.
The concept of URLs is a bit more complex than for a conventional web application. The following section is intended to provide a rough overview of them.
Basis URL
The basic URL consists of several fundamental parts:
Communication protocol |
:// |
Client (mandanat) name („INSTANCE“) |
. |
Connection type |
. |
Where? (e.g.: „Productive broker“ or „Test broker“) |
. |
com |
: |
Port |
ws |
:// |
instance |
. |
private |
. |
Ocpp-broker |
. |
com |
: |
optional |
Sample link
http://energised.private.ocpp-broker.com:80
Client (mandant) name ("INSTANCE")
Each client has its own client name (also called a ‘slug’), which is used for domains, such as the string "energised".
Ports
For the "Production ports" we use to the default settings, which correspond to the values 80 http/ws and 443 for https/wss. These are not mandatory, only use if the station requests a port.
Protocol |
/ |
Who is connected? |
/ |
Communication type |
/ |
OCPP type |
/ |
Chargebox-ID or Central System-ID |
ocpp |
/ |
ChargePoint → cp Central System → cs |
/ |
socket |
/ |
1.5 1.6 2.1 |
/ |
(optional) |
In this example, the URL would look like this:
ws://INSTANCE.private.ocpp-broker.com/ocpp/cp/socket/16/(optional)
Variations on how to create the endpoint using your INSTANCE below. |
OCPP Endpoints
Has·to·be plans long term to connect all stations via the OCPP broker. |
Please use one of the following configurations to use this access, depending on your charging station model: If your station supports a connection via DNS, it is best to use that option. If this is not possible, you can switch to an IP connection.
OCPP 1.6 SOAP Endpoint DNS |
|
Secure OCPP 1.6 Endpoint DNS |
|
OCPP 1.6 Websocket (JSON) DNS |
|
OCPP 1.6 SOAP IP |
http://192.168.17.2:8080/gw/INSTANCE/ocpp16 (UNSUPPORTED) |
Please replace the word "INSTANCE" and "CHARGE_POINT_ID" as follows: INSTANCE
|
OCPP 1.5 SOAP Endpoint DNS |
|
Secure OCPP 1.5 Endpoint DNS |
|
OCPP 1.5 Websocket (JSON) DNS |
|
OCPP 1.5 SOAP Endpoint IP |
http://192.168.17.2:8080/gw/INSTANCE/ocpp15 (UNSUPPORTED) |
OCPP 1.2 SOAP Endpoint DNS |
|
Secure OCPP 1.2 Endpoint DNS |
|
OCPP 1.2 SOAP IP |
http://192.168.17.2:8080/gw/INSTANCE/ocpp12 (UNSUPPORTED) |
A more detailed explanation of the terms "INSTANCE" and "CHARGE_POINT_ID" can be found above. |
Comments
0 comments
Article is closed for comments.