Skip to main content
Version: 5.33

Configuring WLAN

1. Goal​

  • Connect your Charge Controller to your Backend/network through WLAN

2. Requirements​

Make sure that

  • You have access to a WLAN network
  • The Charge Controllers are within range of the WLAN network

2.1. Does my Controller support WLAN?​

Check the capabilities table to find out if your Controller variant provides this feature:

Capabilities table
ModelArt. No.USB HostEthernetInternal ModbusExternal ModbusCellular ModemWLANPLC (ISO 15118)
CC613-ELM4PR-MB940600202x4G
CC613-ELPR-MB940600212x
CC613-ELM4PRB940600262x4G
CC613-ELPRB940600272x
CC613-HEM-X2B940600282x
info

If you can't see configuration options in the Config UI mentioned here, the guide doesn't apply to your Charge Controller. Use the table above for reference.

3. Configuration​

  1. Apply the following configuration:

Location in Config UIParameterValueInfo
BACKEND > ConnectionConnection typeWLAN
NETWORK > WLANWLAN enabled On
NETWORK > WLANWLAN SSID fill in your router's network name
NETWORK > WLANWLAN password fill in your router's password
  1. At the bottom of the Config UI, click , then click to apply the changes

3.1. DHCP-based router configuration​

If your router assigns the IP addresses automatically, choose Auto (DHCP Client) for Mode for network configuration.

info

Whether the DHCP client hostname field has to filled out, depends on your network. Contact your network administrator.

tip

Have your router give out static IP addresses when using DHCP if this option is available.

4. Master-Slave considerations​

On a Master-Slave setup, only the Master requires WLAN. The WLAN configuration on the Slave will be ignored. All OCPP communication is automatically forwarded from the Slave to the Master.