Instructions for some EVSEs, meters and inverters

You need to set a unique Slave ID for each controller: cFos Charging Manager -> System Configuration -> Modbus

AddressCOMx,9600,8,n,1
Slave ID1
Registers2001
Type16 bit word
Count1
Value to writeNew Slave ID
Write func16

Write

From then on, the controller only listens to the new Slave ID. Then write a register >= 2000 (e.g. the register 2001 again with the new slave ID). Then the value remains active after a restart.

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

AddressCharge Point ID, as configured in the EVSE
IDConnector ID, as configured in the EVSE

In cFos Charging Manager -> cFos Power Brain Controller Configuration: Enable "EVSE as OCPP client"

IDAs configured in the Charging Manager (the connector ID is always 1)
ServerURL of your OCPP backend, including port number, e.g. http://192.168.2.115:19520/. The "/" at the end can be important depending on the backend - for cFos Charging Manager, the port number is always 19520

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

Find ID

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 / IDEnter 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 EVSE 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, select either WLAN or LAN depending on the connection; for WLAN, also enter the SSID and the WLAN password. After the EVSE has connected to the network, the backend can be configured. Enter ws://x.x.x.x:p/ as the backend URL, where x.x.x.x stands for the IP of the cFos Charging Manager in the network, e.g. 192.168.2.111, and "p" stands for the port 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, the "ws" at the beginning of the URL must be replaced by a "wss". Under "ChargeBox ID", enter the name under which the EVSE reports to the backend, e.g. LP000123 or CP456. If the EVSE is also to authenticate itself with a password, this can be entered as an option. In this case, the user name must contain the same value as the ChargeBox ID field.

