This article describes the necessary configuration settings of a Hypercharger from Alpitronic to connect to the be.ENERGISED backend.
The charging station is configured via the configuration interface by accessing the charging station locally.
Step by step guide
The "private" connection between the charging station and the be.ENERGISED backend is explained below. First of all, you must access the interface of the charging station. You can find out how to do this in the user manual for the charging station. Once you have access, you will see this window.
In the first step, go to the "NETWORK" tab.
After that, continue with the "SIM" tab and the "APN Configuration" sub-tab.
Here you enter the APN data of the SIM card used. In the example above, we use the configuration data from the following article for connecting the charging station with has·to·be SIM cards (starting with 8988).
|Please note that this article only refers to SIM cards by has·to·be. Alternatively, you must use different APN information from your SIM card provider. Please note that the OCPP endpoints may also have to be adapted according to your provider.|
Once the APN data has been entered, and you have selected "No APN Authentication Required", go to "Save Configuration".
Then go to the "Preferred Network" tab.
For a "private" connection via SIM cards from has·to·be, select "Mobile Connection" here. To save, go to "Change Network".
Then go to "INDEX" at the top right to return to the start page of the charging station interface. From there, go to "OCPP".
From there, go to the "BOOT.INI FILE" tab.
chargePointIdentity: Replace the cp ID with a unique station name. This means that among all your stations, this name (or ID) may be assigned only once.
Please note that the chargepoint identity must not contain spaces, special characters (e.g.: +*!#) and letters unknown in English (e.g.: ä, ö, ü, ß). Exception is the underscore (_), this can be used.
Furthermore, the chargepoint identity must not exceed a maximum length of 45 characters.
WebSocketUrl: Please replace the value "INSTANCE" with your instance name. You can easily read your instance name in the link to the backend. Access to the backend: https://beispiel.htb.solutions/. Here you can read out the instance by taking the value AFTER "https://" and BEFORE ".htb.solutions/". In this example, your instance name would be "beispiel". An overview of the URLs, depending on the connection type, can be found in this article.
WebSocketPassword: This is not required for a "private" connection, but is required for a "public" connection. More about this below.
After you have entered these values, go to "Save Configuration" here as well.
You have to restart the charging station to apply the changes.
To restart the charging station, go to "RESET" on the start page.
There you go to "Hard Reset HYC". The charging station is rebooting and should then be displayed as online in the backend after a few minutes.
The "public" connection differs in some points from the "private" connection described above.
In the first tab "Ethernet Configuration" make sure that the item "Automatic (DHCP)" is selected. If you have to set it to "Automatic (DHCP)" first, make sure to save the change by clicking on "Save Configuration".
For the "public" connection, you can alternatively select "Wired Connection" in the "Preferred Network" tab if you do not use SIM cards. Changes are saved by clicking on "Change Network".
In addition, enter the "public" URL in the "BOOT.INI FILE" tab.
As with the "private" connection, replace the value "INSTANCE" with your instance name. Do not forget to enter the port "443" in the URL (see screenshot above; URL should look like this: wss://INSTANCE.public.ocpp-broker.com:443/ocpp/cp/socket/16) For the "public" connection, the charging station must support BASICAUTH. You find an explanation on how to see your password for BasicAuth in be.ENERGISED in the article on OCPP endpoints. The password must be entered in the "WebSocketPassword" field.
For "WebSocketUsername" enter the ChargePointIdentity again.
Go to "Save Configuration".
Then restart the charging station again and a "public" connection with the be.ENERGISED backend should be established successfully.
Version: 2022-09-15 15:51:35 UTC