Jump to content

External control RS485: Difference between revisions

From Teltonika Energy Wiki
No edit summary
mNo edit summary
(7 intermediate revisions by 2 users not shown)
Line 5: Line 5:
# 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.
# 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==
==Device preparation==
TeltoCharge must be configured as a secondary device via a TeltoCharge mobile application.
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 "User menu"
Line 13: Line 13:
# Enable secondary device
# Enable secondary device
# Check if the address is expected in your system
# Check if the address is expected in your system
[[File:External.png|thumb]]
 
[[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
| -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 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'''
|
|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.
|}

Revision as of 09:58, 22 July 2025

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:

  1. 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;
  2. 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..

  1. Open "User menu"
  2. Open "Installer menu"
  3. Open "Load Managment"
  4. Select "Secondary"
  5. Enable secondary device
  6. 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 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 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
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.