You need to set a unique Slave ID for each controller: cFos Charging Manager -> System Configuration -> Modbus
|Type||16 bit word|
|Value to write||New Slave ID|
Set all DIP switches and rotary switches to default. Set the rotary switch for the maximum current on the main board to 5 (16A / 11kW). Set the desired Modbus Slave ID with DIP S4 according to the table in the manual. In the Charging Manager, enter COMx,19200,8,e,1 as the address
In cFos Charging Manager -> Configuration
|Address||Charge Point ID, as configured in the EVSE|
|ID||Connector ID, as configured in the EVSE|
In cFos Charging Manager -> cFos Charging Controller Configuration: Enable "EVSE as OCPP client"
|ID||As configured in the Charging Manager (the connector ID is always 1)|
|Server||URL of your OCPP backend, including port number, e.g. |
The rotary switch of the TWC must be set to "F"
Caution: You may need to swap the two connection wires to the EVSE if you don't get a response.
In cFos Charging Manager -> System Configuration -> Tesla TWC
An attempt is made to find the ID of the Tesla TWC. Meanwhile, only one TWC may be connected. The ID is 4 digits (in hex).
In cFos Charging Manager -> Configuration
|Address / ID||Enter the found values (COM address / ID) here|
Modbus port is always 502. The slave ID is normally 255. For Phoenix Contact it could also be 180.
The cFos Charging Manager should also run with the "Pro" models from Wallbe (i.e. those with built-in counters). We are still looking for someone to test this with. Please feel free to contact us!
OCPP: Setup via the innogy eConfig app
Once a connection to the wallbox has been established via the innogy eConfig app, click on "Business / Commercial" to set up the configuration. When selecting the backend, select "3rd party backend". For the network, depending on the connection, select WLAN or LAN; for WLAN, the SSID and the WLAN password must also be entered. After the wallbox has connected to the network, the backend can finally be configured.//xxxx: p/ as the backend URL, where xxxx stands for the IP of the cFos load manager in the network, e.g. 192.168.2.111, and "p" stands for the port that is to be used (e.g. 19500) . In the example, the address was ws://192.168.2.111:19500/. If the connection to the backend is to be SSL-encrypted, replace the "ws" with a "wss" at the beginning of the URL. The name under which the wallbox reports to the backend is entered under "ChargeBox ID", e.g. LP000123 or CP456. If the wallbox is also to be authenticated using a password, this can optionally be specified, in which case the username must contain the same value as the ChargeBox ID field.
OCPP: Setup via the wallbox's web interface (from firmware version 1.3.26)
The current firmware version is displayed in the innogy eConfig app after it has connected to the wallbox. The web interface can be accessed via HTTPS (port 443) under the IP address of the wallbox. First, a connection to the network must be established as described above. The IP address of the wallbox must then be determined using the router used (e.g. 192.168.2.111). The web interface can then be called up via a browser. Please ignore certificate warnings. Login with "admin" and enter the PUK of the eBox as the password.
The OCPP configuration takes place in the "ECU" menu, "OCPP" submenu. Under ChargeBox Identity, a name is selected under which the eBox reports to the OCPP backend, e.g. LP000123 or CP456. The URI of the OCPP backend is entered for the end point URI, e.g. ws://192.168.2.111:19500/ for unencrypted or wss://192.168.2.111:19500/ for encrypted connections. If the eBox is also to authenticate itself with a password, this can be entered under "Password". In this case the user name must be the same as the ChargeBox Identity. All other parameters can be left at the default values. The "Use of relative meter readings" parameter should not be activated. The parameter "Validate server certificate" must not be activated. Click "OK" to apply the settings. If necessary, restart the eBox via the menu "System -> Reset -> Router restart".
Operate the innogy eBox via Modbus TCP on the cFos charge manager
As of firmware 1.3.26, the innogy eBox can also be operated via Modbus TCP. The current firmware version can be queried using the innogy eConfig app. The eBox web interface is set up and called up as described above. The Modbus settings are made in the LDP1 -> Load management menu. Modbus_tcp is selected as the load management type. Select the network to be used as the interface, i.e. net1 for LAN1, net2 for LAN2 and wlan1 for the WLAN network. The TCP port to be used can be selected under Port. For Modbus this is 502 by default. The settings are accepted with "OK". If necessary, restart the eBox via the menu "System -> Reset -> Router restart".
Unfortunately, we are currently not aware of any Modbus register for reading out the loaded kWh. We are grateful for any hints on this!
Select 'Kostal Inverter HTTP' as the device type. Enter the IP address of the Kostal inverter as the address. The version of the inverter must be new enough. If necessary, update the inverter firmware. Tested with a newer Piko 7.0.
Select 'SunSpec Solar Inverter' as the device type. Enter the IP address of the Fronius inverter as the address, followed by: 520 as the port number. Fronius uses 200, 201, 202, 203 or 204 as the ID.
Note: For the cFos Charging Controller the COM port is always COM1.