Dynamic Load Balancing EVC2
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.
DLB support
We can achieve DLB support by pairing the charger with one of the following:
DLB can then be configured using the app following 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
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
MODBUS RTU METERS
To access energy measurement through Modbus RTU, connect both charger and the meter together using RS485 terminal for meter.
RS485 communication
For RS485 communication it is recommended to use a twister pair communication cable. Check example below.
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
| Energy meter manufacturer | Technical information | Configuration in mobile application | Wiring scheme |
|---|---|---|---|
| Carlo Gavazzi series 1-3 | EM and ET models | Carlo Gavazzi settings | METER -> TELTOCHARGE |
| Siemens PACxxxx | PAC models | Siemens settings | METER -> TELTOCHARGE |
| ABB A4x ; B2x | A and B models | ABB settings | METER -> TELTOCHARGE |
| Eastron SDMxx | SDM models | Eastron settings | METER -> TELTOCHARGE |
| Inepro PRO380 | PRO model | Inepro settings | METER -> TELTOCHARGE |
| Chint | Chint models | Chint settings | METER -> TELTOCHARGE |
| Entes | ES models | Entes settings | METER -> TELTOCHARGE |
| Acrel | Acrel models | Acrel settings | METER -> TELTOCHARGE |
| 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"
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.
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: HomeWizard P1.pdf
Or in short - install the HomeWizard meter to the P1 port of your utility meter.
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.
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.
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.
Supported Modbus TCP/IP models
| Energy meter manufacturer | Technical information |
|---|---|
| Shelly | 3em models |
| Homewizard | 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).
Make sure that clamp direction is pointing towards source (away from the charger).
Mandatory 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.
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
Modbus register map
| 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 |
| 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
. 
https://docs.smart-stuff.nl/p1-modbus-dongle/quick-start/installation
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.
 |
 |
| 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"