Instructions for some EVSEs

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

Slave ID1
Type16 bit word
Value to writeNew Slave ID
Write func16


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 Charging 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. 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!

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