OCPP 1.6 JSON guide

KarolisS — Thu, 04 Jun 2026 08:17:16 GMT

KarolisS set 5498 as the approved revision for "OCPP 1.6 JSON guide"

EMS configuration EVC2

KarolisS — Wed, 03 Jun 2026 08:51:53 GMT

KarolisS set 5497 as the approved revision for "EMS configuration EVC2"

EMS configuration EVC2

KarolisS — Wed, 03 Jun 2026 08:51:49 GMT

Created page with "== EMS CONFIGURATION == This section provides an overview of the Modbus RTU and TCP interface supported by EVC2. The document provides description of the available Modbus registers for the external control and communication with the charge. This functionality is only available when the charger is configured as a secondary (server) device and waits for acceptable commands from the primary (client) device. Interface allows EVC2 to be controlled via another device over th..."

New page

== EMS CONFIGURATION ==
This section provides an overview of the Modbus RTU and TCP interface supported by EVC2.

The document provides description of the available Modbus registers for the external control and communication with the charge. This functionality is only available when the charger is configured as a secondary (server) device and waits for acceptable commands from the primary (client) device.

Interface allows EVC2 to be controlled via another device over the registers. For example a server might be calculating current electricity price and in so can be limiting or increasing the charging rate of the EVC2 dynamically by modifying its settings on the fly via the provided commands.

=== Device preparation for Modbus RTU ===
EVC2 must be configured as a secondary device via our mobile application and device must have RS485 wired connection with the primary device..

# Open "User menu"
# Open "Installer menu"
# Open "Load Management"
# Select "Modbus RTU"
# Select "Secondary"
# Enable secondary device

Check if the address is expected in your system

[[File:EMS Modbus RTU secondary device.png|frameless|985x985px]]

Connection terminals are marked as '''LM'''

[[File:EVC2_external_controller.png|frameless|460x460px]]

=== Device preparation for Modbus TCP ===
EVC2 must be configured as a secondary device via our mobile application and device must have a connection to the same network as its management system

# Open "User menu"
# Open "Installer menu"
# Open "Load Management"
# Select "Modbus TCP"
# Select "Secondary"
# Enable secondary device

[[File:EMS Modbus TCP secondary device.png|frameless|1074x1074px]]

