Configure a Gateway-based network connection
Goal
- Connect your Charge Controller to the Internet, your Backend or local network through a Gateway
The WAN router and the DLM master function don't have to be configured on the same controller. We recommend to set configure one Charge Controller as the WAN router and another as the DLM Master. This ensures that in case of a defect the system fails only partially.
Before you begin
Make sure that
- The Charge Controllers are connected through Ethernet to an Ethernet Switch
- At least one Charge Controller has a GSM module and a SIM card
We'll call the Charge Controller in charge of the Gateway the WAN Charge Controller. For clarity, we'll refer to the non-WAN Charge Controllers as non-WAN Charge Controllers.
Option 1: Automatic network configuration
With automatic network configuration, it's possible for all Charge Controllers that are connected to each other via Ethernet or WLAN to be automatically assigned an IP address/DNS and Gateway with the help of a built-in DHCP server. The DHCP server is then the controller on which LAN parameter Mode for ethernet configuration is activated on DHCP server.
Recommendations
If the DHCP server is switched on, assign static IP addresses to the Charge Controllers.
Advantages
- A computer connected to the Ethernet switch is automatically assigned an IP address in the same network.
Configuring the Gateway Charge Controller
- Establish a network connection through GSM
- On the Charge Controller you want to act as the WAN router
Apply the following configuration:
| Location in Dashboard | Parameter | Value |
|---|---|---|
| NETWORK > LAN | Mode for ethernet configuration | DHCP server |
| NETWORK > GSM | WAN router | On |
LAN konnte
Mode for ethernet configurationim WebUI selbst nicht finden.
This will create a new network for the other Charge Controllers, with the Gateway Charge Controller acting as a router. All necessary parameters (such as the IP address) of the other Charge Controllers in the network will be assigned automatically by the DHCP server.
- At the bottom of the window, click , then click to apply the changes
The WAN Charge Controller acts as a DHCP server. The Charge Controller comes with the following default values:
| Default value | |
|---|---|
| IP address | 172.16.23.1 |
| Subnet mask | 255.255.255.0 |
| Gateway | 172.16.23.1 |
| DNS | 172.16.23.1 |
| IP address range set for the non-WAN Charge Controllers | 172.16.23.100 — 172.16.23.254 |
| IP address range free for static assignment | 172.16.23.2 — 172.16.23.99 |
Configuring the remaining non-WAN Charge Controllers
As explained above, we advise against automatic configuration and recommend scenario 2: manual network configuration
- Repeat the following configuration for all non-WAN Charge Controllers:
| Location in Dashboard | Parameter | Value |
|---|---|---|
| BACKEND > Connection | Connection Type | Ethernet |
| NETWORK > LAN | Mode for ethernet configuration | Auto (DHCP Client) |
| NETWORK > GSM | WAN router | Off |
- At the bottom of the window, click , then click to apply the changes
Option 2: Manual network configuration.
Here, the network parameters of the individual Charge Controllers are entered manually.
- To avoid conflicts with the DHCP server, choose an IP address that is between
172.16.23.2and172.16.23.99 - The Gateway and DNS server is the IP address of the DHCP server:
172.16.23.1
Configuring the WAN Charge Controller
Make sure to store the values you're changing for later reference, e.g., in an Excel sheet.
- Set up an Internet connection via GSM
Apply the following configuration:
| Location in Dashboard | Parameter | Value |
|---|---|---|
| NETWORK > LAN | Mode for ethernet configuration | Static |
| NETWORK > GSM | Static network configuration IP | 192.168.xxx.xxx (has to start with 192.168, the rest can be set freely) |
| NETWORK > GSM | WAN router | On |
| NETWORK > GSM | Static network configuration netmask | 255.255.255.0 |
| NETWORK > GSM | Static network configuration gateway | leave blank |
| NETWORK > GSM | Static network configuration DNS | 192.168.17.1 (example) |
- At the bottom of the window, click , then click to apply the changes
Configuring the non-WAN Charge Controllers
Make sure to store the info for each Charge Controller for later reference, e.g., in an Excel sheet.
Repeat these steps for each non-WAN Charge Controller:
Apply the following configuration:
| Location in Dashboard | Parameter | Value |
|---|---|---|
| BACKEND > Connection | Connection Type | Ethernet |
| NETWORK > GSM | WAN router | Off |
| NETWORK > LAN | Mode for ethernet configuration | Static |
| NETWORK > GSM | Static network configuration IP | The network ID (first three number blocks) must be identical to the WAN Charge Controller. The last number block can be freely set between 1 — 254. The last number block must be unique among the Charge Controllers as it's the unique identifier in the network (host ID). |
| NETWORK > GSM | Static network configuration netmask | Same as the WAN Charge Controller |
| NETWORK > GSM | Static network configuration gateway | Enter the IP address of the WAN Charge Controller here |
| NETWORK > GSM | Static network configuration DNS | Same as the WAN Charge Controller |
- At the bottom of the window, click , then click to apply the changes
FAQ
How many Charge Controllers can be connected to a WAN Charge Controller?
Theoretically, a maximum of 253 Charge Controllers can be connected to one Gateway.