OCPP: Setup via the web interface of the EVSE (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. Then determine the IP address of the EVSE using the router in use (e.g. 192.168.2.111). The web interface can then be accessed via a browser. Please ignore certificate warnings. Log in with "admin" and enter the PUK of the eBox as the password.
The OCPP configuration is done in the menu "ECU", submenu "OCPP". Under ChargeBox Identity, a name is selected under which the eBox reports to the OCPP backend, e.g. LP000123 or CP456. For the End-Point URI, enter the URI of the OCPP backend, e.g. ws://192.168.2.111:19500/ for unencrypted or wss://192.168.2.111:19500/ for encrypted connections. If the eBox is to authenticate itself additionally 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 their default values. The parameter "Use relative meter readings" 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".

Operating the innogy eBox via Modbus TCP on the cFos Charging Manager

As of firmware 1.3.26, the innogy eBox can also be operated via Modbus TCP. The innogy eConfig app can be used to find out which firmware version is available. The web interface of the eBox can be set up and called up as described above. The Modbus settings are made in the menu LDP1 -> Load management. Select modbus_tcp 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. Under Port, the TCP port to be used can be selected. For Modbus, this is 502 by default. Click "OK" to accept the settings. If necessary, restart the eBox via the menu "System -> Reset -> Router Restart".

Unfortunately, we are not currently aware of a Modbus register for reading out the charged kWh. We would be grateful for any information on this!

Here you need a two-wire connection with twisted cable (bell wire, network cable). In the housing of the eMH1 you will find an RJ12 socket that is connected to RS485 on the board. The (middle two) pins 3 and 4 are Modbus A and B. So you need an adapter from RJ12 to two-wire. Since A and B are not specified for Modbus, you may have to swap the wires if the EVSE is not accessible. Address is COM1,38400,8,E,1 (under Windows and Raspberry possibly other COM port, e.g. COM3). You may have to set the EVSE to "Standalone" in the ABL configuration programme confcab. The Modbus ID here can also be set to values from 1 to 16 if required.

Specify the following parameters in the cFos Charging Manager: Address: Serial number of the EVSE (e.g. EH123ABC), ID: without meaning, User: User name in the EVSE Cloud, i.e. e-mail address or mobile phone number including international dialling code (e.g. +49), Password: Password for the above user name in the EVSE Cloud.

Enter the IP address under which the go-e can be reached in your home network as the address.

Enter the IP address under which the EVSE can be reached in your home network as the address. To activate the KEBA UDP protocol, you must set the DIP switch 1.3 in the EVSE to "on". You can also integrate the x-series via OCPP.

Enter the IP address at which the EVSE can be reached in your home network as the address. Alternatively, you can also integrate it via OCPP.

Integration via Modbus: Possibly deactivate OCPP, deactivate free charging, activate Modbus, select Modbus Register Set TQ-DM100. Then address the EVSE under port 502, e.g. enter 192.168.2.111:502 as the address. Alternatively, you can also integrate it via OCPP: Enter Websockets JSON OCPP backend URL (incl. port) of the cFos Charging Manager, e.g. ws://192.168.2.123:19500/, then start charging with an RFID.

Please note that the Autoaid only runs with a certain firmware with the cFos Charging Manager (currently 1.1.258). It may work with a newer version. However, this is not confirmed. To set up the box, download the EVSE Mesh app from the App Store. Instead of the EN+ backend, the IP address and port of the cFos Charging Manager must be entered. If the IP address of the cFos Charging Manager is 192.168.2.100 and the port is 19520, you must enter the following in the Autoaid EVSE: http://192.168.2.100 (unencrypted) and https://192.168.2.100 (encrypted). Port: 19520. ws://" or "wss://" may also work instead of "http://" or "https://". Encrypted connections are currently untested. In the cFos Charging Manager, "EVSE with OCPP" must be selected as the device type and the OCPP Charging Point ID of the Autoaid Intelligent must be entered as the address. The Charge Point Id is the serial number of the EVSE starting with SN. It is displayed in the app.

Set the identification to "inactive" in the EVSE setup. Set the charging station type to "stand-alone solution". It may be necessary to assign a fixed IP address so that the EVSE is available in the LAN (possibly deactivate the EVSE's DHCP server). Under "Energy Management", set the options "Charging current throttled" to 6A and "Local power reduction" to 16A. In cFos Charging Manager, enter the address of the EVSE and port 502, e.g. 192.168.2.111:502, set ID to 255. If you want to operate the EVSE with OCPP, enter a ws:... as the URL of the backend. as the URL of the backend, no wss:

You can select Mennekes Amtron as the device type, as this wallbox has the same controller from ebee or Bender.

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 pair wire (bell wire, telephone line, network cable). As the switching outputs are normally semiconductor outputs, the S0 lines on the meter may have to be changed. When connecting to the cFos Power Brain Controller, avoid 12V short circuits, which can destroy the controller. Click here for detailed information on S0 meters.

Select the appropriate meter type and use a two-wire line (telephone line / network cable) to wire contacts A to A and B to B, thus creating a bus. For line lengths of 10m or more, we recommend terminating resistors of 120 Ohm, 1/4 Watt at both ends of the bus. Since A and B are not standardised, 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 on which your two-wire line is connected: For the cFos Power Brain Controller always COM1. For 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 of the meter. For ABB usually 19200,8,N,1, for Eastron 9600,8,N,1, for Orno and ZZ4 D513020 9600,8,E,1. Each device on Modbus RTU (two-wire) must have a unique ID. If you operate several units on one bus, you may have to change the ID in the units. This can be done either using the control buttons of the meter or with the Modbus UI in the Charging Manager under "Configuration".

For the Bauer BSM, select SunSpec as the device type, the COM port to which you have connected the 2-wire connection. Select 19200,8,E,1 as the interface parameter and 42 as the ID. If you have set other parameters in the meter, select them accordingly.

The Powerfox meter sends its data to the manufacturer's cloud. You can then retrieve this data with the cFos Charging Manager. Enter the following address: https://user:pwd@backend.powerfox.energy/api/2.0/my/main/current. Here, 'user' is your user name and 'pwd' your password. If your user name contains an @, you must replace this with %40, e.g. claus@example.com becomes claus%40example.com.

The Shelly 3EM is logged into the house network and can then be addressed via HTTP API. The address is then e.g. http://user:pwd@192.168.2.111. Here 'user' is your user name and 'pwd' your password (if your user name contains an @ you must replace this with %40, e.g. claus@example.com becomes claus%40example.com).

Select "Elgris Smartmeter" as the device type. The meter can be integrated via Modbus TCP. Enter the address with which the meter is registered in the house network and port 502, e.g. 192.168.2.111:502. Id is usually 1.

We recommend that you always try the 'SunSpec Solar Inverter' device type first for PV equipment. Enter the IP address under which the device is registered in your home network as the address. Port is often 502 (or 1502), e.g. 192.168.2.111:502. You may also have to enter the ID correctly, as some manufacturers show different devices under certain IDs. If necessary, see the manufacturer's documentation. For some devices, Modbus TCP must also be enabled. SunSpec is a standardisation for different device models. Several models can be mapped in one unit, which you can select (if necessary). Here is information on SunSpec parameters. You can also configure the SunSpec Start register if the IP address of the unit is correct but no SunSpec unit is found. If you need a specific SunSpec model (and want to exclude others), you can use "SunSpec Model Index" to make the Charging Manager skip the registers of the preceding models. For more information about the SunSpec Start Register and the order of the SunSpec models in your unit, please refer to the manufacturer's manual.

The cFos Charging Manager also tries to find storages that are readable according to SunSpec. If your storage supports SunSpec, you can select SunSpec for this meter device type.

Enter the IP address under which the SMA inverter is registered in 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 be read out (meaningfully) in this way, you can try the device type 'SMA Inverter'.

E3/DC units can be addressed in different ways. You should first try the device type 'SunSpec Solar Inverter'. Alternatively, there is the E3/DC Simple Mode which you can select with the device type 'E3/DC Solar Device'. Enter the IP address under which the device is registered in your home network as the address. Port is 502, e.g. 192.168.2.111:502. Id probably 1. In Simple Mode, you must also enter a register for reading out the desired power value (which then refers to all phases together) or a power meter (which allows phase-related power values to be read out) under 'Register or Power Meter'. Valid values for power meters are 0-7. Here is a list of registers. Note: You must activate Modbus and Modbus/TCP in the E3/DC.

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. As Id, Fronius typically uses 1 for the inverter and 240 for the Smartmeter. You can also try 200, 201, 202, 203 or 204. For more information, see the documentation for the respective device.

In connection with inverters, Kostal offers a meter that can measure the mains supply bidirectionally. Select 'Kostal Powermeter' as the device type. Enter the IP address of the Kostal inverter as the address, port is often 1502 (e.g. 192.168.2.111:1502). 71 is often used as the ID.

Note: In almost all cases it is better to select the device type 'SunSpec Solar Inverter / Meter' for Kostal inverters and Smartmeters. 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 firmware of the inverter. Tested with a newer Piko 7.0.

The KSEM can be operated as device type SunSpec with its IP address and port 502, e.g. 192.168.2.111:502. Enter 0 as ID.

The SMA Homemanager transmits its data periodically as UDP multicast to all network participants. Therefore, you do not need to specify an address. You must ensure that your network forwards UDP multicasts. This is often blocked in the WLAN and must therefore be enabled in your router.

For SolarLog and Sonnen devices, you can select which function the device has in the device type, 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 the port 502, e.g. 192.168.2.111:502, for Sonnen add a http:// in front, e.g. http://192.168.2.111.

Thank you, Rainer Z., for these instructions!
There are two possibilities for integration: Modbus RTU (two-wire) and Modbus TCP (via the domestic network). Modbus TCP should be selected if the Huawei dongle is used. This provides a WLAN or a LAN connection. However, older firmware versions often cause problems. Huawei itself recommends the following firmware versions for Modbus TCP: Device Minimum Firmware Version SDongleA-05 V1000R001C00SPC124, SUN2000L V2000R001C00SPC115, SUN2000MA V1000R001C00SPC139 (currently tested with dongle version V100R001C00SPC127 and inverter version V100R001C00SPC141). If necessary, ask the installer to update them with the available packages from FusionSolar website or contact eu_inverter_support (at) huawei.com. The inverter can also be updated by the customer as long as access to the installation menu is available. Likewise, Modbus TCP must be activated in this installation menu:

  • Connect the mobile phone to the inverter via the inverter's Wi-Fi hotspot. If not configured, the hotspot data is located as a sticker with QR code on the dongle (default: SUN2000-xxxxxxxx)
  • Start the current FusionSolar app
  • Confirm the message "Access failed"
  • Open the three-point menu (top right)
  • Select start-up of the unit
  • Log on to the unit (e.g. SUN2000-xxxxx-xx) under "Connection recording". If the installer has not changed the parameters, the password is 00000a
  • Under Settings → Communication Configuration → Dongle Parameter Settings → Modbus TCP, set the "Connection" setting to "Enable (unrestricted)".
If Modbus TCP no longer functions after a dongle update, this Modbus TCP activation must be repeated. Under Maintenance → "Update Device", the software of the devices can be updated, with the exception of the dongle. The Modbus TCP queries are somewhat time-critical with Huawei, so no two instances should query values. For solar surplus charging, the meter "Huawei SUN 2000 Meter" should be selected. The IP of the Huawei inverter should be selected as the IP, as well as its ID (in most cases 1). The port is 502, e.g. 192.168.2.111:502. The grid reference meter shows negative values for grid reference and positive values for feed-in. Therefore, you must invert the meter in the meter settings in the cFos Charging Manager.

Note: For the cFos Power Brain Controller the COM port is always COM1.