=== Modbus register map ===
{| class="wikitable"
!Address
!Type
!Name
!Format
!Values
!Default value
!Unit
!Comment
|-
|0
|R
|'''Voltage L1'''
|int16
| -32768 - 32767
| -
|V
|Input voltage on L1
|-
|1
|R
|'''Voltage L2'''
|int16
| -32768 - 32767
| -
|V
|Input voltage on L2
|-
|2
|R
|'''Voltage L3'''
|int16
| -32768 - 32767
| -
|V
|Input voltage on L2
|-
|3
|R
|'''Current L1'''
|int16
| -32768 - 32767
| -
|*10 A
|Current on L1
|-
|4
|R
|'''Current L2'''
|int16
| -32768 - 32767
| -
|*10 A
|Current on L2
|-
|5
|R
|'''Current L3'''
|int16
| -32768 - 32767
| -
|*10 A
|Current on L3
|-
|6
|R
|'''EVSE status'''
|uint16
|0-9
| -
| -
|Evse state in DLM (see "a" below)
|-
|7
|R
|'''EVSE status time 1st word'''
|uint16
| -32768 - 32767
| -
|s
|Evse status time, first word (uint16_t)
|-
|8
|R
|'''EVSE status time 2nd word'''
|uint16
| -32768 - 32767
| -
|s
|Evse status time, second word (uint16_t) >> 16
|-
|9
|R
|'''EVSE ID'''
|uint16
|21571
|21571("TC")
| -
|Teltocharge ID
|-
|10
|R
|'''EVSE 3ph config'''
|uint16
|0-1
| -
| -
|0 - not possible, 1 - possible
|-
|11
|R
|'''Phase change'''
|uint16
|0-1
| -
| -
|0 - not possible, 1 - possible
|-
|12
|R
|'''Amp limit'''
|uint16
|0,6-32
| -
|A
|Max amps the EVSE can supply
|-
|13
|R
|'''Phase connected'''
|uint16
|0-6
| -
| -
|0 - L1,
1 - L2, 2 - L3, 3 - L1/L2, 4 - L1/L3, 5 - L2/L3, 6 - 3ph 7 - none
|-
|14
|R/W
|'''Phase to use'''
|uint16
|0-7
| -
| -
|Sets which phase to use for slave,
0 - L1, 1 - L2, 2 - L3, 3 - L1/L2, 4 - L1/L3, 5 - L2/L3, 6 - 3ph, 7 - none
|-
|15
|R/W
|'''Amps to use'''
|uint16
|0, 6-32
| -
|A
|Sets max allowed from primary to secondary
|-
|16
|R/W
|'''Request stop charging'''
|uint16
|0-2
| -
| -
|Do not intervene with current session (0), stop session (1) or start session if stopped (2).
|-
|17
|R/W
|'''Request authorize'''
|uint16
|0-1
| -
| -
|Request authorization
|-
|18
|R/W
|'''Lock/unlock socket'''
|uint16
|0-2
|0
| -
|0 - auto lock,
1 - always lock, 2 - force unlock in auto mode (resets on state A)
|-
|19
|R/W
|'''Communication timeout'''
|uint16
|0-600
|30
|s
|Defines communication watchdog (0 - no req for periodic comm)
|-
|20
|R/W
|'''Failsafe current'''
|uint16
|0, 6-32
|6
|A
|Defines max allowed current on comm timeout
|-
|21
|R/W
|'''Request reboot'''
|uint16
|0-1
|0
| -
|Request reboot
|-
|22
|R
|'''Require authorization'''
|uint16
|0-1
| -
| -
|Defines requirement for authorization
|-
|23
|R
|'''Product code'''
|uint16
|0-9999
|1234
| -
|Product code EVCxxxx
|-
|24
|R
|'''Serial number 1st word'''
|
|0-65535
|123456789
|s
|Serial number, first word (uint16_t)
|-
|25
|R
|'''Serial number 2nd word'''
|
|0-65535
|
|s
|Serial number, second word (uint16_t) >> 16
|-
|26
|R
|'''FW version'''
|uint16
|11200-29999
| -
| -
|FW version
|-
|27
|R
|'''Charge point state'''
|uint16
|0-9
| -
| -
|Defines charge point state (see "b" below)
|-
|28
|R
|'''Max power from grid'''
|uint16
|6-1000
|30
| -
|Defines max power from grid
|-
|29
|R
|'''User settable max current'''
|uint16
|6-32
|10
| -
|Defines max settable current by user
|-
|30
|R
|'''Lock status'''
|uint16
|0-1
| -
| -
|0 - unlocked,
1 - locked
|-
|31
|R
|'''Internal temperature'''
|int16
| -400 - +1250
| -
|*10°C
|Device's temperature
|-
|32
|R
|'''OCPP connected'''
|uint16
|0-1
| -
| -
|0 - off,
1 - on
|-
|33
|R
|'''IEC state'''
|uint16
|0-8
| -
| -
|IEC state (see "c" below)
|-
|34
|R
|'''Warning code'''
|uint16
|0-65535
| -
| -
|Warning code with bit positions (see "d" below)
|-
|35
|R
|'''Error code'''
|uint16
|0-65535
| -
| -
|Error code with bit positions (see "e" below)
|-
|36
|R
|'''Current limit cause'''
|uint16
|0-8
| -
| -
|Cause of current limit (see "f" below)
|-
|37
|R
|'''Max supported power'''
|uint16
|0-2
| -
| -
|0 - 7.4 kW (1ph 32 A),
1 - 11 kW (3ph 16 A), 2 - 22 kW (3ph 32 A)
|-
|38
|R
|'''Instant active power'''
|uint16
|0-65535
| -
|W
|Instant power
|-
|39
|R
|'''Energy delivered'''
|uint16
|0-65535
| -
|*100kWh
|Total supplied active power per session
|-
|40
|R
|'''Session duration'''
|uint16
|0-65535
| -
|s
|Session duration
|-
|41
|R
|'''Total kWh supplied 1st word'''
|uint16
|0-65535
| -
|*100kWh
|Total supplied active power in a lifetime (uint16_t)
|-
|42
|R
|'''Total kWh supplied 2nd word'''
|uint16
|0-65535
| -
|*100kWh
|Total supplied active power in a lifetime (uint16_t) >> 16
|-
|43
|R
|'''Total kWh supplied 3rd word'''
|uint16
|0-65535
| -
|*100kWh
|Total supplied active power in a lifetime (uint16_t) >> 32
|-
|44
|R
|'''Total kWh supplied 4th word'''
|uint16
|0-65535
| -
|*100kWh
|Total supplied active power in a lifetime (uint16_t) >> 48
|}
{| class="wikitable"
|+Explanation
|'''a'''
|0 - C: charging;
1 - B1: EV connected, authorization granted, waiting for EV to start charging;

2 - B2: EV connected, authorization granted, was charging, not enough power;

3 - B3: EV connected, authorization granted, wasn't charging, not enough power;

4 - D1: EV connected, charging stopped by EV;

5 - D2: EV connected, no authorization;

6 - D3: EV connected, simplified CP or D state charging not allowed;

7 - A: EV not connected; 8 - F: Error state; 9 - E: Unknown state.
|-
|'''b'''
|0 – no EV connected;
1 – vehicle connected, awaiting permission to charge;

2 – charging authorized;

3 – charging in progress;

4 – charging paused;

5 – charge successful (EV connected);

6 – charge stopped by the user;

7 – charging error;

8 – charging station reserved, no EV connected;

9 – other.
|-
|'''c'''
|0 – A: no vehicle connected;
1 – B1: EV connected, pending authorization, no PWM;

2 – B2: EV connected, EVSE ready for charging, PWM active (state B2);

3 – C1: ready to charge or stop charge request by EVSE, S2 closed, no PWM;

4 – C2: charging EV;

5 – D1: ready to charge or stop charge request by EVSE, S2 closed, ventilation required, no PWM;

6 – D2: charging EV, ventilation required;

7 – E: control pilot (CP) fault;

8 – F: EVSE fault.
|-
|'''d'''
|0 – midplate is open (HW-dependent);
1 – temperature warning;

2 – current draw is higher than allowed;

3 – charging requires ventilation;

4 – real time clock lost;

5 – simplified cp sequence denied;

6 – simplified cp sequence detected;

7 – charging without ventilation denied;

8 – PEN CT clamp not calibrated (HW-dependent);

9 – NFC module fault;

10 – PEN fault was detected (HW-dependent).
|-
|'''e'''
|0 – input voltage not in range;
1 – output voltage not in range;

2 – current leakage sensor test failed;

3 – EV diode is failed, or fault in CP line;

4 – overcurrent error;

5 – temperature error;

6 – PEN fault active (UK HW only);

7 – proximity pilot (cable, socket) error;

8 – current leakage detected;

9 – socket lock error;

10 – internal error.
|-
|'''f'''
|0 – Hardware limits;
1 – Max power from grid;

2 – User setting (static load balance);

3 – Charging cable;

4 – Simple CP sequence;

5 – EVSE default settings;

6 – Load balance;

7 – Temperature.
|}
Systems that support us
{| class="wikitable"
|+
!Product
!Link
|-
|Eniris
|https://docs.eniris.io/en/Controller/Devices/EV-charging-station/Teltonika#teltonika-ev-charging-stations
|}