Teltonika Energy Wiki - User contributions [en]

Dynamic Load Balancing EVC2

2026-05-27T06:42:48Z

Dominykas.Z:

= DYNAMIC LOAD BALANCING =
EVC2 can communicate with a dedicated smart energy meter and adjust its power consumption based on the meter's readings. This functionality helps protect the home's electrical grid from overload during peak hours and optimizes energy usage to match the user's habits. The smart energy meter should always be installed in the main electrical cabinet, as shown below.
[[File:Dynamic_Load_Balancing_Conection_Schematic.png|alt=|center|frameless|395x395px]]

=== DLB support ===
We can achieve DLB support by pairing the charger with one of the following:

* [[Dynamic Load Balancing EVC2#MODBUS RTU METERS|Modbus RTU meters]]
* [[Dynamic Load Balancing EVC2#MODBUS TCP/IP METERS|Modbus TCP/IP meters]]
* [[Dynamic Load Balancing EVC2#CT CLAMPS|CT clamps]]
* [[Dynamic Load Balancing EVC2#EXTERNAL CONTROL|External control (EMS)]]
* [[Dynamic Load Balancing EVC2#SMARTSTUFF P1 CONVERTER|Smartstuff P1 converter]]

DLB can then be configured using the app following [[Dynamic Load Balancing EVC2#TELTONIKA ENERGY APP SETTINGS|these instructions]].

== PHASE BALANCE EXPLANATION ==
TeltoCharge has advanced functionality to detect a car's charging type and, if required, switch phases during mid-charge.

The same phase switch process will happen if the smart meter detects, that less than 6A is available for one of the phases.

=== Adaptation to the car's charging capability ===
If the charger is set for 3phase charging, but the plugged car can only draw current from one phase, TeltoCharge will switch to one-phase mode after a short period of time

[[File:CarExample.png|frameless|493x493px]]

=== Phase balance during lack of power ===
When the smart meter detects that there is less than 6A for each phase, the charging station will switch from 3phase mode to 1phase mode until 6ampers are available for all phases

[[File:PhaseSwitch.png|frameless|600x600px]]

== MODBUS RTU METERS ==
To access energy measurement through Modbus RTU, connect both charger and the meter together using RS485 terminal for meter.

[[File:DLB meter.png|frameless|808x808px]]

=== RS485 communication ===
For RS485 communication it is recommended to use a twister pair communication cable. Check example below.

[[File:TeltoCharge_DLB_CableExample.png|frameless]]

'''Note:''' ''Communication cable should be integrated with power cable.''

In order to strive for wider applicability and compatibility, we constantly test and add new supported devices into list. All of the supported energy meters and schematics how to connect them are provided below.

In order to make '''Dynamic load balancing''' and '''Solar''' functionality work, please always check:

* if the '''wiring''' your Smart energy meter to EVC2 is right.
* if the '''installer menu configuration''' in mobile application according to your smart energy meter is right.

=== Supported Modbus RTU models ===
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 60%;"
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Energy meter manufacturer
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Technical information
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Configuration in mobile application
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Wiring scheme
|-
| style="padding: 2px;" |Carlo Gavazzi series 1-3
| style="padding: 2px;" |[[EM and ET models]]
| style="padding: 2px;" |[[Carlo Gavazzi settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/view/EM_and_ET_models#Carlo_Gavazzi_meters_wiring: METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Siemens PACxxxx
| style="padding: 2px;" |[[PAC models]]
| style="padding: 2px;" |[[Siemens settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/0/0e/Siemens_PAC_Sentron.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |ABB A4x ; B2x
| style="padding: 2px;" |[[A and B models]]
| style="padding: 2px;" |[[ABB settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/e/e8/ABB_serie_A%26B_part_1.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Eastron SDMxx
| style="padding: 2px;" |[[SDM models]]
| style="padding: 2px;" |[[Eastron settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/5/53/Eastron_sdm72.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Inepro PRO380
| style="padding: 2px;" |[[PRO model]]
| style="padding: 2px;" |[[Inepro settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/3/3b/Inepro_pro380.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Chint
| style="padding: 2px;" |[[Chint models]]
| style="padding: 2px;" |[[Chint settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/3/3b/Inepro_pro380.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Entes
| style="padding: 2px;" |[[ES models]]
| style="padding: 2px;" |[[Entes settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/2/21/Entes.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Acrel
| style="padding: 2px;" |[[Acrel models]]
| style="padding: 2px;" |[[Acrel settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/d/d1/Acrel_meter.png METER -> TELTOCHARGE]
|-
| colspan="4" style="padding: 8px;" |''More coming soon...''
|}

== LOAD BALANCING CONFIGURATION ==
To ensure everything works correctly, please apply the following setup :

# Open user menu
# Open "'''''Installer Menu'''''"
# Open "'''''Dynamic Load Balancing'''''" menu
# Enable "'''''Load Balancing'''''"
# If smart meter is connected with RS485 wires, press "'''''Search For Device'''''"
# *'''ONLY If TeltoCharge is unable''' to identify energy meter - use "'''''Manual Setup'''''"

[[File:DLB_settings.png|frameless|989x989px]]

== MODBUS TCP/IP METERS ==
To access energy measurement through Modbus TCP/IP, connect both the meter and your charger to your network. Charger has two options: either WiFi or ethernet cable.

=== Connecting Shelly 3PRO ===
Download the '''Shelly smart control''' app and setup the device to connect to your network. After its configured, find the IP address given to the meter.

[[File:Shelly wiki.png|frameless|935x935px]]

'''''Note:''' Copy the IP as it will be used in EV charging app to connect the meter to the station''

=== Connecting HomeWizard P1 ===
Follow this full guide for easy installation: [[Media:HomeWizard P1 guide.pdf|HomeWizard P1.pdf]]

Or in short - install the HomeWizard meter to the P1 port of your utility meter.

[[File:Wizard p1 utility meter.png|frameless|284x284px]]

Download the '''HomeWizard''' app and follow the setup for the meter to connect to your network. After its configured, find the IP address given to the meter.
[[File:Homewizard wiki 1.png|frameless]] [[File:Homewizard wiki 3.png|frameless|592x592px]]

'''''Note:''' Copy the IP as it will be used in EV charging app to connect the meter to the station''

=== Load balancing using Network meter ===
A given example below is for Shelly 3Pro smart meter integration, but is identical when using HomeWizard P1.

To connect the meter to the station, go to '''load balancing''' section in the app, choose '''network meter''' and the model you're using.

[[File:Shelly DLB 1.png|frameless|938x938px]]

After that select '''IP address''' as was shown in the Shelly app. Set '''max grid load''' to match the value allowed by the grid. If everything is done right - the status should indicate that the network meter has successfully connected.

[[File:Shelly DLB 2.png|937x937px]]

=== Supported Modbus TCP/IP models ===
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 60%;"
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Energy meter manufacturer
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Technical information
|-
| style="padding: 2px;" |Shelly
| style="padding: 2px;" |3em models
|-
| style="padding: 2px;" |Homewizard
| style="padding: 2px;" |P1 models
|-
|Eastron
|SEM
|}

== CT CLAMPS ==
It is possible to measure power readings by connecting CT clamps to each phase. Insert each CT clamp to its dedicated terminal (blue wire to B, red wire to R slot of the terminal).

<u>Make sure that clamp direction is pointing towards source (away from the charger).</u>

[[File:CT clamps EVC2.png|frameless|529x529px]]

<big>'''Mandatory CT clamp specifications:'''
</big>
* Rated input/current - depends on your total power input, but we would recommend not to exceed 150A.
* Turn ratio - 3000:1.
* Burden resistor - CT-Clamp '''must not have integrated burden resistor'''.

Choosing to use CT clamp is done via the app in the '''Load balancing''' section. Set '''Max grid load''' to max available amps in your grid (for example: value of your breaker).

Press calibrate to set the starting point.

Note: Before calibration, CT clamp has to be connected to the port, but not clamped around the cable.

[[File:Load balancing ct clamps.png|frameless|804x804px]]

== EXTERNAL CONTROL ==
This section provides an overview of the Modbus RTU interface supported by TeltoCharge electric vehicle supply equipment (EVSE). The document provides description of the available Modbus registers for the external control and communication with the charger based on a wired RS485 connection. 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. The secondary device can operate on two modes:

# It can be configured to use a watchdog for communication and if no valid communication is present after a configurable time interval, the charging (if ongoing) will stop and EVSE will not perform any charging until valid communication is reestablished;
# the EVSE does not use a watchdog and continuous communication is not needed. As it is possible to change the EVSE settings by using the TeltoCharge mobile application, it is recommended for the primary device to read, compare, and change settings as needed based on user preferences and real-time requirements, ensuring a seamless and secure charging experience for electric vehicle owners. Continuous monitoring and adjustment of EVSE settings enable the primary device to stay synchronized with user inputs, maintain optimal charging conditions, and promptly respond to any changes initiated through the TeltoCharge mobile application, thereby enhancing overall efficiency and user satisfaction.

=== Device preparation ===
TeltoCharge must be configured as a secondary device via a TeltoCharge mobile application and device must have RS485 wired connection with the primary device..

# Open "User menu"
# Open "Installer menu"
# Open "Load Management"
# Select "Secondary"
# Enable secondary device
# Check if the address is expected in your system

[[File:External.png|frameless|900x900px]] [[File:EVC2_external_controller.png|frameless|460x460px]]

=== 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.
|}

== SMARTSTUFF P1 CONVERTER ==
The Modbus P1 Dongle is a device that enables communication between your EVC charging station and a smart meter using the Modbus RS-485 protocol. This setup is essential for accurately monitoring and controlling the energy usage during EV charging sessions.

* Accurate energy monitoring: Ensures that energy usage data is correctly captured and transmitted.
* Optimized charging: By leveraging the data from the smart meter, the charging station can optimize the charging process, potentially reducing costs and improving efficiency.

''Note:'' Before proceeding with the installation, please ensure that your smart meter is compatible with the Modbus P1 Dongle.

=== Smart Meter Connection ===
The dongle is connected to the P1 port of the smart meter via a provided P1 cable. This connection allows the dongle to read energy consumption data directly from the smart meter.

=== RS-485 Connection ===
The dongle features RS-485 terminals which are critical for establishing communication with the EVC2 system. These terminals are usually labeled as Ground (GND), A+ (positive differential signal), and B- (negative differential signal).

* To connect the dongle to the EVC2, you'll need to use an appropriate RS-485 cable.
* Connect the 'A+' terminal of your cable to the 'A+' port on the EVC2 device.
* Connect the 'B-' terminal of your cable to the 'B-' port on the EVC2 device.

''Note :'' In case of communication errors, swapping the 'A+' and 'B-' connections might resolve the issue

. [[File:EVC2 p1 LB.png|frameless|801x801px]]<blockquote>https://docs.smart-stuff.nl/p1-modbus-dongle/quick-start/installation</blockquote>

=== General meter settings ===
According to your smart meter documentation, please enter all the settings into the Energy app as shown.

# '''Energy meter type''': You need to select the type of smart meter (1-phase/3-phase). Please note that you can use a 1-phase charger even if the meter is 3-phase.
# '''RS-485 baud rate''': To ensure optimal performance and compatibility with the P1 smart dongle, the RS-485 baud rate must be configured to 38400.
# '''RS-485 parity/stop bit''': Similarly, this information can also be found in the meter settings. If the client is unable to find it, it is advisable to check the smart meter manual.

{|
|[[File:Smart_stuff.png|left|frameless]]
|[[File:Live_data.png|left|frameless|457x457px]]
|}
{|
|'''''Note:''''' ''Set up the energy meter address''

''according to the smart stuff address.''
|
|
|
|
|
|
|
|
|
|
|
|
|'''''Note:''''' ''After successfully completing these steps,''

please check the diagnostic live data from the energy meter.
|}

== TELTONIKA ENERGY APP SETTINGS ==
To ensure everything works correctly, please apply the following setup :

# Open user menu
# Open "'''''Installer Menu'''''"
# Open "'''''Dynamic Load Balancing'''''" menu
# Enable "'''''Load Balancing'''''"
# If smart meter is connected with RS485 wires, press "'''''Search For Device'''''"
# *'''ONLY If TeltoCharge is unable''' to identify energy meter - use "'''''Manual Setup'''''"

[[File:DLB_settings.png|frameless|1062x1062px]]
__FORCETOC__

A and B models

2026-05-19T13:33:41Z

Dominykas.Z:

← [[Smart energy meters]]
==== ABB smart energy meters technical information ====
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 70%;"
|-
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Energy meter manufacturer
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Type
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Power supply (V)
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Supported model for DLB*
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Supported model for Solar*
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | MID certified
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | 1/3 phase
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Connection
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Direct Connection Rating Value
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" | Datasheet
|-
| style="padding: 2px;" rowspan="4" | ABB series A
| style="padding: 2px;" rowspan="1" | A41 <br>
| style="padding: 1px;" | 230 V
| style="padding: 2px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 1 phase
| style="padding: 2px;" | Direct
| style="padding: 2px;" | 80 Amps
| style="padding: 2px;" | [https://new.abb.com/products/2CMA170500R1000/a41-112-100 A41-112-100]
|-
| style="padding: 2px;" rowspan="1" | A42 <br>
| style="padding: 2px;" | 230 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 1 phase
| style="padding: 2px;" | Direct
| style="padding: 2px;" | NA
| style="padding: 1px;" | [https://new.abb.com/products/2CMA170510R1000/a42-112-100 A42-112-100]
|-
| style="padding: 2px;" rowspan="1" | A43 <br>
| style="padding: 1px;" | 400 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 3 phases
| style="padding: 2px;" | Direct
| style="padding: 2px;" | 80 Amps
| style="padding: 2px;" | [https://new.abb.com/products/2CMA100244R1000/a43-112-100 A43-112-100]
|-
| style="padding: 2px;" rowspan="1" | A44 <br>
| style="padding: 1px;" | 400 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 3 phases
| style="padding: 2px;" | Direct
| style="padding: 2px;" | NA
| style="padding: 2px;" | [https://new.abb.com/products/2CMA100248R1000/a44-112-100 A44-112-100]
|-
| style="padding: 2px;" rowspan="3" | ABB series B <br>
| style="padding: 2px;" rowspan="1" | B21 <br>
| style="padding: 1px;" | 230 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 1 phase
| style="padding: 2px;" | Direct
| style="padding: 2px;" | 65 Amps
| style="padding: 2px;" | [https://new.abb.com/products/2CMA100150R1000/b21-112-100 B21-112-100]
|-
| style="padding: 2px;" rowspan="1" | B23 <br>
| style="padding: 1px;" | 400 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 3 phases
| style="padding: 2px;" | Direct
| style="padding: 2px;" | 65 Amps
| style="padding: 1px;" | [https://new.abb.com/products/2CMA100164R1000/b23-112-100 B23-112-100]
|-
| style="padding: 2px;" rowspan="1" | B24 <br>
| style="padding: 1px;" | 400 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 3 phases
| style="padding: 2px;" | Direct
| style="padding: 2px;" | NA
| style="padding: 2px;" | [https://new.abb.com/products/2CMA100178R1000/b24-112-100 B24-112-100]
|-
| style="padding: 2px;" rowspan="3" | ABB series EV <br>
| style="padding: 2px;" rowspan="1" | EV3 <br>
| style="padding: 1px;" | 400 V
| style="padding: 1px;" | Yes
| style="padding: 1px;" | No
| style="padding: 2px;" | Yes
| style="padding: 2px;" | 3 phases
| style="padding: 2px;" | Direct
| style="padding: 2px;" | 65 Amps
| style="padding: 2px;" | [https://new.abb.com/products/2CMA290881R1000/ev3-012-100 EV3 012-100]
|}

==== ABB meters wiring: ====
[[File:ABB serie A&B part 1.png|alt=|none|frame]]

====Powering the energy meter ====
To correctly connect the smart energy meter to a power source, it is recommended to use the manufacturer's installation manuals

Firmware

2026-05-19T08:15:38Z

Dominykas.Z:

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">Latest firmware version download</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">

===<b><span class="plainlinks">[https://wiki.teltonika-energy.com/images/7/7f/TeltoCharge-v1.16.2-bundle.zip EVC1xx V1.16.2]</span></b> | 2026.05.01===
* <b>New features and settings</b>
** Added new solar charging modes for Dynamic Load Management, including Solar Only, ECO, and Hybrid modes.
** Added Dynamic Load Management support for Delta grid installations.
** Expanded Modbus meter support with additional [https://wiki.teltonika-energy.com/view/SDM%20models Eastron] and [https://wiki.teltonika-energy.com/view/A%20and%20B%20models ABB] meter models.
** Added installer setting for IT grid voltage sampling.
* <b>Bug fixes and improvements</b>
** Improved charging session recovery, troubleshooting logs.
** Improved solar charging and charging session reporting, including ECO mode synchronization and charging session energy graph accuracy.
** Improved Bluetooth and OCPP communication stability, including charging profile handling and tamper event reporting.
** Improved mobile notification handling.
** Improved firmware update stability when updating from older firmware versions.
** Improved Modbus map handling for new meter and diagnostic parameters.
** Improved troubleshooting logs for solar charging modes.

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">Previous firmware versions download</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
Here you can see all the previous firmware versions:
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 60%;"
|+
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Previous FW versions
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Legacy firmware version*
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Firmware version
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Release date
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Whats new?
|-
|-
|1.15.4
| colspan="2" |'''[https://wiki.teltonika-energy.com/images/7/7f/TeltoCharge-v1.16.2-bundle.zip TeltoCharge-v1.15.4]'''
|January 8, 2026
|[[Release note v1.15.2|Release note]]
|-
|1.15.2
| colspan="2" |'''[https://wiki.teltonika-energy.com/images/2/20/TeltoCharge-v1.15.2-bundle.zip TeltoCharge-v1.15.2]'''
|November 24, 2025
|[[Release note v1.15.2|Release note]]
|-
|1.14.7
| colspan="2" |'''[https://wiki.teltonika-energy.com/images/9/99/TeltoCharge-v1.14.7-bundle.zip TeltoCharge-v1.14.7]'''
|May 19, 2025
|[https://wiki.teltonika-energy.com/images/4/40/Release_note_FW_1.14.pdf Release note]
|-
|1.13.9
| colspan="2" | '''[https://wiki.teltonika-energy.com/images/a/ae/TeltoCharge-v1.13.9-bundle.zip TeltoCharge-v1.13.9]'''
|September 10, 2024
|[https://wiki.teltonika-energy.com/images/5/50/Release_note_FW_1.13.pdf Release note]
|-
|1.12.8
| colspan="2" | '''[https://wiki.teltonika-energy.com/images/7/77/TeltoCharge-v1.12.8-bundle.zip TeltoCharge-v1.12.8]'''
|August 05, 2024
|[https://wiki.teltonika-energy.com/images/9/91/Release_note_FW_1.12.pdf Release note]
|-
|1.11.6
| colspan="2" | '''[https://wiki.teltonika-energy.com/images/f/f1/TeltoCharge-v1.11.6-bundle.zip TeltoCharge-v1.11.6]'''
|February 01, 2024
|[https://wiki.teltonika-energy.com/images/1/13/Release_note_FW_1.11.6.pdf Release note]
|-
|1.10.9
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/2/2a/TeltoCharge-v1.10.9-bundle.zip TeltoCharge-v1.10.9]'''
|October 23, 2023
|'''Android 14 optimization'''
|-
|1.10.7
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/2/29/TeltoCharge-v1.10.7-bundle.zip TeltoCharge-v1.10.7]'''
|October 23, 2023
|[https://wiki.teltonika-energy.com/images/e/ed/Release_note_FW_1.10.7.pdf Release note]
|-
|1.9.6
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/7/7b/TeltoCharge-v1.9.6-bundle.zip TeltoCharge-v1.9.6]'''
|September 18, 2023
|[https://wiki.teltonika-energy.com/images/9/90/Release_note_FW_1.9.5.pdf Release note]
|-
|1.9.5
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/9/91/TeltoCharge-v1.9.5-bundle.zip TeltoCharge-v1.9.5]'''
|August 31, 2023
|[https://wiki.teltonika-energy.com/images/9/90/Release_note_FW_1.9.5.pdf Release note]
|-
|1.8
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/4/43/TeltoCharge-v1.8.11-bundle.zip TeltoCharge-v1.8.11]'''
|July 3, 2023
|[https://wiki.teltonika-energy.com/images/e/ea/Release_note_FW_1.8.10.pdf Release note]
|-
|1.7
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/a/ad/TeltoCharge-v1.7.9-bundle.zip TeltoCharge-v1.7]'''
|May 22, 2023
|[https://wiki.teltonika-energy.com/images/1/1f/Release_note_FW_1.7.9.pdf Release note]
|-
|1.6.0
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/b/ba/TeltoCharge-v1.6.7-bundle.zip TeltoCharge-v1.6]'''
|Mar 1, 2023
|[https://wiki.teltonika-energy.com/images/4/4d/FW_1.6.pdf Release note]
|-

|1.5
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/d/dd/TeltoCharge-v1.5.8-bundle.zip TeltoCharge-v1.5]'''
|Dec 22, 2022
|[https://wiki.teltonika-energy.com/images/3/3d/Release_note_v1.5.pdf Release note]
|-
|1.4
|'''TeltoCharge-v1.4.3L'''
|'''TeltoCharge-v1.4.2'''

|Oct 7, 2022
|[https://wiki.teltonika-energy.com/images/b/b6/Release_note_v1.4.3L.pdf Release note]
|-
|1.3
|'''TeltoCharge-v1.3.12L'''
|'''TeltoCharge-v1.3.12'''
|Sep 28, 2022
|[https://wiki.teltonika-energy.com/images/a/a9/Release_note_v1.3.11L.pdf Release note]
|-
|1.2
|colspan="2" |'''TeltoCharge-v1.2.10'''
|Aug 8, 2022
|[https://wiki.teltonika-energy.com/images/0/02/Release_note_v1.2.10.pdf Release note]
|-
|1.1
|colspan="2" |'''TeltoCharge-v1.1.12'''
|Jun 6, 2022
|[https://wiki.teltonika-energy.com/images/2/24/Release_note_v1.1.12.pdf Release note]
|-
|1.0
|colspan="2" |'''TeltoCharge-v1.0.7'''
|Apr 25, 2022
|
|-
|Other
|colspan="2" |'''TeltoCharge-v1.0.4'''
|Apr 22, 2022
|
|}
'''Legacy firmware version* -''' TeltoCharge fw version which was used for chargers before mass production (these chargers are using same hardware, it's only related to separation). These type of chargers can only be updated to legacy FW version. '''From 1.5 version it is fixed and you won't need to keep this in mind.

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">How to check your firmware version?</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
<br>
1. Go to Teltonika Energy app settings, scroll down and press '''Device info'''; <br>

2. Press '''Check for updates'''; <br>

3. At the top, current firmware version can be found. <br>
<br>
[[File:TeltoCharge FirmwareVersionCheck1.png|frameless|588x588px]] [[File:TeltoCharge FirmwareVersionCheck.png|frameless|588x588px]]

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">How to update firmware automatically?</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
The product utilizes FOTA update services (HTTP/HTTPS client).<br>

1. To update firmware, click on the main window bar '''Click to update''' option; <br>

2. You will be automatically transfered to '''Updates''' window . <br>

3. Choose to '''Update Firmware''' from firmware available on server. <br>

4. Do not close Teltonika Energy app and stay in bluetooth range while update ends. <br>
<br>

[[File:Fota 1.png|frameless|588x588px]] [[File:Fota 2.png|frameless|588x588px]]

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">How to update firmware manually?</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
1. To update firmware manually, first of all, download firmware file from this page to your mobile phone which is paired with your TeltoCharge; <br>

2. Go to Teltonika Energy app settings, scroll down and press device info, then press Check for updates; <br>

3. Browse file and select latest firmware version which was downloaded; <br>

4. Press Upload firmware; <br>

5. Do not close Teltonika Energy app and stay in bluetooth range while update ends; <br>
<br>

[[File:Updates2.png|frameless|588x588px]] [[File:Updates3.png|frameless|588x588px]] [[File:Updates4.png|frameless|588x588px]]

[[Category: Resources]]

Firmware

2026-05-18T15:00:04Z

Dominykas.Z:

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">Latest firmware version download</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
Here you can find all information about '''firmware''' of TeltoCharge.
<br>
*1.6 version let you update your charger FW with only one file. You don't need to bother if it's legacy or secure FW installed in your charger:

===<b><span class="plainlinks">[https://wiki.teltonika-energy.com/images/7/7f/TeltoCharge-v1.16.2-bundle.zip EVC1xx V1.16.2]</span></b> | 2026.05.01===
* <b>New features and settings</b>
** Added new solar charging modes for Dynamic Load Management, including Solar Only, ECO, and Hybrid modes.
** Added Dynamic Load Management support for Delta grid installations.
** Expanded Modbus meter support with additional [https://wiki.teltonika-energy.com/view/SDM%20models Eastron] and [https://wiki.teltonika-energy.com/view/A%20and%20B%20models ABB] meter models.
** Added installer setting for IT grid voltage sampling.
* <b>Bug fixes and improvements</b>
** Improved charging session recovery, troubleshooting logs.
** Improved solar charging and charging session reporting, including ECO mode synchronization and charging session energy graph accuracy.
** Improved Bluetooth and OCPP communication stability, including charging profile handling and tamper event reporting.
** Improved mobile notification handling.
** Improved firmware update stability when updating from older firmware versions.
** Improved Modbus map handling for new meter and diagnostic parameters.
** Improved troubleshooting logs for solar charging modes.

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">Previous firmware versions download</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
Here you can see all the previous firmware versions:
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 60%;"
|+
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Previous FW versions
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Legacy firmware version*
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Firmware version
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Release date
|style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Whats new?
|-
|-
|1.15.4
| colspan="2" |'''[https://wiki.teltonika-energy.com/images/7/7f/TeltoCharge-v1.16.2-bundle.zip TeltoCharge-v1.15.4]'''
|January 8, 2026
|[[Release note v1.15.2|Release note]]
|-
|1.15.2
| colspan="2" |'''[https://wiki.teltonika-energy.com/images/2/20/TeltoCharge-v1.15.2-bundle.zip TeltoCharge-v1.15.2]'''
|November 24, 2025
|[[Release note v1.15.2|Release note]]
|-
|1.14.7
| colspan="2" |'''[https://wiki.teltonika-energy.com/images/9/99/TeltoCharge-v1.14.7-bundle.zip TeltoCharge-v1.14.7]'''
|May 19, 2025
|[https://wiki.teltonika-energy.com/images/4/40/Release_note_FW_1.14.pdf Release note]
|-
|1.13.9
| colspan="2" | '''[https://wiki.teltonika-energy.com/images/a/ae/TeltoCharge-v1.13.9-bundle.zip TeltoCharge-v1.13.9]'''
|September 10, 2024
|[https://wiki.teltonika-energy.com/images/5/50/Release_note_FW_1.13.pdf Release note]
|-
|1.12.8
| colspan="2" | '''[https://wiki.teltonika-energy.com/images/7/77/TeltoCharge-v1.12.8-bundle.zip TeltoCharge-v1.12.8]'''
|August 05, 2024
|[https://wiki.teltonika-energy.com/images/9/91/Release_note_FW_1.12.pdf Release note]
|-
|1.11.6
| colspan="2" | '''[https://wiki.teltonika-energy.com/images/f/f1/TeltoCharge-v1.11.6-bundle.zip TeltoCharge-v1.11.6]'''
|February 01, 2024
|[https://wiki.teltonika-energy.com/images/1/13/Release_note_FW_1.11.6.pdf Release note]
|-
|1.10.9
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/2/2a/TeltoCharge-v1.10.9-bundle.zip TeltoCharge-v1.10.9]'''
|October 23, 2023
|'''Android 14 optimization'''
|-
|1.10.7
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/2/29/TeltoCharge-v1.10.7-bundle.zip TeltoCharge-v1.10.7]'''
|October 23, 2023
|[https://wiki.teltonika-energy.com/images/e/ed/Release_note_FW_1.10.7.pdf Release note]
|-
|1.9.6
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/7/7b/TeltoCharge-v1.9.6-bundle.zip TeltoCharge-v1.9.6]'''
|September 18, 2023
|[https://wiki.teltonika-energy.com/images/9/90/Release_note_FW_1.9.5.pdf Release note]
|-
|1.9.5
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/9/91/TeltoCharge-v1.9.5-bundle.zip TeltoCharge-v1.9.5]'''
|August 31, 2023
|[https://wiki.teltonika-energy.com/images/9/90/Release_note_FW_1.9.5.pdf Release note]
|-
|1.8
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/4/43/TeltoCharge-v1.8.11-bundle.zip TeltoCharge-v1.8.11]'''
|July 3, 2023
|[https://wiki.teltonika-energy.com/images/e/ea/Release_note_FW_1.8.10.pdf Release note]
|-
|1.7
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/a/ad/TeltoCharge-v1.7.9-bundle.zip TeltoCharge-v1.7]'''
|May 22, 2023
|[https://wiki.teltonika-energy.com/images/1/1f/Release_note_FW_1.7.9.pdf Release note]
|-
|1.6.0
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/b/ba/TeltoCharge-v1.6.7-bundle.zip TeltoCharge-v1.6]'''
|Mar 1, 2023
|[https://wiki.teltonika-energy.com/images/4/4d/FW_1.6.pdf Release note]
|-

|1.5
|div style="text-align: center;" colspan="2" | '''[https://wiki.teltonika-energy.com/images/d/dd/TeltoCharge-v1.5.8-bundle.zip TeltoCharge-v1.5]'''
|Dec 22, 2022
|[https://wiki.teltonika-energy.com/images/3/3d/Release_note_v1.5.pdf Release note]
|-
|1.4
|'''TeltoCharge-v1.4.3L'''
|'''TeltoCharge-v1.4.2'''

|Oct 7, 2022
|[https://wiki.teltonika-energy.com/images/b/b6/Release_note_v1.4.3L.pdf Release note]
|-
|1.3
|'''TeltoCharge-v1.3.12L'''
|'''TeltoCharge-v1.3.12'''
|Sep 28, 2022
|[https://wiki.teltonika-energy.com/images/a/a9/Release_note_v1.3.11L.pdf Release note]
|-
|1.2
|colspan="2" |'''TeltoCharge-v1.2.10'''
|Aug 8, 2022
|[https://wiki.teltonika-energy.com/images/0/02/Release_note_v1.2.10.pdf Release note]
|-
|1.1
|colspan="2" |'''TeltoCharge-v1.1.12'''
|Jun 6, 2022
|[https://wiki.teltonika-energy.com/images/2/24/Release_note_v1.1.12.pdf Release note]
|-
|1.0
|colspan="2" |'''TeltoCharge-v1.0.7'''
|Apr 25, 2022
|
|-
|Other
|colspan="2" |'''TeltoCharge-v1.0.4'''
|Apr 22, 2022
|
|}
'''Legacy firmware version* -''' TeltoCharge fw version which was used for chargers before mass production (these chargers are using same hardware, it's only related to separation). These type of chargers can only be updated to legacy FW version. '''From 1.5 version it is fixed and you won't need to keep this in mind.

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">How to check your firmware version?</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
<br>
1. Go to Teltonika Energy app settings, scroll down and press '''Device info'''; <br>

2. Press '''Check for updates'''; <br>

3. At the top, current firmware version can be found. <br>
<br>
[[File:TeltoCharge FirmwareVersionCheck1.png|frameless|588x588px]] [[File:TeltoCharge FirmwareVersionCheck.png|frameless|588x588px]]

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">How to update firmware automatically?</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
The product utilizes FOTA update services (HTTP/HTTPS client).<br>

1. To update firmware, click on the main window bar '''Click to update''' option; <br>

2. You will be automatically transfered to '''Updates''' window . <br>

3. Choose to '''Update Firmware''' from firmware available on server. <br>

4. Do not close Teltonika Energy app and stay in bluetooth range while update ends. <br>
<br>

[[File:Fota 1.png|frameless|588x588px]] [[File:Fota 2.png|frameless|588x588px]]

<h2 style="color: #4a4a4a; font-size: 24px; font-weight: bold; margin-bottom: 10px;">How to update firmware manually?</h2>
<ul style="list-style-type: none; margin: 0; padding: 0;">
1. To update firmware manually, first of all, download firmware file from this page to your mobile phone which is paired with your TeltoCharge; <br>

2. Go to Teltonika Energy app settings, scroll down and press device info, then press Check for updates; <br>

3. Browse file and select latest firmware version which was downloaded; <br>

4. Press Upload firmware; <br>

5. Do not close Teltonika Energy app and stay in bluetooth range while update ends; <br>
<br>

[[File:Updates2.png|frameless|588x588px]] [[File:Updates3.png|frameless|588x588px]] [[File:Updates4.png|frameless|588x588px]]

[[Category: Resources]]

File:TeltoCharge-v1.16.2-bundle.zip

2026-05-18T14:44:53Z

Dominykas.Z: TeltoCharge-v1.16.2-bundle.zip

== Summary ==
TeltoCharge-v1.16.2-bundle.zip

EVC2 firmware

2026-05-18T14:34:29Z

Dominykas.Z:

==Changelog==
===<b><span class="plainlinks">[https://wiki.teltonika-energy.com/images/4/47/TeltoCharge-v2.2.6.bin EVC2xx V2.2.6]</span></b> | 2026.05.01===
* <b>New features and settings</b>
** Added new solar charging modes for Dynamic Load Management, including Solar Only, ECO, and Hybrid modes.
** Added new Dynamic Load Management capabilities, including [https://wiki.teltonika-energy.com/view/Potential_free_contact potential-free contact support], dynamic IP device discovery and reconnection, and configurable 1-phase charging behavior.
** Expanded Modbus meter support with additional [https://wiki.teltonika-energy.com/view/SDM%20models Eastron] and [https://wiki.teltonika-energy.com/view/A%20and%20B%20models ABB] meter models.
** Added installer setting for IT grid voltage sampling.
** Added an NFC reader cooldown to prevent accidental repeated actions.
* <b>Bug fixes and improvements</b>
** Improved charging session recovery, troubleshooting logs, and reboot reporting after power loss events.
** Improved solar charging and Dynamic Load Management stability, including power limit handling, Modbus TCP communication, ECO mode synchronization, and DLM failsafe behavior.
** Improved communication stability for Bluetooth, LAN, and WebSocket connections.
** Improved charging session energy graph accuracy and HomeWizard P1 meter data handling.
** Improved OCPP configuration request handling and tamper event reporting.
** Improved internal time synchronization.
===<b><span class="plainlinks">[https://wiki.teltonika-energy.com/images/3/35/TeltoCharge-v2.1.5.bin EVC2xx V2.1.5]</span></b> | 2026.01.06===
* <b>New features and settings</b>
** UK product code handling
* <b>Bug fixes and improvements</b>
** NFC scanning module improvements
** Fixed bugs where the settings were not being saved while switching power selector
** Improved OCPP handling when starting/stopping charge
** Various bug fixes related to parameter and information handling
===<b><span class="plainlinks">[https://wiki.teltonika-energy.com/images/e/e8/TeltoCharge-v2.1.0.bin EVC2xx V2.1.0]</span></b> | 2025.11.24===
* <b>New features and settings</b>
** Support for Shelly 3PRO meters added
*** more information: [[Dynamic Load Balancing EVC2#Modbus TCP/IP models|Shelly 3PRO configuration]]
** Modbus TCP device control enabled
** New settings: Max group load & Max grid load for DLM/DLB functions
** 2x RS-485 port support
*** more information: [[2x RS458 support]]
** EVC2XX potential-free contact support
*** more information: [[Potential free contact]]
** Power rotary switch implementation for easier setup
*** more information: [[Power Selector Switch]]
** Automatic grid type detection and phase rotation support
** LAN-based device control via EV charging app, previously it was possible through Bluetooth only
** Automatic firmware updates support
** Changed installer menu code to 4 digits
* <b>Bug fixes and improvements</b>
** Various metering and charging bug fixes
** Various Modbus and OCPP communication protocol enhancements
** Charger stability issues resolved
** Bluetooth, NFC and UI features improved
----

== Updating ==
Use our app to update the station manually

# Use app and go to settings, scroll down and press '''Device info''';
# Press '''Check for updates''';
# At the top, current firmware version can be found.
# User has 2 options: to update from our cloud or by manually uploading a firmware file to the charger.

[[File:How to update.png|frameless|984x984px]]

File:TeltoCharge-v2.2.6.bin

2026-05-18T14:15:27Z

Dominykas.Z: Firmware v2.2.6

== Summary ==
Firmware v2.2.6

External control RS485

2026-04-07T11:05:27Z

Dominykas.Z: BIG BOSS TOLD ME TO DO IT

=External control RS485=
This section provides an overview of the Modbus RTU interface supported by TeltoCharge electric vehicle supply equipment (EVSE). The document provides description of the available Modbus registers for the external control and communication with the charger based on a wired RS485 connection. 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. The secondary device can operate on two modes:

# It can be configured to use a watchdog for communication and if no valid communication is present after a configurable time interval, the charging (if ongoing) will stop and EVSE will not perform any charging until valid communication is reestablished;
# the EVSE does not use a watchdog and continuous communication is not needed. As it is possible to change the EVSE settings by using the TeltoCharge mobile application, it is recommended for the primary device to read, compare, and change settings as needed based on user preferences and real-time requirements, ensuring a seamless and secure charging experience for electric vehicle owners. Continuous monitoring and adjustment of EVSE settings enable the primary device to stay synchronized with user inputs, maintain optimal charging conditions, and promptly respond to any changes initiated through the TeltoCharge mobile application, thereby enhancing overall efficiency and user satisfaction.
==Device preparation==
TeltoCharge must be configured as a secondary device via a TeltoCharge mobile application and device must have RS485 wired connection with the primary device..

# Open "User menu"
# Open "Installer menu"
# Open "Load Managment"
# Select "Secondary"
# Enable secondary device
# Check if the address is expected in your system

[[File:External.png|frameless|900x900px]]
[[File:External connection2.png|frameless|400x400px]]

==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
| 0-65535
| -
|s
|Evse status time, first word (uint16_t)
|-
|8
|R
|'''EVSE status time 2nd word'''
|uint16
| 0-65535
| -
|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 the maximum value of amps the EVSE can supply currently. Setting to 0 amps stops charging
|-
|16
|R/W
|'''Start/Stop charging session'''
|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'''
|uint16
|0-65535
|123456789
|s
|Serial number, first word (uint16_t)
|-
|25
|R
|'''Serial number 2nd word'''
|uint16
|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.
|}

Dynamic Load Balancing EVC2

2026-03-25T10:30:07Z

Dominykas.Z: fix desc

= DYNAMIC LOAD BALANCING =
EVC2 can communicate with a dedicated smart energy meter and adjust its power consumption based on the meter's readings. This functionality helps protect the home's electrical grid from overload during peak hours and optimizes energy usage to match the user's habits. The smart energy meter should always be installed in the main electrical cabinet, as shown below.
[[File:Dynamic_Load_Balancing_Conection_Schematic.png|alt=|center|frameless|395x395px]]

=== DLB support ===
We can achieve DLB support by pairing the charger with one of the following:

* [[Dynamic Load Balancing EVC2#MODBUS RTU METERS|Modbus RTU meters]]
* [[Dynamic Load Balancing EVC2#MODBUS TCP/IP METERS|Modbus TCP/IP meters]]
* [[Dynamic Load Balancing EVC2#CT CLAMPS|CT clamps]]
* [[Dynamic Load Balancing EVC2#EXTERNAL CONTROL|External control]]
* [[Dynamic Load Balancing EVC2#SMARTSTUFF P1 CONVERTER|Smartstuff P1 converter]]

DLB can then be configured using the app following [[Dynamic Load Balancing EVC2#TELTONIKA ENERGY APP SETTINGS|these instructions]].

== PHASE BALANCE EXPLANATION ==
TeltoCharge has advanced functionality to detect a car's charging type and, if required, switch phases during mid-charge.

The same phase switch process will happen if the smart meter detects, that less than 6A is available for one of the phases.

=== Adaptation to the car's charging capability ===
If the charger is set for 3phase charging, but the plugged car can only draw current from one phase, TeltoCharge will switch to one-phase mode after a short period of time

[[File:CarExample.png|frameless|493x493px]]

=== Phase balance during lack of power ===
When the smart meter detects that there is less than 6A for each phase, the charging station will switch from 3phase mode to 1phase mode until 6ampers are available for all phases

[[File:PhaseSwitch.png|frameless|600x600px]]

== MODBUS RTU METERS ==
To access energy measurement through Modbus RTU, connect both charger and the meter together using RS485 terminal for meter.

[[File:DLB meter.png|frameless|808x808px]]

=== RS485 communication ===
For RS485 communication it is recommended to use a twister pair communication cable. Check example below.

[[File:TeltoCharge_DLB_CableExample.png|frameless]]

'''Note:''' ''Communication cable should be integrated with power cable.''

In order to strive for wider applicability and compatibility, we constantly test and add new supported devices into list. All of the supported energy meters and schematics how to connect them are provided below.

In order to make '''Dynamic load balancing''' and '''Solar''' functionality work, please always check:

* if the '''wiring''' your Smart energy meter to EVC2 is right.
* if the '''installer menu configuration''' in mobile application according to your smart energy meter is right.

=== Supported Modbus RTU models ===
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 60%;"
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Energy meter manufacturer
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Technical information
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Configuration in mobile application
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Wiring scheme
|-
| style="padding: 2px;" |Carlo Gavazzi series 1-3
| style="padding: 2px;" |[[EM and ET models]]
| style="padding: 2px;" |[[Carlo Gavazzi settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/view/EM_and_ET_models#Carlo_Gavazzi_meters_wiring: METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Siemens PACxxxx
| style="padding: 2px;" |[[PAC models]]
| style="padding: 2px;" |[[Siemens settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/0/0e/Siemens_PAC_Sentron.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |ABB A4x ; B2x
| style="padding: 2px;" |[[A and B models]]
| style="padding: 2px;" |[[ABB settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/e/e8/ABB_serie_A%26B_part_1.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Eastron SDMxx
| style="padding: 2px;" |[[SDM models]]
| style="padding: 2px;" |[[Eastron settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/5/53/Eastron_sdm72.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Inepro PRO380
| style="padding: 2px;" |[[PRO model]]
| style="padding: 2px;" |[[Inepro settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/3/3b/Inepro_pro380.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Chint
| style="padding: 2px;" |[[Chint models]]
| style="padding: 2px;" |[[Chint settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/3/3b/Inepro_pro380.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Entes
| style="padding: 2px;" |[[ES models]]
| style="padding: 2px;" |[[Entes settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/2/21/Entes.png METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Acrel
| style="padding: 2px;" |[[Acrel models]]
| style="padding: 2px;" |[[Acrel settings]]
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/images/d/d1/Acrel_meter.png METER -> TELTOCHARGE]
|-
| colspan="4" style="padding: 8px;" |''More coming soon...''
|}

== LOAD BALANCING CONFIGURATION ==
To ensure everything works correctly, please apply the following setup :

# Open user menu
# Open "'''''Installer Menu'''''"
# Open "'''''Dynamic Load Balancing'''''" menu
# Enable "'''''Load Balancing'''''"
# If smart meter is connected with RS485 wires, press "'''''Search For Device'''''"
# *'''ONLY If TeltoCharge is unable''' to identify energy meter - use "'''''Manual Setup'''''"

[[File:DLB_settings.png|frameless|989x989px]]

== MODBUS TCP/IP METERS ==
To access energy measurement through Modbus TCP/IP, connect both the meter and your charger to your network. Charger has two options: either WiFi or ethernet cable.

=== Connecting Shelly 3PRO ===
Download the '''Shelly smart control''' app and setup the device to connect to your network. After its configured, find the IP address given to the meter.

[[File:Shelly wiki.png|frameless|935x935px]]

'''''Note:''' Copy the IP as it will be used in EV charging app to connect the meter to the station''

=== Connecting HomeWizard P1 ===
Follow this full guide for easy installation: [[Media:HomeWizard P1 guide.pdf|HomeWizard P1.pdf]]

Or in short - install the HomeWizard meter to the P1 port of your utility meter.

[[File:Wizard p1 utility meter.png|frameless|284x284px]]

Download the '''HomeWizard''' app and follow the setup for the meter to connect to your network. After its configured, find the IP address given to the meter.
[[File:Homewizard wiki 1.png|frameless]] [[File:Homewizard wiki 3.png|frameless|592x592px]]

'''''Note:''' Copy the IP as it will be used in EV charging app to connect the meter to the station''

=== Load balancing using Network meter ===
A given example below is for Shelly 3Pro smart meter integration, but is identical when using HomeWizard P1.

To connect the meter to the station, go to '''load balancing''' section in the app, choose '''network meter''' and the model you're using.

[[File:Shelly DLB 1.png|frameless|938x938px]]

After that select '''IP address''' as was shown in the Shelly app. Set '''max grid load''' to match the value allowed by the grid. If everything is done right - the status should indicate that the network meter has successfully connected.

[[File:Shelly DLB 2.png|937x937px]]

=== Supported Modbus TCP/IP models ===
{| class="wikitable" style="text-align: center; border: 1px solid #dddddd; font-family: arial, sans-serif; width: 60%;"
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Energy meter manufacturer
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Technical information
! style="background-color: #0054A6; color:#FFFFFF; padding: 8px;" |Configuration in mobile application
|-
| style="padding: 2px;" |Shelly
| style="padding: 2px;" |3em models
| style="padding: 2px;" |[https://wiki.teltonika-energy.com/view/Dynamic_Load_Balancing_EVC2#Load_balancing_using_Shelly_3PRO METER -> TELTOCHARGE]
|-
| style="padding: 2px;" |Homewizard
| style="padding: 2px;" |P1 models
| style="padding: 2px;" |tba
|}

== CT CLAMPS ==
It is possible to measure power readings by connecting CT clamps to each phase. Insert each CT clamp to its dedicated terminal (blue wire to B, red wire to R slot of the terminal).

<u>Make sure that clamp direction is pointing towards source (away from the charger).</u>

[[File:CT clamps EVC2.png|frameless|529x529px]]

Recommended CT clamp specifications:

* Rated input/current - depends on your total power input, but we would recommend not to exceed 150A.
* Turn ratio - 3000:1.
* Burden resistor - CT-Clamp '''must not have integrated burden resistor'''.

Choosing to use CT clamp is done via the app in the '''Load balancing''' section. Set '''Max grid load''' to max available amps in your grid (for example: value of your breaker).

Press calibrate to set the starting point.

Note: Before calibration, CT clamp has to be connected to the port, but not clamped around the cable.

[[File:Load balancing ct clamps.png|frameless|804x804px]]

== EXTERNAL CONTROL ==
This section provides an overview of the Modbus RTU interface supported by TeltoCharge electric vehicle supply equipment (EVSE). The document provides description of the available Modbus registers for the external control and communication with the charger based on a wired RS485 connection. 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. The secondary device can operate on two modes:

# It can be configured to use a watchdog for communication and if no valid communication is present after a configurable time interval, the charging (if ongoing) will stop and EVSE will not perform any charging until valid communication is reestablished;
# the EVSE does not use a watchdog and continuous communication is not needed. As it is possible to change the EVSE settings by using the TeltoCharge mobile application, it is recommended for the primary device to read, compare, and change settings as needed based on user preferences and real-time requirements, ensuring a seamless and secure charging experience for electric vehicle owners. Continuous monitoring and adjustment of EVSE settings enable the primary device to stay synchronized with user inputs, maintain optimal charging conditions, and promptly respond to any changes initiated through the TeltoCharge mobile application, thereby enhancing overall efficiency and user satisfaction.

=== Device preparation ===
TeltoCharge must be configured as a secondary device via a TeltoCharge mobile application and device must have RS485 wired connection with the primary device..

# Open "User menu"
# Open "Installer menu"
# Open "Load Management"
# Select "Secondary"
# Enable secondary device
# Check if the address is expected in your system

[[File:External.png|frameless|900x900px]] [[File:EVC2_external_controller.png|frameless|460x460px]]

=== 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.
|}

== SMARTSTUFF P1 CONVERTER ==
The Modbus P1 Dongle is a device that enables communication between your EVC charging station and a smart meter using the Modbus RS-485 protocol. This setup is essential for accurately monitoring and controlling the energy usage during EV charging sessions.

* Accurate energy monitoring: Ensures that energy usage data is correctly captured and transmitted.
* Optimized charging: By leveraging the data from the smart meter, the charging station can optimize the charging process, potentially reducing costs and improving efficiency.

''Note:'' Before proceeding with the installation, please ensure that your smart meter is compatible with the Modbus P1 Dongle.

=== Smart Meter Connection ===
The dongle is connected to the P1 port of the smart meter via a provided P1 cable. This connection allows the dongle to read energy consumption data directly from the smart meter.

=== RS-485 Connection ===
The dongle features RS-485 terminals which are critical for establishing communication with the EVC2 system. These terminals are usually labeled as Ground (GND), A+ (positive differential signal), and B- (negative differential signal).

* To connect the dongle to the EVC2, you'll need to use an appropriate RS-485 cable.
* Connect the 'A+' terminal of your cable to the 'A+' port on the EVC2 device.
* Connect the 'B-' terminal of your cable to the 'B-' port on the EVC2 device.

''Note :'' In case of communication errors, swapping the 'A+' and 'B-' connections might resolve the issue

. [[File:EVC2 p1 LB.png|frameless|801x801px]]<blockquote>https://docs.smart-stuff.nl/p1-modbus-dongle/quick-start/installation</blockquote>

=== General meter settings ===
According to your smart meter documentation, please enter all the settings into the Energy app as shown.

# '''Energy meter type''': You need to select the type of smart meter (1-phase/3-phase). Please note that you can use a 1-phase charger even if the meter is 3-phase.
# '''RS-485 baud rate''': To ensure optimal performance and compatibility with the P1 smart dongle, the RS-485 baud rate must be configured to 38400.
# '''RS-485 parity/stop bit''': Similarly, this information can also be found in the meter settings. If the client is unable to find it, it is advisable to check the smart meter manual.

{|
|[[File:Smart_stuff.png|left|frameless]]
|[[File:Live_data.png|left|frameless|457x457px]]
|}
{|
|'''''Note:''''' ''Set up the energy meter address''

''according to the smart stuff address.''
|
|
|
|
|
|
|
|
|
|
|
|
|'''''Note:''''' ''After successfully completing these steps,''

please check the diagnostic live data from the energy meter.
|}

== TELTONIKA ENERGY APP SETTINGS ==
To ensure everything works correctly, please apply the following setup :

# Open user menu
# Open "'''''Installer Menu'''''"
# Open "'''''Dynamic Load Balancing'''''" menu
# Enable "'''''Load Balancing'''''"
# If smart meter is connected with RS485 wires, press "'''''Search For Device'''''"
# *'''ONLY If TeltoCharge is unable''' to identify energy meter - use "'''''Manual Setup'''''"

[[File:DLB_settings.png|frameless|1062x1062px]]
__FORCETOC__

OCPP 1.6 JSON guide EVC2

2026-01-30T10:30:46Z

Dominykas.Z: Teltonika EVC stations from Teltocharge

= Integratig Teltonika EVC stations with OCPP 1.6 JSON =

This guide explains how to integrate '''Teltonika EVC stations''' with your existing system using the OCPP 1.6 JSON protocol.

== Getting started ==

Before you begin, you will need the following:

* Teltonika EVC station is installed and configured.
* Teltonika EVC station has access to the internet.
* Knowledge of the OCPP 1.6 JSON protocol.

== Steps ==

1. Configure the charging station to connect to your OCPP 1.6 JSON server. You will need to know the IP address or domain name of your server and the port number for the OCPP 1.6 JSON protocol.

2. Set up a charging station account on your OCPP 1.6 JSON server. You will need to provide the following information:

* Charging station ID: This is a unique identifier for your charging station.
* Charging station type: Specify the type of charging station you have. (AC)
* Other settings as required by your OCPP 1.6 JSON server.

3. Connect the charging station to your OCPP 1.6 JSON server. The charging station will communicate with your server using the OCPP 1.6 JSON protocol.

4. Test the connection by starting a charging session from your OCPP 1.6 JSON server.

5. Monitor the charging station from your OCPP 1.6 JSON server. You will be able to view the charging status, energy usage, and other important information about the charging station '''(for configuration keys available at the moment from Teltonika EVC station please communicate with your Sales manager or directly through Teltonika Energy VIP HelpDesk)'''.

== How to connect Teltonika EVC stations to chosen OCPP provider ==

*'''Connect Teltonika EVC station to the internet''' - make sure, that the charging station has the internet connection. (all types are acceptable)
[[File:Connectivity for OCPP.png|frameless|990x990px]]

*'''Connect Teltonika EVC station to the chosen OCPP server'''

<u>OCPP provider must give you info about:</u>

#'''URL address''' - URL address must end with "/"
#'''Charge point ID''' - Most of the time it's the serial number of the charging station
When you have that information, insert it as shown in the picture below and press save.

[[File:OCPP settings2.png|frameless]]

= COMPATIBLE SOFTWARE PROVIDERS FOR OCPP INTEGRATION =
This section provides an overview of the software providers that have been tested and proven compatible with Teltonika EVC station using the OCPP 1.6 JSON (Open Charge Point Protocol).

→For detailed Teltonika EVC stations OCPP documentation contact Teltonika Energy Technical Support team via HelpDesk.←

<u>Segments description:</u>

* '''Public Charging Networks''' - managing large networks of public EV charging stations.

Real-time monitoring, dynamic pricing, user authentication, remote diagnostics, and reporting.

* '''Commercial and Fleet Charging''' - supporting commercial fleets and workplace charging solutions.

Fleet management tools, scheduled charging, energy usage reporting, and integration with fleet management systems.

* '''Residential Charging Solutions''' - providing home EV charging management for individual users.

User-friendly interfaces, mobile app control, energy usage tracking, and integration with smart home systems.

* '''Retail and Hospitality Charging''' - offering EV charging as an amenity at retail locations, hotels, and restaurants.
Customer engagement tools, loyalty programs integration, payment processing, and usage analytics.

== Tested Software Providers ==
The software providers listed here have undergone comprehensive testing with Teltonika EVC station hardware, ensuring that they meet standards for performance and reliability.
*For integration of your OCPP software, please contact Teltonika Energy Technical Support team via HelpDesk.

==List of supported platforms==
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center; font-size: 18px;" |'''Software Vendor'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center; font-size: 18px;" |'''Public Charging Networks'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center; font-size: 18px;" |'''Commercial and Fleet Charging'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center; font-size: 18px;" |'''Residential Charging Solutions'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center; font-size: 18px;" |'''Retail and Hospitality Charging'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center; font-size: 18px;" |'''Official page'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" | Focus EV
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.radiuscharge.com/products/software/ FOCUS EV]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" | Monta
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://monta.com/uk/#dropdown MONTA]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |EEVY
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://eevy-charge.com/en/ EEVY]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |Ampeco
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.ampeco.com/ev-charging-platform/ AMPECO]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |LastMilesSolutions
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.lastmilesolutions.com/ LMS]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |GreenFlux
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.greenflux.com/ GREENFLUX]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" | SaasCharge
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://saascharge.com/ SAASCHARGE]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |Daloop
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://daloop.io/ DALOOP]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |Go To-U
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://go-tou.com/en GO TO-U]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |Tap Electric
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.tapelectric.app/ TAP ELECTRIC]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |Clenergy EV
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.clenergy-ev.com/ Clenergy EV]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |Enerlink
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.enerlink.com/ ENERLINK]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |E-Flux
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.e-flux.io/ E-FLUX]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" | PlugFuse
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://plug-fuse.com/ PLUGFUSE]
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white; font-size: 18px;" |eMabler
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | +
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" |[https://www.emabler.com/ eMABLER]
|-
|}

= OCPP IMPLEMENTATION =
Our station can accept various messages and configuration keys. The following is a list of supported standard messages, key names and values
{| class="wikitable"
|+
! colspan="2" |Supported messages
|-
!Message
!Comment
|-
|Authorize
|
|-
|BootNotification
|
|-
|ChangeAvailability
|
|-
|ChangeConfiguration
|
|-
|ClearCache
|Authorization Cache with max 20 entries
|-
|DataTransfer
|No custom commands
|-
|GetConfiguration
|Max 60 elements per request
|-
|Heartbeat
|
|-
|MeterValues
|In MeterValuesSampledData, MeterValuesAlignedData and StopTxnSampledData only.
Supported measurands: Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import.
''Minimum interval 5s''
|-
|RemoteStartTransaction
|
|-
|RemoteStopTransaction
|
|-
|Reset
|
|-
|StartTransaction
|
|-
|StopTransaction
|
|-
|StatusNotification
|
|-
|UnlockConnector
|For socket version charger only
|-
! colspan="2" |Local Auth List Management
|-
|GetLocalListVersion
|
|-
|SendLocalList
|
|-
|LocalAuthListMaxLength
|Max 50 entries
|-
! colspan="2" |Smart Charging
|-
|SetChargingProfile
|
|-
|GetCompositeSchedule
|Max GetCompositeSchedule.req duration 24h
|-
|ClearChargingProfile
|
|-
! colspan="2" |Remote Trigger
|-
|TriggerMessage
|
|-
| colspan="2" |Reservation
|-
|ReserveNow
|
|-
|CancelReservation
|
|-
! colspan="2" |Firmware Management
|-
|GetDiagnostics
|
|-
|DiagnosticsStatusNotification
|
|-
|FirmwareStatusNotification
|
|-
|UpdateFirmware
|
|-
! colspan="2" |Improved Security
|-
|CertificateSigned
|
|-
|ExtendedTriggerMessage
|
|-
|GetInstalledCertificateIds
|Only CentralSystemRootCertificate type is supported
|-
|GetLog
|
|-
|InstallCertificate
|Only CentralSystemRootCertificate type is supported
|-
|LogStatusNotification
|
|-
|SecurityEventNotification
|Only ReconfigurationOfSecurityParameters, SettingSystemTime, SecurityLogWasCleared,
StartupOfTheDevice, ResetOrReboot, FirmwareUpdated notifications are used
|-
|SignCertificate
|
|}
{| class="wikitable"
! colspan="4" |Supported Configuration Key Names & Values
|-
! colspan="2" rowspan="2" |Key
! colspan="2" |Values
|-
!Default
!Supported range
|-
! colspan="4" |Core
|-
| colspan="2" |AllowOfflineTxForUnknownId
|0
|0, 1
|-
| colspan="2" |AuthorizeRemoteTxRequests
|1
|0, 1
|-
| colspan="2" |AuthorizationCacheEnabled
|1
|0, 1
|-
| colspan="2" |ClockAlignedDataInterval
|3600
|300-86400
|-
| colspan="2" |ConnectionTimeOut
|120
|1-3600
|-
| colspan="2" |ConnectorPhaseRotation
|Unknown
|Unknown,RST,RTS,SRT, STR,TRS,TSR
|-
| colspan="2" |GetConfigurationMaxKeys
|60
| -
|-
| colspan="2" |HeartbeatInterval
|3600
|60-86400
|-
| colspan="2" |LocalAuthorizeOffline
|0
|0, 1
|-
| colspan="2" |LocalPreAuthorize
|1
|0, 1
|-
| colspan="2" |MeterValuesAlignedData
|""
|Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import
|-
| colspan="2" |MeterValuesSampledData
|Energy.Active.Import.Register
|Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import
|-
| colspan="2" |MeterValueSampleInterval
|3600
|5-84600
|-
| colspan="2" |NumberOfConnectors
|1
| -
|-
| colspan="2" |ResetRetries
|10
|0-10
|-
| colspan="2" |StopTransactionOnEVSideDisconnect
|1
| -
|-
| colspan="2" |StopTransactionOnInvalidId
|0
|0, 1
|-
| colspan="2" |StopTxnAlignedData
|""
|""
|-
| colspan="2" |StopTxnSampledData
|""
|Energy.Active.Import.Register,Current.Import,Current.Offered,
Temperature,Voltage,Power.Active.Import
|-
|TransactionMessageAttempts
| colspan="2" |3
|1-100
|-
|TransactionMessageRetryInterval
| colspan="2" |20
|5-60
|-
|UnlockConnectorOnEVSideDisconnect
| colspan="2" |1
|0, 1
|-
|WebSocketPingInterval
| colspan="2" |10
|1-1200
|-
! colspan="4" |Local Auth List Management
|-
|LocalAuthListEnabled
| colspan="2" |1
|0, 1
|-
|LocalAuthListMaxLength
| colspan="2" |50
| -
|-
|SendLocalListMaxLength
| colspan="2" |10
| -
|-
! colspan="4" |Smart Charging
|-
|ChargeProfileMaxStackLevel
| colspan="2" |5
| -
|-
|ChargingScheduleAllowedChargingRateUnit
| colspan="2" |"Current"
| -
|-
|ChargingScheduleMaxPeriods
| colspan="2" |5
| -
|-
|MaxChargingProfilesInstalled
| colspan="2" |9
| -
|-
! colspan="4" |Firmware Management
|-
|SupportedFileTransferProtocols
| colspan="2" |"HTTP,HTTPS,FTP"
| -
|-
! colspan="4" |Improved Security
|-
|SecurityProfile
| colspan="2" |0
|0-3
|-
|CpoName
| colspan="2" |""
|0-128 symbols
|-
|AdditionalRootCertificateCheck
| colspan="2" |0
|0
|-
|CertificateStoreMaxLength
| colspan="2" |1
|1
|-
|AuthorizationKey
| colspan="2" |""
|32-40 symbols
|}
''If you have more questions about OCPP please visit our FAQ section: https://wiki.teltonika-energy.com/view/FAQ''

[[Category: EVC2 Advanced Topics]]

EVC 2 Declarations of conformity

2025-12-08T12:33:56Z

Dominykas.Z: /* EVC200 series declarations */

File:2025-09-30 EU declaration of conformity SIGNED thbnl.png

2025-12-08T12:32:17Z

Dominykas.Z: 2025-09-30_EU_declaration_of_conformity_SIGNED thbnl

== Summary ==
2025-09-30_EU_declaration_of_conformity_SIGNED thbnl

EVC 2 Declarations of conformity

2025-12-08T12:02:40Z

Dominykas.Z:

= Declarations for the EVC 2 product group =
<center> Here are the newly uploaded declarations of conformity for the available products.
<center>
'''Note:''' Thumbnails might differ from the contents of the main document.

== EVC200 series declarations ==
[[File: EVC2 7.4kW DoC thbnl.png|alt=|center|407x407px|link=https://https://wiki.teltonika-energy.com/view/File:2025-09-30_EU_declaration_of_conformity_SIGNED.pdf|thumb]]

== EVC20X1 series declarations ==
[[File:EVC2 11kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/5/5b/EVC2XX_EU_DECLARATION_OF_CONFORMITY_11kW_Teltonika_Energy.pdf|thumb]]

== EVC20X2 series declarations ==
[[File:EVC2 22kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/1/10/EVC2XX_EU_DECLARATION_OF_CONFORMITY_22kW_Teltonika_Energy-2025-06-04.pdf|thumb]]

File:2025-09-30 EU declaration of conformity SIGNED.pdf

2025-12-08T11:59:51Z

Dominykas.Z:

evc2 dec cert proved by Aidas

EVC2 DoC

2025-12-08T11:54:17Z

Dominykas.Z: Dominykas.Z moved page EVC2 DoC to EVC 2 Declarations of conformity

#REDIRECT [[EVC 2 Declarations of conformity]]

EVC 2 Declarations of conformity

2025-12-08T11:54:17Z

Dominykas.Z: Dominykas.Z moved page EVC2 DoC to EVC 2 Declarations of conformity

= Declarations for the EVC 2 product group =
<center> Here are the newly uploaded declarations of conformity for the available products.
<center>
'''Note:''' Thumbnails might differ from the contents of the main document.

== EVC200 series declarations ==
[[File: EVC2 7.4kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/1/15/EVC2XX_EU_DECLARATION_OF_CONFORMITY_7.4kW_Teltonika_Energy-2025-06-04.pdf|thumb]]

== EVC20X1 series declarations ==
[[File:EVC2 11kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/5/5b/EVC2XX_EU_DECLARATION_OF_CONFORMITY_11kW_Teltonika_Energy.pdf|thumb]]

== EVC20X2 series declarations ==
[[File:EVC2 22kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/1/10/EVC2XX_EU_DECLARATION_OF_CONFORMITY_22kW_Teltonika_Energy-2025-06-04.pdf|thumb]]

EVC 2 Declarations of conformity

2025-12-08T11:41:18Z

Dominykas.Z: https://teltonikaenergy.atlassian.net/browse/CD-272

= Declarations for the EVC 2 product group =
<center> Here are the newly uploaded declarations of conformity for the available products.
<center>
'''Note:''' Thumbnails might differ from the contents of the main document.

== EVC200 series declarations ==
[[File: EVC2 7.4kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/1/15/EVC2XX_EU_DECLARATION_OF_CONFORMITY_7.4kW_Teltonika_Energy-2025-06-04.pdf|thumb]]

== EVC20X1 series declarations ==
[[File:EVC2 11kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/5/5b/EVC2XX_EU_DECLARATION_OF_CONFORMITY_11kW_Teltonika_Energy.pdf|thumb]]

== EVC20X2 series declarations ==
[[File:EVC2 22kW DoC thbnl.png|alt=|center|407x407px|link=https://wiki.teltonika-energy.com/images/1/10/EVC2XX_EU_DECLARATION_OF_CONFORMITY_22kW_Teltonika_Energy-2025-06-04.pdf|thumb]]