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
If a connection to the EVSE has been established via the innogy eConfig app, click on "Business / Commercial" to set up the configuration. When selecting the backend, choose "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 EVSE 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 established with SSL encryption, the "ws" must be replaced by a "wss" at the beginning of the URL. The name under which the EVSE reports to the backend is entered under "ChargeBox ID", e.g. LP000123 or CP456. If the EVSE is also to be authenticated using a password, this can be specified as an option. In this case, the username must contain the same value as the ChargeBox ID field.
OCPP: Setup via the EVSE'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 EVSE. The web interface can be accessed via HTTPS (port 443) under the IP address of the EVSE. First, a connection to the network must be established as described above. The IP address of the EVSE 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. Log in 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. The settings are accepted with "OK". 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. Which firmware version is available can be queried using the innogy eConfig app. The web interface of the eBox must be 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 by default 502. 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!
Here you need a two-wire connection with a twisted cable (bell wire, network cable). Since A and B are not specified for Modbus, you may have to swap the wires if the wallbox cannot be reached. Address is COM1,38400,8, E, 1 (under Windows and Raspberry possibly another COM port, e.g. COM3). Since the support of the ABL eMH1 is currently still "experimental", we look forward to positive feedback if you operate the wallbox on the cFos Charging Manager.
Enter the IP address at which the go-e can be reached in your home network as the address.
Enter the IP address at which the wallbox can be reached in your home network as the address. You can also integrate the x-series via OCPP.
Enter the IP address at which the wallbox can be reached in your home network as the address. Alternatively, you can also integrate them via OCPP.
S0 meters trigger a certain number of pulses per kWh with a switching output. The number of pulses per kWh must be set correctly. The wiring is done with twisted two-wire (bell wire, telephone line, network cable). Since the switching outputs are normally semiconductor outputs, the S0 lines on the meter may have to be swapped. When connecting to the cFos Power Brain Controller, avoid 12V short circuits that can destroy the controller. Here you will find detailed information on S0 meters.
Select the appropriate meter type and wire the contacts A with A and B with B using a two-wire line (telephone line / For cable lengths exceeding 10m, we recommend terminating resistors of 120 ohms, 1/4 watts at both ends of the bus. Since A and B are not standardized, you may have to swap the wires. Each device on the bus has a unique ID that you must enter in addition to the address. Enter COMx, baud, bits, parity, stops as the address, e.g. COM1,9600,8, N, 1 where x is the COM port to which your two-wire line is connected: Always COM1 with the cFos Power Brain Controller. With Windows and Raspberry you have to find out the COM port of your RS485 adapter. Baud, bits, parity, stops can be found in the manual for the counter. At ABB mostly 19200.8, N, 1, at Eastron 9600.8, N, 1, at Orno and ZZ4 D513020 9600.8, E, 1. Each device on Modbus RTU (two-wire) must have a unique ID. If you operate several devices on one bus, you may have to change the ID in the devices. This can be done either using the control buttons on the meter or with the Modbus UI in the Charging Manager under "Configuration".
The Powerfox meter sends its data to the manufacturer's cloud. You can then call this up again with the cFos Charging Manager. Enter the address: https://user:email@example.com/api/2.0/my/main/current. Here, 'user' is your username and 'pwd' is your password. If your username contains an @ you have to %40 , e.g. firstname.lastname@example.org becomes claus%40example.com.
The Shelly 3EM is booked into the house network and can then be addressed via HTTP API. The address is then//user: email@example.com. 'User' is your username and 'pwd' is your password (%40 , eg firstname.lastname@example.org becomes claus%40example.com).
With PV equipment, we always recommend trying the 'SunSpec Solar Inverter' device first. Enter the IP address under which the device is logged into your home network as the address. Port is often 502, e.g. 192.168.2.111:502. You may still have to enter the ID correctly, as some manufacturers display different devices under certain IDs. If necessary, see the manufacturer's documentation. SunSpec is a standardization for different device models. Several models can be shown in one device, which you can select (if necessary). Here information about SunSpec parameters. You can also configure the SunSpec start register if the IP address of the device is correct but no SunSpec device is found. If you need a certain SunSpec model (and want to exclude others), you can use the "SunSpec Model Index" to ensure that the Charging Manager skips the registers of the previous models. You can find more about the respective SunSpec Start Register and the sequence of the SunSpec models in your device in the manufacturer's manual.
Enter the IP address under which the SMA inverter is logged into your home network as the address. Port is typically 502, e.g. 192.168.2.111:502. Id is often 3. Then you can first try to select 'SunSpec Solar Inverter' as the device type. If the inverter cannot (meaningfully) be read out in this way, you can try the device type 'SMA Inverter'.
E3/DC devices can be addressed in different ways. You should try 'SunSpec Solar Inverter' as the first device type. Alternatively there is the E3/DC Simple Mode which you/DC Solar Device'. Enter the IP address under which the device is logged into your home network as the address. Port is 502, e.g. 192.168.2.111:502. Id presumably 1. In simple mode you also have to enter a register under 'Register or power meter' for reading out the desired power value (which then relates to all phases together) or a power meter (which allows phase-related power values to be read out). Valid values for power meters are 0-7. Here is a list of the registers.
Select 'SunSpec Solar Inverter' as the device type. Enter the IP address of the Fronius inverter as the address, followed by: 502 as the port number. Fronius typically uses 1 for the inverter and 240 for the smart meter as the ID. You can also try the 200, 201, 202, 203 or 204. For more details, see the documentation for the respective device.
Note: In almost all cases it is better to select / Only if this is not possible should you use 'Kostal Inverter HTTP'.
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.
The SMA Homemanager transmits its data periodically as UDP multicast to all network participants. Therefore you do not need to enter an address. You have to make sure that your network forwards UDP multicasts. This is often blocked in the WLAN and must therefore be activated in your router.
With devices from SolarLog and Sonnen you can select in the device type which function the device has, e.g. 'SolarLog Production' or 'Sonnen Production HTTP'. Then enter the IP address with which the device is logged into your home network as the address. For SolarLog add port 502, e.g. 192.168.2.111:502, for Sonnen place an http:// front of it, e.g. http://192.168.2.111.
Note: For the cFos Charging Controller the COM port is always COM1.