User's Manual

User Manual Installation Guide

2.4.2 Use Case 2: vSECC with Power Electronics

The goal is to use a power electronics circuitry together with the vSECC.

1. Follow the Use Case 1 instructions above. Make sure that you do not connect

the power supply yet.

2. Connect one of the ethernet ports to an ethernet network, which is provid-

ing access to the power electronics communication controller (PECC). This

connection is used to control the power electronics via PEP.

3. Connect the X304 safety output connector. Make sure that the pins for REL1

and REL2 are connected to the appropriate inputs of the power electronics

itself. REL1 corresponds to the first charging connector and REL2 to the

second.

4. Flip the DIP Switches 1, 2, 3 and 4 to the ”ON” position. This disables the

PP1, PP2, CC1 AC and CC1 DC loss detection. Note that the Proximity Pin

(PP) is not yet supported, but will be in a future release.

5. (Optional) Connect the X301 (analog and temperature inputs) and X306 (dig-

ital inputs and outputs) connectors. This is necessary for the PECC to get

input values or control digital outputs through PEP. See Section 3.7 for the

PEP identifiers that correspond to each pin.

6. Connect the X307 power supply connector. Take care of the correct polarity.

Ensure that 24 V and at least 200 mA are provided.

After the vSECC has started up, set the correct power electronics URI for both connectors

using the Web-UI or CSMS.

2.4.3 Use Case 3: vSECC with CSMS

The goal is to use a Charging Station Management System (CSMS) to configure and man-

age the vSECC.

1. Follow the Use Case 1 instructions above. Make sure that you do not connect

the power supply yet.

2. Connect one of the ethernet ports to an ethernet network, which is providing

access to the CSMS.

3. Use the Web-UI (see Section 3.1.1) to set the correct backend URI and pos-

sibly login credentials.

4. Connect the X307 power supply connector. Take care of the correct polarity.

Ensure that 24 V and at least 200 mA are provided.

After the vSECC has started up, the vSECC tries to connect repeatedly to the CSMS using

the configured URI and credentials.