Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH User Manual
  1. Manuals
  2. Brands
  3. Phoenix Contact Manuals
  4. Automobile Accessories
  5. EV-CC-AC1-M3-CBC-RCM-ETH
  6. User manual

Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH User Manual

Ev charge control charging controller
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Installing and starting up the
EV Charge Control charging controller
User manual

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EV-CC-AC1-M3-CBC-RCM-ETH and is the answer not in the manual?

Questions and answers

Related Manuals for Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH

Summary of Contents for Phoenix Contact EV-CC-AC1-M3-CBC-RCM-ETH

  • Page 1 Installing and starting up the EV Charge Control charging controller User manual...
  • Page 2 UM EN EV-CC-AC1-M3-CBC-RCM-ETH, Revision 04 2020-09-17 This user manual is valid for: Designation Revision Order No. EV-CC-AC1-M3-CBC-RCM-ETH 1018701 EV-CC-AC1-M3-CBC-RCM-ETH-3G 1018702 EV-CC-AC1-M3-RCM-ETH-XP 1139449 EV-CC-AC1-M3-RCM-ETH-3G-XP 1139452 PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany phoenixcontact.com...

  • Page 3: Table Of Contents

    Connecting the energy measuring device ..........31 4.8.2 Connecting an RFID card reader ............33 Cellular interface ........................35 Basics of signal contacts and charging sequences ..............36 Control Pilot signal....................36 Proximity signal (Proximity Plug) ................. 41 3 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 4 Modbus description .........................70 Modbus register types ..................70 Register assignment.................... 71 Function assignment of input and output registers ..........90 Appendix for document lists......................93 List of figures ....................... 93 List of tables ......................95 Index........................97 4 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 5: For Your Safety

    For your safety Correct use The EV-CC-AC1-M3-CBC-RCM-ETH (-3G/-XP) charging controllers are designed exclu- sively for use in electric vehicle charging stations in accordance with IEC 61851-1, mode 3. The charging stations must be permanently connected to the power grid. No other uses are permitted.

  • Page 6: Shutdown And Disposal

    Provide a disconnecting device for disconnecting the charging station from the voltage. Disposal Do not dispose of the device with household waste; it should instead be disposed of in ac- cordance with the currently applicable national regulations. 6 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 7: Properties Of The Charging Controller

    OCPP interface (via OCPP 1.6J, JSON). Table 2-1 Interfaces Charging controller Communication OCPP 1.6J communication Ethernet Cellular Ethernet Cellular EV-CC-AC1-M3-CBC-RCM-ETH – – – EV-CC-AC1-M3-CBC-RCM-ETH-3G – EV-CC-AC1-M3-RCM-ETH-XP – – EV-CC-AC1-M3-RCM-ETH-3G-XP You can combine several charging controllers to create a master/slave group. This group can communicate with the central management system via the master using the OCPP pro- tocol.

  • Page 8: Ordering Data

    161.6 mm x 90 mm x 61 mm Weight 460 g Power supply Nominal voltage 230 V AC Tolerance ±10% Mains frequency 50/60 Hz Power consumption, maximum 10 W Power consumption, no load < 3 W 8 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 9 Length of connecting cable 0.2 m Connection at main device (connector) 6-pos. Load current, maximum 3 x 32 A (4 x 6 mm²), maximum Standards IEC 60364-7-722 IEC 62752 DIN VDE 0100-722 (VDE 0100-722:2013-01) 9 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 10 Protocol Modbus/TCP EV-CC-...-XP: OCPP 1.6J (WebSockets) Transmission speed 10/100 Mbps Transmission distance 100 m Cellular interface (EV-CC-AC1-M3-CBC-RCM-ETH-3G and ...3G-XP only) Frequency bands HSPA 900 MHz, 2100 MHz GSM/GPRS/EDGE 850 MHz, 900 MHz, 1800 MHz, 1900 MHz Maximum transmission power UMTS/HSPA...
  • Page 11 < 2000 m Mounting position Conformance/approvals CE-compliant Low Voltage Directive 2014/35/EU Function and safety tests IEC 60950-1 / EN 60950-1 Air clearances and creepage distances IEC 60950-1 / EN 60950-1 Housing conformance with standards DIN 43880 11 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 12: Declaration Of Conformity In Accordance With 2014/53/Eu

    Pst < 0.25 low-voltage networks Declaration of conformity in accordance with 2014/53/EU Phoenix Contact hereby declares that wireless system type EV-CC-AC1-M3-CBC-RCM-ETH-3G complies with Directive 2014/53/EU. The complete text of the EU declaration of conformity is available at the following address: phoenixcontact.net/products/1018702.

  • Page 13: Connections, Indicators, And Configuration Switches

    Contactor monitoring, checks the output signal for voltages on completion of the charging process Line Phase, power grid 230 V AC Neutral Neutral conductor, power grid Protective Functional ground connected to protective earth ground earth Ethernet RJ45 jack for 100Base-TX Ethernet interface 13 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 14 Contactor 4 Antenna SMA antenna connector for cellular connection For further information on the configuration options for the digital inputs and outputs, please refer to “Status indicator and configuration via web server” on page 46. 14 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 15: Operating Elements And Indicators

    Enable charging process and charging station availability via Ethernet (Modbus/web server), RFID card with locally stored release list or via OCPP backend Enabling of charging process and charging station availability via Ethernet (Modbus/web server) not required 15 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 16: Rotary Coding Switch

    Maximum current 32 A Maximum current 63 A Maximum current 70 A Maximum current 80 A Table 3-5 Reset button Name Function Reset Pressing once: device restart Pressing > 10 s: reset to factory default settings 16 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 17: Dimensions

    Connections, indicators, and configuration switches Dimensions Figure 3-3 Charging controller dimensions 161,6 EV Charge Control EV-CC-AC1-M3-CBC-RCM IEC 61815-1, Mode 3 52,3 Figure 3-4 Measuring sensor dimensions 17 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 18: Mounting And Startup

    NOTE: Electrostatic discharge Electrostatic discharge can damage or destroy components. When handling the de- vice, observe the necessary safety precautions against electrostatic discharge (ESD) in accordance with EN 61340-5-1 and IEC 61340-5-1. 18 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 19: Din Rail Mounting

    Push down the locking latch using a screwdriver, needle-nose pliers or similar. • Pull the bottom edge of the device slightly away from the mounting surface. • Pull the device diagonally upward from the DIN rail. 19 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 20: Supply Voltage Connection

    EV Charge Control EV-CC-AC1-M3-CBC-RCM IEC 61815-1, Mode 3 230 V L, L1-L3 • Connect the supply voltage to the device via terminal blocks N, L, and PE (connection block 1, see Figure 3-1 on page 13). 20 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 21: Charging Contactor Connection

    Route the 12 V device voltage to a free digital input via a N/C (normally closed) or N/O (normally open) auxiliary contact. • Assign the function to the corresponding input via the web server (see “Status” tab). • Enable contactor monitoring (see “Configuration” tab). 21 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 22 “Contactor Failure” event (see “Status” tab, “Configuration” tab “Modbus description” on page 70). The signal of this output can be used to open a redundant switching element or force the upstream RCD to trip. 22 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 23: Connection Of The Current Measuring Transducer For Residual Current Detection

    The charging controller enters an error state. The error state is reset when the vehicle is disconnected from the charging station. NOTE: Type A RCD required Residual current detection does not release you from the obligation to provide a sep- arate type A RCD for the charging station. 23 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 24: Connection Of The Vehicle Charging Connector And Infrastructure Charging Socket

    Figure 3-1 “Connections on the charging con- troller”) of the charging controller. • For charging case C, set DIP switch #1 to position 0 at configuration switch 1 (Figure 3-2 “Operating elements and indicators”). 24 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 25: Infrastructure Charging Socket

    R1 and R2. When a defined state is reached, the output is disconnected from the power supply. In the factory default settings, the switching times are matched to the infrastructure charging sockets from Phoenix Contact. 25 / 100 108191_en_04...
  • Page 26 To detect the locking state, a High signal is expected at input LD, e.g., by means of a floating contact. The EV-T2M3SE12-... infrastructure charging sockets from Phoenix Contact fea- ture this type of floating contact. A closed contact indicates locking. Connect the floating...

  • Page 27: Wiring Of The Digital Inputs

    The inputs can also be controlled by an external higher-level controller with 12 V outputs. Here too GND is used as the common reference point. Figure 4-10 Wiring of the digital inputs, internal supply EV Charge Control EV-CC-AC1-M3-CBC-RCM IEC 61815-1, Mode 3 27 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 28: Wiring Of The Digital Inputs, External Supply

    The charging controller can be configured via the web server or via Modbus/TCP. For the configuration options for the digital inputs and outputs, refer to section “Status indicator and configuration via web server” on page 46, from “Status” tab, and “Modbus description” on page 28 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 29: Wiring Of The Digital Outputs

    In status 0 (OFF), the outputs are connected to GND and in status 1 (ON), they are con- nected to the potential of 12a. GND is connected to PE internally. NOTE: Observe the current capacity per output Please note the maximum current capacity of 600 mA per output. 29 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 30: Wiring Of The Digital Outputs, External Feed-In

    NOTE: Possible damage to the transistors Never connect a supply voltage to the outputs. One of the transistors is always acti- vated. This means that the transistors may be destroyed. The outputs are not short-circuit-proof or protected against overload. 30 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 31: Rs-485 Interface

    (on the “Energy Meter” tab). Up to firmware 1.11: Figure 4-14 Connection of the EEM-350-D-MCB energy measuring device via RS-485 EEM-350-D-MCB EMpro EV Charge Control EV-CC-AC1-M3-CBC-RCM IEC 61815-1, Mode 3 4142 43 3132 33 31 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 32: Connection Of The Eem-Em357 Energy Measuring Device Via

    – Currents of I/Imax < 1.1 are tolerated. The energy measuring device interface is activated and configured via the web server (see “Energy Meter” tab) or Modbus (see “Modbus register types” on page 70). 32 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 33: Connecting An Rfid Card Reader

    To check the UID by means of a higher-level management system, suppress the buzzer via er-level management sys- Modbus/TCP (register address 425, see “Register assignment” on page 71). The buzzer signal is suppressed for 60 s and must be suppressed again on a continuous basis. 33 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 34 Enabling is also performed via Modbus/TCP. If charging cannot be enabled, the buzzer can be activated via Modbus/TCP, register address 421. Charging remains enabled until it is reset again by the higher-level system via Modbus. 34 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 35: Cellular Interface

    The charging controllers are available in versions with a cellular interface. Table 5-1 Communication interfaces Charging controller Communication Ethernet Cellular EV-CC-AC1-M3-CBC-RCM-ETH – EV-CC-AC1-M3-CBC-RCM-ETH-3G EV-CC-AC1-M3-RCM-ETH-XP – EV-CC-AC1-M3-RCM-ETH-3G-XP Antenna Only use the supplied antenna to connect to the cellular network. Connect it to the SMA fe- male antenna connector (see Figure 3-1 “Connections on the charging...

  • Page 36: Basics Of Signal Contacts And Charging Sequences

    The assignment of the permissible charging current value to the pulse width of the PWM sig- nal and the assignment of the voltage value to the vehicle states are defined in IEC 61851-1 (see Table 6-2 on page 38). 36 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 37: Typical Curve Of The Control Pilot Signal

    The charging station can be set to an operational state, e.g., by a signal at the Enable input or using the relevant Modbus command. ‡‡ In the delivery configuration, status D is not supported Figure 6-2 Typical curve of the Control Pilot signal B1/B2 B1/B2 -12V 37 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 38 The vehicle stops the charging process and opens S2. The charging con- troller disconnects the charging contactor again and with it the voltage from the charging cable. Vehicle discon- – 12 V nected from the charging station 38 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 39: Controlling The Maximum Charging Current That May Be Taken In Accordance With Iec 61851-1

    Available current = (pulse duty factor % - 64) x 2.5 A 96% < pulse duty factor ≤ 97% 80 A Pulse duty factor > 97% Available current = (pulse duty factor % - 64) x 2.5 A Function not supported by this controller 39 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 40: Activation Mode

    Activation mode is activated again under these conditions: – The vehicle is disconnected from the charging controller and connected again. – The charging process is interrupted by the charging station (e.g., for reasons of load management). 40 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 41: Proximity Signal (Proximity Plug)

    63 (70) A 220 Ω 150 Ω ... 330 Ω 32 A 680 Ω 330 Ω ... 1000 Ω 20 A 680 Ω 1000 Ω ... 2200 Ω 13 A – > 2200 Ω 41 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 42: Ocpp Backend Connection

    Open Charge Point Protocol OCPP 1.6J (JSON) and the Web- Sockets protocol. Table 7-1 Interfaces Charging controller OCPP 1.6J communication Ethernet Cellular EV-CC-AC1-M3-CBC-RCM-ETH – – EV-CC-AC1-M3-CBC-RCM-ETH-3G – EV-CC-AC1-M3-RCM-ETH-XP – EV-CC-AC1-M3-RCM-ETH-3G-XP The following table provides an overview of the supported operations from the OCPP pro-...
  • Page 43 Only for the implemented messages Unlock Connector Limited Change Configuration Parameters – ConnectorTimeOut – HeartbeatInterval – MeterValueSampleInterval – StopTransactionOnInvalidId – PricePerkWh – WebSocketPingInterval Get Diagnostics Upload to an FTP server Firmware-Update FW update downloaded from an FTP server 43 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 44: Configurationkeys Of The Charging Controller

    PricePerkWh false ResetRetries false StopTransactionOnEVSideDisconnect true true StopTransactionOnInvalidId true true StopTxnAlignedData true true StopTxnSampledData true true SupportedFeatureProfiles true Core, Reservation, SmartCharging, RemoteTrigger TransactionMessageAttempts false TransactionMessageRetryInterval false UnlockConnectorOnEVSideDisconnect true true WebsocketPingInterval false 44 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 45 OCPP backend connection 45 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 46: Status Indicator And Configuration Via Web Server

    Configurations on the individual pages are transferred to the device using the “Submit” but- ton. Individual configuration parameters only take effect after the device has been restarted. Once all of the parameters have been set, a single reset via the corresponding button is nec- essary. 46 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 47: Status" Tab

    Corresponds to the current carrying capacity of the connected charging cable, determined by evaluating the proximity contact. Active Charging Duration Time in hh:mm that the vehicle has been charging. Reset via status A. (hh:mm) 47 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 48 “PWM on”, see Table 8-3. Buttons Submit Transfers selected configurations to the charging controller. Reset Restarts the charging controller. A restart is required to apply any changes to the configu- ration. 48 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 49: Configuration Options For Digital Inputs

    The active transaction is not terminated. Error Input The charging controller can be set to a specific error state via a digital input. Bit 2 is set in register (see Table 9-2). 49 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 50: Configuration Options For Digital Outputs

    The “Output2” register has been set via Modbus (logic 1). Register Output3 The “Output3” register has been set via Modbus (logic 1). Register Output4 The “Output4” register has been set via Modbus (logic 1). 50 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 51 The output is switched on permanently if the enable is issued and status B2 or C2/D2 is present. The output is reset if one of these states occurs: – Charging process stopped – Charging not enabled – Charging revoked 51 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 52: Network" Tab For Ethernet

    EV Charge Control “Network” tab for Ethernet Table 8-4 Interfaces Charging controller Communication OCPP 1.6J communication Ethernet Cellular Ethernet Cellular EV-CC-AC1-M3-CBC-RCM-ETH – – – EV-CC-AC1-M3-CBC-RCM-ETH-3G – EV-CC-AC1-M3-RCM-ETH-XP – – EV-CC-AC1-M3-RCM-ETH-3G-XP Figure 8-2 “Network” tab for Ethernet communication Table 8-5 “Network” tab for Ethernet...
  • Page 53 Table 8-5 “Network” tab for Ethernet [...] Option Meaning Buttons Submit Transfers selected configurations to the charging controller. Reset Restarts the charging controller after transferring the selected configuration. 53 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 54: Network" Tab For Cellular

    EV Charge Control “Network” tab for cellular Table 8-6 Interfaces Charging controller Communication OCPP 1.6J communication Ethernet Cellular Ethernet Cellular EV-CC-AC1-M3-CBC-RCM-ETH – – – EV-CC-AC1-M3-CBC-RCM-ETH-3G – EV-CC-AC1-M3-RCM-ETH-XP – – EV-CC-AC1-M3-RCM-ETH-3G-XP Figure 8-3 “Network” tab for cellular 54 / 100 PHOENIX CONTACT...

  • Page 55: Network" Tab (3G Version)

    Table 8-7 “Network” tab (3G version) Mobile Network (EV-CC-AC1-M3-CBC-RCM-ETH-3G only) ICCID Integrated Circuit Card Identifier: unique SIM card serial number. RSSI (dBm) Received Signal Strength Indication: signal strength of the incoming wireless signal. Ide- ally in the range from -70 to -80 dBm for a stable wireless connection.
  • Page 56 EV Charge Control Table 8-7 “Network” tab (3G version) [...] Mobile Network (EV-CC-AC1-M3-CBC-RCM-ETH-3G only) OCPP End Point Address Backend connection data. The connection data is typically provided by the backend oper- ator. Protocol: WebSocket (WS) or WebSocketSecure (WSS): – End point address –...

  • Page 57: Configuration" Tab

    “Configuration” tab Figure 8-4 “Configuration” tab 57 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 58: Display Values For The "Configuration" Tab

    (0.5 s Default, max. 3 s) Time between Locking Cycles Waiting time between the locking and unlocking pulses if errors occur while the automatic (2 s Default, max. 10 s) locking option is running 58 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 59 Checkbox for locking and unlocking the charging connector in the infrastructure charging socket. Set DIP 4 and DIP 9 to 1 for this. Buttons Firmware-Update Opens a dialog window to update the firmware Submit Transfers the selected configuration to the charging controller 59 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 60: Energy Meter" Tab

    For firmware 1.12 or later, the energy measuring device values of the charging controllers are displayed in Wh and transferred to the OCPP backend. Following an update to firmware 1.12 or later, you need to manually adjust the configuration of the energy measuring devices. 60 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 61 EEM-350-D-MCB Figure 8-5 “Energy Meter” tab for EEM-350-D-MCB 61 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 62 EV Charge Control Figure 8-6 “Energy Meter” tab for EEM-EM357 62 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 63: Configuration Parameters For The Energy Measuring Device

    In the event of an overcurrent of I/Imax > 1.25, shutdown occurs after 10 s. In the event of an overcurrent of I/Imax > 1.1, shutdown occurs after 100 s. Currents of I/Imax < 1.1 are tolerated. 63 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 64 (max. two data words long) to the specified address area. The charging controller Reset 2 Address/Value automatically writes these values after the charging process has been completed (status A). If the value 0 is entered for “# Register (0...2)”, no values are reset. 64 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 65: Card Reader" Tab

    Address under which an integrated buzzer for the card reader can be activated. Whitelist Last Card Unique identifier (UID) of the last RFID card read. Card Name Freely selectable name that can be assigned to an RFID card. 65 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 66 Storing of “Card Name”, “Card UID”, and enable in the whitelist on the charging controller. You can copy the read UID to the whitelist. There you can name the UID and enable it for charging processes. 66 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 67: Remote Control" Tab

    The master handles communication to the OCPP backend for all con- nected charging points. The 3G versions can be used as masters. Table 8-12 Master/slave group Charging controller OCPP 1.6J communication Number of slaves Ethernet Cellular EV-CC-AC1-M3-CBC-RCM-ETH – – – EV-CC-AC1-M3-CBC-RCM-ETH-3G – EV-CC-AC1-M3-RCM-ETH-XP – –...

  • Page 68: Remote Control" Tab

    All vehicles are charged with the same relative charging power. The relative charging power is based on the maxi- mum charging power of the vehicle. 68 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 69 Connector 0 are applied to all connected connectors. If current default val- TxProfile ues are specified by load management or the OCPP backend for a connector or transaction, the lower value is applied. 69 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 70: Modbus Description

    Read/write Coil 1-bit Read/write You can combine several Input and Holding registers to transmit 32-bit data. This data is coded in Little Endian format. The word with the least significant element is listed first. 70 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 71: Register Assignment

    Charging time Integer, seconds Input Input 16-bit Read DIP switch configuration Binary, DIP 1 = LSB Each switch corresponds to one bit. Input 32-bit Read Firmware version ASCII, e.g., 1.21 = 0x2E31 0x3132 Input 71 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 72 V3 Input Input 32-bit Read Display energy measuring device Integer [A] current I1 Input Input 32-bit Read Display energy measuring device current I2 Input Input 32-bit Read Display energy measuring device current I3 Input 72 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 73 Integer [cent] “PricePerkWh” Input 16-bit Read OCPP configuration Integer [s] “HeartbeatInterval” Input 16-bit Read OCPP configuration Integer [s] “ConnectionTimeOut” Input 16-bit Read OCPP configuration Integer [s] “MeterValueSampleInterval” Input 16-bit Read OCPP configuration Integer “ResetRetries” 73 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 74: Register Assignment, Discrete Type

    Register assignment, Holding type Type Address Value Access Function Coding Holding 16-bit Read Set charging current (PWM sig- Integer [A] nal) Holding 3 x 16-bit Read MAC address Hexadecimal E.g., 00:A00:45:66:4F:40: Holding 0xA000 0x6645 0x404F Holding 74 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 75 Definition of output ER Decimal, see Table 9-6 “Func- tion assignment of digital out- Holding 16-bit Read/write Definition of output LR puts” Holding 16-bit Read/write Definition of output VR Holding 16-bit Read/write Definition of output CR 75 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 76 Voltage V2 nected energy measuring device Holding 16-bit Read/write Voltage V3 (Default: EEM-350-D-MCB en- Holding 16-bit Read/write Current I1 ergy measuring device from Phoenix Contact) Holding 16-bit Read/write Current I2 Holding 16-bit Read/write Current I3 Holding 16-bit Read/write Active power...
  • Page 77 Read/write Voltage V2 nected energy measuring device Holding 16-bit Read/write Voltage V3 (Default: EEM-EM357 energy Holding 16-bit Read/write Current I1 measuring device from Phoenix Contact) Holding 16-bit Read/write Current I2 Holding 16-bit Read/write Current I3 Holding 16-bit Read/write Active power...
  • Page 78 Conversion factors for values from the energy measuring device up to firmware 1.11 Holding 32-bit Read/write Voltage V1 Decimal EEM-350-D-MCB energy mea- Holding suring device from Holding 32-bit Read/write Voltage V2 Phoenix Contact Holding Holding 32-bit Read/write Voltage V3 Holding Holding 32-bit Read/write Current I1 Holding Holding...
  • Page 79 Coding Conversion factors for values from the energy measuring device with firmware 1.12 or later Holding 32-bit Read/write Voltage V1 Decimal EEM-EM357 energy measuring Holding device from Phoenix Contact Holding 32-bit Read/write Voltage V2 Holding Holding 32-bit Read/write Voltage V3...
  • Page 80 Evaluation of voltage mea- surement from energy mea- suring device Holding 8 x 16-bit Read/write Name of energy measuring de- ASCII hex.-coded, 15 characters vice + F68 Holding Holding Holding Holding Holding Holding Holding 80 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 81 Access Function Coding Number of data words for the measured values up to firmware 1.11 Holding 16-bit Read/write Voltage V1 Integer (0 - 2) (According to Phoenix Contact Holding 16-bit Read/write Voltage V2 EEM-350-D-MCB energy mea- Holding 16-bit Read/write Voltage V3...
  • Page 82 Access Function Coding Number of data words for the measured values with firmware 1.12 or later Holding 16-bit Read/write Voltage V1 Integer (0 - 2) (According to Phoenix Contact Holding 16-bit Read/write Voltage V2 EEM-EM357 energy measuring Holding 16-bit Read/write...
  • Page 83 16-bit Read/write RFID card reader Decimal, default: 0 Buzzer coil address Holding 16-bit Read/write RFID cards: number of data Decimal, default: 16 words Holding 16-bit Read/write RFID cards: Modbus address Decimal, default: 17 data 83 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 84 16 x 16-bit Read Current cellular network opera- ASCII Holding 3376 8 x 16-bit Read Energy of current charging pro- Integer [Wh] cess Holding 3386 16-bit Read/write Pulse length of RFID buzzer Integer [ms] 84 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 85 Value Access Function Coding Holding 3387 6 x 16-bit Read/write Freemode RFID UID ASCII Holding 3396 3 x 16-bit Read Active cellular standard ASCII Holding 3403 64 x 16-bit Read/write OCPP path (extended) ASCII 85 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 86: Register Assignment, Coil Type

    (permanent) COIL 1-bit Read/write Buzzer on RFID card reader 1-bit activated (single-pulse) COIL 1-bit Read/write Byte sequence for communi- 1-bit, 0 = Little Endian cation with RFID card reader 1 = Big Endian (Modbus/RTU) 86 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 87 1: OCPP via Ethernet (…-XP ver- sion only) COIL 1-bit Read/write Unlocking (regardless of the 1-bit position of DIP 9) 1: charging point is unlocked COIL 1-bit Read Connection status slave 1 1-bit 1: slave 1 connected to master 87 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 88 1: charging connector locked COIL 1-bit Read/write Activation of “Freemode after 1-bit Power Loss” 1: “FreemodeAfterPowerLoss” ac- tivated COIL 1-bit Read Status “Suspended EVSE” 1-bit: (charging process paused) 1: OCPP status “Suspended- EVSE” active 88 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 89 COIL 1-bit Read/write Modbus register type of the 1-bit energy meter 0: Holding (0x03) 1: Input (0x04) COIL 1-bit Read/write Modbus stop bits of the energy 1-bit meter 0: 1 bit 1: 2 bits 89 / 100 108191_en_04 PHOENIX CONTACT...

  • Page 90: Function Assignment Of Input And Output Registers

    13 A, 20 A or 32 A charging connector detected Charging connector with low current carrying capacity rejected Charging controller switches charging contactor ON Status D ventilation on Locking active (default for output LR) Output 1 register Output 2 register 90 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 91: Function Assignment Of Digital Inputs

    Charging current at 70 A Enable charging process by pulsed signal Locking (pulsed signal) (default for input ML) Reserved for future function Charging current at maximum permissible value Pause charging process (OCPP: Suspend EVSE) Generate error state 91 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 92 EV Charge Control 92 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 93: A Appendix For Document Lists

    Section 6 Figure 6-1: Control Pilot signal ................36 Figure 6-2: Typical curve of the Control Pilot signal ..........37 Figure 6-3: Activation mode .................. 40 Figure 6-4: Proximity signal (Proximity Plug) ............41 93 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 94 “Energy Meter” tab for EEM-EM357 ............ 62 Figure 8-7: “Card Reader” tab for QUIO QDE 950-4 RFID reader ......65 Figure 8-8: “Remote Control” tab (EV-CC-…-3G / …-3G-XP) ....... 67 Figure 8-9: “Remote Control” tab (EV-CC-…-ETH / …-ETH-XP) ......67 94 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 95: A 2 List Of Tables

    Coding of the permissible current for the resistance value in accordance with IEC 61851-1.............. 41 Section 7 Table 7-1: Interfaces..................... 42 Table 7-2: Overview of supported OCPP operations ..........42 Table 7-3: ConfigurationKeys of the charging controller ........44 95 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 96 Register assignment, Discrete type ............. 74 Table 9-4: Register assignment, Holding type ............74 Table 9-5: Register assignment, COIL type ............86 Table 9-6: Function assignment of digital outputs..........90 Table 9-7: Function assignment of digital inputs........... 91 96 / 100 PHOENIX CONTACT 108191_en_04...

  • Page 97: Index

    Holding (register assignment) ........74 Indicators ..............15 Input (register assignment) ......... 71 Load management ............68 Modbus register types..........70 Network (tab) – cellular ..........54 Network (tab) – Ethernet ..........52 OCPP backend connection ......... 42 97 / 100 108191_en_04 PHOENIX CONTACT...
  • Page 98 EV Charge Control 98 / 100 PHOENIX CONTACT 108191_en_04...
  • Page 99 The receipt of technical documentation (in particular user documentation) does not constitute any further duty on the part of Phoenix Contact to furnish information on modifications to products and/or technical documentation. You are responsible to verify the suitability and intended use of the products in your specific application, in particular with regard to observing the applicable standards and regulations.
  • Page 100 Should you have any suggestions or recommendations for improvement of the contents and layout of our manuals, please send your comments to: tecdoc@phoenixcontact.com PHOENIX CONTACT GmbH & Co. KG • Flachsmarktstraße 8 • 32825 Blomberg • Germany 100 / 100 phoenixcontact.com...
  • Page 102 PHOENIX CONTACT GmbH & Co. KG Flachsmarktstraße 8 32825 Blomberg, Germany Phone: +49 5235 3-00 Fax: +49 5235 3-41200 E-mail: info@phoenixcontact.com phoenixcontact.com...

This manual is also suitable for:

Ev-cc-ac1-m3-cbc-rcm-eth-3gEv-cc-ac1-m3-rcm-eth-xpEv-cc-ac1-m3-rcm-eth-3g-xp

Table of Contents