| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
Hardware
.png?version=1&modificationDate=1711548616460&cacheVersion=1&api=v2&width=185)
About this document
This manual contains information about the connection to the local web interface (WebConfig) of Compleo eBOX smart, Compleo eBOX professional and Compleo eBOX touch. The purpose of this document is to describe how to properly configure and operate the advanced features of the WebConfig platform. This includes the implementation of important settings for optimal operationsmart charge regulations.
Please note
Make sure that the eBOX is set up and wired correctly. You will find a detailed assembly description in the user manual you received with your eBOX.
Preparations
To connect to the WebConfig of the eBOX, you need a working laptop and a LAN cable. Make sure you have the eBOX PUK of the eBOX ready to access the web interface. You can find the PUK on the last page of the user manual you received with your eBOX.
System overview and structure
Before mounting the eBOX, make sure that ensure the eCLICK is not connected to power. To access the eBOX web interface, the eBOX must be properly connected to the computer. For this to succeed, the entire system must be set up and wired as shown in Figure 1.
1 LAN 1RJ45 (communication to eBOX)
2a LAN 2RJ45 (to internet router)
2b LAN 2 LSA+ (to internet router)
3a Output eSMARTMETER (optional)
3b Input eSMARTMETER (optional)
4 Position cable clamps for S/FTP cable
5 RJ50 Terminal (communication eBOX)
6 Grid control box connection
7 Shunt release connection
8 LAN 1 RJ45 (deactivated)
eSMARTMETER output (optional)
2 RJ50 Terminal (eBOX communication)
3 Grid control box connection
4 Shunt release connection
5 Cable clip position for S/FTP cable
6 LAN 2 LSA-Plus (to Internet router)
7 LAN 2 RJ45 (to Internet router)
8 LAN 3 RJ45 (eBOX communication)
9 LAN 1 RJ45 (local connection)
10 eSMARTMETER input (optional)
.png?version=3&modificationDate=1711619572326&cacheVersion=1&api=v2&width=319)
Take the eBOX and identify the connection points
on its back. Connect the
white ribbon data cable of the eBOX to the port "
8 LAN 3 RJ45 (eBOX communication)".
.png?version=3&modificationDate=1711619177890&cacheVersion=1&api=v2&width=659)
All communication cables (e.g. LAN cable, etc) are connected to the interface board (See Figure
Before plugging the eBOX into the eCLICK, several components must be connected with various cables. First the LAN cable of the eBOX (black LAN cable, see Fehler! Verweisquelle konnte nicht gefunden werden.) is connected to the LAN RJ50 Terminal (5) of the eCLICK. Then connect the eSMARTMETER (3a) to the port (3b) of the eCLICK. Then connect the white LAN cable of the eBOX to the LAN port 1 of the eCLICK. Please note: Port 2a is for the LAN cable (yellow cable, Figure 4), which allows you to connect your computer to the eBOX.
Clicking the eBox into the eClick
After successfully connecting, the eBOX can be plugged into the eCLICK.
To do this, follow the installation steps 1 to 3:
Please prepare the installation by fully pulling down the locking bracket and holding it firmly in this position. Now place the eBOX carefully on the eCLICK and push
2 Hold the eBOX while pulling down the locking bar on the eCLICK. Now release the locking bar. As soon as the locking bar is pulled up, press the eBOX by pressing the eCLICK.
3 If necessary, press the locking bar until it is in its original position again. Markings for orientation are visible on the eCLICK locking bar. Check whether the locking bar is fully inserted. The triangular recesses on the left and right of the locking bar must be flush with the eCLICK housing.
Now the voltage can be switched on to the eCLICK. In the next step you can connect your computer to the eBOX via a LAN cableit firmly in the middle with the other hand until it stops Be careful not to exert excessive pressure on the circle LEDs.
Now release the bracket and let it lift automatically. Please hold the eBOX in place with one hand.
Please continue to hold the eBOX in place with one hand. Check the final position of the locking bracket, it must be fully raised. The enlarged detail view demonstrates the desired final position. The pin on the locking bracket must be exactly level with the triangle on the eBOX. If the bracket has not reached the desired final position, please push it further upwards to the desired final position.
Now the eBOX is mounted on the eCLICK and Power on the eCLICK circuit.
Initial access
You will need at least a laptop and a LAN cable. If the backend connection is to be made via a SIM card, now is a good time to insert it. Then connect the laptop to one of the Ethernet ports on the board in the charging station using a network cable.
In the Windows search bar, search “View network connections” and open.
| Info |
|---|
This interface may vary for each operating system. |
Right-click the used Ethernet port and go to properties (admin rights required)
Double click "Internet Protocol Version 4 (TCP/IPv4)".
Assign an IP address in the address range 172.16.0.x. Everything except .1 is OK , because the charging station has this address. We recommend 172.16.0.99. Also, enter subnet mask 255.255.255.0. Then click on "OK" in both previously opened windows.
If necessary, skip the security warning by clicking “Advanced” and “Proceed to 172.16.0.1(unsafe)”.
Login information for WebConfig:
User name: admin Password: To log in to WebConfig, you need the PUK of your eBOX. You can find it on the back of the supplied user manual. The default username is "admin".
User name: admin
Password: PUK
Smart Charge Point Regulation
OFF-Peak Charging
Please set the charger up as described below, to prevent charging during Peak hours. If you have lost your PUK, please contact support. The default username is "admin"
Check the Box “This eBox is installed in the UK” as shown in Figure 11
Set the desired hours during which the charger is not supposed to charge under the tab “Off-Peak Charging”
If a DSR agreement is in place, place check the Box “DSR agreement in place”, this will disable the Off-Peak charging and remove the settings from the configuration screen.
The presets for Off-Peak Charging can be seen in Figrue 11
Select the desired application timeframe from the left dropdown
Off
weekday
weekends
daily
Select the desired times from the right two dropdowns
Press “OK” to save the settings
Randomized delay
Every charging session and change in current output is subject to a randomized delay between 0 and 600 seconds (10 minutes) in the standard configuration.
Reason
Maintaining grid stability is a key Government policy objective for smart charging.
There is a risk that large numbers of charge points could start charging or change
their charging rate simultaneously, for example when recovering from a power
outage or in response to an external signal such as a ToU tariff. This could cause a
spike or sudden drop in demand and destabilize the grid.
Conclusion
To mitigate this, the Regulations set out requirements for randomized delay
functionality. Applying a randomized offset ensures grid stability by distributing
demand placed on the grid, gradually ramping up the electricity demand.
Default Config
A charge point must be configured to operate a default randomized delay of up to
600 seconds (10 minutes) at each charging instance (that is, any switch in the load that
is on, up, or down). The exact delay must:
be of a random duration between 0 to 600 seconds;
be conferred to the nearest second; and
be of a different duration for each charging instance.
The maximum randomized delay is configurable up to 1800 seconds (30 min)
There are two options for configuring this.
Text configuration
Download the configuration file and open it with the text editor of your choice.
Change the following parameter according to your desired maximum randomized delay in seconds:
ecu.uk_settings.max_charge_delay
Save the configuration file and upload the text file again via the "Select file" button during upload. Confirm your upload with "OK".
Restart the eBOX to make the settings effective.
OCPP configuration
To change the maximum randomized delay via OCPP, use the change configuration command in your Backend to change the following parameter according to your desired duration in seconds:
ecu.uk_settings.max_charge_delay=600
Delay Override
The charge point is configured such that the random delay will not operate when:
an equivalent random delay has already been applied to the operation of the charge point with respect to this time
the owner or end-user who is not the owner has canceled the randomized delay by overriding it
Manual Delay Override
After successful connection and authentication, the flow of electricity is delayed, meaning the charging session starts in a pause state. The LED ring Pulses Blue. Because the charging process can start very quickly, the connection success is indicated in the form of the static green EV LED for another 5 seconds before the EV LED Pulses Blue in sync with the LED Ring and the RFID LED jumps to static white if authorized by RFID, otherwise switches off. The Bluetooth LED pulses white every second to signal the started delay.
To cancel the Randomized Delay the user must press the Bluetooth button at least 5 times quickly (at least as fast as the Bluetooth LED pulses).
The successful cancellation of the Randomized Delay is indicated analogously to the signals for authorization success by the Bluetooth LED glowing green statically for 5 seconds.
Once the flow of electricity starts the LED ring and the EV LED light up blue statically.
Security Log
Local Security Log
To analyze the behavior of the eBOX, see the event log and possible errors, you can configure logging under the menu item "ECU" and the tab "Logging".
One level down under "Download" you can download the log file.
Press the “Download LogFile” button and open the downloaded “.txt” document to see the Log File.
Security Log from Backend
In addition to the local download, another option is to download the diagnostics file from the OCPP Backend.
Please refer to your specific Backend provider on how to execute the OCPP standard command “GetDiagnostics”. The Log File will be included in the provided Diagnostics package.