This article describes how to systematically analyse and resolve connection problems between an Alfen charging station and the reev backend.
Note: Work on electrical equipment may only be carried out by trained specialist personnel.
Prerequisites
The following prerequisites must be met before starting the fault analysis:
You have the ACE Service Installer installed and are connected to the charging station.
You have the login credentials for the ACE Service Installer to hand (see guide here).
Step 1: Check Configuration and Connectivity Settings
Check the connectivity settings in the ACE Service Installer as described in our guide Alfen – Configure reev Software.
Step 2: Upload Server Certificates
If not yet done, upload the server certificates.
Note: Uploading the server certificates is mandatory before carrying out the further steps for network troubleshooting.
Step 3: Check System Date & Time
Check whether the system date and time of the charging station are correct. A guide can be found here.
Step 4: Check Network Connection
Different troubleshooting steps apply depending on the connection type. Select the section that applies to your installation.
Connection via reev SIM Card
The following points must be checked when using a reev SIM card:
Are the APN credentials correctly configured under the network settings? The APN data is entered automatically when the reev backoffice template is used.
Is the mobile signal reception at the site sufficient?
Is the SIM card correctly inserted?
Connection via Wi-Fi
Note: The Wi-Fi function is only available on certain Alfen models. Check with your electrician or the manufacturer's documentation whether your model supports Wi-Fi. In addition, the firmware of the charging station must be version 7.1 or higher to use Wi-Fi. Further information can be found here.
The following points must be checked for a Wi-Fi connection:
Is the Wi-Fi coverage at the site sufficient?
Are the stored Wi-Fi credentials correct (check for typos)?
The Wi-Fi credentials can be configured under Connectivity -> Wireless.
Is "WIFI" set as the "Connection Method" under the network profiles for the backend connection?
The following settings must be configured manually in the network profile:
Setting | Value |
Connect Method | WIFI |
Protocol | OCPP 1.6 |
CSMS URL |
|
Security Profile | 0 (Default) |
Connection via Local Network (LAN)
The network settings of the charging station can be viewed under Connectivity -> Wired. The IP addresses of the station are displayed there.
The following points must be checked for a LAN connection:
Check the network cables and any network switches for defects.
Is the charging station reachable within the local network?
Are the IP addresses of the charging station correctly assigned?
For static IP addresses: a DNS server and gateway must also be configured.
For DHCP: check whether the IP addresses have been correctly assigned (usually by the network administrator).
Have the firewall settings checked. The following network ports must be open outbound for the charging station:
Port | Protocol | Purpose |
443 | TCP | Backend connection (encrypted) |
53 | UDP | DNS |
Note: Port forwarding is not required.
Note: If Deep Packet Inspection (DPI) is active in the network, it may prevent the encrypted TLS connection to the backend from being established. To test this, a temporary unencrypted connection can be set up. Replace the CSMS URL in the connectivity settings with ws://ocpp.reev.com:80 and save the setting. If the connection works with the unencrypted URL, the issue is likely caused by the DPI configuration. Discuss this with the network administrator.
Still Having Integration Issues?
Create a diagnostic file with screenshots of the configuration and send it to reev Support. A guide on how to create the diagnostic file can be found here.
Note: For hardware defects or faults, contact the manufacturer Alfen support or your electrician directly.
Frequently Asked Questions
Which OCPP version is used for the connection to the reev backend?
The connection to the reev backend uses OCPP 1.6.
Do I need to re-upload the server certificates after every configuration change?
No, the server certificates only need to be uploaded once. However, check that they are already correctly configured before carrying out further steps.
What is Deep Packet Inspection and why can it block the connection?
Deep Packet Inspection (DPI) is a network technology that analyses data traffic and may block encrypted connections. If DPI is active in the network, the TLS connection to the reev backend may be blocked. Discuss this with the responsible network administrator.
Which ports need to be open for the backend connection?
Port 443 (TCP) for the backend connection and port 53 (UDP) for DNS must be open outbound. Port forwarding is not required.